IIS 5 & IIS 6
Reporting Services 2005 Web service: OutOfMemory
Last post Jan 11, 2008 10:26 PM by NeoCanada
Jan 05, 2008 11:26 AM|NeoCanada|LINK
When rendering a report to Excel format through Reporting Services Web service, I got an “OutOfMemory” Exception logged in the Report Server log file.
Our box has 16G physical memory. When the Exception occurs, the process “w3wp” consumes 1.1G “Working Set” memory and 1.6G “Virtual Bytes”, the whole system “Commit Charge” is around 3G, and the total “Kernel Memory” consumed is less than 400M.
If I schedule the report to run in Reporting Services Windows service, it would be fine, even though the process “ReportingSerivesService.exe” sometimes consumes more than 1.2G “Working Set” memory.
There is a KB talking about this issue:
http://support.microsoft.com/kb/909678. My case is same as what the section “The Reporting Services Web service and the System.OutOfMemoryException error” describes.
My question is, since our box already has enough physical memory, why I still run into this problem? I didn’t set any memory limitations to IIS and the application pool. How can I allocate more physical memory to IIS? Currently, redesigning the report is
not a option.
Please help. Thanks.
IIS 6.0 Memory
Jan 07, 2008 07:51 AM|Zhao Ji Ma - MSFT|LINK
Is it 32-bit or 64-bit version of Windows?
Jan 07, 2008 02:20 PM|NeoCanada|LINK
It's a 32-bit Windows Server 2003 Enterprise Edition.
Jan 07, 2008 02:45 PM|NeoCanada|LINK
Sorry, I also forgot to mention the versions of other softwares.
Reporting Services: 2005
Jan 08, 2008 01:12 PM|NeoCanada|LINK
Anyone can help?
Jan 11, 2008 07:16 AM|Zhao Ji Ma - MSFT|LINK
If you have more than 2 gigabytes (GB) of memory, you can enable the /3GB switch in the Boot.ini file for better performance. This article describes how to configure SQL Server to use more than 2 GB of physical memory.
Have you tried enabling /3Gb Switch mentioned in that KB?
Jan 11, 2008 10:26 PM|NeoCanada|LINK
Thanks Zhao Ji Ma. I believe turning on the /3GB will probably help. I just want to know why it fails before it even hit the 2GB limitation... Anyway, I may have to compromise since it seems not easy to discover what is going on behind the scene.