none
Configuration Manager 1602 "Installation failed"

    Question

  • I am trying to upgrade my 1511 environment to 1602. Prereq check succeeds, but the "State" column eventually moves to "Installation failed" and shows "Failed to install" under Site Servicing Status.

    There don't appear to be an real errors in ConfigMgrSetup.log, shown below. I don't know where to go from here, and don't see any documentation on troubleshooting this. I have the entire log available here as well as the ConfigMgrPrereq.log.

    CMUPreReqCheckListener::ReportPrereqStatus : [INFO] Saved prereq message[CC872765-21DF-47F7-BF05-47040268B927][4][1] into Database.  $$<Configuration Manager Setup><03-28-2016 16:51:27.660+300><thread=6608 (0x19D0)>
    INFO: Checking Windows Cluster.  $$<Configuration Manager Setup><03-28-2016 16:51:27.668+300><thread=6608 (0x19D0)>
    CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e~  $$<Configuration Manager Setup><03-28-2016 16:51:27.671+300><thread=6608 (0x19D0)>
    INFO: WMI namespace root\MSCluster not exists on SiteServer.domain.com.  $$<Configuration Manager Setup><03-28-2016 16:51:27.672+300><thread=6608 (0x19D0)>
    CMUPreReqCheckListener::ReportPrereqStatus : [INFO] Saved prereq message[434BC39E-3403-4E5C-BED4-4C7AB6483D1A][4][1] into Database.  $$<Configuration Manager Setup><03-28-2016 16:51:27.683+300><thread=6608 (0x19D0)>
    Found the latest 'Windows Assessment and Deployment Kit'. 'Windows 10 ADK' is installed.  $$<Configuration Manager Setup><03-28-2016 16:51:27.686+300><thread=6608 (0x19D0)>
    INFO: 'Windows Deployment Tools' component of ADK is installed.  $$<Configuration Manager Setup><03-28-2016 16:51:27.687+300><thread=6608 (0x19D0)>
    CMUPreReqCheckListener::ReportPrereqStatus : [INFO] Saved prereq message[BD521D01-9101-4C4C-AE0C-3E84BFAA78CD][4][1] into Database.  $$<Configuration Manager Setup><03-28-2016 16:51:27.698+300><thread=6608 (0x19D0)>
    Found the latest 'Windows Assessment and Deployment Kit'. 'Windows 10 ADK' is installed.  $$<Configuration Manager Setup><03-28-2016 16:51:27.699+300><thread=6608 (0x19D0)>
    INFO: 'Windows PE' component of ADK is installed.  $$<Configuration Manager Setup><03-28-2016 16:51:27.700+300><thread=6608 (0x19D0)>
    CMUPreReqCheckListener::ReportPrereqStatus : [INFO] Saved prereq message[7A8F33D3-D255-4875-AF48-40F38396131C][4][1] into Database.  $$<Configuration Manager Setup><03-28-2016 16:51:27.711+300><thread=6608 (0x19D0)>
    CMUPreReqCheckListener::ReportPrereqStatus : [INFO] Saved prereq message[733E2FC6-0565-4311-BB6A-CB1901B79073][4][1] into Database.  $$<Configuration Manager Setup><03-28-2016 16:51:27.722+300><thread=6608 (0x19D0)>
    ~Prereq check passed, site installation will continue.  $$<Configuration Manager Setup><03-28-2016 16:51:27.727+300><thread=6608 (0x19D0)>
    INFO: SiteServer.domain.com is a 64 bit operating system.  $$<Configuration Manager Setup><03-28-2016 16:51:27.732+300><thread=6608 (0x19D0)>







    • Edited by ptilsen Tuesday, March 29, 2016 5:54 PM
    Tuesday, March 29, 2016 3:45 PM

Answers

  • I ended up solving this. There were two synonyms in the SQL database associated with a custom hardware inventory class I'd created. Deleting the synonyms allowed the instalation to progress, but they were recreated and the same error appeared after exec dbo.spExtRenewInvGroupExtractViews was executed a second time by the installation. I used a SQL script that looped concurrently with the upgrade to re-delete these synonyms. I also deleted the hardware inventory class after removing collection queries referencing it following successful completion of the 1602 upgrade.
    • Marked as answer by ptilsen Wednesday, April 06, 2016 4:04 PM
    Wednesday, April 06, 2016 4:04 PM

All replies

  • I tried installing it interactively using splash.hta in the download location. It still failed, but there is quite a bit more in the setup log now, though I'm still not sure next steps.

    ~===================== << Starting Configuration Manager 2012 Setup >> ===================== Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: ConfigMgr2012 Setup was started by DOMAIN\MyAccount. Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Command line specified was: "E:\Program Files\Microsoft Configuration Manager\EasySetupPayload\037cd17e-4d7b-40e1-802b-14bb682364c7\SMSSETUP\BIN\X64\SetupWpf.exe" Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    FQDN for server SiteServer12 is SiteServer12.DOMAIN.com Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Target computer is a 64 bit operating system. Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Checking for existing setup information. Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Setting setup type to  1. Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Checking for existing SQL information. Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: 'SiteServer12.DOMAIN.com' is a valid FQDN. Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Verifying the registry entry for Asset Intelligence installation Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Found registry key for installation of Asset Intelligence full version Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 8325 Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Phase is 1C7 Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    WARNING: Failed to initialize COM to get SDK Providers. It might already be initialized. return code: 80010106. Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: SDK Provider is on SiteServer12.DOMAIN.com. Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Setting the default CSV folder path Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Language: Mobile Device (INTL), LangPack: 0. Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Configuration Manager Build Number = 8325 Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Configuration Manager Version = 5.0 Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Configuration Manager Minimum Build Number = 800 Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Verifying Configuration Manager Active Directory Schema Extensions. Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Found DS Root:CN=Schema,CN=Configuration,DC=DOMAIN,DC=com Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Verifying Configuration Manager Active Directory Schema Extensions. Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Found DS Root:CN=Schema,CN=Configuration,DC=DOMAIN,DC=com Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    Setup Command Line is "E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\EASYSETUPPAYLOAD\037CD17E-4D7B-40E1-802B-14BB682364C7\SMSSETUP\BIN\X64\SETUPWPF.EXE" Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    Setup Type is 1 Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: SQL Server Native Client: SQLNCLI11 version:<11.2.5613.0> Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Installing msxml60 Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: Executing Command <msiexec.exe /i "H:\Temp\Sccm1602\msxml6_x64.msi" /quiet /norestart>. Configuration Manager Setup 3/29/2016 11:42:52 AM 21684 (0x54B4)
    INFO: H:\Temp\Sccm1602\msxml6_x64.msi installation process returned 0. Configuration Manager Setup 3/29/2016 11:42:53 AM 21684 (0x54B4)
    INFO: Installing SQL Common Language Runtime types Configuration Manager Setup 3/29/2016 11:42:53 AM 21684 (0x54B4)
    INFO: Executing Command <msiexec.exe /i "H:\Temp\Sccm1602\SQLSysClrTypes.msi" /quiet /norestart>. Configuration Manager Setup 3/29/2016 11:42:53 AM 21684 (0x54B4)
    INFO: H:\Temp\Sccm1602\SQLSysClrTypes.msi installation process returned 0. Configuration Manager Setup 3/29/2016 11:42:54 AM 21684 (0x54B4)
    INFO: Installing SQL Server Shared Management Objects Configuration Manager Setup 3/29/2016 11:42:54 AM 21684 (0x54B4)
    INFO: Executing Command <msiexec.exe /i "H:\Temp\Sccm1602\SharedManagementObjects.msi" /quiet /norestart>. Configuration Manager Setup 3/29/2016 11:42:54 AM 21684 (0x54B4)
    INFO: H:\Temp\Sccm1602\SharedManagementObjects.msi installation process returned 0. Configuration Manager Setup 3/29/2016 11:42:57 AM 21684 (0x54B4)
    Removed SQL alias SiteServer12.DOMAIN.com successfully. Configuration Manager Setup 3/29/2016 11:42:57 AM 21684 (0x54B4)
    INFO: Registered type SiteServer12.DOMAIN.COM MASTER for SiteServer12.DOMAIN.com master Configuration Manager Setup 3/29/2016 11:42:57 AM 21684 (0x54B4)
    INFO: Registered type SMS Master for SiteServer12.DOMAIN.com master Configuration Manager Setup 3/29/2016 11:42:57 AM 21684 (0x54B4)
    INFO: Registered type SiteServer12.DOMAIN.COM CM_ABC for SiteServer12.DOMAIN.com CM_ABC Configuration Manager Setup 3/29/2016 11:42:57 AM 21684 (0x54B4)
    INFO: Registered type SMS ACCESS for SiteServer12.DOMAIN.com CM_ABC Configuration Manager Setup 3/29/2016 11:42:57 AM 21684 (0x54B4)
    ERROR: Cannot install from programs and features. Configuration Manager Setup 3/29/2016 11:42:57 AM 21684 (0x54B4)
    Tuesday, March 29, 2016 4:54 PM
  • When doing the in-console upgrade, the ConfigMgrSetup log still lacks anything useful, but the CMUpdate log file gets the error message bolded at the same time the console shows the installation failed:

    INFO: Installing Site Component Manager...  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:55.333+300><thread=1536 (0x600)>
    INFO: Installing Site Component Manager under acct <NT AUTHORITY\SYSTEM> path <E:\Program Files\Microsoft Configuration Manager\bin\x64\sitecomp.exe>~  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:55.339+300><thread=1536 (0x600)>
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Unsecure  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:55.402+300><thread=1536 (0x600)>
    INFO: Running Post Auto Upgrade script.  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:55.403+300><thread=1536 (0x600)>
    SQL MESSAGE:  - Running ConfigMgr-022016-RemovedOldQFE  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:55.448+300><thread=1536 (0x600)>
    SQL MESSAGE:  - Purging duplicate ClientDeploymentState records...  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:55.936+300><thread=1536 (0x600)>
    INFO: Starting Site Component Manager...  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:55.942+300><thread=1536 (0x600)>
    INFO: Started Site Component Manager service  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:58.033+300><thread=1536 (0x600)>
    INFO: Site Component Manager installation completed.  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:58.034+300><thread=1536 (0x600)>
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:58.037+300><thread=1536 (0x600)>
    Turned on activation for service broker queue  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:58.142+300><thread=1536 (0x600)>
    Failed to apply update changes 0x87d20b15  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:58.142+300><thread=1536 (0x600)>
    Waiting for changes to the "E:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...  $$<CONFIGURATION_MANAGER_UPDATE><03-29-2016 12:29:58.145+300><thread=1536 (0x600)>

    • Edited by ptilsen Tuesday, March 29, 2016 6:25 PM
    Tuesday, March 29, 2016 5:56 PM
  • You need to go further back in your CMUpdate.log and see what the actual failure was.  If you are able to then post the CMUpdate.log somewhere so we can take a look.

    Cheers Paul | http://sccmentor.wordpress.com

    Tuesday, March 29, 2016 9:55 PM
  • Paul,

    I've got the entire CMUpdate.log linked in the above post.

    Edit: The actual failure seems to be here:

    SQL MESSAGE: spExtRenewInvGroupExtractViews - Creating inventory extraction views. CONFIGURATION_MANAGER_UPDATE 3/29/2016 12:29:25 PM 1536 (0x0600)
    *** exec dbo.spExtRenewInvGroupExtractViews CONFIGURATION_MANAGER_UPDATE 3/29/2016 12:29:28 PM 1536 (0x0600)
    *** [42S01][2714][Microsoft][SQL Server Native Client 11.0][SQL Server]There is already an object named 'v_GS_NET_Framework_4.x0' in the database. CONFIGURATION_MANAGER_UPDATE 3/29/2016 12:29:28 PM 1536 (0x0600)
    INFO: Executing SQL Server command: <exec dbo.spExtRenewInvGroupExtractViews> CONFIGURATION_MANAGER_UPDATE 3/29/2016 12:29:28 PM 1536 (0x0600)
    ERROR: Failed to execute SQL Server command, error <> CONFIGURATION_MANAGER_UPDATE 3/29/2016 12:29:28 PM 1536 (0x0600)
    ERROR: Failed to create extraction views for system discovery data. CONFIGURATION_MANAGER_UPDATE 3/29/2016 12:29:28 PM 1536 (0x0600)
    Failed to update database. CONFIGURATION_MANAGER_UPDATE 3/29/2016 12:29:28 PM 1536 (0x0600)


    • Edited by ptilsen Wednesday, March 30, 2016 5:41 PM
    Wednesday, March 30, 2016 3:52 PM
  • I ended up solving this. There were two synonyms in the SQL database associated with a custom hardware inventory class I'd created. Deleting the synonyms allowed the instalation to progress, but they were recreated and the same error appeared after exec dbo.spExtRenewInvGroupExtractViews was executed a second time by the installation. I used a SQL script that looped concurrently with the upgrade to re-delete these synonyms. I also deleted the hardware inventory class after removing collection queries referencing it following successful completion of the 1602 upgrade.
    • Marked as answer by ptilsen Wednesday, April 06, 2016 4:04 PM
    Wednesday, April 06, 2016 4:04 PM
  • I have a customer who is experiencing a very similar issue, would you be able to share some more information and/or the script itself?

    Friday, April 29, 2016 6:42 PM
  • Sure. Are they experiencing the exact SQL error bolded in my second to last post?
    Wednesday, May 04, 2016 3:08 PM
  • I am having the same issue:

    *** [42S01][2714][Microsoft][SQL Server Native Client 11.0][SQL Server]There is already an object named 'v_GS_PRINT_JOB' in the database. : v_GS_PRINT_JOB CONFIGURATION_MANAGER_UPDATE 1/06/2016 10:43:53 a.m. 1224 (0x04C8)
    INFO: Executing SQL Server command: <exec dbo.spExtRenewInvGroupExtractViews> CONFIGURATION_MANAGER_UPDATE 1/06/2016 10:43:53 a.m. 1224 (0x04C8)
    ERROR: Failed to execute SQL Server command, error <> CONFIGURATION_MANAGER_UPDATE 1/06/2016 10:43:53 a.m. 1224 (0x04C8)
    ERROR: Failed to create extraction views for system discovery data. CONFIGURATION_MANAGER_UPDATE 1/06/2016 10:43:53 a.m. 1224 (0x04C8)
    Failed to update database. CONFIGURATION_MANAGER_UPDATE 1/06/2016 10:43:53 a.m. 1224 (0x04C8)
    Successfully reverted SQL function fnCurrentSiteVersion. CONFIGURATION_MANAGER_UPDATE 1/06/2016 10:43:53 a.m. 1224 (0x04C8)

    But now after rebooting the server we are unable to image, "No Task sequence available for this computer", and I am seeing critical errors in the Windows Application log. It looks like it has not rolled back the failed update correctly:

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

    Missing management class description for class 'SMS_PolicyProperty'\r\nSystem.Collections.Generic.KeyNotFoundException\r\nThe given key was not present in the dictionary.\r\n   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
       at Microsoft.ConfigurationManagement.AdminConsole.FrameworkInitializer.ReadSecurityInformationFromXml.Initializer(QueryProcessorBase queryProcessor, ConnectionManagerBase connectionManager, SmsNamedValuesDictionary namedValues)\r\n

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

    Missing management class description for class 'SMS_MDMAppleVppToken'\r\nSystem.Collections.Generic.KeyNotFoundException\r\nThe given key was not present in the dictionary.\r\n at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at Microsoft.ConfigurationManagement.AdminConsole.FrameworkInitializer.ReadSecurityInformationFromXml.Initializer(QueryProcessorBase queryProcessor, ConnectionManagerBase connectionManager, SmsNamedValuesDictionary namedValues)\r\n

    Can you please provide some more information about what synonyms you deleted and the script you ran during the update?

    Thanks in advance.

    Wednesday, June 01, 2016 5:05 AM
  • Same problem here... 

    upgrade to 1602 failed with :

    INFO: Site Component Manager installation completed. CONFIGURATION_MANAGER_UPDATE 18.06.2016 14:12:06 1496 (0x05D8)

    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure CONFIGURATION_MANAGER_UPDATE 18.06.2016 14:12:06 1496 (0x05D8)

    Turned on activation for service broker queue CONFIGURATION_MANAGER_UPDATE 18.06.2016 14:12:07 1496 (0x05D8)

    Failed to apply update changes 0x87d20b15 CONFIGURATION_MANAGER_UPDATE 18.06.2016 14:12:07 1496 (0x05D8)

    Some advice would be great..

    Thanks a lot

    Sebastien

    Monday, June 20, 2016 6:41 AM
  • in my case... posting just the final error code is completly useless...

    Real and understandable error is a little bit earlier in cmupdate.log : 

    *** [23000][1505][Microsoft][SQL Server Native Client 11.0][SQL Server]The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.ClientPushMachine_G' and the index name 'ClientPushMachine_G_AK'. The duplicate key value is (-2).

    Resolution is in progress with Robert...

    I post more info later..

    Thanks 

    Sebastien

    Monday, June 20, 2016 11:11 AM
  • Thanks Sebastien.

    When hitting an error in Configuration Manager Update installation. The detailed error will be in cmupdate.log/lo_ (We also recommend CM Admins enable archive logging on the site server to help with troubleshooting).

    • For server archive logging

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing\ArchiveEnabled = 1

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing\ArchivePath = <UNC or local path>

    To read the cmupdate.log/lo_

    Failed to apply update changes 0x87d20b15 just indicates there was an error, the details are above.

    --- template of the cmupdate.log/lo_

    • Validation of the files from content library (for security measures to make sure the files are not tempered with)
    • apply changes... (if there is failure, there will be details here as show by Sebastien)
    • in case of failure, it will revert a bunch of SQL objects, and then restart CM services
    • in case of failure, CM Admins/support figure out the root cause, retry from CM Admin console
    • no failure, this site server is done with update. 

    What may cause the error in cmupdate.log

    • file validation failure. (the hash/version/signature of the file did not pass the validation.)

    Make sure anti-malware/virus software have exclusion for CM directories; make sure do not temper with the files manually)

    • Sql failure (some odd data in Customer database may prevent certain SQL constrain/objects to be created)

    clean up the bad data in the database

    • file copy failure. ConfigMgr will try to copy files even when it is in use. There might be certain files get into a state where even the special logic we have can not handle it. i.e. SYSTEM lost permission to the file; or the file is corrupted; or the disk has bad section.

    All the above failures can be fixed; and then CM Admins can retry the installation through CM Console.

    Thanks


    --Richard This posting is provided “AS IS” with no warranties and confers no rights.

    Monday, July 25, 2016 5:50 PM
  • I have a similar error with the (offline) Upgrade from 1602 to 1606.

    The only errors I've had in the CMUpdate.log

    Failed to apply update changes 0x80004005
    CONFIGURATION_MANAGER_UPDATE 27-7-2016 09:17:56 11988 (0x2ED4)
    ERROR: Failed to process configuration manager update.
    CONFIGURATION_MANAGER_UPDATE 27-7-2016 09:17:56 11988 (0x2ED4)

    I still need to do some more investigation but wanted to add my (similar) experience with the update. Will keep you posted.

    Update: Giving it another try gave me the following end result

    INFO: Running Post Auto Upgrade script.
    INFO: Starting Site Component Manager...
    INFO: Started Site Component Manager service
    INFO: Site Component Manager installation completed.
    INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure
    Turned on activation for service broker queue
    Failed to apply update changes 0x80004005
    Waiting for changes to the "D:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 600 seconds...


    • Edited by Ariendg Wednesday, July 27, 2016 2:01 PM
    Wednesday, July 27, 2016 8:48 AM
  • I have the exact same issue as you, same logs, same scenario 1602 - 1606. I do not know what to try. The only errors i have are file validation/hash type errors which usually mean nothing.
    Sunday, July 31, 2016 11:27 PM
  • I also faced the same issue from 1602-1606, few fie validation errors/hash errors. has one tried this.

    Few Errors:

    GetFileVersionInfoSizeW failed for file (\\?\D:\Program Files\Microsoft Configuration Manager\CMUStaging\705820EF-6982-4417-8E54-307454C9A17A\SMSSetup\OSD\bin\i386\winpe.jpg)(0X80070714) CONFIGURATION_MANAGER_UPDATE 8/1/2016 10:25:09 AM 6364 (0x18DC)

    GetFileVersionInfoSizeW failed for file (\\?\d:\program files\microsoft configuration manager\osd\bin\i386\winpe.jpg)(0X80070714) CONFIGURATION_MANAGER_UPDATE 8/1/2016 10:25:09 AM 6364 (0x18DC)

    ERROR: File hash check failed for D:\Program Files\Microsoft Configuration Manager\CMUStaging\705820EF-6982-4417-8E54-307454C9A17A\SMSSetup\Client\x64\msrdcoob_amd64.exe CONFIGURATION_MANAGER_UPDATE 8/1/2016 10:25:09 AM 6364 (0x18DC)

    Failed to validate version for file D:\Program Files\Microsoft Configuration Manager\CMUStaging\705820EF-6982-4417-8E54-307454C9A17A\redist\msrdcoob_amd64.exe (d:\program files\microsoft configuration manager\cmuclient\x64\msrdcoob_amd64.exe) CONFIGURATION_MANAGER_UPDATE 8/1/2016 10:25:09 AM 6364 (0x18DC)

    Monday, August 01, 2016 4:39 PM
  • Yes, those are the only errors i see in my log. Errors of that sort that is.
    Monday, August 01, 2016 4:44 PM
  • I gave the Update from 1602 to 1606 another try and it's installed now. Yay!

    When you've done the offline download try to use the latest version of the ServiceConnectionTool you can find. Some details can be found in my addition in this post.


    • Edited by Ariendg Wednesday, August 10, 2016 3:18 PM
    Wednesday, August 10, 2016 3:12 PM
  • I am having the same issue:

    *** [42S01][2714][Microsoft][SQL Server Native Client 11.0][SQL Server]There is already an object named 'v_GS_PRINT_JOB' in the database. : v_GS_PRINT_JOB CONFIGURATION_MANAGER_UPDATE 1/06/2016 10:43:53 a.m. 1224 (0x04C8)
    INFO: Executing SQL Server command: <exec dbo.spExtRenewInvGroupExtractViews> CONFIGURATION_MANAGER_UPDATE 1/06/2016 10:43:53 a.m. 1224 (0x04C8)
    ERROR: Failed to execute SQL Server command, error <> CONFIGURATION_MANAGER_UPDATE 1/06/2016 10:43:53 a.m. 1224 (0x04C8)
    ERROR: Failed to create extraction views for system discovery data. CONFIGURATION_MANAGER_UPDATE 1/06/2016 10:43:53 a.m. 1224 (0x04C8)
    Failed to update database. CONFIGURATION_MANAGER_UPDATE 1/06/2016 10:43:53 a.m. 1224 (0x04C8)
    Successfully reverted SQL function fnCurrentSiteVersion. CONFIGURATION_MANAGER_UPDATE 1/06/2016 10:43:53 a.m. 1224 (0x04C8)

    But now after rebooting the server we are unable to image, "No Task sequence available for this computer", and I am seeing critical errors in the Windows Application log. It looks like it has not rolled back the failed update correctly:

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

    Missing management class description for class 'SMS_PolicyProperty'\r\nSystem.Collections.Generic.KeyNotFoundException\r\nThe given key was not present in the dictionary.\r\n   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
       at Microsoft.ConfigurationManagement.AdminConsole.FrameworkInitializer.ReadSecurityInformationFromXml.Initializer(QueryProcessorBase queryProcessor, ConnectionManagerBase connectionManager, SmsNamedValuesDictionary namedValues)\r\n

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

    Missing management class description for class 'SMS_MDMAppleVppToken'\r\nSystem.Collections.Generic.KeyNotFoundException\r\nThe given key was not present in the dictionary.\r\n at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at Microsoft.ConfigurationManagement.AdminConsole.FrameworkInitializer.ReadSecurityInformationFromXml.Initializer(QueryProcessorBase queryProcessor, ConnectionManagerBase connectionManager, SmsNamedValuesDictionary namedValues)\r\n

    Can you please provide some more information about what synonyms you deleted and the script you ran during the update?

    Thanks in advance.

    Stuydnz, you will have to fix the database problem first, and then "retry installation" for the ConfigMgr Update.
    The particular database upgrade failure could be result of how the hardware inventory schemas are extended. One possible workaround for your env is to drop the conflicting view v_GS_Print_JOB and then go back to Admin Console to "retry installation"

    Thanks


    --Richard This posting is provided “AS IS” with no warranties and confers no rights.

    Wednesday, August 10, 2016 6:58 PM
  • We are currently facing the same problem on a 1606 Primary Site going to 1610. The upgrade of the CAS in the hierarchy completed without any problems and then a day later, the Primary Site fails with duplicate entries in the dbo.SC_SysResUse_Property table, thus not being able to create unique index statements, same as Sebastien a couple of posts above.

    I know that altering tables may only be done by MS or by us when told to it by MS, otherwise we loose supportability. Can anyone provide a query however, with which we might be able to find duplicate key entries and perform a check on all tables?

    Best Regards,

    Fred

     

    Wednesday, March 08, 2017 10:23 AM
  • Just wanted to add that I also experienced this error. In my situation the database was locked. A reboot before install cleared that issue and the install was a success :)
    Thursday, August 24, 2017 8:13 AM