- Report in CRM 4.0
- Posted by Ron Weatherup on June 16th, 2008
I created a report in CRM 4.0 using the Report Wizard. This worked ok for all
users until I took the report and amended in it Visual Studio. Now I can only
run the report when logged in as the administrator. I get the following error
message when running the report as any other user
An error has occurred during report processing.
Query execution failed for data set 'DSOrganizationInfo'.
For more information about this error navigate to the report server
on the local server machine, or enable remote errors
Any ideas?
Thanks
Ron
- Posted by Donna on June 16th, 2008
Do you use the SQL Report Connector in your CRM Report environment?
"Ron Weatherup" wrote:
- Posted by Jonathan Nachman on June 18th, 2008
If its not the above (reporting connector), you may need to modify the data
source.
--
http://halo9.co.uk/blog
"Donna" wrote:
- Posted by Donna on June 18th, 2008
He will probably need to modify the data source, just need to understand if
he is using the Connector for CRM 4 because there are specific settings he
will need if he is using it.
Thank you
"Jonathan Nachman" wrote:
- Posted by Ron Weatherup on June 19th, 2008
Hi, I don't think we do use the SQL Report Connector. how would i go about
changing the data source? would it have changed since it was generated using
the Report Wizard...? Thanks, Ron
"Donna" wrote:
- Posted by Donna on June 19th, 2008
Hi Ron,
When you ammended the report in Visual Studio, it may have changed the data
source.
Take these steps to check or change your datasource:
Open the report in VS
Select the Data tab
Select the button with the three dots to the right of DataSource
That will give you your connection information and also allow you to edit
the Connection String
Ensure your Connection or Type is set to Microsoft SQL Server
Select the Edit button
Ensure you have your CRM SQL server selected
Ensure Windows Authentication is selected and the CRM database name is
selected.
Save and Close your report
After that, try uploading the report to CRM using New Report button in CRM.
Select the Record Type of 'Existing file' and upload the report.
Once you complete the upload, CRM should adjust the datasource as needed.
The above worked for me.
Best Regards
"Ron Weatherup" wrote:
- Posted by Ron Weatherup on June 19th, 2008
Donna, this worked, thanks very much!
"Donna" wrote:
- Posted by Steven Levada on June 24th, 2008
Hi all,
I have the same problem as Ron. I modified the Quote report and added some
fields in VS 2005. I set the datasource connection properties according to
Donna.
Server name SRVR01\MSDYNAMICS (We have a seperate instance for it)
Use windows authentication
Database Company_MSCRM
If I press <test connection> in the connection properties window it works.
I do this for Quote report and sub report.
Then I upload the 2 rdl files to CRM. When I run them as administrator it
works fine. When another user tries they get the error:
An error has occurred during report processing.
Query execution failed for data set 'Dataset1'.
For more information about this error navigate to the report server
on the local server machine, or enable remote errors
How can I see the information on the report server? In the sql server log
under management I do not see any errors. Also the evernt viewer does not
display anything.
I am kind of lost here so any help is very welcome!
Steven
"Ron Weatherup" wrote:
- Posted by Steven Levada on June 24th, 2008
I just found the error log. Ther seems to be a permissions problem. The
message is
Throwing
Microsoft.ReportingServices.ReportProcessing.Repor tProcessingException: Query
execution failed for data set 'DataSet1'., ;
Info:
Microsoft.ReportingServices.ReportProcessing.Repor tProcessingException: Query
execution failed for data set 'DataSet1'. --->
System.Data.SqlClient.SqlException: The SELECT permission was denied on the
object 'AccountBase', database 'xxxxxxx_MSCRM', schema 'dbo'.
The user has organization read permissions on the account table. So what
could be wrong?
"Steven Levada" wrote:
- Posted by Steven Levada on June 24th, 2008
I found the problem. I linked the account table incorrect in the query. It
works now
"Ron Weatherup" wrote: