Hi, We are receiving the below error in one of the Windows 32 bit Enterprise Edition desktop. Please let me know how to resolve it Initializing COM. Registering for logging change notifications. Setting default logging component for process. Setting service status to RUNNING. Checking configuration. Successfully Created Thread for CheckConfiguration. Waiting for Configuration to Complete The CCM namespace does not exist. Repair required. Detected faulty configuration. Repair will be started in 5 minutes. Entering main message loop. WM_QUIT received in the main message loop. Initiating repair. Initiated repair of configuration. Service will now exit. Shutting down CCMEXEC... UninitCommandExec failed (0x800401fb). SystemTaskProcessor::Shutdown failed with code 0x8000ffff Error invoking shutdown system tasks (0x8000ffff)

This snippet shows that the agent tried repairing , but failed . There would be a msi log inside the same folder.. Look for errors in that log file.. Also seems like WMI is corrupt.

Hi, This is a Windows 7 Enterprise Edition and i have tired by winmgmt /salvagereporsitory. It did not help. How should resolve wmi errors in Windows 7 OS Regards, Boopathi S-

I vote for a WMI issue, could you please follow this blog http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspxBechir Gharbi | My blog: @myITforum.com | Twitter: @Bechir_Gharbi | Linkedin: Bechir Gharbi | Time zone: GMT + 1

winmgmt /resetreporsitory This will do the destructive repair, similar to deleting the repository on an XP machine. Use at your own risk. If an application doesn't recompile its MOF then you will need to do it manually. I haven't yet seen this happen on win 7 or 2008http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com