SMS Site Component Manager failed to reinstall this component on this site system.
Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the reinstallation in 60 minutes. To force SMS Site Component Manager to immediately retry the reinstallation, stop and restart SMS Site Component Manager using the SMS Service 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.
--------------------------------------------------------------------------------------------------
We are running Server 2008 sp2 with IIS7. I did as much research as I could with my limited knowledge and found that in IIS Manager when I try to open BITS I get the error message:
BITS server was unable to read from the IIS Meta-base as it is corrupt. The settings for this virtual directory have been reset to the BITS defaults. Parameter count mismatch.
At this point none of the updates are getting pushed and I getting errors from all the secondary's because of this. I am leaning towards reinstalling BITS but need to do more research since I am not sure exactly what that will involve.
Thanks
http://technet.microsoft.com/en-us/library/cc431377.aspx
Do you have another site system that you can make the default MP while you troubleshoot this?
-Karl M
Can you check that the IIS configuration is still as requierd for ConfigMgr:
http://technet.microsoft.com/en-us/library/cc431377.aspx
Can you check the MPsetup.log for more information?
<03-03-2010 10:26:53> mp.msi exited with return code: 1603
<03-03-2010 10:26:53> Backing up d:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to d:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<03-03-2010 10:26:53> Fatal MSI Error - mp.msi could not be installed.
<03-03-2010 10:27:01> ====================================================================
<03-03-2010 10:27:01> SMSMP Setup Started....
<03-03-2010 10:27:01> Parameters: D:\PROGRA~1\MICROS~2\bin\i386\ROLESE~1.EXE /install /siteserver:CNXSCCM SMSMP
<03-03-2010 10:27:01> Installing Pre Reqs for SMSMP
<03-03-2010 10:27:01> ======== Installing Pre Reqs for Role SMSMP ========
<03-03-2010 10:27:01> Found 1 Pre Reqs for Role SMSMP
<03-03-2010 10:27:01> Pre Req MSXML60 found.
<03-03-2010 10:27:01> No versions of MSXML60 are installed. Would install new MSXML60.
<03-03-2010 10:27:01> Enabling MSI logging. msxml6.msi will log to d:\Program Files\Microsoft Configuration Manager\logs\msxml6MSI.log
<03-03-2010 10:27:01> Installing d:\Program Files\Microsoft Configuration Manager\bin\i386\00000409\msxml6.msi
<03-03-2010 10:27:01> msxml6.msi exited with return code: 0
<03-03-2010 10:27:01> msxml6.msi Installation was successful.
<03-03-2010 10:27:01> ======== Completed Installion of Pre Reqs for Role SMSMP ========
<03-03-2010 10:27:01> Installing the SMSMP
<03-03-2010 10:27:01> Passed OS version check.
<03-03-2010 10:27:01> IIS Service is installed.
<03-03-2010 10:27:01> checking WebDAV configuraitons
<03-03-2010 10:27:01> WebDAV is configured
<03-03-2010 10:27:01> SMSMP already installed (Product Code: {7AF53388-F428-4A8B-8F20-DBB4851E3424}). Upgrading/Reinstalling SMSMP
<03-03-2010 10:27:01> New SMSMP is the same product code. This is a minor upgrade.
<03-03-2010 10:27:01> Enabling MSI logging. mp.msi will log to d:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
<03-03-2010 10:27:01> Installing d:\Program Files\Microsoft Configuration Manager\bin\i386\mp.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="d:\Program Files\SMS_CCM" CCMSERVERDATAROOT="d:\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
Thanks.
That is the same error in the log over and over.
Did you see " Fatal MSI Error - mp.msi could not be installed. " 4 lines down?
That is the same error in the log over and over.
It is strange because just below that error the MP seems to install. Is that also happening over and over again?
Setup was unable to create the Internet virtual directory CCM_Incoming. The error code is 800CC801
I have a somewhat similar issue. Clients can't send inventory to the CCM_Incoming virtual directory. When I try to open BITS in IIS Manager I get the same error (BITS server was unable to read from the IIS Meta-base).
Just to be sure how you solved it...
Did you uninstall and reinstall IIS Server Extension (subcomponent of BITS), or the full BITS feature?
I uninstalled IIS Server Extension, rebooted, installed it again and rebooted again.
After that I could open the BITS-page in IIS Manager without problems. Then I manually enabled BITS upload on the CCM_Incoming virtual directory, and clients started to send inventory again. I suppose reinstalling the MP would perform that last action.
Hey,
Thanks a lot! We had the same issue, this post really helped us out!
Thank you, thank you, thank you!
All of a sudden one of our servers showed a lot of errors this morning. I followed this post when a colleague pointed it out to me and this resolved our issue!
Greetings,
C.Vos
PS;:
this is the message i saw multiple times :
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.
Wow.. perfect. Lots of research and bingo, this fixed it. I wasn't receiving any hardware inventory and bdps were showing "install pending" on new bdps. The dataldr.log was showing very little activity. I did this fix and everything now looks great. logs cleared up!
I did not run the mp.msi though. Only reinstalled the iis server extensions under the bits feature
Thanks again!!!
Had exactly this issue since 13 August 2013 here.
I can confirm that "risc" solution worked here. I did not have to run mp.msi to fix.
Used default BITS upload option(s) in IIS for CCM_Incoming virtual directory after BITS IIS Server Extension removal (then reboot) and re-installation (then reboot) using Features section in Server Manager.
MP_Hinv.log and dataldr.log are now showing loads of status reports being delivered. No BITS errors in IIS logs and BITS Uploads settings does not now report error (e.g.):
"bits server was unable to read from the iis metabase as it is corrupt" - note may not be exact message
I was not being notified in ConfigMgr console about the specific issue but had noticed BDPs were being shown in critical state - I now have all BDPs showing OK status.
I initially also noticed that timestamps in v_GS_ views (and our reports) were not current and client data was not being updated in reports. Timestamps are now current.
Then I noticed BITS errors in IIS logs when tracking down the issue e.g.
BITS_POST /CCM_Incoming/{5A71608B-A582-4C2C-B863-33B3DBF94F27} (bits_error:,501,0x80070005) 443
Also BITS upload errors on clients e.g. using "bitsadmin /list /allusers":
{4D9C5F11-CCD4-4A63-89CE-360531431C68} 'CCM Message Upload {6F1C844A-0928-4F9E-A417-F31C4314526D}' TRANSIENT_ERROR 0 / 1 0 / 12271
{C93AA6DB-454E-4F34-9BA2-D8737EE4293B} 'CCM Message Upload {0EB0799C-93DD-4AD1-9
B0C-84DF73B29A46}' TRANSIENT_ERROR 0 / 1 0 / 16819
{6AAD9250-B7D4-44CB-B14D-9C089A589969} 'CCM Message Upload {911AD63C-0A02-48D9-B
588-EECB2B38A0C1}' TRANSIENT_ERROR 0 / 1 0 / 42801
Thanks - this was driving me crazy!