If you have one particular report in SQL Reporting Services (2000 or 2005) that mysteriously prompts for credentials, or refuses to run without any particular reason given, take a look at the server logs. It’s possible you may be running into a memory-related error.
There are a number of reasonable explanations if none of the reports will run in SQL Reporting Services, but what if the problem is just with one particular report? In my case, this rouge report would just prompt for credentials (the server was set to Windows Authentication only), and refuse to display regardless of the credentials entered.
Take a look at the Event Viewer. You may or may not see an Event ID: 1011 (“A process serving application pool 'ReportServer Pool' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '1284'. The data field contains the error number.”). If this is the case, dive into the latest ReportServer log (usually located in c:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\LogFiles). This is where you might find this error:
In this case, either the report is so beefy that it’s taking up way too much memory, or maybe your Reporting Services box needs a memory boost. You can try raising the MemoryLimit or MaximumMemoryLimit values as described here: http://support.microsoft.com/kb/909678 (don’t raise the MemoryLimit value to over 90% unless you’re into explosions)
In my case, I found I was able to economize on the design on my report (I had a number of unnecessary parameters), and once I simplified it, it ran just fine.
Good luck and good reporting.
There are a number of reasonable explanations if none of the reports will run in SQL Reporting Services, but what if the problem is just with one particular report? In my case, this rouge report would just prompt for credentials (the server was set to Windows Authentication only), and refuse to display regardless of the credentials entered.
Take a look at the Event Viewer. You may or may not see an Event ID: 1011 (“A process serving application pool 'ReportServer Pool' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '1284'. The data field contains the error number.”). If this is the case, dive into the latest ReportServer log (usually located in c:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\LogFiles). This is where you might find this error:
| ERROR: Found System.OutOfMemoryException exception: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. ---> System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. |
In this case, either the report is so beefy that it’s taking up way too much memory, or maybe your Reporting Services box needs a memory boost. You can try raising the MemoryLimit or MaximumMemoryLimit values as described here: http://support.microsoft.com/kb/909678 (don’t raise the MemoryLimit value to over 90% unless you’re into explosions)
In my case, I found I was able to economize on the design on my report (I had a number of unnecessary parameters), and once I simplified it, it ran just fine.
Good luck and good reporting.
No comments:
Post a Comment