This entry was posted on Thursday, January 17th, 2008 at 2:50 pm and is filed under SQL Reporting Services. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
SQL Reporting Services 2005 – (rsinternal error) internal error occurred when running reports.
We recently had an incounter with a system that was having major issues with their SRS 2005 implementation. CRM would randomly run reports and more often than not simply halt the process of running the report.
This process was extremely frustrating and not alot more helpful from the output from the event logs. An internal error has occurred on the report server. See the error log for more details (rsInternalError).
There are a few things that you can try to validate that you have the same issue.
- Make sure that you can actually manually load both your report manager and reportserver. This can be accomplished by visiting http://SRSServername/reports and http://SRSServername/reportserver
- Also, can you run a report sucessfully from the report manager? Or, does it give you the same message you are recieving in Microsoft CRM?
- Are your SQL and SRS Servers members of the CRM OU PrivUserGroup and SQLAccessgroup?
- If you have your SRS installation on another server do you have trust deligation setup in active directory for the SRS Server?
- Does your server have multiple processors installed? yes, this applies
- Are your processors equipped with AMD Cool N Quiet Technology? if so, disable
My problem turned out to be because of a SQL Reporting Services timing error from the multiple processors installed on the machine. The reports where being generated based on the processor timing and died out from there.
The solution of this is something at the time of this writing isn’t out quite yet but it is going to be covered in SQL Server Reporting Services SP3 update, which by now may be available. The KB article is available about it here.
http://support.microsoft.com/kb/943656
Also, you can contact Microsoft to aquire the cumulative update package 5 for SQL Server 2005 SP2. This fixed my issues, and hopefully SP3 will be released to the masses soon.
Take Care!
Leave a Reply
You must be logged in to post a comment.
