Answered by:
CRM Reports

Question
-
Hi,
I am new to CRM so apologies in advance if this question is naive. I have a problem whenever I try to run any report. I get a simple error message saying "An error has occurred". When I look on the report server I can't see any report definitions, model etc which I presume should have been created during the install. Can you help?
Thanks
Stu
Thursday, March 27, 2008 6:46 AM
Answers
-
Tried a number of things to make it work. One of them did the trick (unfortunately i'm not sure which)
1. Rebooted the SSRS server
2. Deleted and recreated the Data source which all the reports where using. Did this because the data source seemed to be defective i.e. when I tried to open it I got an error
I set the DevErrors value in the web.config of CRM to "On" and this gave me a bit more info. Definately worth trying
Cheers
Stu
Thursday, March 27, 2008 11:22 AM
All replies
-
Dear Stu
See your reportserver should work http://localhost/reportserver and then configure Reporting Service configuration.
http://www.microsoft.com/dynamics/crm/using/customizing/reporttutorial.mspx
http://www.microsoft.com/dynamics/crm/using/reporting/default.mspx
Regards,
Imran
http://microsoftcrm3.blogspot.com
Thursday, March 27, 2008 8:00 AMModerator -
Thanks for your quick response Imran,
The report server is running on a remote SQL Server. The reporting service is configured and is all ready running a number of other reports. I can run the reports if I connect to the report server manually however I still get the same error whenever I run it from the CRM site
Thursday, March 27, 2008 10:24 AM -
Tried a number of things to make it work. One of them did the trick (unfortunately i'm not sure which)
1. Rebooted the SSRS server
2. Deleted and recreated the Data source which all the reports where using. Did this because the data source seemed to be defective i.e. when I tried to open it I got an error
I set the DevErrors value in the web.config of CRM to "On" and this gave me a bit more info. Definately worth trying
Cheers
Stu
Thursday, March 27, 2008 11:22 AM -
This sounds like it may be an AD delegation issue, especially if you are using CRM 3.0. The following document should help:
Thursday, March 27, 2008 11:23 AMModerator