System.OutOfMemoryException error thrown when running ReportViewer

 

 

-------------------------------

For System.OutOfMemory.Exception, try to check if this problem will go away after iis reset or terminating aspnet_wp.exe worker process in asp.net web server.

The .net memory profiler is a good tools for your troubleshooting. Try to find if the memory problem is caused by the remote serviced component. You can stop the remote serviced component to see if the memory exception goes away.

Try to refer to the following links to find the memory exception

#Watching Your Server Processes
http://msdn.microsoft.com/library/en-us/dnaspp/html/aspnet-watchserverprocesses.asp?frame=true
#ASP.NET Performance Monitoring, and When to Alert Administrators
http://msdn.microsoft.com/library/en-us/dnaspp/html/monitor_perf.asp?frame=true
#Production Debugging for .NET Framework Applications
http://msdn.microsoft.com/library/en-us/dnbda/html/DBGch02.asp?frame=true
#Performance Counters for ASP.NET
http://msdn.microsoft.com/library/en-us/cpguide/html/cpconPerformanceCountersForASPNET.asp?frame=true
Thanks.

 

http://forums.asp.net/p/1309087/2573177.aspx

-------------------------------

I have same problem exporting 400 pages to pdf (10 barcodes on each page), database is mssql, no problem when export 50 pages 

 

When the report viewer is running in local mode, it does not have the same infrastructure available for performance and scale that the report server does.  As you have seen, the memory footprint can be quite large and does depend on the report definition, size of the data sets, and the rendering format.  An image based rendering will use much more memory than HTML, for example.  The report server is better suited to handle large reports.

http://social.msdn.microsoft.com/forums/en-US/vsreportcontrols/thread/c89c8006-79b6-4cb5-88c6-346f0766a2a9

-------------------------------

I got a report which gives an exception when exported to excel from the report viewer. I got the same export correctly without error once and then again it throws everytime on the dev and prodn environments. I did search many articles but did not find the perfect answer in implemnting this. This is a local report(NOT SERVER Report) .rdlc file and attach the dataset and get the report. Only problem is when exported to excel but not with PDF. Not sure..why this is happening.

You can increase the memory of your client,
or you should reduce the size of your report output :
- limit the nr of rows
- limit the nr of columns (remove 1 column, e.g. an identity column)
- use smaller data types, eg. replace dates (12-25-2008) by integers (20081225) ...

 

http://www.sqlservercentral.com/Forums/Topic602053-162-1.aspx

-------------------------------

 

-------------------------------