Unable to install Client after 1511 Update

[Hannes]

Hi there,

 

recently I've updated our SCCM Test environment to 1511 which all went fine. Afterward when installing the client on our Primary Site I get an error. On the Sitesystem Servers and the 2ndSite the client updated automatically.

 

part of the ccmsetup.log:

MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent. ccmsetup 10/12/2016 3:38:46 PM 3904 (0x0F40)

MSI: Action 15:38:46: SmsStopUIComponents. This custom action forces all open client UI components to stop and exit. ccmsetup 10/12/2016 3:38:46 PM 3904 (0x0F40)

MSI: Action 15:38:46: SmsStopUserComponents. This custom action forces all open client UI and SCNotification components to stop and exit. ccmsetup 10/12/2016 3:38:46 PM 3904 (0x0F40)

MSI: Action 15:38:46: CcmUnloadWmiProviders. Enumerates all providers and unloads them, verifies they are unloaded, and then reloads them. ccmsetup 10/12/2016 3:38:46 PM 3904 (0x0F40)

MSI: Action 15:39:16: SmsRemoveUIEvents. This custom action is no longer used. The custom action used to remove the COM+ event subscriber and publisher used for UI notifications. We no longer use COM+ events for UI notifications. ccmsetup 10/12/2016 3:39:16 PM 3904 (0x0F40)

MSI: Action 15:39:16: CcmUnregisterPerfCounters. Removes performance counters gathered in the CcmUnregisterPerfCountersInit action ccmsetup 10/12/2016 3:39:16 PM 3904 (0x0F40)

MSI: Action 15:39:16: CcmRemoveLanternDocuments. Removing documents from Microsoft Policy Platform that have been submitted by Configuration Manager authority. ccmsetup 10/12/2016 3:39:16 PM 3904 (0x0F40)

MSI: Action 15:39:26: CcmTypelibRollback. In the event of install failing, this event rolls back the type libraries to the state before install started. ccmsetup 10/12/2016 3:39:26 PM 3904 (0x0F40)

MSI: Action 15:39:26: RemoveRegistryValues. Removing system registry values ccmsetup 10/12/2016 3:39:26 PM 3904 (0x0F40)

MSI: Action 15:39:27: SmsDeinstallDesktopClient. This custom action uninstalls the desktop client with following steps-

1. Makes sure there are no desktop client installations in progress and prevents any new instance of intallation.

2. Checks the desktop client version and gets the installation direcotry.

3. Stops remote control and other desktop components.

4. Kills the following client processes - clisvc1.exe, pea32.exe, smsapm32.exe, smsmon32.exe and sms_reen.exe.

5. Saves information needed for migration and uninstalls the desktop components followed by clean up. ccmsetup 10/12/2016 3:39:27 PM 3904 (0x0F40)

MSI: Action 15:39:27: CreateFolders. Creating folders ccmsetup 10/12/2016 3:39:27 PM 3904 (0x0F40)

MSI: Action 15:39:27: CcmDetectFilesInUseRollback. Rolls back files moved by CcmDetectFilesInUse. ccmsetup 10/12/2016 3:39:27 PM 3904 (0x0F40)

MSI: Action 15:39:27: CcmDetectFilesInUse. Moves files that are in use so that they will be deleted upon the next reboot. ccmsetup 10/12/2016 3:39:27 PM 3904 (0x0F40)

MSI: Action 15:39:28: CcmDetectFilesInUseCommit. Commits action of CcmDetectFileInUse. After this we cannot rollback. ccmsetup 10/12/2016 3:39:28 PM 3904 (0x0F40)

MSI: Action 15:39:28: InstallFiles. Copying new files ccmsetup 10/12/2016 3:39:28 PM 3904 (0x0F40)

MSI: Action 15:39:30: CcmCreateEmbeddedClientState. Creates the client state file, which is needed for write filter handing. ccmsetup 10/12/2016 3:39:30 PM 3904 (0x0F40)

MSI: Action 15:39:30: CcmCreateEmbeddedClientStateRollback. Rolls back the action of creating the client state file. ccmsetup 10/12/2016 3:39:30 PM 3904 (0x0F40)

MSI: Action 15:39:30: RegisterExtensionInfo. Registering extension servers ccmsetup 10/12/2016 3:39:30 PM 3904 (0x0F40)

MSI: Action 15:39:30: WriteRegistryValues. Writing system registry values ccmsetup 10/12/2016 3:39:30 PM 3904 (0x0F40)

MSI: Action 15:39:32: WriteIniValues. Writing INI files values ccmsetup 10/12/2016 3:39:32 PM 3904 (0x0F40)

MSI: Action 15:39:32: RegisterTypeLibraries. Registering type libraries ccmsetup 10/12/2016 3:39:32 PM 3904 (0x0F40)

MSI: Action 15:39:32: SelfRegModules. Registering modules ccmsetup 10/12/2016 3:39:32 PM 3904 (0x0F40)

MSI: Action 15:39:35: RegisterProduct. Registering product ccmsetup 10/12/2016 3:39:35 PM 3904 (0x0F40)

MSI: Action 15:39:35: MsiPublishAssemblies. Publishing assembly information ccmsetup 10/12/2016 3:39:35 PM 3904 (0x0F40)

MSI: Action 15:39:35: PublishFeatures. Publishing Product Features ccmsetup 10/12/2016 3:39:35 PM 3904 (0x0F40)

MSI: Action 15:39:35: CcmCreateSqlCEDatabases. Create Sql CE databases that were queued by CcmCreateSqlCEDatabasesInit. ccmsetup 10/12/2016 3:39:35 PM 3904 (0x0F40)

MSI: Action 15:39:36: CcmCompileSqlCEScripts. Compiles Sql CE script files that were queued by CcmCompileSqlCEScriptsInit. ccmsetup 10/12/2016 3:39:36 PM 3904 (0x0F40)

MSI: Setup was unable to compile Sql CE script file P:\Program Files\SMS_CCM\StateMessageStore.sqlce.

The error code is 80004005. ccmsetup 10/12/2016 3:39:36 PM 3904 (0x0F40)

MSI: Action 15:39:36: Rollback. Rolling back action: ccmsetup 10/12/2016 3:39:36 PM 3904 (0x0F40)

File C:\Windows\ccmsetup\{F3F94F41-35CF-4195-B84F-EBA47435ADC9}\client.msi installation failed. Error text: ExitCode: 1603

Action: CcmCompileSqlCEScripts.

ErrorMessages:

Setup was unable to compile Sql CE script file P:\Program Files\SMS_CCM\StateMessageStore.sqlce.

The error code is 80004005.

ccmsetup 10/12/2016 3:39:47 PM 3904 (0x0F40)

Next retry in 120 minute(s)... ccmsetup 10/12/2016 3:39:47 PM 3904 (0x0F40)

client.msi.log:

MSI (s) (70:70) [15:39:47:144]: Product: Configuration Manager Client - Update 'CLP1031' could not be installed. Error code 1603. Additional information is available in the log file C:\Windows\ccmsetup\Logs\client.msi.log.

MSI (s) (70:70) [15:39:47:144]: Windows Installer installed an update. Product Name: Configuration Manager Client. Product Version: 5.00.8325.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: CLP1031. Installation success or error status: 1603.

MSI (s) (70:70) [15:39:47:145]: Note: 1: 1708

MSI (s) (70:70) [15:39:47:145]: Product: Configuration Manager Client -- Installation operation failed.

MSI (s) (70:70) [15:39:47:145]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.8325.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

MSI (s) (70:70) [15:39:47:301]: Closing MSIHANDLE (1) of type 790542 for thread 2928

MSI (s) (70:70) [15:39:47:301]: Attempting to delete file C:\Windows\Installer\bb6f7.msp

MSI (s) (70:70) [15:39:47:301]: Unable to delete the file. LastError = 32

MSI (s) (70:70) [15:39:47:309]: Deferring clean up of packages/files, if any exist

MSI (s) (70:70) [15:39:47:309]: Attempting to delete file C:\Windows\Installer\bb6f7.msp

MSI (s) (70:70) [15:39:47:310]: MainEngineThread is returning 1603

MSI (s) (70:60) [15:39:47:313]: RESTART MANAGER: Session closed.

MSI (s) (70:60) [15:39:47:313]: No System Restore sequence number for this installation.

=== Logging stopped: 10/12/2016 15:39:47 ===

MSI (s) (70:60) [15:39:47:322]: User policy value 'DisableRollback' is 0

MSI (s) (70:60) [15:39:47:322]: Machine policy value 'DisableRollback' is 0

MSI (s) (70:60) [15:39:47:322]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (70:60) [15:39:47:322]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (70:60) [15:39:47:322]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (70:60) [15:39:47:323]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1

MSI (s) (70:60) [15:39:47:323]: Destroying RemoteAPI object.

MSI (s) (70:64) [15:39:47:323]: Custom Action Manager thread ending.

MSI © (14:D0) [15:39:47:324]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1

MSI © (14:D0) [15:39:47:325]: MainEngineThread is returning 1603

=== Verbose logging stopped: 10/12/2016 15:39:47 ===

So far I tried:

• ccmsetup /uninstall
• ccmclean /client
• Install manually
• reinstall via the SCCM Console
• also I rebooted after the uninstall/clean

• ccmsetup /uninstall
• delete SMSCFG.ini
• re-install ccmsetup
• ​https://social.technet.microsoft.com/Forums/en-US/d3cb3b25-8195-47dd-8121-993681c21b5e/cm2012-client-install-fails-with-unable-to-compile-sql-ce-script-file?forum=configmanagerdeployment

• http://www.windowscapture.com/2016/02/install-sccm1511-client-error-warning.html

Any ideas how to get the client on the Server? If you need me to provide the whole logs or additional informations let me know.

Thanks in advance.

Hannes

[gus-bus]

Hi Hannes,

 

I too am having this exact same issue on our primary site server. I'm fairly new to my current organization but I have had experience with SCCM and this one is a new one. As you said, it certainly seems to be something in relation to 1511.

 

It gets to this point:

 

File C:\Windows\ccmsetup\{A468E717-9650-405E-B971-F5BE44093864}\client.msi installation failed. Error text: ExitCode: 1603
Action: CcmCompileSqlCEScripts.
ErrorMessages:
Setup was unable to compile Sql CE script file C:\Program Files\SMS_CCM\StateMessageStore.sqlce.
The error code is 80004005.

 

----------------------------------------

 

​Then you see the rollback:

 

MSI: Action 7:48:03: Rollback. Rolling back action:

 

​---------------------------------------

 

We are not seeing this issue with any other clients in our organization except for the primary site server at this time. If anyone has run across this or has ideas I would greatly appreciate the info.

 

Thanks

/Gus-Bus

[faabiiiooo]

Hi Hannes and Gus-Bus

I'm experiencing exactly the same issue. Did anyone of you find a solution until now? And also only on our Primary Site Server.

Thanks!

 

[nazimb]

Hello,

There is a known issue in 1511 where the client won't install during OSD.

You'll have to add a repair step, than restart the computer (see attached screenshot).

 

 

[pittfrog]

Forgive the dumb question, but how do I get to the tasks as captured in your screenshot?