Welcome to the Blogcast Repository Sign in | Join | Help
Search BlogCastRepository.com for:
in Search

254 BlogCasts in The BlogCast Repository!

Setup failed to install SMS Provider

Last post 02-22-2008 9:24 AM by klosie. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 01-30-2008 2:50 PM

    Setup failed to install SMS Provider

    Hi,

    I am installing SCCM on a physical server which is install with the SQL 2005 SP2 . I have installed all prerequisites and run successfully prerequisites check.

    while running  its giving following error.

    <01-29-2008 20:39:25> CompileMOFFile: Failed to compile MOF C:\Program Files\Microsoft Configuration Manager\bin\i386\smsRprt.mof, error -2147217407

    <01-29-2008 20:39:25> Setup cannot compile MOF file C:\Program Files\Microsoft Configuration Manager\bin\i386\smsRprt.mof.  Do you want to continue?

    <01-29-2008 20:39:25> 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.

    I have googled this error and come across some solution given by Microsoft. Please go through link

    http://technet.microsoft.com/en-us/library/bb932163.aspx

    http://myitforum.com/cs2/blogs/jgilbert/archive/2007/10/11/using-sql-server-named-instances-to-host-the-configuration-manager-site-database.aspx

    I have done everything, which has written in the above article. But still i am getting the same error....

    any one has any idea....

    However,Few days before I have installed SCCM on virtual machine and it was installed fine, I had came across this issue.

     

    Thanks and Regards
    Abhishek Joshi | SMS 2003/SCCM2007 certified,ITIL Foundation
    http://blogcastrepository.com/blogs/abi/default.aspx
    Filed under: ,
    • Post Points: 35
  • 02-01-2008 6:22 PM In reply to

    • turbomcp
    • Top 50 Contributor
    • Joined on 03-01-2007
    • Posts 21
    • Points 255

    Re: Setup failed to install SMS Provider

    hey there

    check the sql server computer name with adsi,you got duplicate and diffrent spn's for diffrent sql services.

    check it with adsi and youll see.(FQDN and netbios,nothing but those two should be there or atleast they all should be running same user)

    for example one thing like reporting running with domain user and other sql service running as system.

    also make sure named pipes is added(if its missing) using cliconfg.

    reboot server after that,if it still doesnt work,post more logs,enable kerberose logging,send setspn -l (for fqdn and netbios)

    thanks

     

    • Post Points: 20
  • 02-20-2008 8:32 PM In reply to

    Re: Setup failed to install SMS Provider

    Ufff..... problem not resolved ..So i have reinstall OS and successfully install SCCM. MS says, this issue applicable to only if we are installing remote sql server. But i wonder why it was coming when sql server was installed locally. After installing again SQL 2005 SP2 on newly build server . i have cheked the settings for SPN via ADSIEDIT for a user who has installed SQL but In the CN= Properties dialog box,-----> servicePrincipalName ,nothing is there , But still able to install SCCM
    Thanks and Regards
    Abhishek Joshi | SMS 2003/SCCM2007 certified,ITIL Foundation
    http://blogcastrepository.com/blogs/abi/default.aspx
    Filed under:
    • Post Points: 5
  • 02-22-2008 9:24 AM In reply to

    • klosie
    • Top 100 Contributor
    • Joined on 02-21-2008
    • Posts 9
    • Points 120

    Re: Setup failed to install SMS Provider

    I ran into this as well, and this solved my problem:

    http://myitforum.com/cs2/blogs/rcrumbaker/archive/2007/10/12/system-center-configuration-management-with-remote-sql-installations.aspx

    It is my understanding that it occurs when you are running SQL on a different box than SCCM and SQL is running under a domain account which is often the prefered method.  From what I understand when you install SQL and run it under the default account, it automatically updates the SPN in your active directory, but when you change it to run under a domain account it doesn't do this for you.  Hence you having to manually update the SPN, I did this for both the NetBios name and the FQDN.

    • Post Points: 5
Page 1 of 1 (4 items)