Post Config Manager 2012 R2 Upgrade Errors - Help Needed

[TopherWilkes]

Hi Everyone,

 

Firstly I just wanted to say these forums are great. They have helped so much with my installation and management of Configuration Manager at my site.

 

Yesterday I upgraded from Configuration Manager 2012 SP1 (on Server 2008 R2) to Configuration Manager 2012 R2. I followed this guide on this website:

 

http://www.windows-noob.com/forums/index.php?/topic/8451-how-can-i-install-system-center-2012-r2-configuration-manager/

 

I used the actual release version instead of the Preview Release version in the guide above.

 

The installation went very smoothly just like the guide. At the end I had all green checks and everything seemed fine. Very shortly afterwards we tried to image some machines and noticed they were failing. Diving into our logs using the CMTrace tool we discovered lots of red errors.

 

Within the sitecomp.log it looks like the upgrade on the SMSMP failed or is failing:

 

Remove STORM.MERCEDES.WA.EDU.AU from user group SMS_SiteSystemToSiteServerConnection_MP_MCP SMS_SITE_COMPONENT_MANAGER 23/10/2013 5:42:01 AM 712 (0x02C8)
NetLocalGroupDelMembers(MERCEDES\STORM$) failed with (1377) SMS_SITE_COMPONENT_MANAGER 23/10/2013 5:42:01 AM 712 (0x02C8)
Starting bootstrap operations... SMS_SITE_COMPONENT_MANAGER 23/10/2013 5:42:01 AM 712 (0x02C8)
Installed service SMS_SERVER_BOOTSTRAP_STORM. SMS_SITE_COMPONENT_MANAGER 23/10/2013 5:42:01 AM 712 (0x02C8)
Starting service SMS_SERVER_BOOTSTRAP_STORM with command-line arguments "MCP D:\Program Files\Microsoft Configuration Manager /install D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe SMSMP "... SMS_SITE_COMPONENT_MANAGER 23/10/2013 5:42:01 AM 712 (0x02C8)
Execution of "D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:STORM.MERCEDES.WA.EDU.AU" on server STORM.MERCEDES.WA.EDU.AU failed: Child process ""D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe" /install /siteserver:STORM SMSMP 0" took too long to execute, and the process (PID = 7652) was orphaned. SMS_SITE_COMPONENT_MANAGER 23/10/2013 6:12:07 AM 712 (0x02C8)
INFO: 'STORM.MERCEDES.WA.EDU.AU' is a valid FQDN. SMS_SITE_COMPONENT_MANAGER 23/10/2013 6:12:07 AM 712 (0x02C8)
Bootstrap operation failed. SMS_SITE_COMPONENT_MANAGER 23/10/2013 6:12:07 AM 712 (0x02C8)
Deinstalled service SMS_SERVER_BOOTSTRAP_STORM. SMS_SITE_COMPONENT_MANAGER 23/10/2013 6:12:07 AM 712 (0x02C8)
Bootstrap operations aborted. SMS_SITE_COMPONENT_MANAGER 23/10/2013 6:12:07 AM 712 (0x02C8)
Reinstallation failed and will be retried in the next polling cycle. SMS_SITE_COMPONENT_MANAGER 23/10/2013 6:12:07 AM 712 (0x02C8)

 

Then within the MPSetup.log it looks like it is trying to update the CCM Client as part of the SMSMP update, but fails:

 

<10/23/13 10:12:27> ======== Installing Pre Reqs for Role SMSMP ========
<10/23/13 10:12:27> Found 3 Pre Reqs for Role SMSMP
<10/23/13 10:12:27> Pre Req MSXML60 found.
<10/23/13 10:12:27> No versions of MSXML60 are installed. Would install new MSXML60.
<10/23/13 10:12:27> Enabling MSI logging. msxml6_x64.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log
<10/23/13 10:12:27> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi
<10/23/13 10:12:27> msxml6_x64.msi exited with return code: 0
<10/23/13 10:12:27> msxml6_x64.msi Installation was successful.
<10/23/13 10:12:27> Pre Req CcmSetup found.
<10/23/13 10:12:27> Installing pre-req using command line "D:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp
<10/23/13 10:12:27> Pre-req installer "D:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp finished with exit code 1
<10/23/13 10:12:27> Failed to Install Pre Req CcmSetup. Return Code is 1
<10/23/13 10:12:27> This was a required Pre Req, can not continue.
<10/23/13 10:12:27> Installation Failed. Error Code: 1
<10/23/13 10:12:27> ~RoleSetup().

 

Then in the client.msi.log it shows more errors with the CCM Client:

 

MSI (s) (74:E8) [10:12:30:507]: Product: Configuration Manager Client - Update '{15424A7E-6B05-4134-8598-1DBE006CEC12}' could not be installed. Error code 1642. Additional information is available in the log file C:\Windows\ccmsetup\Logs\client.msi.log.
MSI (s) (74:E8) [10:12:30:507]: Windows Installer installed an update. Product Name: Configuration Manager Client. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: {15424A7E-6B05-4134-8598-1DBE006CEC12}. Installation success or error status: 1642.
MSI (s) (74:E8) [10:12:30:508]: Note: 1: 1708
MSI (s) (74:E8) [10:12:30:508]: Product: Configuration Manager Client -- Installation failed.
MSI (s) (74:E8) [10:12:30:508]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1642.
MSI (s) (74:E8) [10:12:30:510]: Attempting to delete file C:\Windows\Installer\3df4d0c.msp

 

We have tried removing the Management Point and re-adding it. This has not fixed the issue. The same errors remain.

 

Has anyone had any similar issues or does anyone have any idea on what may be the issue?

 

Any help is much appreciated.

 

Topher Wilkes

[Geekdevil]

Hi Topher,

 

I was upgrading our server to R2 this morning and ran into the same issue where the management point stopped working. By chance do you have a "PATCH=" in your automatic client install because I think this is what killed me. I had put that there for SP1.

 

When looking at the mpsetup and mpmsi logs I could see it failing. Like you, I saw the that management point needs the client, so I looked at the ccmsetup and client.msi logs and noticed that it was trying to install the patch for SP1.

 

Long story short, to get the management point back up I did the following:

1. Removed the management point from my server.

2. Ran "C:\Program Files\Microsoft Configuration Manager\client\ccmsetup SMSSITECODE=<mysite>" (with no other options. Change mysite to your actual site code).

4. Monitored my ccmsetup.log to make sure the client installs correctly.

3. Added the management point to my server.

5. Monitored mpsetup and saw that it got past the prereqs and actually installed mp.msi.

 

Eventually I could see activity again in my mpcontrol.log

 

I hope this helps,

David

[TopherWilkes]

Hi David,

 

Just wanted to say THANK YOU SO MUCH! I did as you said and removed the Management Point then installed the CCM Client manually with only the sitecode. Monitored the install and saw that it was successful. Reinstalled the Management Point and it looks like we are ready to go!

 

Thanks so much for you help. Really appreciate it!

 

Topher

[anyweb]

Hi David and Topher,

can you please tell me what your patch statement said and where you had it defined (client installation properties ?), did both of you have Automatic client upgrade selected ? I'm raising a bug on connect for this issue

 

cheers

niall

[Geekdevil]

Hi Niall,

 

Under Client Push Installation properties

 

General tab:

Enabled automatic site-wide client push, unchecked.

 

Installation Properties tab:

 

SMSSITECODE=<my site> SMSCACHESIZE=20000 SMSMP=<my mp> FSP=<my fs> PATCH=<UNC path to SP1.msp>

 

 

Under Hierarchy Settings

 

Automatic Client upgrade tab:

Upgrade client automatically, checked.. I don't remember turning this on because we use Deep Freeze for some machines, so this would be a waste of resrouces.

 

 

When I ran the upgrade, everything was green. The first thing that I attempted was do to an OSD because WDS is usually the first thing to break. When I couldn't PXE boot, I reinstalled it twice but it was throwing a 80004005 trying to connect to the management point, I decided to look somewhere else. When I looked at my component status, I saw that SMS_MP_CONTROL_MANAGER was in error. I tried to restart it but it would error querying the component. This was when I attempted to reinstall the management point. While monitoring the mpsetup.log I saw that it was trying to install the client as a pre-req and that was failing, so I went to look at my ccmsetup.log and noticed the "PATCH="

 

mpsetup.log

<10/23/13 10:54:49> Installing pre-req using command line "C:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp
<10/23/13 10:54:49> Pre-req installer "C:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp finished with exit code 1
<10/23/13 10:54:49> Failed to Install Pre Req CcmSetup. Return Code is 1

 

ccmsetup.log

[LOG[Loaded command line: "C:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" "/runservice" "/mp:<my mp>" "SMSSITECODE=<my site code>" "SMSCACHESIZE=20000" "FSP=<my fsp>" "PATCH=<UNC to SP1 .msp&gt]

[anyweb]

ok thanks, i've filed a bug on connect and pointed to this post, thanks for your information and troubleshooting

[geckostech]

ok thanks, i've filed a bug on connect and pointed to this post, thanks for your information and troubleshooting

Hi Niall,

 

Check this post:

 

http://www.windows-noob.com/forums/index.php?/topic/7217-client-version-50078041000-is-not-compatible-with-the-site-111-version-50077110000/

 

DerGali near the bottom made a post which has at least got the client installing for me. I will wait to see if the management points sort their pickle out by the morning.