When trying to install the SCCM client on a Windows Server 2003 R2 SP2 Domain Controller the installation fails.
In the ccmsetup.log the following entries are logged:
- Setup was unable to compile smsclient.mof. The error code is 8004100E.
- Installation failed with error code 1603
Looked up the error code 1603: "fatal error". Not much to go on there.
After some research we found that this might be related to WMI and we ran WMIDiag.
The output showed a few errors, of which some were related to the WMI namespace security.
We did an attempt to rebuild WMI, using the following procedure:
- net stop winmgmt
- Rename the folder %windir%\System32\Wbem\Repository.
- net start winmgmt : repository folder is now created again
---> reran the ccmsetup again afterwards but the error remains the same
Anybody who can recommend other ways to further troubleshoot/resolve this?
I am using SMS Client Center to repair WMI remotely. I am pretty sure it does the same as you described, but it's automatic and it works - you can download SMS Client Center here - http://sourceforge.net/projects/smsclictr
Client center has an option to repair wmi on systems where this functionality is available.
Wmi repair is a very different process from rebuild repository
"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm
Ddid you check the client.msi.log file? CCMSetup is just a wrapper for a bunch of other activities including the actual installation of the client via client.msi. 1603 is such a generic error from Windows Installer that you can often narrow down by checking the actual msi log file for more detailed ifomration on what failed (it's a big log file, so it'll take you a while to search through, ignore all the lines at the end that start with PROPERTY).
Jason | http://myitforum.com/cs2/blogs/jsandys
Jason Sandys said:
it's a big log file, so it'll take you a while to search through, ignore all the lines at the end that start with PROPERTY).
Search for "value 3" in the msi logfile. There's a high chance that the error is displayed right above that part in the log.
Could you try to this option to repair the WMI? http://technet.microsoft.com/en-us/library/cc180915.aspx
Try this script, for me worked fine
net stop "sms agent host"
net stop winmgmt
rd /S /Q repository
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
net start winmgmt
net start "sms agent host"
- Proposed as answer by Patrick Stalman Wednesday, January 08, 2014 5:34 PM