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>

IIS_1

Open ASP feature

IIS_2

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.

IIS_3

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.

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!

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!
SCCM_SMS_DEFmof
Technorati-taggar: ,,,

SCCM Solve child site replicaton problems

If you look at the replication logs I posted yesterday but still can’t understand why child site is not accepting packages from Central site.

If you get Errorcodes and errors about cetificates not valid for some packages etc but you have solved the public keys and done everything by the book then you have one more thing to try.

Disconnect Child site from Central parent site  and wait a weekend then reconnect it and re-replicate all packages. This solved a corrupted replication for me a couple of times.

Repair broken or corrupt WMI

When SMS or SCCM agents fails to install it’s often due to broken or corrupt WMI database. Recreating WMI database is not a good way to solve it since other applications might have stored configuration and values there.

So, I have written together a set of commands which fixes WMI problems in most cases without need of rebuilding whole WMI.

Open an administrative CMD Window and run these commands.

msiexec /unregister
msiexec /regserver

rundll32 wbemupgd, RepairWMISetup
Restart the “Windows Management Instrumentation service”

Change directory to %windir%\System32\WBEM
(\SysWOW64\WBEM on x64)

Then run these FOR loops:
FOR /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
Net stop /y winmgmt
FOR /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
Net start winmgmt

Now, try to install the SMS or SCCM agent again.
If it still fails, reboot and try agent installation once more.

Technorati-taggar: ,,,,,

SCCM Investigate package replication problems

Connect with RDP or Console to Parent and Child site servers.

Install Trace32.exe from SMS2003 toolkit (Installation is easy, copy it into %Windir% and start it). With Trace32 you can look at the log’s without locking them and they also update on the screen when there are changes in them. Excellent tool which you must have as SCCM specialist.

Open all below log files and put them up so you see them all on both child and parent RDP window.

Parent: Sender.log, Replmgr.log, Objreplmgr.log
Child: Despool.log, Replmgr.log, Objreplmgr.log, Distmgr.log

In console, update the distribution point that is not updating, look for errors in the logs..

SCCM Child site out of sync

Use below command from Central SCCM site server to force a full sync of  child site that is having problems.

<SCCM folder>\i386\00000409\preinst.exe /syncchild <child sitecode>

If child keeps getting out of sync, start investigating replication logs, see separate post.

SCCM sites in different AD Forrest, public keys!

If you have added the correct sender accounts in our hirarchy and you still can’t get the replication to work between sites? Public keys can make a mess when site servers try to communicate between forests since they do not share the same AD objects but I have found a solution!

1. Use “preinst.exe” to fix this problem.
2. Export the keys in both child and parent.
3. Copy the exported files according to the help text.
4. Restart Hierarchy Manager
5. Check hman.log

No HW inventory after SCCM client upgrade

I encountered this problem when migrated Windows 2000 servers from SMS 2003 to SCCM 2007.

CCMsetup finalised successfully and the client registered in the new SCCM site and downloaded policies but no HW inventory is sent back to the site server.

Check “InventoryAgent.log” on the client computer.

Unknown error encountered processing an instance of class CCM_System: 80041013 Collection: Failed to process mandatory data item for class: CCM_System. Cycle abandoned !!   InventoryAgent Failed to process instances of CCM_System: 80004005

Resolution was to restart the Windows 2000 system and the SCCM agent started to work as expected again. This error did not occur on all Windows 2000 servers at my customer.

Running SCCM site server on VM-Ware

I migrated about 2500 servers from SMS2003 to SCCM where the new Primary server and other SCCM infrastructure servers were virtual servers.

I migrated the clients by sending out a CCMsetup package from SMS in batches of 500 systems per hour. When the agents started to report initial full inventory the new Site server it needed more hardware and after upgrade of 2 more CPU’s and 2GB of extra RAM it’s running smooth and with good performance.

OS and roles:
Windows 2008 R2 x64
SQL Server 2008 x64
Site Database
Management point
Reporting point

Virtual Hardware:
4 CPU’s
8GB RAM
400GB virtual disc

SUP and Distribution points are placed on own machines.

Find and Delete duplicates in SMS and SCCM db

SMS 2.0 had problems with duplicates in the database and this problem was not solved in SMS2003. Now I have seen it also in SCCM.

I have been using these two below scripts many times to manually find and delete all duplicates only keeping the latest record.

First script shows all duplicates:

SELECT DIS.*
FROM System_DISC DIS
Join ( Select Name0, resource_domain_or_workgr0
FROM System_DISC
group by Name0, resource_domain_or_workgr0
having count(*) > 1)
As DUP on DUP.Name0 = DIS.Name0
And DUP.resource_domain_or_workgr0 = DIS.resource_domain_or_workgr0
order by Netbios_Name0

Second script deletes the duplicates but keep the most recently discovered record:

delete from system_disc where
itemkey in
(SELECT distinct DIS.itemkey
FROM System_DISC DIS
Join ( Select Name0, Creation_Date0
FROM System_DISC where Name0 IN ( Select Name0
FROM System_DISC
group by Name0
having count(*) > 1))
As DUP on DUP.Name0 = DIS.Name0
where (DIS.Creation_Date0 < DUP.Creation_Date0 or DIS.Creation_Date0 is null))

CCMsetup parameters

I post a url to a good Technet article covering all the different Client installation paratmeters.

http://technet.microsoft.com/en-us/library/bb680980.aspx

Really nice to have while customizing and building an automated client installation package!

Move SCCM database to another server

I have been forced to move SCCM database in a couple of cases and it sounds a bit scary if you are running a big environment but it’s an easy task and you have several ways to be sure not to loose any data.

For my migration task I used this good instruction guide:
http://www.windows-noob.com/forums/index.php?/topic/693-guide-moving-your-site-database/

Remove SCCM Primary Child Site Manually

Sometimes you get in to trouble when hardware crashes or child site teams just terminates a site server without letting you remove it the right way first.

At this site you can get good instructions how to solve the removal manually:

http://isatechie.blogspot.com/2009/05/how-to-remove-sccm-primary-site-child.html

I have used the instructions a couple of times and it saved my day :)

Portable SCCM lab environment

I have built up a my SCCM lab environment in Virtual PC and running it in my Laptop (together with two external usb 2.0 drives).

Brief setup:
One virtual Windows 2008 server with one outbound NIC (NAT, with internet connection) and one local network card.
On this server I have installed AD, DHCP, DNS, SQL2008, SCCM2007. This is my SCCM site server and the DHCP service gives IP adresses to all the other virtual images I have.

Then I have all OS platforms as own virtual images which I can run 1-2 of together with the site server before my Laptop starts to feel ill. :) A portable virtual Lab is exellent when doing demo’s or testing something in really Beta status.

I call this environment my “portable sanbox”

Microsoft has published several virtual labs on technet, one good one is this:
https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032456557&EventCategory=3&culture=en-US&CountryCode=US

Prenumerera på: Kommentarer (Atom)