Event Viewer Error: On 08/18/08 09:26:17, component SMS_SITE_COMPONENT_MANAGER on computer EDCMSCCM01 reported: SMS Site Component Manager failed to install 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 installation in minutes. To force SMS Site Component Manager to immediately retry the installation, stop and restart SMS Site Component Manager using the SMS Service Manager. ComponentSetup.log ==================== <<08-11-2008 09:09:53>> ====================Create accounts: CompletedConfigure registry: CompletedCreate and initialize site database: CompletedTransfer files: CompletedRegister controls: CompletedInitialize Configuration Manager site: CompletedInstall site component manager: CompletedInstall SMS provider components: CompletedCreate boot image packages: CompletedCreate program group: CompletedInstall Configuration Manager services (site component manager): CompletedInstall component monitor: CompletedInstall SMS executive: CompletedInstall database notification monitor: CompletedInstall site control manager: CompletedInstall hierarchy manager: CompletedInstall inbox manager: CompletedInstall policy provider: CompletedInstall MP control manager: UnknownInstall management point: Unknown ==================== <<08-14-2008 14:04:10>> ====================Shutdown Configuration Manager Services: CompletedReset ConfigMgr related accounts: CompletedReset permissions for ConfigMgr related directories: Not StartedUpgrade site control file: CompletedUpdate registry: CompletedVerify permissions for ConfigMgr related directories: Not Started I have read many articles where "Unknown" status is normal for the Management Point installation, and that all I need to do is check the mpmsi.log and mpcontrol.log. I do not have either. I can open the Config Manager Console. Under System Status\Site Status\Compenent Status the SMS_MP_CONTROL_MANAGER and the SMS_SITE_COMPENENT_MANAGER are both in critical. Both report the error every hour. What should I do here?

Triage191 wrote: Solution: Review the previous status messages to determine the exact reason for the failure. Did any of the other status messages give you a clue why the install failed? Is this your central site, a child primary or child secondary site?

Is this an upgrade to SP1? What does sitecomp.log and mpsetup.log say?

This is my primary site. This is also a fresh install with a full SP1 load. No upgrade. This is on a Sever 2008 machine. The MPSetup.log is in a loop of some sort.I can attach the log, if need. The loop basically is trying to install MSXML60. It calls the msxml6.msi and returns an installation successful return code of 0. It also creates a log file. Msxml6msi.log. The Msxml6msi.log does show errors. Here is odd part. The install completes successfully, but then throws an error. Here is the last 15 lines of the log: Property(S): OriginalDatabase = C:\Program Files\Microsoft Configuration Manager\bin\i386\00000409\msxml6.msiProperty(S): UILevel = 2Property(S): ACTION = INSTALLMSI (s) (10:2C) [15:14:09:269]: Note: 1: 1707 MSI (s) (10:2C) [15:14:09:269]: Product: MSXML 6.0 Parser -- Installation completed successfully. MSI (s) (10:2C) [15:14:09:285]: Windows Installer installed the product. Product Name: MSXML 6.0 Parser. Product Version: 6.10.1129.0. Product Language: 1033. Installation success or error status: 0. MSI (s) (10:2C) [15:14:09:285]: Cleaning up uninstalled install packages, if any existMSI (s) (10:2C) [15:14:09:285]: MainEngineThread is returning 0MSI (s) (10:20) [15:14:09:285]: Destroying RemoteAPI object.MSI (s) (10:48) [15:14:09:285]: Custom Action Manager thread ending.MSI (s) (10:20) [15:14:09:285]: RESTART MANAGER: Session closed.MSI (s) (10:20) [15:14:09:285]: No System Restore sequence number for this installation.=== Logging stopped: 8/18/2008 15:14:09 ===MSI (c) (FC:04) [15:14:09:285]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1MSI (c) (FC:04) [15:14:09:285]: MainEngineThread is returning 0=== Verbose logging stopped: 8/18/2008 15:14:09 === I went to Microsoft and it does not look like xml60 is supported on server 2008. Is this my issue? SiteComp.log: I find this line of interest. I am not sure what to check on the WebDav config. Component [SMS_MP_CONTROL_MANAGER] could not install correctly on server EDCMSCCM01. WebDAV on the Windows Longhorn server is not configured correctly.SMS_SITE_COMPONENT_MANAGER8/18/2008 3:14:11 PM2556 (0x09FC)

I may have found my issue. Please hold on replies until I can verify. Thanks to Torsten'semail. Ihave foundthat my WebDav setttings were not set properly. I have updated these setting and will see what happens.

There should be a huge popup message when installing on server 2008 that points you to the docs. Almost all the cases here that someone is using 2k8 is because they didnot follow the steps required in the docs for 2k8 http://technet.microsoft.com/en-us/library/cc431377.aspx

We are having the same issue. The doc that was posted (twice) by John Marcum was followed word for word at install, and done again after noticing this event... it has not helped at all. Any other suggestions?

The exact same issue? What about the logfiles I mentioned earlier?

Hi,I have just had the same error this morning, and found a solution which I posted here - http://scug.dk/blogs/configurationmanager/archive/2009/12/30/webdav-fails-on-windows-server-2008-r2.aspx Hopefully it will help you.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

You can configure WebDav settings at two places when running on server 2008 R2: on server level (IIS) or on the default website. It has to be configured on the default website, otherwise you will see the errors described in this thread.

Hi, I have just had the same error this morning, and found a solution which I posted here - http://scug.dk/blogs/configurationmanager/archive/2009/12/30/webdav-fails-on-windows-server-2008-r2.aspx Hopefully it will help you. Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products Really struggled to sort this, checked webdav settings 1K times!... This sorted it out for me! Thanks Kent And I was configuring on the default website and still had the issue (6 months after this post with r2 installed!!)

This solution did not work with me!!