locked
SCCM 2012 Client uprade fails on newly upgraded SCCM 2012 SP2 server RRS feed

  • Question

  • Hi,

    I'm in the process of testing the upgrade process from SCCM 2012 SP1 CU4 to SCCM 2012 SP2 and the server SCCM component upgrade appears to have worked great. There were no issues I could see during the upgrade process.

    My problem is related to the SCCM 2012 client that is installed on my SCCM 2012 server.  I was reviewing the ccmsetup.log file on the newly upgraded SCCM server and I saw these errors:

    [GetTargetPatchCode failed with 0x80070664 when getting patch code for 'D:\Program']

    [Patch 'D:\Program' isn't targeted for the current client.msi]LOG]

    My SCCM 2012 server components are installed on the D: drive of my server.  It appears that there is a directory specification that isn't quoted or something maybe?  If I look in the root of my D: drive I actually have a file called "Program" which appears to be a text file

    Any clue as to what is happening here?  Can I manually run the SCCM client setup somehow?

    Here is what the rest of the ccmsetup.log file shows

    <![LOG[Download complete.]LOG]!><time="13:56:37.723+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="ccmsetup.cpp:6008">
    <![LOG[Successfully downloaded client files.]LOG]!><time="13:56:37.723+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="ccmsetup.cpp:1388">
    <![LOG[Retrieved client version '5.00.8239.1000' and minimum assignable site version '5.00.8200.1000' from client package]LOG]!><time="13:56:37.735+420" date="08-18-2015" component="ccmsetup" context="" type="0" thread="5560" file="siteinfo.cpp:704">
    <![LOG[Checking compatibility of site version '5.00.8239.1000', expect newer than '5.00.8200.1000']LOG]!><time="13:56:37.735+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="siteinfo.cpp:729">
    <![LOG[Client (5.00.7804.1000) is installed but is a different SKU. Initiating install.]LOG]!><time="13:56:37.743+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="msiutil.cpp:671">
    <![LOG[Upgrade code '{252DA259-82CA-4177-B8D0-49C78937BA3E}': product = '{D6804B3A-BFEC-4AB4-BFA5-FD9BECC80630}', installed = 1, version = 5.00.7804.1000]LOG]!><time="13:56:37.777+420" date="08-18-2015" component="ccmsetup" context="" type="0" thread="5560" file="msiutil.cpp:1274">
    <![LOG[A SCCM client with version '5.00.7804.1000' is detected. It's greater than or equal to the minimum upgradable version '5.00.7705.0000' so no need to uninstall current client.]LOG]!><time="13:56:37.778+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="util.cpp:607">
    <![LOG[Installing version 5.00.8239.1000 of the client with product code {343D4507-997F-4553-9F86-2BB81F19A05E}]LOG]!><time="13:56:37.778+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="ccmsetup.cpp:8233">
    <![LOG[GetTargetPatchCode failed with 0x80070664 when getting patch code for 'D:\Program']LOG]!><time="13:56:37.778+420" date="08-18-2015" component="ccmsetup" context="" type="3" thread="5560" file="msiutil.cpp:1582">
    <![LOG[Patch 'D:\Program' isn't targeted for the current client.msi]LOG]!><time="13:56:37.779+420" date="08-18-2015" component="ccmsetup" context="" type="2" thread="5560" file="msiutil.cpp:1702">
    <![LOG[No features were excluded and will be excluded.]LOG]!><time="13:56:37.781+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="ccmsetup.cpp:7650">
    <![LOG[MSI PROPERTIES are   Files\Microsoft Configuration Manager\hotfix\KB2882125\Client\x64\configmgr2012ac-sp1-kb2882125-x64.msp" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMFIRSTCERT="1" SMSSITECODE="P01" CCMHTTPSSTATE="224" CCMCERTID="SMS;853721CA25A2211929B03FEDBFD589006A7FE3FD" CCMFORCECOLOCUPGRADE="true" INSTALL=ALL]LOG]!><time="13:56:37.781+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="ccmsetup.cpp:7608">
    <![LOG[Expanded MSI PROPERTIES are   Files\Microsoft Configuration Manager\hotfix\KB2882125\Client\x64\configmgr2012ac-sp1-kb2882125-x64.msp" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMFIRSTCERT="1" SMSSITECODE="P01" CCMHTTPSSTATE="224" CCMCERTID="SMS;853721CA25A2211929B03FEDBFD589006A7FE3FD" CCMFORCECOLOCUPGRADE="true" INSTALL=ALL]LOG]!><time="13:56:37.781+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="ccmsetup.cpp:8257">
    <![LOG[C:\Windows\ccmsetup\{72875A95-4007-4DAC-88D8-66366F9A5045}\client.msi is Microsoft trusted.]LOG]!><time="13:56:37.950+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="util.cpp:1574">
    <![LOG[Running installation package
      Package:     C:\Windows\ccmsetup\{72875A95-4007-4DAC-88D8-66366F9A5045}\client.msi
      Log:         C:\Windows\ccmsetup\Logs\client.msi.log
      Properties:    Files\Microsoft Configuration Manager\hotfix\KB2882125\Client\x64\configmgr2012ac-sp1-kb2882125-x64.msp" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMFIRSTCERT="1" SMSSITECODE="P01" CCMHTTPSSTATE="224" CCMCERTID="SMS;853721CA25A2211929B03FEDBFD589006A7FE3FD" CCMFORCECOLOCUPGRADE="true" INSTALL=ALL]LOG]!><time="13:56:37.950+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="msiutil.cpp:796">
    <![LOG[File C:\Windows\ccmsetup\{72875A95-4007-4DAC-88D8-66366F9A5045}\client.msi installation failed. Error text: ExitCode: 1639
    Action:
    ErrorMessages:
    ]LOG]!><time="13:56:38.048+420" date="08-18-2015" component="ccmsetup" context="" type="3" thread="5560" file="msiutil.cpp:877">
    <![LOG[Next retry in 120 minute(s)...]LOG]!><time="13:56:38.102+420" date="08-18-2015" component="ccmsetup" context="" type="0" thread="5560" file="ccmsetup.cpp:8999">

    Thanks
    Nick

    Tuesday, August 18, 2015 9:16 PM

All replies

  • This isn't a quoting issue. Windows Installer is attempting to install a patch for the SP1 client which isn't valid for the SP2 client.

    How are you performing the client upgrade?



    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, August 18, 2015 11:44 PM
  • Hi,

    This is the client upgrade on the SCCM server itself.  I'm actually not running anything. This process seems to be happening automatically. 

    But I still have the update groups and deployment groups that I setup for the SP1 CU3 update.  Should I remove those?  From looking at the path that is specified that is what is being pointed to.

    Nick

    Wednesday, August 19, 2015 12:08 AM
  • Hi,

    Please remove the deployment for SP1 CU3, then check if the problem still appears.


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 19, 2015 6:59 AM
  • So I think I'm understanding a little more what is going wrong. First I removed the deployments and restarted the machine and the log still shows the client setup is failing.  I found the following in my logs:

    <![LOG[Site version '5.00.8239.1000' is newer than the current client version '5.00.7804.1000'. Client should be upgraded along with the site role.]LOG]!><time="13:56:34.428+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="util.cpp:2938">
    <![LOG[Loaded command line: "D:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" "/runservice"  "/UpgradePackageVersion:4"  "PATCH=D:\Program Files\Microsoft Configuration Manager\hotfix\KB2882125\Client\x64\configmgr2012ac-sp1-kb2882125-x64.msp" "CCMHTTPPORT=80" "CCMHTTPSPORT=443" "CCMFIRSTCERT=1"  "/mp:http://SCCMServer.mydomain.com" SMSSITECODE="P01"]LOG]!><time="13:56:34.428+420" date="08-18-2015" component="ccmsetup" context="" type="1" thread="5560" file="ccmsetup.cpp:3916">

    First, where I'm curious where the "PATCH=D:\Program Files\Microsoft Configuration..." part is coming from? I've removed the deployment packages for the CU3 updates but seems like there is something else still adding the PATCH= thing.

    Second I looked in some other SCCM logs and I see that I have messages logged that the site role wasn't installed correctly:

    Error Milestone P01 8/18/2015 3:26:24 PM SCCMServer.mydomain.COM SMS_MP_CONTROL_MANAGER 1020 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. Site Component Manager will automatically retry the reinstallation in 60 minutes. To force Site Component Manager to immediately retry the reinstallation, stop and restart Site Component Manager using the Configuration Manager Service Manager.
    Error Detail P01 8/18/2015 3:26:24 PM SCCMServer.mydomain.COM SMS_MP_CONTROL_MANAGER 1083 Site Component Manager successfully used the SMS_SERVER_BOOTSTRAP_SCCMServer service to run the following program on site system "\\SCCMServer.mydomain.COM":     D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:SCCMServer.mydomain.COM    The program failed for the following reason:     Child process ""D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe" /install /siteserver:SCCMServer SMSMP 0" took too long to execute, and the process (PID = 5460) was orphaned.    Possible cause: Site Component Manager does not have sufficient access rights to administer the site system.  Solution: Verify that the Site System Installation accounts are properly configured to allow the site to administer the site system.    Site Component Manager cannot install component SMS_MP_CONTROL_MANAGER until the program runs successfully. If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.
    Information Milestone P01 8/18/2015 2:56:16 PM SCCMServer.mydomain.COM SMS_MP_CONTROL_MANAGER 1018 Site Component Manager is reinstalling this component on this site system.

    I've tried to manually run the rolesetup command from the log but it also just hangs.

    Thankfully I'm doing this on a test SCCM server and not my production server so I'm going to restore from a backup and run the upgrade process again but this time first remove the SP1 CU3 deployment packages.

    Could the client update failing cause the site role to fail to install during the upgrade process? 

    Thanks

    Nick

    Wednesday, August 19, 2015 6:42 PM