Configuration Manager in Control Panel is blank

[Kazi]

We upgraded from SCCM 2007 to SCCM 2012 in March of 2013. The update went rather well and all computers that had the old 2007 client successfully upgraded to 2012. Our current configuration is one Primary Server with no Secondary Servers. Within the last month or so, two of our servers became INACTIVE in the SCCM console - both of these servers are Windows 2003 Server, one is 32 bit and the other is 64 bit. The 32 bit Windows 2003 Server is going to be retired soon, so that's the server I did my troubleshooting on. What I found on that server was in the Configuration Manager in the Control Panel, all tabs show blank white windows, even thought it used to have the same information in it as the other servers that aren't having the issue.

 

The General, Components, Actions, Site, Cache, and Network tabs have absolutely no information and are blank. When I click on the Site tab and click on Find Site, it successfully finds my Primary Site Server and I get a message that Configuration Manager has successfully found a site to manage this client, but when I click Apply, I get an error message that Failed to update site assignment and the site code stays empty.

 

Since this server was being retired soon, I removed the client and tried to push it again. Well, since I removed the client, no matter what I do I cannot get the client to reinstall again. I checked the 64 bit Windows 2003 Server and it exhibits the exact same issues - the Configuration Manager is blank and I cannot update the site assignment or anything else. I have attempted to push the client to that server again as well but it doesn't install or fix any issues.

 

I am hoping someone has an idea that I haven't tried yet. I initially thought it was a WMI error, so I did all the necessary steps to get WMI working again. Even with that, I cannot get the Configuration Manager to populate with any information.

 

Any thoughts are appreciated. I can't unjoin/rejoin to the domain or anything as these are production servers - the first one is just getting close to retirement but it isn't there yet.

 

Thanks in advance.

 

[Kazi]

More updates on this - I tried to rebuild WMI on the server that is "close to retirement" and install the client again, but the install never completes. I get the following error in the CCMSetup.log:

 

MSI: Action 13:33:32: CcmRegisterWmiMofFile. Compiles MOF files that were queued by CcmRegisterWmiMofFilesInit. ccmsetup 8/8/2013 1:33:32 PM 3128 (0x0C38)
MSI: Setup was unable to compile the file UpdatesAgentSchema.mof
The error code is 8004100E ccmsetup 8/8/2013 1:33:45 PM 3128 (0x0C38)
MSI: Action 13:33:45: Rollback. Rolling back action: ccmsetup 8/8/2013 1:33:45 PM 3128 (0x0C38)
File C:\WINDOWS\ccmsetup\{1AF71F68-6089-4211-ADDC-06DF40606141}\client.msi installation failed. Error text: ExitCode: 1603
Action: CcmRegisterWmiMofFile.
ErrorMessages:
Setup was unable to compile the file UpdatesAgentSchema.mof
The error code is 8004100E
ccmsetup 8/8/2013 1:34:03 PM 3128 (0x0C38)
Client installation has failed too many times. Ccmsetup will try again after the next reboot. ccmsetup 8/8/2013 1:34:03 PM 3128 (0x0C38)
Sending Fallback Status Point message to 'SCCM12.INT.LAN, STATEID='313'. ccmsetup 8/8/2013 1:34:03 PM 3128 (0x0C38)
Params to send FSP message '5.0.7804.1000 Deployment ExitCode: 1603 Action: CcmRegisterWmiMofFile. ErrorMessages: Setup was unable to compile the file UpdatesAgentSchema.mof The error code is 8004100E ' ccmsetup 8/8/2013 1:34:03 PM 3128 (0x0C38)
State message with TopicType 800 and TopicId {6F6AE20B-3397-4A33-8E81-6DF265A2C333} has been sent to the FSP FSPStateMessage 8/8/2013 1:34:04 PM 3128 (0x0C38)
ccmsetup is shutting down ccmsetup 8/8/2013 1:34:04 PM 3128 (0x0C38)
Shutdown has been requested ccmsetup 8/8/2013 1:34:04 PM 3128 (0x0C38)
InstallFromManifest failed 0x80004004 ccmsetup 8/8/2013 1:34:04 PM 3128 (0x0C38)
CcmSetup failed with error code 0x80004004 ccmsetup 8/8/2013 1:34:04 PM 3084 (0x0C0C)

 

I've looked up StateID=313, ExitCode 1603, error codes 8004100e, 0x80004004... I just can't seem to pin point the problem.

[GarthMJ]

Have you seen this. http://support.microsoft.com/kb/281888

[Kazi]

Thanks for the reply Garth. Yes, I checked that as well - and the Default Namespace is root\cimv2. That's why I have been pulling my hair out... I obviously MUST be missing something, yet I feel that I tried everything.

 

When I go into the Configuration Manager in the Control Panel, like I said before, all tabs are blank. If I go to the site tab and click on Find Site, it successfully finds the site code without me having to enter it, but when I click APPLY, I get an error that ConfigMgr cannot update the site. See below:

 

[Kazi]

Sorry to bump this thread - I'm still looking for anyone with ideas on how to fix this? I don't know what else to try.

 

Thanks in advance.

[Kazi]

Hello everyone - I just wanted to give an update on this issue.

 

This last weekend, I came in off hours to do Windows Updates on this server manually. After I installed Windows Updates and rebooted I got some WMI errors on different software. Although risky, I rebuilt WMI just like I did on the "close to retirement server" mentioned above. This fixed the issues I was having with the software I had issues with after the reboot but my Configuration Manager was still blank at that time. I got an error message during the WMI rebuild but I really wasn't thinking about the Config Manager.

 

When I came in this morning, I thought I'd check it just to see if anything changed. Low and behold, the Configuration Manager is no longer blank and is showing ACTIVE in the SCCM Console again... Why it worked on this server and not the other one that is close to retirement is beyond me. I just wanted to share with everyone that WMI was the issue and once it was rebuilt, the Configuration Manager information is back and talking with SCCM again.

 

Thanks to everyone who looked at this and thought about what could be wrong. I appreciate it.