none
[SCCM 2012] WSUS Sync Problem

    Question

  • Hi guys,

    I have a primary server with active SUP and a remote SQL. After a Site and DB restore I'm getting errors trying to synchronize WSUS with SCCM so the updates list in completely empty.

    I followed the steps in http://support.microsoft.com/kb/2709082 and everything is as stated in that KB, besides there's no records when I run:
    "select * from CI_DocumentStore where Document_ID not in (select Document_ID from CI_CIDocuments)"

    I also tried all combinations of removing SUP, adding SUP, remove WSUS, install WSUS, etc... but nothing seems to make it work.

    Here is my wsyncmgr.log:

    Wakeup by SCF change $$<sms_wsus_sync_manager><09-21-2012 19:38:16.154+180><thread=4800 (0x12C0)="">
    Requesting local sync due to a change in main WSUS server location. $$<sms_wsus_sync_manager><09-21-2012 19:38:21.182+180><thread=4800 (0x12C0)="">
    Performing sync on local request $$<sms_wsus_sync_manager><09-21-2012 19:38:21.183+180><thread=4800 (0x12C0)="">
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=<smsserver>SITE=GME PID=2996 TID=4800 GMTDATE=vie sep 21 22:38:21.184 2012 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<sms_wsus_sync_manager><09-21-2012 19:38:21.184+180><thread=4800 (0x12C0)="">
    STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=<smsserver>SITE=GME PID=2996 TID=4800 GMTDATE=vie sep 21 22:39:43.270 2012 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<sms_wsus_sync_manager><09-21-2012 19:39:43.272+180><thread=4800 (0x12C0)="">
    Synchronizing WSUS server <smsserver>$$<sms_wsus_sync_manager><09-21-2012 19:39:43.289+180><thread=4800 (0x12C0)="">
    Synchronizing WSUS server <smsserver>... $$<sms_wsus_sync_manager><09-21-2012 19:39:43.340+180><thread=6932 (0x1B14)="">
    sync: Starting WSUS synchronization $$<sms_wsus_sync_manager><09-21-2012 19:39:43.342+180><thread=6932 (0x1B14)="">
    sync: WSUS synchronizing categories $$<sms_wsus_sync_manager><09-21-2012 19:39:48.626+180><thread=6932 (0x1B14)="">
    sync: WSUS synchronizing categories, processed 1724 out of 1724 items (100%) $$<sms_wsus_sync_manager><09-21-2012 19:44:26.509+180><thread=6932 (0x1B14)="">
    sync: WSUS synchronizing updates $$<sms_wsus_sync_manager><09-21-2012 19:44:29.540+180><thread=6932 (0x1B14)="">
    sync: WSUS synchronizing updates, processed 3972 out of 20693 items (19%), ETA in 00:16:58 $$<sms_wsus_sync_manager><09-21-2012 19:48:32.110+180><thread=6932 (0x1B14)="">
    sync: WSUS synchronizing updates, processed 4744 out of 20693 items (22%), ETA in 00:16:55 $$<sms_wsus_sync_manager><09-21-2012 19:49:32.251+180><thread=6932 (0x1B14)="">
    sync: WSUS synchronizing updates, processed 7043 out of 20693 items (34%), ETA in 00:15:38 $$<sms_wsus_sync_manager><09-21-2012 19:52:33.710+180><thread=6932 (0x1B14)="">
    sync: WSUS synchronizing updates, processed 8704 out of 20693 items (42%), ETA in 00:13:51 $$<sms_wsus_sync_manager><09-21-2012 19:54:33.791+180><thread=6932 (0x1B14)="">
    sync: WSUS synchronizing updates, processed 11504 out of 20693 items (55%), ETA in 00:10:27 $$<sms_wsus_sync_manager><09-21-2012 19:57:35.595+180><thread=6932 (0x1B14)="">
    sync: WSUS synchronizing updates, processed 15300 out of 20693 items (73%), ETA in 00:06:02 $$<sms_wsus_sync_manager><09-21-2012 20:01:38.623+180><thread=6932 (0x1B14)="">
    sync: WSUS synchronizing updates, processed 18604 out of 20693 items (89%), ETA in 00:02:22 $$<sms_wsus_sync_manager><09-21-2012 20:05:39.644+180><thread=6932 (0x1B14)="">
    sync: WSUS synchronizing updates, processed 20693 out of 20693 items (100%) $$<sms_wsus_sync_manager><09-21-2012 20:08:35.995+180><thread=6932 (0x1B14)="">
    Done synchronizing WSUS Server <smsserver>$$<sms_wsus_sync_manager><09-21-2012 20:08:35.995+180><thread=6932 (0x1B14)="">
    STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=<smsserver>SITE=GME PID=2996 TID=4800 GMTDATE=vie sep 21 23:10:36.695 2012 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<sms_wsus_sync_manager><09-21-2012 20:10:36.704+180><thread=4800 (0x12C0)="">
    Synchronizing SMS database with WSUS server <smsserver>$$<sms_wsus_sync_manager><09-21-2012 20:10:36.716+180><thread=4800 (0x12C0)="">
    Synchronizing SMS database with WSUS server <smsserver>... $$<sms_wsus_sync_manager><09-21-2012 20:10:36.761+180><thread=6856 (0x1AC8)="">
    sync: Starting SMS database synchronization $$<sms_wsus_sync_manager><09-21-2012 20:10:36.762+180><thread=6856 (0x1AC8)="">
    requested localization languages: en,es $$<sms_wsus_sync_manager><09-21-2012 20:10:36.762+180><thread=6856 (0x1AC8)="">
    Syncing all updates $$<sms_wsus_sync_manager><09-21-2012 20:10:36.794+180><thread=6856 (0x1AC8)="">
    requested update classifications: Critical Updates, Definition Updates, Feature Packs, Security Updates, Service Packs, Tools, Update Rollups, Updates $$<sms_wsus_sync_manager><09-21-2012 20:10:36.836+180><thread=6856 (0x1AC8)="">
    sync: SMS synchronizing categories $$<sms_wsus_sync_manager><09-21-2012 20:10:36.877+180><thread=6856 (0x1AC8)="">
    sync: SMS synchronizing categories, processed 0 out of 189 items (0%) $$<sms_wsus_sync_manager><09-21-2012 20:10:36.930+180><thread=6856 (0x1AC8)="">
    sync: SMS synchronizing categories, processed 189 out of 189 items (100%) $$<sms_wsus_sync_manager><09-21-2012 20:10:54.686+180><thread=6856 (0x1AC8)="">
    sync: SMS synchronizing categories, processed 189 out of 189 items (100%) $$<sms_wsus_sync_manager><09-21-2012 20:10:54.687+180><thread=6856 (0x1AC8)="">
    sync: SMS synchronizing updates $$<sms_wsus_sync_manager><09-21-2012 20:10:54.699+180><thread=6856 (0x1AC8)="">
    sync: SMS synchronizing updates, processed 0 out of 27630 items (0%) $$<sms_wsus_sync_manager><09-21-2012 20:10:55.873+180><thread=6856 (0x1AC8)="">
    Skipped update 862b36ee-9748-492e-bfd3-53f9d14c1956 - Flaw In Windows Media Player May Allow Media Library Access (819639) because it was superseded. $$<sms_wsus_sync_manager><09-21-2012 20:10:56.438+180><thread=6856 (0x1AC8)="">
    Referenced configuration items are not available yet: <missingreferences><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_123bf469-116c-493f-a105-d04c468afbdf" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_25e59d2f-bcbd-4600-b6e9-6a03b21c10a6" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_2c31d3a8-f09a-4d6b-8b16-84342c882e17" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_301eff2a-1a15-4778-81dd-718aaa988c22" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_58d2e465-8916-4b76-a855-672194b25d34" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_626c93ab-5629-43dc-af1f-b77684e008ec" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_7b995c20-8c64-4272-8afc-a7ee79a13acf" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_7d84304c-a8ec-46a0-80f5-a602630bd219" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_8418cfb4-164b-4c88-884b-5756f95e625d" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_a2e7bd9d-2026-40c0-9eee-dfc7698590e4" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_a6e2b8dc-e007-45b8-9956-4b0d20b8b37d" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_cb472cea-6f41-4780-bd6d-3944cd9977c3" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_cdf60dbe-88a0-4a8b-815a-38eec23c4e3c" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_d3b5e822-8ffc-429d-bd31-a583f432fe21" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_d49632a2-0dd6-438e-9dcb-7bcb97e2dff9" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_ec228c67-d1f4-4a88-9cfc-36835849723c" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_ed909584-9e36-407c-8b0c-cfd78dfa0f64" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_ee21f72b-b502-4021-85e4-4b044efc41e6" RelationType="1"></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></missingreferences>~ $$<sms_wsus_sync_manager><09-21-2012 20:11:13.126+180><thread=6856 (0x1AC8)="">
    Failed to sync update 6a083d59-71bc-4942-a16f-58d0f44cbc4d. Error: Failed to save update 6a083d59-71bc-4942-a16f-58d0f44cbc4d. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate $$<sms_wsus_sync_manager><09-21-2012 20:11:13.137+180><thread=6856 (0x1AC8)="">
    Referenced configuration items are not available yet: <missingreferences><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_0ce8cfec-ddc7-406e-a6a0-e82a7a767d16" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_142473f4-2fbc-4670-8bba-e2c34b4f61f9" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_292e1e3d-1f9f-4c44-9d5c-8fd72b104588" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_2ddfa04a-85de-429f-bed6-2b59df948803" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_3239e856-034c-40a8-bedd-eba1392b55d1" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_5d5543c5-21fa-4701-b100-03ace04e58f9" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_6cc7d60c-36c8-419d-b84e-722b45870a94" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_7ce77290-a92d-40dc-a59a-0ccae174ef16" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_7f0cc567-81ca-4d68-b0d8-c4d794b9d617" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_8311948c-e2fb-4348-a997-32acd8c237f0" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_89ce3dcd-3a98-49f4-bcca-757895d97379" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_8b3387e1-6226-41b3-ae96-cc90f9209c7c" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_98c0173a-cd30-4121-bb0f-8d01d657ae58" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_b118b11f-2972-4c10-a99a-2a45096b238a" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_b860cb20-7497-42ca-b6cc-46e297e9410a" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_cde53c0a-55ff-44b7-80e6-69ba947ce09d" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_e837bdba-72eb-43dd-a90c-3d64d995b8b1" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_fe9069d3-a333-4b5f-b3ea-3d70bc2a19d6" RelationType="1"></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></missingreferences>~ $$<sms_wsus_sync_manager><09-21-2012 20:11:18.175+180><thread=6856 (0x1AC8)="">
    Failed to sync update aec3fee6-e956-41ff-b444-e3630eaee400. Error: Failed to save update aec3fee6-e956-41ff-b444-e3630eaee400. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate $$<sms_wsus_sync_manager><09-21-2012 20:11:25.480+180><thread=6856 (0x1AC8)="">
    Referenced configuration items are not available yet: <missingreferences><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_0ab6349d-02c4-45c4-a7a0-87da827d622d" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_208cbca6-12c5-42a1-804a-bb31dd84aecf" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_2637c156-a1b8-4277-ac55-f99fef74aeff" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_31b51542-538f-41ef-88db-6e4d4fcbd99a" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_40d1a54d-954c-4777-afec-00f825ca3723" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_5c5c2916-d2c1-4a49-84c5-37b7c98cdd45" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_61f10d4f-f59f-4316-960f-4d26632608f1" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_90af12e4-4907-4464-a139-8323a5d3b1c1" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_9519a5ab-0ab5-41a7-a2af-0096ad1ab894" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_97de906c-704a-489a-af72-996d742a36c4" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_9eccf808-3ed2-42a1-89ce-9c377f32f3f8" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_bbba98cf-9a6c-42a4-b2e2-86ad07d651a9" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_c12a279c-6ab9-4884-9575-1a3458bfdc63" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_da0bf960-5030-45b9-a2d5-c42fa6467e28" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_dcbce885-5617-4107-9465-7f8e0e98767b" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_ec2ac75e-829c-4985-88b3-7b613561020c" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_f06d96ef-a23b-49d5-a0aa-9a92e8b3511a" RelationType="1"><reference ModelName="Site_2DA48318-5F6E-493F-9FC2-AB5B8482C6EB/SUM_fc0e7df8-9998-4abe-aba3-b842221b06e7" RelationType="1"></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></reference></missingreferences>~ $$<sms_wsus_sync_manager><09-21-2012 20:11:45.318+180><thread=6856 (0x1AC8)="">
    Failed to sync update 3c683c60-ebd8-405d-a9c5-566499e6529d. Error: Failed to save update 3c683c60-ebd8-405d-a9c5-566499e6529d. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate $$<sms_wsus_sync_manager><09-21-2012 20:11:45.320+180><thread=6856 (0x1AC8)="">
    .....
    .....
    Sync failures summary: $$<sms_wsus_sync_manager><09-21-2012 20:12:05.559+180><thread=6856 (0x1AC8)="">
    Failed to sync update 6a083d59-71bc-4942-a16f-58d0f44cbc4d. Error: Failed to save update 6a083d59-71bc-4942-a16f-58d0f44cbc4d. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate $$<sms_wsus_sync_manager><09-21-2012 20:12:05.560+180><thread=6856 (0x1AC8)="">
    Failed to sync update adadffe2-2230-4a38-b412-30788a8e322f. Error: Failed to save update adadffe2-2230-4a38-b412-30788a8e322f. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate $$<sms_wsus_sync_manager><09-21-2012 20:12:05.562+180><thread=6856 (0x1AC8)="">
    Failed to sync update 6dba0924-ac9f-4449-9672-405976297297. Error: Failed to save update 6dba0924-ac9f-4449-9672-405976297297. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate $$<sms_wsus_sync_manager><09-21-2012 20:12:05.563+180><thread=6856 (0x1AC8)="">
    Failed to sync update b141dc09-8a53-4939-b2fb-2db1011840be. Error: Failed to save update b141dc09-8a53-4939-b2fb-2db1011840be. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate $$<sms_wsus_sync_manager><09-21-2012 20:12:05.563+180><thread=6856 (0x1AC8)="">
    Failed to sync update aec3fee6-e956-41ff-b444-e3630eaee400. Error: Failed to save update aec3fee6-e956-41ff-b444-e3630eaee400. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate $$<sms_wsus_sync_manager><09-21-2012 20:12:05.564+180><thread=6856 (0x1AC8)="">
    Failed to sync update 902adae3-e34b-4ef0-b7c8-d91020685901. Error: Failed to save update 902adae3-e34b-4ef0-b7c8-d91020685901. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate $$<sms_wsus_sync_manager><09-21-2012 20:12:05.564+180><thread=6856 (0x1AC8)="">
    Failed to sync update 3c683c60-ebd8-405d-a9c5-566499e6529d. Error: Failed to save update 3c683c60-ebd8-405d-a9c5-566499e6529d. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate $$<sms_wsus_sync_manager><09-21-2012 20:12:05.566+180><thread=6856 (0x1AC8)="">
    Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates $$<sms_wsus_sync_manager><09-21-2012 20:12:05.743+180><thread=4800 (0x12C0)=""></thread=4800></sms_wsus_sync_manager></thread=6856></sms_wsus_sync_manager>

    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=<smsserver>SITE=GME PID=2996 TID=4800 GMTDATE=vie sep 21 23:12:05.744 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><09-21-2012 20:12:05.753+180><thread=4800 (0x12C0)="">
    Sync failed. Will retry in 60 minutes $$<sms_wsus_sync_manager><09-21-2012 20:12:05.764+180><thread=4800 (0x12C0)="">
    Setting sync alert to active state on site GME $$<sms_wsus_sync_manager><09-21-2012 20:12:05.764+180><thread=4800 (0x12C0)="">
    Updated 242 items in SMS database, new update source content version is 19 $$<sms_wsus_sync_manager><09-21-2012 20:12:05.766+180><thread=4800 (0x12C0)="">
    Set content version of update source {2DA48318-5F6E-493F-9FC2-AB5B8482C6EB} for site GME to 19 $$<sms_wsus_sync_manager><09-21-2012 20:12:05.776+180><thread=4800 (0x12C0)="">
    Sync time: 0d00h33m44s $$<sms_wsus_sync_manager><09-21-2012 20:12:05.778+180><thread=4800 (0x12C0)="">

    Even when it says "Updated 242 items in SMS database" the update repository remains empty.
    My WSUSCtrl.log log is absolutely clean... no errors at all.

    Any thought on where the problem might be?...

    Thanks,
    -JP

    PS: I can create packages, SW and other stuff... I'm even working with OSD.
    • Edited by JPMuniz Saturday, September 22, 2012 12:48 AM
    Saturday, September 22, 2012 12:10 AM

Answers

  • I rebuild the whole service from the start... now it's working :/

    • Marked as answer by JPMuniz Tuesday, September 25, 2012 3:45 PM
    Monday, September 24, 2012 8:14 PM

All replies

  • Regarding this "Failed to sync update" or "Error: Failed to save update" error, I realize there's a slight difference between my case and all others I saw on internet and even in this forum.

    Failed to sync update 98d1463d-2b3d-4c3b-841a-1a28f71277dd. Error: Failed to save update 98d1463d-2b3d-4c3b-841a-1a28f71277dd. CCISource error: 2. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate

    Al other posts shows "CCISource error: -1" instead of my "CCISource error: 2" but I don't know what this means.

    Saturday, September 22, 2012 6:58 PM
  • How did you restore the DB?

    After restoring the DB, did you perform a site reset?


    Jason | http://blog.configmgrftw.com

    • Marked as answer by JPMuniz Sunday, September 23, 2012 2:18 AM
    • Unmarked as answer by JPMuniz Sunday, September 23, 2012 3:19 AM
    Saturday, September 22, 2012 11:24 PM
  • How did you restore the DB?

    After restoring the DB, did you perform a site reset?


    Jason | http://blog.configmgrftw.com


    After apply the site reset I still had this error. I removed SUP and uninstall WSUS, and reinstall WSUS and SUP... but this time, in the product list (from products and classifications) I only select "Office 2003" which wasn't part of the selected products in the original list and worked fine. But if I add other products like Windows 7, (which was part of those old products... prior to site restore), then I get the error again. So I'm seeing the problem is with old records in the DB

    Is there any way to delete records from udate with this IDs?

    6a083d59-71bc-4942-a16f-58d0f44cbc4d
    98d1463d-2b3d-4c3b-841a-1a28f71277dd
    8d1f6795-726f-4870-b246-7ad5ba9ac8c8
    eadb0f9b-28eb-43c8-b5e1-12238fb21e9d
    4beb6ee7-4b39-471a-9b2a-4a1212b3407a
    adadffe2-2230-4a38-b412-30788a8e322f
    6dba0924-ac9f-4449-9672-405976297297
    b141dc09-8a53-4939-b2fb-2db1011840be
    aec3fee6-e956-41ff-b444-e3630eaee400
    902adae3-e34b-4ef0-b7c8-d91020685901
    3abbf4bd-9ced-4d98-b7c5-3654aae3d9ec
    78fedc95-792b-4600-977e-60de8feb3522
    8434fc5d-acc9-4da3-a13a-9cdb40d6f92a
    3c683c60-ebd8-405d-a9c5-566499e6529d

    Thanks again for your help.


    • Marked as answer by JPMuniz Sunday, September 23, 2012 2:19 AM
    • Unmarked as answer by JPMuniz Sunday, September 23, 2012 3:19 AM
    • Edited by JPMuniz Sunday, September 23, 2012 3:29 AM
    Sunday, September 23, 2012 2:18 AM
  • I rebuild the whole service from the start... now it's working :/

    • Marked as answer by JPMuniz Tuesday, September 25, 2012 3:45 PM
    Monday, September 24, 2012 8:14 PM
  • Gentleman,

    This is a known bug to Microsoft in SCCM 2012 RTM when repairing an standalone Site.

    When recovering a site, a new site ID was generated in HKLM\Software\Microsoft\SMS\Identification. The string Valeu "Site ID" is a new one.

    To repair this, backup you SCCM using the Site Maintenance task. After that, stop all SMS_ services.

    Back to CM_XXX database, execute the following query in SQL Management Studio:

    SELECT * FROM CI_UpdateSources

    The result should be two rows, note the value under UpdateSource_UniqueID. Check the date under DateCreated and copy the OLDEST UpdateSource_UniqueID.

    Now edit the string "Site ID" in HKLM\Software\Microsoft\SMS\Identification and replace the value with the OLD ID you copied from the step above.

    Also, execute the following query to update the ID in the Database and replace the X with the ID u just pasted in the "Site ID" string value

    update SMSData set ThisSiteGUID = '{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}'

    Now delete the newest ID executing the following query:

    delete from CI_UpdateSources where UpdateSource_UniqueID = '{YYYYYYYY-YYYY-YYYY-YYYY-YYYYYYYYYYYY}'

    Start all SMS_ services again, go to Sites, Configure Site Components, Software Update Point. Set a schedule to run a Sync in 5 minutes or so. It must be schedule, do not sync manually.

    Check wsyncmgr.log, it should be ok now.

    • Proposed as answer by minsell Wednesday, April 03, 2013 12:34 PM
    Tuesday, November 27, 2012 5:12 PM
  • What steps did you take to rebuild the whole service?
    Monday, July 08, 2013 9:07 PM
  • The site reset option is greyed out for me in the SCCM setup wizard.  I am using SCCM 2012 with SP1 on Server 2012
    Monday, July 08, 2013 9:09 PM
  • I know this is an old thread but I was hoping maybe someone can give a little more info.

    Did a Primary site recovery from a Windows 2008 R2 server to Windows 2012 and also from SQL 2008 R2 to SQL 2012 SP1.  SCCM 2012 SP1 was installed and WSUS is co-located on same server.  On new server I installed WSUS and configured.  Site recovery process went fine but am having the same issue as listed above: Referenced configuration items are not available yet: <MissingReferences> and also Failed to sync update... Error: Failed to save update ... CCISource error: 2 on some updates which eventually causes the sync to fail.

    Reading HandryMR's helpful post seemed to be a great starting point, but then I realized the new Update Source version is obviously different from the "original" WSUS 3.0 that was running under 2008 R2.  So deleting the newest entry with the different UniqueID doesn't seem correct since it would then be referencing an update source with version 3.x which doesn't exist anymore.

    Is there a way or is it recommended to modify the UniqueID of the "new" update source to change it back to the original site ID?  That way I would be able to update the Site ID back to the original and change the Update Source_Unique ID to the same, but keep it as the 6.2 entry.  And then delete the original 3.x entry.

    I hope that makes sense...I'm kind of grasping at straws on this issue since I haven't had much luck in correcting the problem yet.

    Monday, August 12, 2013 7:24 PM
  • I´m having exact the same situation as Brian above. Unfortunately, SQL 2012 SP1 is not yet supported in Configuration Manager 2012 SP1.

    I have a lot of failed updates in syncs, so I really don´t wont to query each update in DB. I was thinking, if I remove SUP, and wait 7 days (I´ve read this somewhere, that it might help), do DP clear itself.. will that help? Also, is there a way to speed up the database cleanup of updates?


    • Edited by yannara Monday, August 26, 2013 10:50 AM
    Monday, August 26, 2013 8:17 AM
  • Unfortunately, SQL 2012 SP1 is not yet supported in Configuration Manager 2012 SP1.

    It is now Yannara

    http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLSrvReq



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson

    Monday, August 26, 2013 8:22 AM