Jump to content


herrando

error reinstalling MP

Recommended Posts

Hi First post here for me, but I've been reading solutions on here for a good while now and find this forum to be an invaluable resource. Keep up the good work!

 

Now my issue, I'm hoping someone call assist with this - becuase it's driving me around the twist now...

 

We had SCCM 2007 R3 working all fine and well up until this morning. The only thing that we couldn't get working was asset intelligence synchronisation with Microsoft online catalog - it reported bad certificate. It was decided to remedy this by installing SCCM2007-SP2-KB2483225-ENU.msi.

 

Immediatly after installing this patch we had several information warnings in SCCM saying that "SMS site component manager detected that this componant should be reinstalled on the system, error 1071

 

After this it looked like it reinstalled some of these sucessfully, but then this warning apears:

 

"SMS Site Component Manager could not stop the SMS_EXECUTIVE service on site system \\SCCMA01.

Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system.

Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system.

If this problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information."

 

"

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.

 

"

Eventually it appears - without doing anything that the reinstall is sucessful.

 

pretty much all the other roles get reinstalled at this point sucessfully but then this error appears:

 

"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.

 

"

 

"

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.

 

"

MS Site Component Manager failed to install this component, because the Microsoft Installer File for this component (MP.msi) could not install.

Refer to the MPSetup.log, the MPMSI.log, as well as the SMS documentation and the Microsoft Knowledge Base for further information.

 

"

 

I checked my MPSetup.log and MPMSI.log and they contain the following:

 

 

<09-05-2012 21:13:51> ====================================================================

<09-05-2012 21:13:51> SMSMP Setup Started....

<09-05-2012 21:13:51> Parameters: D:\PROGRA~1\MICROS~1\bin\i386\ROLESE~1.EXE /install /siteserver:SCCMA01 SMSMP

<09-05-2012 21:13:51> Installing Pre Reqs for SMSMP

<09-05-2012 21:13:51> ======== Installing Pre Reqs for Role SMSMP ========

<09-05-2012 21:13:51> Found 1 Pre Reqs for Role SMSMP

<09-05-2012 21:13:51> Pre Req MSXML60 found.

<09-05-2012 21:13:51> No versions of MSXML60 are installed. Would install new MSXML60.

<09-05-2012 21:13:51> Enabling MSI logging. msxml6_x64.msi will log to D:\Program Files (x86)\Microsoft Configuration Manager\logs\msxml6_x64MSI.log

<09-05-2012 21:13:51> Installing D:\Program Files (x86)\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi

<09-05-2012 21:13:54> msxml6_x64.msi exited with return code: 1618

<09-05-2012 21:13:54> Backing up D:\Program Files (x86)\Microsoft Configuration Manager\logs\msxml6_x64MSI.log to D:\Program Files (x86)\Microsoft Configuration Manager\logs\msxml6_x64MSI.log.LastError

<09-05-2012 21:13:54> ======== Completed Installion of Pre Reqs for Role SMSMP ========

<09-05-2012 21:13:54> Installing the SMSMP

<09-05-2012 21:13:54> Passed OS version check.

<09-05-2012 21:13:54> IIS Service is installed.

<09-05-2012 21:13:54> checking WebDAV configuraitons

<09-05-2012 21:13:55> WebDAV is configured

<09-05-2012 21:13:55> SMSMP already installed (Product Code: {B391E30E-C8BD-41FC-8B8C-540C4365DBE0}). Upgrading/Reinstalling SMSMP

<09-05-2012 21:13:55> New SMSMP is the same product code. This is a minor upgrade.

<09-05-2012 21:13:55> Enabling MSI logging. mp.msi will log to D:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log

<09-05-2012 21:13:55> Installing D:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\mp.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\Program Files (x86)\SMS_CCM" CCMSERVERDATAROOT="D:\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

<09-05-2012 21:13:58> mp.msi exited with return code: 1618

<09-05-2012 21:13:58> Backing up D:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log.LastError

<09-05-2012 21:13:58> mp.msi could not be installed. The return code was 1618

 

 

MPMSI.LOG

 

=== Verbose logging started: 05/09/2012 21:13:55 Build type: SHIP UNICODE 5.00.7601.00 Calling process: D:\PROGRA~1\MICROS~1\bin\i386\ROLESE~1.EXE ===

MSI © (54:98) [21:13:55:100]: Resetting cached policy values

MSI © (54:98) [21:13:55:100]: Machine policy value 'Debug' is 0

MSI © (54:98) [21:13:55:100]: ******* RunEngine:

******* Product: D:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\mp.msi

******* Action:

******* CommandLine: **********

MSI © (54:98) [21:13:55:100]: Client-side and UI is none or basic: Running entire install on the server.

MSI © (54:98) [21:13:58:111]: Failed to grab execution mutex. System error 258.

MSI © (54:98) [21:13:58:111]: Cloaking enabled.

MSI © (54:98) [21:13:58:111]: Attempting to enable all disabled privileges before calling Install on Server

MSI © (54:98) [21:13:58:111]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI © (54:98) [21:13:58:111]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1

MSI © (54:98) [21:13:58:111]: MainEngineThread is returning 1618

=== Verbose logging stopped: 05/09/2012 21:13:58 ===

MSI (s) (B4:D0) [21:18:29:726]: User policy value 'DisableRollback' is 0

MSI (s) (B4:D0) [21:18:29:726]: Machine policy value 'DisableRollback' is 0

MSI (s) (B4:D0) [21:18:29:726]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (B4:D0) [21:18:29:726]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (B4:D0) [21:18:29:726]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (B4:D0) [21:18:29:726]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1

MSI (s) (B4:D0) [21:18:29:726]: Restoring environment variables

MSI (s) (B4:D0) [21:18:29:726]: Destroying RemoteAPI object.

MSI (s) (B4:E4) [21:18:29:726]: Custom Action Manager thread ending.

 

I did notice that initially before checking this that Webdav did not appear to be running (mapped drive to the localhost)

 

I then checked IIS settings and there were several errors present- Webdav seemed to be configured correctly but upon checking the webdav schema file it was set as follwing:

 

 

<element name="properties">

<attribute name="allowAnonymousPropfind" type="bool" defaultValue="false" />

<attribute name="allowInfinitePropfindDepth" type="bool" defaultValue="false" />

<attribute name="allowCustomProperties" type="bool" defaultValue="true" />

<collection addElement="add" removeElement="remove" clearElement="clear" allowUnrecognizedAttributes="true">

<attribute name="xmlNamespace" type="string" isUniqueKey="true" required="true" validationType="nonEmptyString" />

<attribute name="propertyStore" type="string" required="true" validationType="nonEmptyString" />

</collection>

</element>

 

 

I have changed it back to :

 

<element name="properties">

<attribute name="allowAnonymousPropfind" type="bool" defaultValue="true" />

<attribute name="allowInfinitePropfindDepth" type="bool" defaultValue="true" />

<attribute name="allowCustomProperties" type="bool" defaultValue="false" />

<collection addElement="add" removeElement="remove" clearElement="clear" allowUnrecognizedAttributes="true">

<attribute name="xmlNamespace" type="string" isUniqueKey="true" required="true" validationType="nonEmptyString" />

<attribute name="propertyStore" type="string" required="true" validationType="nonEmptyString" />

</collection>

</element>

 

and restarted the componant services, and now webdav is working again - but still the MP wont reinstall.

 

IIS logs keep throwing this error continually :

 

Log Name: System

Source: Microsoft-Windows-WAS

Date: 05/09/2012 21:06:32

Event ID: 5009

Task Category: None

Level: Warning

Keywords: Classic

User: N/A

Computer: SCCMA01.ourdomain.net

Description:

The description for Event ID 5009 from source Microsoft-Windows-WAS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

CCM Server Framework Pool

1376

fffffffe

Event Xml:

<Event xmlns="http://schemas.micro...08/events/event">

<System>

<Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />

<EventID Qualifiers="32768">5009</EventID>

<Version>0</Version>

<Level>3</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2012-09-05T20:06:32.000000000Z" />

<EventRecordID>801029</EventRecordID>

<Correlation />

<Execution ProcessID="0" ThreadID="0" />

<Channel>System</Channel>

<Computer>SCCMA01.ourdomain.net</Computer>

<Security />

</System>

<EventData>

<Data Name="AppPoolID">CCM Server Framework Pool</Data>

<Data Name="ProcessID">1376</Data>

<Data Name="ExitCode">fffffffe</Data>

</EventData>

</Event>

 

And I can see BITS errors too:

 

Log Name: Application

Source: BITS Server Extensions

Date: 05/09/2012 10:10:39

Event ID: 9

Task Category: None

Level: Error

Keywords:

User: SYSTEM

Computer: SCCMA01.ourdomain.net

Description:

Enabling BITS uploads for the virtual directory failed with error 0x800CC801. The error occurred while creating the directory IIS://LocalHost/W3SVC/1/Root/CCM_Incoming

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="BITS Server Extensions" Guid="{38398B57-93F3-4C42-AC26-DB3F5998745B}" />

<EventID>9</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000000</Keywords>

<TimeCreated SystemTime="2012-09-05T09:10:39.473139100Z" />

<EventRecordID>37814</EventRecordID>

<Correlation />

<Execution ProcessID="6096" ThreadID="8584" />

<Channel>Application</Channel>

<Computer>SCCMA01.ourdomain.net</Computer>

<Security UserID="S-1-5-18" />

</System>

<EventData>

<Data Name="name">IIS://LocalHost/W3SVC/1/Root/CCM_Incoming</Data>

<Data Name="hr">2148321281</Data>

<Data Name="vdir">

</Data>

</EventData>

</Event>

 

 

Its seems there is way too much going on here to try and start troubleshooting this....

 

Should I uninstall this KB? or will this cause more harm? i'm really struggling wiht this one to explain to my boss why this is on it's knees given it should have been a pretty straight forward update... Any help will be greatly appreciated.

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...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.