Phil Schwan has a new post up talking about how to raise the ASP buffer limit to show “large” reports.

As an FYI, another solution to this issue is to use SQL Reporting Services as the 10k row limit and the ASP buffer issue don’t apply when using SRS.

Read the full post here.

If you have more than a couple thousand clients in your SCCM 2007 site and have ever tried to run a large report (like “Hardware 01A – Summary of computers in a specific collection” against the All Systems collection, for example), you’ve probably encountered this HTTP 500 error:


This problem and resolution are pretty well documented for Windows Server 2003 and IIS6, but in this particular case we’re running Windows Server 2008 SP2, so we’re using IIS7.  The underlying cause is the same (default ASP Buffering Limit is set too low to handle the size of the report) and the fix is the same (increase the limit), but the steps to fix are just a little different for IIS7