HTTP 500 Internal Server Error when accessing SCCM Reports


HTTP 500 Internal Server Error when accessing SCCM Reports

1. Make sure that you are not hitting the limit of maximum rows returned by a report query. By default, report viewer in SCCM 2007 is configured to limit the results returned by a report query to 10 000 rows.
To change the number of rows returned by a report query, create the Rowcount DWORD value under the HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Reporting registry key.
Set its value to the number of rows that you want returned in the report query. If you want to return all rows, set the value to 0xffffffff, which is the hexadecimal equivalent of –1.
For more information, refer to the following TechNet article: How to Configure the Maximum Rows Returned by a Report Query
     
2. Increase the ASP response buffer limit size (aspbufferinglimit).
In IIS 6.0 change has been introduced which limits a default ASP response buffer to 4 MB. Increasing the buffer limit might help you in resolving this problem. To increase the buffer limit, follow these steps:
  • Click Start, click Run, type cmd, and then click OK.
  • Type the following command, and then press ENTER:
cd /d %systemdrive%\inetpub\adminscripts
  • Type the following command, and then press ENTER:
cscript.exe adsutil.vbs SET w3svc/aspbufferinglimit LimitSize
LimitSize represents the buffering limit size in bytes. For example, the number 67108864 sets the buffering limit size to 64 MB.
3. To confirm that the buffer limit is set correctly, follow these steps:
  •   Click Start, click Run, type cmd, and then click OK.
  • Type the following command, and then press ENTER:
cd /d %systemdrive%\inetpub\adminscripts
  • Type the following command, and then press ENTER:
cscript.exe adsutil.vbs GET w3svc/aspbufferinglimit
In my case, setting the limit to the value of 12582912 (12 MB) did the trick in the Configuration Manager environment of approximately 10 000 managed devices (SCCM Clients).

Comments

Popular posts from this blog

The install4j wizard could not find a Java Runtime Environment on your system. Please locate a suitable JRE...

Clients Unable to update - "Cached cookie has expired or new PID is available"

Java Control Panel Icon "Application Not Found"