none
SCCM 2012 and SQL 2008 R2 Sync problems

    Question

  • Hi

    I installed 2 servers for SCCM 2012:

    -1 with SCCM 2012, FEP, WSUS console admin

    -1 with SQL Server 2008 R2 complete install, WSUS complete install

    When I made or the system mades the synchronization, it shows this error in SMS_WSUS_SYNC_MANAGER:

    Error 6703: 

    WSUS Synchronization failed.
     Message: Failed to sync some of the updates.
     Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates.
     

    And in the wsyncmgr.log appears:

    sync: SMS synchronizing updates, processed 3336 out of 3368 items (99%), ETA in 00:00:06  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:14:11.663+300><thread=4640 (0x1220)>
    sync: SMS synchronizing updates, processed 3360 out of 3392 items (99%), ETA in 00:00:06  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:15:11.669+300><thread=4640 (0x1220)>
    sync: SMS synchronizing updates, processed 3383 out of 3415 items (99%), ETA in 00:00:07  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:16:13.206+300><thread=4640 (0x1220)>
    sync: SMS synchronizing updates, processed 3412 out of 3444 items (99%), ETA in 00:00:07  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:17:14.152+300><thread=4640 (0x1220)>
    Synchronized update 3a572bd0-5976-4abc-b2d8-955008c5466f - Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.131.558.0).  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:17:18.227+300><thread=4640 (0x1220)>
    sync: SMS synchronizing updates, processed 3446 out of 3463 items (99%), ETA in 00:00:04  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:18:14.400+300><thread=4640 (0x1220)>
    Synchronized update 3eeb75c2-81aa-4cc0-9b7a-237a6a0bf737 - Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.131.574.0).  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:18:47.964+300><thread=4640 (0x1220)>
    sync: SMS synchronizing updates, processed 3482 out of 3484 items (99%), ETA in 00:00:00  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:19:15.587+300><thread=4640 (0x1220)>
    Synchronized update 74e86346-9384-4304-9625-2c865738c552 - Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.131.574.0).  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.659+300><thread=4640 (0x1220)>
    sync: SMS synchronizing updates, processed 3508 out of 3508 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.662+300><thread=4640 (0x1220)>
    Sync failures summary:  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.664+300><thread=4640 (0x1220)>
    Failed to sync update 1ba2d28f-75fe-49d7-9cb4-cd39b8706f48. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.666+300><thread=4640 (0x1220)>
    Failed to sync update 8a042978-e6d7-4ae6-b3ab-687d8f9bcd9c. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.669+300><thread=4640 (0x1220)>
    Failed to sync update a3aff37b-ad3b-4dde-9464-767a516c76e5. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.671+300><thread=4640 (0x1220)>
    Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.421+300><thread=3536 (0xDD0)>
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=GDVSCCM1.gdar.local SITE=CRP PID=1908 TID=3536 GMTDATE=mar jul 24 14:20:06.423 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates" ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.425+300><thread=3536 (0xDD0)>
    Sync failed. Will retry in 60 minutes  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.501+300><thread=3536 (0xDD0)>
    Setting sync alert to active state on site CRP  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.503+300><thread=3536 (0xDD0)>
    Updated 173 items in SMS database, new update source content version is 36  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.526+300><thread=3536 (0xDD0)>
    Set content version of update source {6A4B4446-1B80-4CF4-838D-405D3847A8E3} for site CRP to 36  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.572+300><thread=3536 (0xDD0)>
    Sync time: 0d00h19m46s  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.575+300><thread=3536 (0xDD0)>
    Wakeup by SCF change  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 10:00:06.651+300><thread=3536 (0xDD0)>
    Next scheduled sync is a retry sync at 24/07/2012 10:20:06 a.m.  $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 10:00:11.940+300><thread=3536 (0xDD0)>

    Why is this behavior?

    Thanks


    Doc MX


    • Edited by DocMX Tuesday, July 24, 2012 3:32 PM
    Tuesday, July 24, 2012 3:32 PM

Answers

  • Hi

    Today I think I discovered what was the problem:

    I used an user in the domain for deploying the role of SUP, but I forgot to put that user in the group of SQL Admins of the SQL Server.

    I done that and after reseting the servers, the error for sync with SQL didn't appear again, al least from this morning until now, before this change every hour showed the error 6703.

    Thanks to all for your comments.


    Doc MX

    • Marked as answer by DocMX Thursday, July 26, 2012 9:51 PM
    • Unmarked as answer by DocMX Thursday, July 26, 2012 9:52 PM
    • Proposed as answer by Anoop C Nair Friday, July 27, 2012 5:50 AM
    • Marked as answer by DocMX Sunday, July 29, 2012 1:39 PM
    Thursday, July 26, 2012 9:51 PM

All replies

  • Does it always fails?

    Tuesday, July 24, 2012 4:14 PM
  • can you finish the sync wihtout endpoint protection updates?

    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund

    Tuesday, July 24, 2012 4:22 PM
    Moderator
  • Hi

    Yes, every hour, appear the follow events in order:

    Star sync - EventID: 6701

    Progress - EventID: 6704

    Sync Database - 6705

    Error - 6703

    Every hour appear in the  SMS_WSUS_SYNC_MANAGER.


    Doc MX

    Tuesday, July 24, 2012 5:00 PM
  • Ken, I'm not sure about your question, I chequed with some clients and They looks updated with the FEP, but I'm not sure if the SCCM gave these updates or they obtained directly from microsoft.


    Doc MX

    Tuesday, July 24, 2012 5:04 PM
  • I'm not quite sure, but I think that the updates that are superseded o expired sccm can not delete from the database, because I continue looking several updates that are superseded or expired in the sccm console

    Doc MX

    Tuesday, July 24, 2012 6:34 PM
  • Hi

    Any suggestion?

    Thanks!!


    Doc MX

    Wednesday, July 25, 2012 3:33 PM
  • Hi

    Today I think I discovered what was the problem:

    I used an user in the domain for deploying the role of SUP, but I forgot to put that user in the group of SQL Admins of the SQL Server.

    I done that and after reseting the servers, the error for sync with SQL didn't appear again, al least from this morning until now, before this change every hour showed the error 6703.

    Thanks to all for your comments.


    Doc MX

    • Marked as answer by DocMX Thursday, July 26, 2012 9:51 PM
    • Unmarked as answer by DocMX Thursday, July 26, 2012 9:52 PM
    • Proposed as answer by Anoop C Nair Friday, July 27, 2012 5:50 AM
    • Marked as answer by DocMX Sunday, July 29, 2012 1:39 PM
    Thursday, July 26, 2012 9:51 PM