SMS provider fails to install
I'm trying to install SCCM 2007 on Windows Server 2003 SP2 andsetup fails because the SMS provider failed to install. SQL 2005 is running on the same box and I have checked the SPN. Errors from ConfigMgrSetup.log: <06-10-2008 09:56:14> CompileMOFFile: Starting to compile MOF E:\Program Files\Microsoft Configuration Manager\bin\i386\NetDisc.mof<06-10-2008 09:56:15> CompileMOFFile: Failed to compile MOF E:\Program Files\Microsoft Configuration Manager\bin\i386\NetDisc.mof, error -2147217407<06-10-2008 09:56:17> Setup cannot compile MOF file E:\Program Files\Microsoft Configuration Manager\bin\i386\NetDisc.mof. Do you want to continue?<06-10-2008 09:56:17> Setup failed to install SMS Provider. For more information about this error, see Microsoft Knowledge Base at http://microsoft.com or contact Microsoft Technical Support for further assistance. Errors from mofcomp.log (Tue Jun 10 09:56:14 2008.62806593) : Parsing MOF file: E:\Program Files\Microsoft Configuration Manager\bin\i386\NetDisc.mof(Tue Jun 10 09:56:14 2008.62806671) : An error occurred while processing item 2 defined on lines 21 - 62 in file E:\Program Files\Microsoft Configuration Manager\bin\i386\NetDisc.mof:(Tue Jun 10 09:56:14 2008.62806671) : Error Number: 0x80041026, Facility: WMIDescription: Class has instances (Tue Jun 10 09:56:14 2008.62806671) : Compiler returned error 0x80041001 Errors from smsprov.log [1F08][Tue 06/10/2008 09:56:13]:CExtUserContext::LeaveThread : Releasing IWbemContextPtr=33529656[19E8][Tue 06/10/2008 09:56:31]:CSspBackgroundThread WaitForSingleObject - WAIT_TIMEOUT[19E8][Tue 06/10/2008 09:56:31]:CSspBackgroundThread::Run, Polling ..[19E8][Tue 06/10/2008 09:56:31]:CSspClassManager::EnsureConnectionToSiteServer, siteserver = BOS-ADMIN1, root dir = E:\Program Files\Microsoft Configuration Manager[19E8][Tue 06/10/2008 09:56:31]:Creating SQL Trigger registry entries....[19E8][Tue 06/10/2008 09:56:31]:Could not get copy of registry config[19E8][Tue 06/10/2008 09:56:31]:CSspClassManager::EnsureConnectionToSiteServer, siteserver = BOS-ADMIN1, root dir = E:\Program Files\Microsoft Configuration Manager[19E8][Tue 06/10/2008 09:56:31]:**e:\nts_sms_fre\sms\siteserver\sdk_provider\smsprov\ssppdf.cpp(117) : Unknown file error (GetLastError=53): \\BOS-ADMIN1\SMS_BOS\scripts\00000409\pdfstore\load Does anyone have any ideas for what might be causing this or suggestions for what I might try? Thanks for your help! - Katrina
June 10th, 2008 6:01pm
This issue is addressed in the "Troubleshooting Configuration Manger Setup". http://technet.microsoft.com/en-us/library/bb932163.aspx Look for "Setup Fails to Install SMS Provider Components" on this link.
June 10th, 2008 6:20pm
I did read that article. My site database is not on a remote SQL server, it is running on the same server as SCCM. However, I did already follow the procedure and setup SPN's for both the netbios and fqdn of the server, since the services are running with a domain account. Unfortunately, I continue to get the SMS provider error. Thanks for your help. - Katrina
June 10th, 2008 6:27pm
The problem may also occur when the 'NetworkModel' namespace is left behind from a SCCM 2007 SP1 (any beta or SP1 RTM) install/uninstall on the same machine and then an SCCM 2007 RTM install is attempted. To remove the "NetworkModel" namespace:1. Launch "wbemtest" from start/run or command line.2. Connect to the "root" namespace.3. Press the "Enum Classes" button, select "Recursive" radio button and press "OK".4. In the Query Result window, locate and double click on the "__NAMESPACE (__SystemClass)" class5. In the "Object editor for __NAMESPACE" window, push the "Instances" button.6. In the Query Results window, locate and delete the "NetworkModel" instance.7. Close out all of the open wbemtest windows. Let me know if this works. Also, pleaseset the thread as 'Mark as Answer' if it does solve the install issue.
June 11th, 2008 6:29pm
Removing the NetworkModel namespace solved my problem. I have now installed successfully. Thanks so much for your help!! - Katrina
June 12th, 2008 6:02pm
I have the same (exact) errors in the logs as posted above. The only Namespace listed is Namespace.Name="MS 409". I have registered and verified SPN's (SQL 2005 Cluster, so did them for both nodes). SCCM computer's account is a member of local admin group on both SQL cluster nodes. Background: New server for SCCM, no Betas or earlier SMS versions installed on it. I Installed SCCM RTM (Mixed Mode) with no problems. Immediately following the install, I ran SCCM SP1 installation (didn't even open the SCCM console). It hung at "installing configuration manager services" for over 40 minutes. I cancelled it, and retried a few times before declaring ita mess, uninstalling SP1 and SCCM, and startedover figuring I would wait for further developments on the SP1 error before trying again (Found a few similar reports, but no solutions). Since then, every attempt to install SCCM RTM fails at the SMS Provider. I even removed and re-installed WSUS to get rid of its SP1. I didn't do anything with the SPN's before the first successful install. Ire-registered them after I got the failures on the re-install, when I saw that as the most common cause. Any suggestions? Thanks! -Gary
June 21st, 2008 7:00am
We just created a hotfix for an issue with installing the SMS Site Component Manager in a SQL cluster environment for SP1. I don't know that it is public yet, so you may have to contact product support to get it. However it would be a free call to do so for a hotfix scenario. I'd start there.
June 22nd, 2008 2:11am
OK, Thanks. I'll definietly look into that once I get SCCM re-installed, but I am still unable to get past the SMS Provider. If there are nosuggestionsbeyond what has been done above, I'll try wiping and re-building the server.
June 24th, 2008 12:36am
I thought the hotfix was to allow you to get the site installed. I'd check it out now as it may help you to proceed.
June 24th, 2008 3:09am
Hi Gary, In case you had the same problem as I did... When you connect to the root namespace, are you actually typing "root" or are you using the root (default) that comes up automatically? When I initially tried this I took what came up automatically and saw only the MS 409 namespace also. Later, when I instead typed in "root" myself, I found that there were many others, including the one causing the problem. I hope this helps you, too! - Katrina
June 24th, 2008 3:17am
Thanks Katrina. I was just leaving it at the /Default. The NetworkModel was there, and I removed it as well as SMS and SMS/DM (or something like that). However, installation still failed. I decided to look at setspn again and found this: http://poseidom.wordpress.com/2007/12/16/set-spn-for-sql-2005-sccm-remote-sql-fix/, which ultimately fixed my issue. The part about doing setspn without the port number is what I hadn't done or seen previously.I also did the ADSIEdit change for SELF on theSQL Service account, followed by a restart of SQL services. I ran the query mentioned before restarting, and it was NTLM. After service restart, it changed to Kerberos. I'm configuring now without SP1, and will get the hotfix Wally mentioned and install SP1 in a week or so. Thanks for your help everyone! Gary
June 24th, 2008 6:16pm
this works great thanx
September 24th, 2008 2:01pm
The "default" thing got me as well - Thanks for the info!
November 24th, 2008 4:14am
This worked great on my Win2k3 box, however I got an access denied on my Win2k8 box, has anyone done this on 2008?
March 24th, 2009 2:04am
hi friend, you must run cmd as administrator, and then write the command wbemtest
September 17th, 2009 10:26pm
works great! thanks
November 19th, 2009 6:42pm
thank you jeff .this did solve my problem . Going forward , I was even able to successfully restore my primary SCCM Site
March 11th, 2010 6:06pm
Thank you jeff. It's work for me :)Amol Maindarkar
May 21st, 2010 4:01pm
Thank you jeff. It's work for me :)
February 4th, 2011 8:45pm