Hello Everybody...
Here I am sharing my experience during the investigations of a very serious but easy to fix issue :-) which our team faced with CRM Reports. Hope you find it useful...
Recently our CRM team faced a serious issues when suddenly all the CRM Reports got break down and were unable to load.
The errors which got logged in the event viewer of the CRM Server were something like below:
"Web service request GetDataSources to Report Server http://report server name/reportserver failed. Error: Unable to connect to the remote server"
AND
"Web service request GetDataSources to Report Server http://report server name/reportserver failed with SoapException. Error: The path of the item '/CRM Database Name/4.0/' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. (rsInvalidItemPath)"
After some hours of investigations in every nook and corner of CRM for finding the root cause of this issue. One of my team member caught the source of the issue. Issue was due to the settings on the Reporting Server which somehow got changed. Catch the below screen shot for details.
Solution:
Make sure that the settings on the report server are as per the below screenshot. The URL to access your Reporting server will be like http://Report Server Name/Reports. After you go to this URL, get yourself reach to the below page and check your settings.
Here I am sharing my experience during the investigations of a very serious but easy to fix issue :-) which our team faced with CRM Reports. Hope you find it useful...
Recently our CRM team faced a serious issues when suddenly all the CRM Reports got break down and were unable to load.
The errors which got logged in the event viewer of the CRM Server were something like below:
"Web service request GetDataSources to Report Server http://report server name/
AND
After some hours of investigations in every nook and corner of CRM for finding the root cause of this issue. One of my team member caught the source of the issue. Issue was due to the settings on the Reporting Server which somehow got changed. Catch the below screen shot for details.
Solution:
Make sure that the settings on the report server are as per the below screenshot. The URL to access your Reporting server will be like http://Report Server Name
Wasn't it really an easy fix...? J
No comments:
Post a Comment