HTTP 500 Error SCCM web reports 80004005 Response_Buffer_Limit_Exceeded

I have built big custom Web reports with SQL views and if running on default SCCM settings you will soon get HTTP 500 errors in web reporting page since the IIS buffers reaches the limit.

First open latest IIS log file in trace32:
<drive>:\inetpub\logs\LogFiles\W3SVC1

Then Run the failing report again and check status in log.

I got this error:
ASP_0251_:_80004005 Response_Buffer_Limit_Exceeded

This means that the IIS buffers needs to be increased from the default value 4MB.

Open IIS management console and select SMSReporting_<sitecode>

Open ASP feature

Adjust the buffer limit by counting 2MB for each 500 rows in the report. I put 40MB of memory (4MB is default).

I also adjusted the Time-out value to 5 minutes.

Restart IIS service.

This solved my HTTP 500 problems since I got the
“ASP_0251_:_80004005 Response_Buffer_Limit_Exceeded”
error in the IIS log. Other errorcodes might hade other solutions.

Technorati-taggar: HTTP500,80004005,Response_Buffer_Limit_Exceeded,IIS,Buffer

Repair Broken WSUS installation (MS DTC)

On one SCCM site (Windows 2008 R2 and SCCM2007) WSUS core services failed because "MS DTC" service was not able to start.

Read more –> http://support.microsoft.com/kb/916926

This is how I got the site back online:

1. First I re-run WSUS installation so files were unpacked to C:\<folder>
2. Copy SSEE_10.msi to temp folder
3. Cancel WSUS setup (temp files are removed)
4. Open Admin CMD.exe and run this repair string from msi file folder:

Msiexec /i SSEE_10.msi CALLERID=OCSetup.exe REINSTALL=ALL REINSTALLMODE=omus /l*v c:\my_logfile.log

5. I removed and reinstallaed SUP service on the WSUS server.
6. After reboot the MS DTC started and SUP was back online!

Technorati-taggar: SCCM,Troubleshooting,WSUS,SUP,repair,MS DTC

SCCM Add Service Started/State info to default hw inv SMS_DEF.MOF

I wonder why Microsoft removed “Started” and “State” values for services from the default hardware inventory in SCCM (In SMS2003 both values  were default)?
I used those values a lot in SMS2003 during SW deployments to check if applications were installed correctly.
It’s quite easy to fix them back in SCCM. Just change two rows in
<SCCM folder>\inboxes\clifiles.src\hinv\sms_def.mof
(Make a copy of the sms_def.mof file first)
Open the file on all Primary servers in your hirarchy and change the “FALSE” to “TRUE” on the values you want to add to next hardware inventory cycle.
In my case I searched for “win32_service” and then changed Started and State to TRUE. Worked perfect!

Technorati-taggar: SCCM,HW,Inventory,SMS_DEF.MOF