locked
SMS_MP_CONTROL_MANAGER Failed to create the CCM_Incoming Virtual Directory RRS feed

  • Question


  • Hello -

    I'm hoping someone could help me with this problem. I've searched so many websites trying to resolve this issue and it seems no matter what I try I keep getting the same error message.

    I've followed the steps in setting up SCCM 07 from this web site which was very nicely done! I've also followed the directions on Microsofts Tech Net website on how to configure WebDav and IIS settings.

    I'm working on a Virtual Windows Server 2008 32-bit OS, SP2, SCCM 07 SP2, IIS7

    Here is the message I get in the log files:

    ----------------------------------------------------------------------------------------------------------------------------
    Message ID: 4963
    Process ID: 4364
    Thread ID: 7996

    Componet: SMS_MP_CONTROL_MANAGER


    MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory.

    Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: "net user IWAMMachineName)
    Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties.

    Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: "net user IWAMMachineName)
    Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties.

    Possible cause: The designated Web Site is disabled in IIS.
    Solution: Verify that the designated Web Site is enabled, and functioning properly.
    -------------------------------------------------------------------------------------------------------------------------------

    I could be completely wrong but I read somewhere that with the latest version of IIS doesn't install these user accounts. I checked to see if those accounts existed and they didn't.

    I've tried what this one website mentioned:

    http://myitforum.com...-directory.aspx

    - Remove the MP role from the Site Server. Watch the MPSetup.log to ensure that the removal is complete.
    - Uninstall the IIS component from the OS of the Site Server.
    - Reboot the Site Server.
    - Run ccmdelcert.exe from the SMS Toolkit.
    - Reinstall the IIS component (with BITS) on the OS of the Site Server.
    - Go into the IIS manager and allow WebDav.
    - Add the MP role to the Site Server. Watch the MPSetup.log to ensure that the installation completes correctly.


    These steps didn't seem to work, probably because it was for SMS 2003.

    Here is the MPmsi log file:

    <11-24-2009 17:39:28> SMSMP Setup Started....
    <11-24-2009 17:39:28> Parameters: C:\PROGRA~1\MICROS~3\bin\i386\ROLESE~1.EXE /install /siteserver:DELGADO SMSMP
    <11-24-2009 17:39:28> Installing Pre Reqs for SMSMP
    <11-24-2009 17:39:28> ======== Installing Pre Reqs for Role SMSMP ========
    <11-24-2009 17:39:28> Found 1 Pre Reqs for Role SMSMP
    <11-24-2009 17:39:28> Pre Req MSXML60 found.
    <11-24-2009 17:39:28> No versions of MSXML60 are installed. Would install new MSXML60.
    <11-24-2009 17:39:28> Enabling MSI logging. msxml6.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\msxml6MSI.log
    <11-24-2009 17:39:28> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\00000409\msxml6.msi
    <11-24-2009 17:39:30> msxml6.msi exited with return code: 0
    <11-24-2009 17:39:30> msxml6.msi Installation was successful.
    <11-24-2009 17:39:30> ======== Completed Installion of Pre Reqs for Role SMSMP ========
    <11-24-2009 17:39:30> Installing the SMSMP
    <11-24-2009 17:39:30> Passed OS version check.
    <11-24-2009 17:39:30> IIS Service is installed.
    <11-24-2009 17:39:30> checking WebDAV configuraitons
    <11-24-2009 17:39:30> WebDAV is configured
    <11-24-2009 17:39:30> No versions of SMSMP are installed. Installing new SMSMP.
    <11-24-2009 17:39:30> Enabling MSI logging. mp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
    <11-24-2009 17:39:30> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\mp.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" CCMSERVERDATAROOT="C:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
    <11-24-2009 17:40:24> mp.msi exited with return code: 1603
    <11-24-2009 17:40:24> Backing up C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
    <11-24-2009 17:40:24> Fatal MSI Error - mp.msi could not be installed. 


    Component Services (DCOMCNFG) is running properly, no error messages when I was browsing around.

    Any advice would be greatly appricated!

    Thanks!
    • Changed type John Marcum Wednesday, November 25, 2009 2:37 AM
    Wednesday, November 25, 2009 2:23 AM

Answers



  • I just wanted to follow up with this in case someone else runs into this issue, I found out that a conflicker worm group policy had been applied to the entire OU, this had caused several problems and the reason why I could reproduce the same issue over and over again. I had created an OU that blocked all inheritances and was able to setup the SCCM sever without any issues!

    Rebecca
    • Marked as answer by tymque Thursday, March 11, 2010 2:30 AM
    Thursday, March 11, 2010 2:30 AM

All replies

  • Your post indicates that this is SCCM SP2. SP2 is not available on slipstreamed media as far as I know so are you saying you are trying to upgrade a site to SP2? The reason I ask is because if you are mistaken and you are actually trying to install SCCM RTM on Server 2008 it will not work. It's been awhile since this was an issue but if I remember correctly it was an MP component that would fail if you tried to install SCCM RTM on server 08.


    If you do have SCCM SP1 media and it is failing I suggest you try what jason did here:

    http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/48bc0278-3809-4b80-80ec-cf51b4e4bc25



    John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
    Wednesday, November 25, 2009 2:35 AM
  • I can confirm that reinstalling BITS resolves this issue, and had a post about it earlier today in backup/restore.
    Wednesday, November 25, 2009 4:50 AM
  • Just read the post below

    http://social.technet.microsoft.com/Forums/en-AU/configmgrswdist/thread/5638cdf2-09d3-4750-995e-ae60973e86b8

    <Remember to copy tasks from task scheduler to some different location because it gets wiped off in process)

    Imp. Note: Running ccmclean /all on SCCM is one of these unsupported things.

    Remove the MP as a site system role (if it is still installed), wait for it to finish

    2.        Remove IIS completely

    4.      Reboot

    5.      Stop the Task Scheduler Service

    6.      Rename the %windir%\Tasks folder to something else (or move it)

    7.      Start the Task Scheduler Service (this will recreate the %windir%\Tasks folder)

    8.      Optional: Enable auditing on the \inetpub\wwwroot folder (and subfolders). Make sure to set local security policy to trap failures of file access.  We will need this in case we see the same security failure.

    9.      Reinstall IIS, BITS, WebDAV

    10.  Insure BITS and WebDAV are enabled

    11.  Reinstall the MP


    Server Engineer
    • Proposed as answer by veday001 Wednesday, November 25, 2009 7:30 AM
    • Edited by veday001 Tuesday, July 19, 2011 10:37 PM
    Wednesday, November 25, 2009 6:20 AM
  •       Run a ccmclean /all (this is a tool you can find in the SMS 2003 Toolkit 2)


    Anytime I post something that is clearly not supported I like to try to leave a note that it's unsupported so people don't get mad when they break something and call PSS and can't get help. Running ccmclean /all on SCCM is one of these unsupported things. In this case I can't see where it would do any good, if the MP is not installed then all ccmclean /all is going to do is remove the client. I have never once seen the reinstallation of IIS actually fix a site and it's a pain to do so I would try just reinstlaling BITS as Jason and the other poster mentioned first and as a last resort remove IIS and WebDav etc etc.




    John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
    Wednesday, November 25, 2009 12:51 PM
  • Thank you for replying John, Yes I have SP2 installed on the SCCM 07 server. I had gotten the update from Microsoft's website.

    http://www.microsoft.com/downloads/details.aspx?FamilyID=3318741a-c038-4ab1-852a-e9c13f8a8140&displaylang=en

    Thank you,

    Rebecca
    Tuesday, December 1, 2009 12:46 AM
  • Thank you for replying, I've reinstalled BITS several times, yet the same issue.

    Rebecca
    Tuesday, December 1, 2009 12:47 AM
  • Thank you for replying veday001, I've seen this article as well, I even mentioned it in my troubleshooting process, this does not work. I've done this nearly a dozen times thinking perhaps a process needs to be done in a different order.. Yet, no luck.

    Rebecca
    Tuesday, December 1, 2009 12:49 AM
  • Thank you for replying John, your correct running ccmclean /all off the sms 2003 toolkit did not work. Perhaps with SMS 2003 it would! I wish it was that simple to just reinstall BITS but i've done that numerous times. I've even started from scratch, rebuilt the server and I can duplicate this problem every time. I've removed IIS & WebDAV, installed, reconfigured yet the same error messages come up.. I've tried manually doing the install and I get:

    Setup was unable to create the Internet Virtual Directory CCM_Incoming the error code is: 80070005

    After looking up what that code means, "Access Denied". That doesn't help much...

    I've gone to the C:\intpub\ and have given everyone permissions (not recommended but tested) yet it still failed. I've installed FTP service to get the ISUR account that the log file is asking for, yet it still fails.

    Tuesday, December 1, 2009 12:55 AM
  • You shouldn't be able to duplicate this issue. Installing SCCM on a clean Server 08 is pretty straight forward. I would be willing to do a Live meeting with you and take a look if you are stuck. I can't do it tonight but tomorrow is open. email me offline if you wanna do that. john marcum at gmail dot com.




    John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
    Tuesday, December 1, 2009 1:31 AM
  • I have the same problem with SCCM2007 SP2 R2 RTM on Windows 2003 EE x64. I can not try to reinstall MP and IIS, as there is PKI. How did you deal?
    Tuesday, January 5, 2010 9:55 AM
  • Not once have I ever seen a case where reinstalling IIS actually fixed and SCCM issue. It's recomended a lot but I have never seen that work for anything. Reinstalling the MP does fix things from time to time though. When you say there is PKI I assume you are in native mode?


    John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
    • Proposed as answer by darthbeav Wednesday, January 20, 2010 6:18 PM
    Tuesday, January 5, 2010 3:31 PM
  • make sure your permissions for the svchost key and your tasks folders are adequate. there was a fix for conficker that had alot of admins creating gpo that changed the default permissions. I had the same problem untill i restored the permissions to what was shown as the default in this document

    http://support.microsoft.com/kb/962007
    Wednesday, January 20, 2010 6:20 PM
  • Not once have I ever seen a case where reinstalling IIS actually fixed and SCCM issue. It's recomended a lot but I have never seen that work for anything. Reinstalling the MP does fix things from time to time though. When you say there is PKI I assume you are in native mode?


    John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

    Yes, use Configuration Manager 2007 in native mode. However I solved reinstalling IIS and PKI and CM2007. It 'a test environment. but I did not want to reinstall everything.

    Thanks.
    Vid.
    Thursday, January 21, 2010 3:12 PM


  • I just wanted to follow up with this in case someone else runs into this issue, I found out that a conflicker worm group policy had been applied to the entire OU, this had caused several problems and the reason why I could reproduce the same issue over and over again. I had created an OU that blocked all inheritances and was able to setup the SCCM sever without any issues!

    Rebecca
    • Marked as answer by tymque Thursday, March 11, 2010 2:30 AM
    Thursday, March 11, 2010 2:30 AM
  • Thanks for the valuable information - I just inherited the EXACT same issue in my new position. I will try your solution (spent about two days on this so far).
    Wednesday, March 31, 2010 7:17 PM
  • Hi everyone,

    Win 2008 R2, SCCM 2007 SP2. We also have the conficker policy.
    I was also getting "Setup was unable to create the Internet Virtual Directory CCM_Incoming the error code is: 80070005" error.

    This worked for me(Manual MP install completed successfully):

    CD C:\Windows

    cacls TASKS  /T /E /P BUILTIN\Users:C

    Before that I had given Full access to System and BUILTIN\Administrators, but it wasn't enough.

    Regards,

    Sezgin RAFET

    Tuesday, September 7, 2010 12:47 PM
  • The removal of the conficker policy worked for us, too.  We did, however, need to manually change the permissions back instead of just blocking the policy.  Note that the conficker policy that Microsoft wrote about does say that the policy will interfere with SCCM and other installations and should be removed once cleanup of conficker is complete.  It was one of those statements that we just passed right over.
    Wednesday, April 6, 2011 3:41 PM
  • I had this problem today on a new client site.  After what felt like an age, I found this thread, found out that the customer had conficker, set the default W2008 permissions on SVCHOST reg key and Tasks folder (http://support.microsoft.com/kb/962007) and everything suddenly worked.  Thanks for the tip, tymque!  BTW, turns out this also solved a problem they were having with scheduled tasks :)
    Friday, July 15, 2011 5:19 PM
  • We had some issues because when conficker hit MS made some reccomendations to prevet it from spreading. There's a KB on it somewhere. At my cocmpany the settings never got reversed. When we tried to deploy a SP to our clients it failed. Removing the settings let it install.

     

     


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
    Sunday, July 17, 2011 4:06 PM
  • This was one of a series of error messages including 1603 and 25001, 80070057 messages.Confiker indeed. Followed https://support.microsoft.com/en-us/kb/962007#Mitigationsteps adding the recommended settings in a group policy which i pushed out.  Issues resolved after a few days of troubleshooting.  Thanks guys!!
    Thursday, March 19, 2015 1:48 PM