locked
Client reinstall failing on upgraded clients RRS feed

  • Question

  • Hello,

    I have run into an issue with some of our clients since upgrading to SP1. The initial issue came to light recently during a pilot deployment (our first major one since upgarding to SP1). The problem first presented as clients failing to run application enforcement for applicable content. I could see policy applied, ApplicdationDiscovery.log and ApplictionIntentEval.log both showed appropriate activity, however ApplicationEnforceme.log would show no new activity and applicable content was not running/installing.

    One resolution I found so far was to remove and reinstall the client (simple, run ccmsetup.exe /uninstall and then follow it up with ccmsetup.exe). This has worked on a couple of systems that had become unresponsive in this manner.

    However, I've now come across two systems (out of a small number pilot, so part of my concern here is how widespread this may be) that I am unable to re-install the client for. Uninstall succeeded, but since then, I am receiving errors in ccmsetup.log and client.msi.log. The errors in ccmsetup.log are basically that client.msi is returning 1603 and no more detail than that, so I have omitted that log from the post. If it would be helpful to see I can add it. I think that I have included the appropriate part of client.msi.log (I searched for Return Value 3 and grabbed the content immeidately preceeding).

    Both of these systems were SCCM 2007 clients before an upgrade to 2012 (I was not present for this, and the administrator who was is no longer here, so details on that upgrade process are sparse) and then upgraded to SP1. Other than the issue I outlined initially I don't see evidence of any issues prior to this, however given the highlighted errors below I wonder if there is a conflict with old agent components? Both still had 2007 files in place (CCM and CCMSETUP). I have removed those files and folders on one system, with no change in install attempt results. Unfortunately I can't seem to find anything to point me to what might be causing the error that I'm getting in the logs below, so I'm hopeful I can get some help here. I appreciate anything you can provide! Thanks!

    MSI (s) (14!70) [11:06:29:643]: Creating MSIHANDLE (24945) of type 790531 for thread 6768

    MSI (s) (14!70) [11:06:29:643]: Closing MSIHANDLE (24945) of type 790531 for thread 6768

    MSI (s) (14!70) [11:06:29:643]: Creating MSIHANDLE (24946) of type 790531 for thread 6768

    [11:06:29] WARNING: Failed to delete setup in progress time-stamp with error 0x80070002

    MSI (s) (14!70) [11:06:29:643]: Closing MSIHANDLE (24946) of type 790531 for thread 6768

    MSI (s) (14:70) [11:06:29:643]: Closing MSIHANDLE (24944) of type 790536 for thread 2700

    MSI (s) (14:8C) [11:06:29:643]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)

    MSI (s) (14:8C) [11:06:29:643]: Error in rollback skipped. Return: 5

    MSI (s) (14:8C) [11:06:29:643]: Entering MsiProvideAssembly. AssemblyName: Microsoft.ConfigurationManager.AssetProvider.dll,Version="5.0.0.0",Culture="neutral",PublicKeyToken="31bf3856ad364e35", AppContext: , InstallMode: -4

    MSI (s) (14:8C) [11:06:29:643]: Pathbuf: 0, pcchPathBuf: 0

    MSI (s) (14:8C) [11:06:29:643]: MsiProvideAssembly is returning: 1607

    [11:06:29] The service 'ccmexec' is not installed

    MSI (s) (14:8C) [11:06:29:674]: Note: 1: 2318 2: 

    MSI (s) (14:8C) [11:06:29:674]: No System Restore sequence number for this installation.

    MSI (s) (14:8C) [11:06:29:674]: Unlocking Server

    MSI (s) (14:8C) [11:06:29:674]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.

    Action ended 11:06:29: INSTALL. Return value 3.

    Property(S): UpgradeCode = {252DA259-82CA-4177-B8D0-49C78937BA3E}

    Property(S): SourceDir = C:\Windows\ccmsetup\{1AF71F68-6089-4211-ADDC-06DF40606141}\

    Property(S): TARGETDIR = C:\Windows\CCM\

    Property(S): ALLUSERS = 1

    Property(S): ErrorDialog = ErrorDialog

    Friday, March 8, 2013 4:29 PM

All replies

  • I think it had a problem registering ccmexec.exe as a service earlier in the installation, is there residual client components on these affected machines?

    Also check the event log and see if anything was reported by service control manager or other issues noted there


    Rob Marshall | UK | My Blog | WMUG | File CM12 Feedback | CM12 Docs | CM12 Release Notes

    Saturday, March 9, 2013 6:37 PM
  • Thank you for the reply. Both systems did have CCM and CCMSETUP folders still in place from their 2007 installations. I removed those as part of troubleshooting on one, with no improvements or changes.

    I will continue to look, and also follow up with the event logs.

    Again, thank you!

    Eric

    Monday, March 11, 2013 1:39 PM
  • Are you running ccmsetup from the client folder or the clientupgrade folder?
    Monday, March 11, 2013 2:48 PM
  • I have been using the files from the client folder.

    Monday, March 11, 2013 2:59 PM
  • As Rob suggested there are issues earlier in the installation that might be more informative. Though the logs and errors aren't exactly the same, both seem to indicate an error in registering the 'Configuration Manager Idle Detection' Task. I thought this might be a scheduled task, and there is a Configuration Manager task still present on both systems, but its the Configuration Manager Health Evaluation task. I'm going to try removing that on one of these systems and see what that does, but I thought I'd post the logs from one of the systems in case anyone has any other ideas. Thanks again!

    INSTALL
    [7:17:32] Installation directory "C:\Windows\CCM\"\.
    [7:17:32] Calling InstallUtil on Microsoft.ConfigurationManager.WinRTProvider.dll|Microsoft.ConfigurationManager.AssetProvider.dll|.
    [7:17:32] InstallUtil commandline: C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe /ShowCallStack C:\Windows\CCM\Microsoft.ConfigurationManager.WinRTProvider.dll
    [7:17:35] WARNING: Cannot InstallUtil C:\Windows\CCM\Microsoft.ConfigurationManager.WinRTProvider.dll, return code -1
    [7:17:35] InstallUtil commandline: C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe /ShowCallStack C:\Windows\CCM\Microsoft.ConfigurationManager.AssetProvider.dll
    [7:17:36] Ngen context is C:\Windows\CCM\
    INSTALL
    SCClient.exe.config
    SCClient.data.dll
    SCClient.common.dll
    SCClient.exe
    SCClient.Pages.dll
    SCNotification.exe
    SCNotification.exe.config
    SCToastNotification.exe
    SCToastNotification.exe.config
    [7:17:36] Calling NGEN on necesary files.
    [7:17:36] Initiating compilation of NGEN QUEUE
    [7:17:39] (NGEN) C:\Windows\Microsoft.NET\Framework\v4.0.30319\NGen.exe install "C:\Windows\CCM\SCClient.exe.config" /queue:1
    [7:17:39] (NGEN) C:\Windows\Microsoft.NET\Framework\v4.0.30319\NGen.exe install "C:\Windows\CCM\SCClient.data.dll" /queue:1
    [7:17:39] (NGEN) C:\Windows\Microsoft.NET\Framework\v4.0.30319\NGen.exe install "C:\Windows\CCM\SCClient.common.dll" /queue:1
    [7:17:39] (NGEN) C:\Windows\Microsoft.NET\Framework\v4.0.30319\NGen.exe install "C:\Windows\CCM\SCClient.exe" /queue:1
    [7:17:39] (NGEN) C:\Windows\Microsoft.NET\Framework\v4.0.30319\NGen.exe install "C:\Windows\CCM\SCClient.Pages.dll" /queue:1
    [7:17:39] (NGEN) C:\Windows\Microsoft.NET\Framework\v4.0.30319\NGen.exe install "C:\Windows\CCM\SCNotification.exe" /queue:1
    [7:17:39] (NGEN) C:\Windows\Microsoft.NET\Framework\v4.0.30319\NGen.exe install "C:\Windows\CCM\SCNotification.exe.config" /queue:1
    [7:17:39] (NGEN) C:\Windows\Microsoft.NET\Framework\v4.0.30319\NGen.exe install "C:\Windows\CCM\SCToastNotification.exe" /queue:1
    [7:17:39] (NGEN) C:\Windows\Microsoft.NET\Framework\v4.0.30319\NGen.exe install "C:\Windows\CCM\SCToastNotification.exe.config" /queue:1
    [7:17:39] Initiating compilation of NGEN QUEUE
    [7:17:39] Automatic Delayed Start configuration is enabled for CCMEXEC
    [7:17:39] Registering windows task 'Configuration Manager Idle Detection'
    [7:17:39] Created Idle settings...
    [7:17:39] Created Custom Handler...
    [7:17:39] ERROR: RegisterTaskDefinition failed with error 0x800700b7
    CustomAction CcmRegisterWinTask returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    Action ended 7:17:39: InstallFinalize. Return value 3.
    [7:17:40] Removing windows task 'Configuration Manager Idle Detection'

    Wednesday, March 13, 2013 1:15 PM
  • I've just fixed RegisterTaskDefinition failed by manually wiping all existing Task Sheduler CCM entries in the registry.

    Seems some permissions needed for reinstall were missing/corrupted.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Configuration Manager

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks


    • Edited by i3laze_ Tuesday, May 16, 2017 10:45 AM
    Tuesday, May 16, 2017 10:39 AM