Setup failed to install SMS Provider (Setup cannot compile MOF file \bin\i386\NetDisc.mof)

I had uninstalled the SCCM 2007 secondary site & again was trying to install it on the same hardware without formatting the OS. In the setup installation, while installing the SMS provider component it gave the error  'Setup failed to install SMS provider'
When I checked it in ConfigMgrSetup.log

CompileMOFFile:Failed to compile MOF E:\SMS\bin\i386\NetDisc.mof, error -2147217407
Setup cannot compile MOF file E:\SMS\bin\i386\NetDisc.mof. Do you want to continue?
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.
This type of error can also occur when the namespace 'NetworkModel' is not removed from WMI, while uninstallation of SCCM, on the same machine and then an SCCM 2007 RTM install is attempted. In my case  I had uninstalled the secondary site from the same hardware machine & was trying to install SCCM 2007 RTM.
Following are the steps to remove the "NetworkModel" namespace from WMI
1) Go to cmd prompt & type wbemtest
2) Connect to the "root" namespace.
3) Click on the "Enum Classes" , select "Recursive" radio button and click  "OK".
4) In the Query Result window, locate and double click on the "__NAMESPACE (__SystemClass)" class
5) In the "Object editor for __NAMESPACE" window, Click the "Instances" button.
6) In the Query Results window, locate and delete the "NetworkModel" instance.
7) Close all  the open wbemtest windows.


I again tried to reinstall the secondary site & it got successful.

Comments

Post a Comment

Popular posts from this blog

Hardware Inventory Action missing

Other than the obvious, if on your site server or client the Hardware Inventory action is missing, most of the time the issue is may be a misconfigured hardware inventory MOF file, configuration.mof, on your primary site. In this case, the Hardware Inventory Action was missing on some of the Primary site Server as shown in the following figure. Also looked in %systemroot%\system32\wbem\logs --> mofcomp.log file, it was showing  following error Error Number: 0x80041026, Facility: WMI In this case the MOF file it was compiling was correct, but somehow from the log file it was showing that there is some issue with WMI. As per the above error, while compiling the mof file, the a ttempt was made to delete or modify a class that has instances in WMI . But anyway it was not happening. Further we compared the sms_def.mof file objects with the WMI & found that one additional customized entry in WMI. On further investigation we found that earlier, some day’s back one
Read more

Description = "User \"Domain\\SCCMAdmin2\" does not have permissions to grant rights on this instance."; ErrorCode = 1112017920;

The domain user account which had full Security rights in SCCM console, if got disabled & your new domain account is not having equivalent full rights. Then how will you access SCCM objects or delgate access to other user accounts? Security rights provide the capability to define and refine the level of access that users have when working with configuration manager objects. This gives you the ability to delegate specific tasks to specific groups of users. In my environment SCCM 2007 was installed by domain admin account "domain\SCCMAdmin1" on Primary site server. Domain\SCCMAdmin1 account has full access on all instances. As employee left the organization, this user account got disabled. Then we created another domain admin account "domain\SCCMAdmin2", Now if anyone will try to copy permissions of "domain\SCCMAdmin1" to "domain\SCCMAdmin2", definately it will give following error Errors ConfigMgr Error Object: instance of SMS_Extende
Read more

SMS Advanced Client Push Installation process

The article describes the SMS Advanced Client Push Installation process Pre-installation stage  1. During the pre-installation stage, When the Client Push Installation wizard starts, Client Configuration Request (CCR) is created for each targeted computer. Each CCR is placed into the Inboxes\CCR.box folder on the site server. Client Configuration Manager (CCM) selects a CCR from the Inboxes\CCR.box folder on the site server (CCM tasks are logged in ccm.log on the site server) The CCR file contains the client computer name and additional information.  2. The SMS Client Configuration Manager connects to the ADMIN$ share on the client. This is based on the information in the CCR file.  3. The Client Configuration Manager attempts to connect to the computer using the Client Push Installation Account (if the connection was not successful it attempts to connect to the computer by using the site server computer account). The Client Configuration Manager connects to the client registry an
Read more