locked
wsus sync fails, unknown SQL error RRS feed

  • Question

  • I get the bellow errors when trying to sync WSUS via SCCM 2012 for the first time.  My SCCM database is using the SA account on a remote SQL server while the WSUS database is local.  The 'All Software Updates' node in the Software library is empty.  This is a new install; have already tried removing and reinstalling the SUP as well as WSUS.   Exact same error as http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/797176fc-7bc5-4817-8892-292a6ca978a3 but my DB is using the SA account (though it was moved and detached/reatached to a new drive).

    sync: SMS synchronizing updates, processed 0 out of 108480 items (0%)  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:09.837+360><thread=4564 (0x11D4)>
    *** declare @rc int, @errxml xml; EXEC @rc=sp_SetupCI 16777312, 0, @errxml out; select @rc, @errxml  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:13.084+360><thread=4564 (0x11D4)>
    *** *** Unknown SQL Error!  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:13.087+360><thread=4564 (0x11D4)>
    Failed to sync update 1847ae6d-8360-4e5a-9d15-da82b24deffd. Error: Failed to save update 1fd4eb6d-808f-4693-bf9a-425fdc345c9a. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:13.199+360><thread=4564 (0x11D4)>
    *** declare @rc int, @errxml xml; EXEC @rc=sp_SetupCI 16777313, 0, @errxml out; select @rc, @errxml  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:13.459+360><thread=4564 (0x11D4)>
    *** *** Unknown SQL Error!  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:13.459+360><thread=4564 (0x11D4)>
    Failed to sync update 15441c35-cd5f-4ea9-b067-7f50c7649e4f. Error: Failed to save update b9afe9e1-5b8d-44cf-b362-0c7dd84c955c. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:13.463+360><thread=4564 (0x11D4)>
    *** declare @rc int, @errxml xml; EXEC @rc=sp_SetupCI 16777314, 0, @errxml out; select @rc, @errxml  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:13.729+360><thread=4564 (0x11D4)>
    *** *** Unknown SQL Error!  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:13.729+360><thread=4564 (0x11D4)>
    Failed to sync update 5ccb9b39-9aae-44c7-abd0-485dec8dd824. Error: Failed to save update 93ae87a4-71fb-4623-9622-a83176f583df. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:13.733+360><thread=4564 (0x11D4)>
    *** declare @rc int, @errxml xml; EXEC @rc=sp_SetupCI 16777315, 0, @errxml out; select @rc, @errxml  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:13.968+360><thread=4564 (0x11D4)>
    *** *** Unknown SQL Error!  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:13.968+360><thread=4564 (0x11D4)>
    Failed to sync update 682aa9e2-fef6-441a-a9ed-d320bdefd8ca. Error: Failed to save update 9694f3af-c1ce-49aa-806e-bf146b0d3fd3. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:13.971+360><thread=4564 (0x11D4)>
    *** declare @rc int, @errxml xml; EXEC @rc=sp_SetupCI 16777316, 0, @errxml out; select @rc, @errxml  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:14.201+360><thread=4564 (0x11D4)>
    *** *** Unknown SQL Error!  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:14.201+360><thread=4564 (0x11D4)>
    Failed to sync update 417801f3-4d06-42a6-91c7-75cca218f392. Error: Failed to save update 85db15b6-dfd1-4308-a13e-e299274e22ea. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:14.205+360><thread=4564 (0x11D4)>
    Too many consecutive failures. Aborting sync.  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:14.205+360><thread=4564 (0x11D4)>
    sync: SMS synchronizing updates, processed 4 out of 4 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:14.205+360><thread=4564 (0x11D4)>
    Sync failures summary:  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:14.206+360><thread=4564 (0x11D4)>
    Failed to sync update 1847ae6d-8360-4e5a-9d15-da82b24deffd. Error: Failed to save update 1fd4eb6d-808f-4693-bf9a-425fdc345c9a. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:14.206+360><thread=4564 (0x11D4)>
    Failed to sync update 5ccb9b39-9aae-44c7-abd0-485dec8dd824. Error: Failed to save update 93ae87a4-71fb-4623-9622-a83176f583df. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:14.206+360><thread=4564 (0x11D4)>
    Failed to sync update 682aa9e2-fef6-441a-a9ed-d320bdefd8ca. Error: Failed to save update 9694f3af-c1ce-49aa-806e-bf146b0d3fd3. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:14.206+360><thread=4564 (0x11D4)>
    Failed to sync update 417801f3-4d06-42a6-91c7-75cca218f392. Error: Failed to save update 85db15b6-dfd1-4308-a13e-e299274e22ea. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:14.207+360><thread=4564 (0x11D4)>
    Failed to sync update 15441c35-cd5f-4ea9-b067-7f50c7649e4f. Error: Failed to save update b9afe9e1-5b8d-44cf-b362-0c7dd84c955c. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate  $$<SMS_WSUS_SYNC_MANAGER><05-01-2012 18:19:14.207+360><thread=4564 (0x11D4)>
    Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates 

    Thursday, May 3, 2012 2:59 PM

Answers

  • Make sure you reconfigure the SQL TRUSTWORTHY property back to ON after you move and reattach your SQL databases. After I did this, I these unknown SQL errors disappeared. 

    http://support.microsoft.com/kb/2709082

    • Proposed as answer by Frode Henriksen Thursday, May 31, 2012 8:38 AM
    • Marked as answer by sgrigg Friday, June 1, 2012 10:49 PM
    Thursday, May 17, 2012 11:08 PM
  • Wasn't able to find an easy fix.  Reinstalled with new database which fixed the problem.
    • Marked as answer by sgrigg Friday, May 4, 2012 2:30 PM
    Friday, May 4, 2012 2:30 PM

All replies

  • Hi,

    It looks like your config is not well. In effect, note that ConfigMgr supports only "SQL Server Windows Authentication" and uses the site server computer account [that should be in the local admin group on the SQL box] to access the site DB.  Also the WSUS console should be installed on the site server box and WSUS should not be configured manually, let's SUP doing this.


    Bechir Gharbi | My blog: @myITforum.com | Twitter: @Bechir_Gharbi | Linkedin: Bechir Gharbi | Time zone: GMT + 1



    • Edited by Bechir Gharbi Thursday, May 3, 2012 5:03 PM
    • Marked as answer by sgrigg Friday, May 4, 2012 2:29 PM
    • Unmarked as answer by sgrigg Friday, May 4, 2012 2:29 PM
    Thursday, May 3, 2012 5:00 PM
  • Wasn't able to find an easy fix.  Reinstalled with new database which fixed the problem.
    • Marked as answer by sgrigg Friday, May 4, 2012 2:30 PM
    Friday, May 4, 2012 2:30 PM
  • Make sure you reconfigure the SQL TRUSTWORTHY property back to ON after you move and reattach your SQL databases. After I did this, I these unknown SQL errors disappeared. 

    http://support.microsoft.com/kb/2709082

    • Proposed as answer by Frode Henriksen Thursday, May 31, 2012 8:38 AM
    • Marked as answer by sgrigg Friday, June 1, 2012 10:49 PM
    Thursday, May 17, 2012 11:08 PM
  • Make sure you reconfigure the SQL TRUSTWORTHY property back to ON after you move and reattach your SQL databases. After I did this, I these unknown SQL errors disappeared. 

    http://support.microsoft.com/kb/2709082

    This fixed it for me. It was essential to change the db owner to SA for it to work.

    Thanks a bunch!


    - Frode Henriksen

    Thursday, May 31, 2012 8:38 AM
  • This did not work for me either looks like I am going to have to preform a rip and replace as well.

    lipanitech | http://www.lipanitechnologies.com | A+,Network+,Linux+,Security+,MCTS,HP Pro

    Friday, June 8, 2012 3:28 PM
  • These key violations are due to CI documents not being properly cleaned-up in some scenarios.

    Run this on site database Query in SQL Server Management Studio:

    delete from CI_DocumentStore d where Document_ID not in (select Document_ID from CI_CIDocuments)"


    Nicolai

    Thursday, August 30, 2012 8:47 PM
  • should be

    delete from CI_DocumentStore where Document_ID not in (select Document_ID from CI_CIDocuments)

    Wednesday, September 12, 2012 6:18 PM