October 14, 2010 at 8:14 am
We are runing into an Out of Memrory exception when running a report. The report is returning around 1000 records. We are currently on 10.0.2789.0 --> SP1. He is the error from the log file.
library!ReportServer_0-22!1f0!10/14/2010-09:04:34:: Call to GetPermissionsAction(http://pmiportal/sites/reportcentral/Reports/Health e Systems/HeS Referral Report .rdl).
library!ReportServer_0-22!1f0!10/14/2010-09:04:37:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ;
Info: 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.
October 14, 2010 at 9:43 am
Eventhough its returning just 1000 rows but it does matters how many rows its processing and how many joins it has....?
Also is your SQL Sever physical one or virtual?
Is it shared one or you have only your application database on it?
If its shared one then how much usage is allocated to you in terms of CPU and Memory and how much your query is currently utilizing...
check on these questions and you may get the answer...
:rolleyes:
October 14, 2010 at 11:22 am
What Sacheen said is true, but, this error is on the report server, not the sql server, so I'd be more interested to hear more about the report server itself. Is it on its own server? What are your memory settings on the report server as set in the rsreportserver.config (<workingsetmaximum> and <workingsetminimum>) ?
How much physical RAM is available to ReportServer?
Also, look at the executionlog2 view for this report execution. what is the bytecount?
I agree with Sacheen, 1000 rows doesnt mean the report has a small memory footprint.
One more thing, is this report chocked full of expressions?
October 15, 2010 at 1:56 pm
Thank You. I will get back with all of your answers. For starters it is a physical box and it has 128GB of RAM.
October 16, 2010 at 2:43 am
I'd first eliminate any problems in the query by cutting and pasting it into SSMS and seeing what gets returned and in what time. (It could have a bad join and be returning too much data).
Then I'd eliminate any problems in the report by creating a blank report with the same query and a simple table that just directly dumps most of the rows returned, and see if it runs and in what time. (It could have some weird grouping that causes things to repeat endlessly, or too many pages, over a few thousand, to be generated).
Once we know if it's the query or the report, we could then dig deeper. Another thing to do would be to run task manager on the server and watch the memory usage of the reporting services process. It might tell us something interesting (like they only use a max of 2gb of available memory or something).
You could also check which version of reporting services is in use (not SQL server, if you have the two running on separate machines like most places). 2008 SP2 just got released, and SP1 and SP2 both aren't that common in standalone RS instances (IMO) and one or both of them do fix some intermittent memory problems.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply