Jump to content


tymque

SMS_MP_CONTROL_MANAGER

Recommended Posts

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/cs2/blogs/mlucero/archive/2007/05/16/sms-2003-troubleshooting-mp-control-manager-detected-mpsetup-has-failed-to-create-the-ccm-incoming-virtual-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.

 

Any advice would be greatly appricated!

 

Thanks!

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Hello There,

 

Did we manage to resolve this issue as it appears I have the exact same issue. I have followed the guides on the website to the letter, but am still getting the same error as the OP.

 

My setup is as follows:

Windows Server 2008 R2

SQL 2005 SP3

SCCM 2007 SP2 R2

MDT 2010

 

 

 

This is the error:

 

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.

 

 

 

This is the output of MPSetup.log

 

<11-30-2009 13:29:30> ====================================================================

<11-30-2009 13:29:30> SMSMP Setup Started....

<11-30-2009 13:29:30> Parameters: C:\PROGRA~2\MIE096~1\bin\i386\ROLESE~1.EXE /install /siteserver:S10VM8MTEST SMSMP

<11-30-2009 13:29:30> Installing Pre Reqs for SMSMP

<11-30-2009 13:29:30> ======== Installing Pre Reqs for Role SMSMP ========

<11-30-2009 13:29:30> Found 1 Pre Reqs for Role SMSMP

<11-30-2009 13:29:30> Pre Req MSXML60 found.

<11-30-2009 13:29:30> No versions of MSXML60 are installed. Would install new MSXML60.

<11-30-2009 13:29:30> Enabling MSI logging. msxml6_x64.msi will log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\msxml6_x64MSI.log

<11-30-2009 13:29:30> Installing C:\Program Files (x86)\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi

<11-30-2009 13:29:30> msxml6_x64.msi exited with return code: 0

<11-30-2009 13:29:30> msxml6_x64.msi Installation was successful.

<11-30-2009 13:29:30> ======== Completed Installion of Pre Reqs for Role SMSMP ========

<11-30-2009 13:29:30> Installing the SMSMP

<11-30-2009 13:29:30> Passed OS version check.

<11-30-2009 13:29:30> IIS Service is installed.

<11-30-2009 13:29:30> checking WebDAV configuraitons

<11-30-2009 13:29:31> WebDAV is configured

<11-30-2009 13:29:31> No versions of SMSMP are installed. Installing new SMSMP.

<11-30-2009 13:29:31> Enabling MSI logging. mp.msi will log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log

<11-30-2009 13:29:31> Installing C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\mp.msi CCMINSTALLDIR="C:\Program Files (x86)\SMS_CCM" CCMSERVERDATAROOT="C:\Program Files (x86)\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1

<11-30-2009 13:29:53> mp.msi exited with return code: 1603

<11-30-2009 13:29:53> Backing up C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log.LastError

<11-30-2009 13:29:53> Fatal MSI Error - mp.msi could not be installed.

 

 

If you have had any luck fixing this can you please post the fix, as I am stompped as how to proceed.

 

Many Thanks.

Share this post


Link to post
Share on other sites

what does this log tell us

 

C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log

 

I've attached the mpMSI.log file as it's faily large (1.88MB)

 

It seems to install the MSI partly, but then at the end of the log it says;

 

MSI (s) (7C:14) [14:45:25:043]: Note: 1: 1708

MSI (s) (7C:14) [14:45:25:043]: Product: SMS Management Point -- Installation operation failed.

MSI (s) (7C:14) [14:45:25:044]: Windows Installer installed the product. Product Name: SMS Management Point. Product Version: 4.00.6487.2000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

 

Also I only have two critical components in "Component Status" - SMS_MP_CONTROL_MANAGER and SMS_MP_DEVICE_MANAGER

 

Any ideas?

 

Cheers

mpMSI.log

Share this post


Link to post
Share on other sites

are you sure thats the log file, doesnt look anything like a normal log file to me,

 

please doublecheck and try again

 

Hey Anyweb, I've doubled checked "C:\Program Files(x86)\Microsoft Configuration Manager\Logs\mpMSI.log" and the log I attached is the correct log.

 

Are we perhaps after "C:\Program Files(x86)\Microsoft Configuration Manager\Logs\MPSetup.log"? I've attached that log incase that's what we need.

 

Cheers

MPSetup.log

Share this post


Link to post
Share on other sites

MPSetup.log

<12-02-2009 08:56:41> mp.msi exited with return code: 1603

<12-02-2009 08:56:41> Backing up C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log.LastError

<12-02-2009 08:56:41> Fatal MSI Error - mp.msi could not be installed.

 

mpMSI.log (always search for "Return value 3")

[14:45:20] @@ERR:25006

MSI (s) (7C!40) [14:45:20:952]: Product: SMS Management Point -- Error 25006. Setup was unable to create the Internet virtual directory CCM_Incoming

The error code is 80070005

Error 25006. Setup was unable to create the Internet virtual directory CCM_Incoming

The error code is 80070005

CustomAction CcmCreateIISVirtualDirectories returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

MSI (s) (7C:14) [14:45:20:993]: User policy value 'DisableRollback' is 0

MSI (s) (7C:14) [14:45:20:993]: Machine policy value 'DisableRollback' is 0

Action ended 14:45:20: InstallFinalize. Return value 3.

[...]

[14:45:24] The service 'ccmexec' is not installed

MSI (s) (7C:14) [14:45:24:927]: Note: 1: 2318 2:

MSI (s) (7C:14) [14:45:24:928]: No System Restore sequence number for this installation.

MSI (s) (7C:14) [14:45:24:928]: Unlocking Server

MSI (s) (7C:14) [14:45:24:931]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.

Action ended 14:45:24: INSTALL. Return value 3.

Share this post


Link to post
Share on other sites

can this be due to webdav 7.5. did you see this yet?

 

Yeah, I came across that post. And I did install webdav 7.5 via add/remove features - then set it up as per the instructions in the doco. The reporting services components are working fine, it's just the management point causing problems. Perhaps I should start from scratch using Windows 2008 Std?

Share this post


Link to post
Share on other sites

I finally found the issue. Our local domain policy locks down the regkey

 

HKLM\Software\Microsoft\Windows NT\CurrentVersion\SvcHost

 

After stopping the GPO applying to my SCCM server the Management Point installed fine. It looks as though ScvHost is used by IIS to create virtual directories, and the Management Point (MP.msi) was failing to install due to this.

 

It's a good lesson to learn, that I should have created a proper test enviroment for testing SCCM, rather then going the easy way of using the production domains resources.

 

Cheers for your help.

Share this post


Link to post
Share on other sites

I finally found the issue. Our local domain policy locks down the regkey

 

HKLM\Software\Microsoft\Windows NT\CurrentVersion\SvcHost

 

After stopping the GPO applying to my SCCM server the Management Point installed fine. It looks as though ScvHost is used by IIS to create virtual directories, and the Management Point (MP.msi) was failing to install due to this.

 

It's a good lesson to learn, that I should have created a proper test enviroment for testing SCCM, rather then going the easy way of using the production domains resources.

 

Cheers for your help.

 

 

Hello

I'm facing to the same probleml.

I would like to know after suspend the GPO for your computer what are you doing next ??

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...