none
SUP SYNC Error 0X80131509 RRS feed

  • Question

  • I have an issue, I can not figure out..   

    Originally, I had SUP obtain windows updates directly from Microsoft.   Things worked very well.

    We purchased Retina CS to mitigate WIndows & 3rd Party updates. 

     

    So, for this to work,  we had to point SUP to an existing Upstream WSUS Server.

     

    The Architecture is as follows;
    SCCM Server 2012 -  2012 server, has a Back-End SQL Server 2012 Server.
    The SCCM Server SUP connects to the Upstream WSUS Server [2008 server R2], that has a Backend 2008 SQL Server
    The SCCM Server 2012 is a Automonus, 

     

     

    WSYNCMGR  Log:

     

    Sometimes in the WSYNCMGR, I get succeeded;  mostly I get Failed as show here..

     

    Sync succeeded. Setting sync alert to canceled state on site NET  $$<SMS_WSUS_SYNC_MANAGER><08-08-2013 23:04:49.592+300><thread=5944 (0x1738)>
     

    Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse  $$<SMS_WSUS_SYNC_MANAGER><08-09-2013 06:17:09.689+300><thread=5944 (0x1738)>

     

     

    Software Update Point Synchronization Status

     

    Synchronization source:  BR-WSUS

    Synchronization: failed

    Code:  0X80131509

     

    Thank you for your help..

    Saturday, August 10, 2013 12:15 PM

Answers

  • Based on the 404 and the operation timed out messages that look pop up multiple times, I'd say you've got some kind of network issue or security software/appliance in place that only intermittently kicks in.

    Maybe you've got a proxy configured or a network security device that requires authentication?


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Semperfi4000 Wednesday, August 14, 2013 7:29 PM
    Saturday, August 10, 2013 10:20 PM

All replies

  • Do yo have ConfigMgr 2012 *SP1* installed?

    Also, posting a single line from a log file is useless. Log files have lots of lines for a reason, context. A single line never tells the story.

    Have you tried to manually sync the WSUS instance?

    Have you reviewed the application event log on both systems?

    Have you verified connectivity during the failure times?


    Jason | http://blog.configmgrftw.com

    Saturday, August 10, 2013 3:40 PM
  • The SCCM Server SUP connects to the Upstream WSUS Server [2008 server R2], that has a Backend 2008 SQL Server

    Have you installed KB2734608 on the WSUS v3.2 upstream server?

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Proposed as answer by SourabhR Monday, August 8, 2016 5:33 AM
    • Unproposed as answer by SourabhR Monday, August 8, 2016 5:33 AM
    Saturday, August 10, 2013 3:41 PM
  • Thank you for your reply;

    1) yea, ConfigMgr 2012 SP1

         Sorry, thought it would be confusing.   Down Below I have a partial wsyncmgr log, below the event app errors,  it show Successes and Failures. 

    2) Yea, I've done Manual Sync's..   I have noticed they fail..   So,  I would wait,  review the logs 5 - 8 hours later, and notice there would be some that are successful.  I don't recall one being successful, during a manual scan.

    3)  yea, I am seeing the following "Event App Errors" errors, but it is not always consistent.  But, has happened during a Sync.

    4)  yea, if I understand correctly,  I am able to connect to BRDC-WSUS server.

    Event App Errors

    Event 12072 

    On 8/10/2013 9:05:41 AM, component SMS_WSUS_SYNC_MANAGER on computer HTL-SCCM.network.internal reported:   WSUS Synchronization failed.
     Message: The operation has timed out.
     Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse.
      The operating system reported error 2148734217: 

    Event 12072

    The WSUS content directory is not accessible.
    System.Net.WebException: The remote server returned an error: (404) Not Found.
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)

    Event 13001 Warning

    Client computers are installing updates with a higher than 10 percent failure rate. This should be monitored.

    WSYNCMGR  Log:

    Sync time: 0d00h06m28s  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 07:06:29.774+300><thread=5944 (0x1738)>
    Next scheduled sync is a regular sync at 8/10/2013 8:00:00 AM  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 07:06:29.892+300><thread=5944 (0x1738)>
    Wakeup for scheduled regular sync  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:00.956+300><thread=5944 (0x1738)>
    Starting Sync  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:00.979+300><thread=5944 (0x1738)>
    Performing sync on regular schedule  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:01.003+300><thread=5944 (0x1738)>
    Read SUPs from SCF for HTL-SCCM.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:01.555+300><thread=5944 (0x1738)>
    Found 1 SUPs  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:01.600+300><thread=5944 (0x1738)>
    Found active SUP HTL-SCCM.network.internal from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:01.621+300><thread=5944 (0x1738)>
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 13:00:01.646 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:01.647+300><thread=5944 (0x1738)>
    Synchronizing WSUS server HTL-SCCM.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:03.054+300><thread=5944 (0x1738)>
    STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 13:00:03.068 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:03.068+300><thread=5944 (0x1738)>
    Synchronizing WSUS server htl-sccm.network.internal ...  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:03.514+300><thread=7796 (0x1E74)>
    sync: Starting WSUS synchronization  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:03.535+300><thread=7796 (0x1E74)>
    sync: WSUS synchronizing categories  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:18.023+300><thread=7796 (0x1E74)>
    sync: WSUS synchronizing updates  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:19.079+300><thread=7796 (0x1E74)>
    Done synchronizing WSUS Server htl-sccm.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:24.854+300><thread=7796 (0x1E74)>
    Sleeping 2 more minutes for WSUS server sync results to become available  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:00:24.879+300><thread=7796 (0x1E74)>
    Set content version of update source {1800435A-AD61-4561-814C-4442F922187A} for site NET to 963  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:25.439+300><thread=5944 (0x1738)>
    Synchronizing SMS database with WSUS server HTL-SCCM.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:25.463+300><thread=5944 (0x1738)>
    STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 13:02:25.486 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:25.536+300><thread=5944 (0x1738)>
    Synchronizing SMS database with WSUS server htl-sccm.network.internal ...  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:25.694+300><thread=644 (0x284)>
    sync: Starting SMS database synchronization  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:25.715+300><thread=644 (0x284)>
    requested localization languages: en  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:25.735+300><thread=644 (0x284)>
    Syncing updates arrived after 08/09/2013 23:02:26  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:25.813+300><thread=644 (0x284)>
    Requested categories: Company=Igor Pavlov (LGPL), Company=Adobe Systems Incorporated, Company=win.rar GmbH, Company=WinZip International LLC, Company=Mozilla, Company=Local Publisher, Company=Google, Company=Skype Limited, Company=Opera Software ASA, Company=Foxit Corporation, Company=Apple Incorporated, Company=Oracle Corporation, Product=Office 2007, Product=Microsoft Lync Server 2010, Product=Forefront TMG MBE, Product=Forefront Client Security, Product=Windows Vista, Product=Exchange Server 2007, Product=Internet Security and Acceleration Server 2006, Product=Windows 8, Product=Windows XP x64 Edition, Product=System Center 2012 SP1 - App Controller, Product=Windows Internet Explorer 8 Dynamic Installer, Product=Windows XP, Product=Microsoft SQL Server 2012, Product=Forefront TMG, Product=Forefront code named Stirling Beta version, Product=Microsoft Lync 2010, Product=SQL Server 2005, Product=Windows Server 2003, Datacenter Edition, Product=SQL Server 2012 Product Updates for Setup, Product=System Center 2012 SP1 - Operation Manager, Product=Forefront Threat Management Gateway, Definition Updates for HTTP Malware Inspection, Product=Office 2010, Product=New Dictionaries for Microsoft IMEs, Product=Windows Defender, Product=Windows Vista Dynamic Installer, Product=System Center 2012 SP1 - App Controller Setup Self-update, Product=Exchange Server 2010, Product=Windows Server 2012, Product=Forefront Endpoint Protection 2010, Product=Windows XP 64-Bit Edition Version 2003, Product=Forefront Protection Category, Product=Exchange Server 2007 and Above Anti-spam, Product=Threat Management Gateway Definition Updates for Network Inspection System, Product=System Center Advisor, Product=Windows Server 2008, Product=System Center 2012 SP1 - Virtual Machine Manager, Product=SQL Server 2008 R2, Product=Windows 7, Product=SQL Server 2008, Product=SQL Server Feature Pack, Product=Windows Internet Explorer 7 Dynamic Installer, Product=TMG Firewall Client, Product=System Center Configuration Manager 2007, Product=Firewall Client for ISA Server, Product=Windows Server 2003, Product=System Center 2012 SP1 - Data Protection Manager, Product=Windows Server 2008 Server Manager Dynamic Installer, Product=Forefront Server Security Category, Product=Dictionary Updates for Microsoft IMEs, Product=Windows Server 2008 R2, ProductFamily=Skype, ProductFamily=Bing, ProductFamily=Developer Tools, Runtimes, and Redistributables, ProductFamily=Office Communications Server And Office Communicator, ProductFamily=Active Directory, ProductFamily=Virtual Server, ProductFamily=System Center Virtual Machine Manager, ProductFamily=Windows Embedded, ProductFamily=Microsoft Security Essentials, ProductFamily=Silverlight, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Service Packs, UpdateClassification=Feature Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, UpdateClassification=Critical Updates  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:28.182+300><thread=644 (0x284)>
    sync: SMS synchronizing categories  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:28.216+300><thread=644 (0x284)>
    sync: SMS synchronizing categories, processed 0 out of 250 items (0%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:28.857+300><thread=644 (0x284)>
    sync: SMS synchronizing categories, processed 250 out of 250 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:32.778+300><thread=644 (0x284)>
    sync: SMS synchronizing categories, processed 250 out of 250 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:32.800+300><thread=644 (0x284)>
    sync: SMS synchronizing updates  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:33.403+300><thread=644 (0x284)>
    sync: SMS synchronizing updates, processed 0 out of 6 items (0%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:47.983+300><thread=644 (0x284)>
    Skipped update 208537a7-5971-4844-b007-448feb579638 - HTTP Malware Definition Update for Microsoft Forefront Threat Management Gateway (Antimalware 1.155.1938.0) because it is up to date.  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:49.140+300><thread=644 (0x284)>
    Skipped update 5f192144-a6df-435b-b4da-e9ee9974b6e8 - Definition Update for Microsoft Forefront Client Security - KB977939 (Definition 1.155.1965.0) because it is up to date.  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:49.208+300><thread=644 (0x284)>
    Skipped update 5088494e-31b3-4d22-8f22-967f8256d305 - Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.155.1965.0) because it is up to date.  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:49.284+300><thread=644 (0x284)>
    Skipped update 81afbc9e-422d-45cb-ab74-258cfd1e725c - Definition Update for Windows Defender - KB2267602 (Definition 1.155.1965.0) because it is up to date.  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:49.345+300><thread=644 (0x284)>
    Skipped update 12d4893d-43a8-45aa-9ba7-fa8291459213 - Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.155.1968.0) because it is up to date.  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:49.425+300><thread=644 (0x284)>
    Skipped update 2f74adc2-1095-4a79-a106-8ca83871e293 - Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.155.1968.0) because it is up to date.  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:49.514+300><thread=644 (0x284)>
    sync: SMS synchronizing updates, processed 6 out of 6 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:49.545+300><thread=644 (0x284)>
    sync: SMS performing cleanup  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:02:49.566+300><thread=644 (0x284)>
    Removed 353 unreferenced updates  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:04:59.493+300><thread=644 (0x284)>
    Done synchronizing SMS with WSUS Server htl-sccm.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:04:59.514+300><thread=644 (0x284)>
    Set content version of update source {1800435A-AD61-4561-814C-4442F922187A} for site NET to 964  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:05:00.185+300><thread=5944 (0x1738)>
    STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 13:05:00.209 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:05:00.209+300><thread=5944 (0x1738)>
    Sync succeeded. Setting sync alert to canceled state on site NET  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:05:00.248+300><thread=5944 (0x1738)>
    Updated 353 items in SMS database, new update source content version is 964  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:05:00.382+300><thread=5944 (0x1738)>
    Sync time: 0d00h04m58s  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:05:00.403+300><thread=5944 (0x1738)>
    Next scheduled sync is a regular sync at 8/10/2013 9:00:00 AM  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 08:05:00.467+300><thread=5944 (0x1738)>
    Wakeup for scheduled regular sync  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:00.424+300><thread=5944 (0x1738)>
    Starting Sync  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:00.450+300><thread=5944 (0x1738)>
    Performing sync on regular schedule  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:00.473+300><thread=5944 (0x1738)>
    Read SUPs from SCF for HTL-SCCM.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:01.228+300><thread=5944 (0x1738)>
    Found 1 SUPs  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:01.264+300><thread=5944 (0x1738)>
    Found active SUP HTL-SCCM.network.internal from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:01.284+300><thread=5944 (0x1738)>
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 14:00:01.338 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:01.339+300><thread=5944 (0x1738)>
    Synchronizing WSUS server HTL-SCCM.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:02.647+300><thread=5944 (0x1738)>
    STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 14:00:02.670 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:02.671+300><thread=5944 (0x1738)>
    Synchronizing WSUS server htl-sccm.network.internal ...  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:02.913+300><thread=7616 (0x1DC0)>
    sync: Starting WSUS synchronization  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:02.934+300><thread=7616 (0x1DC0)>
    sync: WSUS synchronizing categories  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:13.165+300><thread=7616 (0x1DC0)>
    sync: WSUS synchronizing updates  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:14.252+300><thread=7616 (0x1DC0)>
    Done synchronizing WSUS Server htl-sccm.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:18.709+300><thread=7616 (0x1DC0)>
    Sleeping 2 more minutes for WSUS server sync results to become available  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:00:18.730+300><thread=7616 (0x1DC0)>
    Set content version of update source {1800435A-AD61-4561-814C-4442F922187A} for site NET to 964  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:19.443+300><thread=5944 (0x1738)>
    Synchronizing SMS database with WSUS server HTL-SCCM.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:19.465+300><thread=5944 (0x1738)>
    STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 14:02:19.486 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:19.497+300><thread=5944 (0x1738)>
    Synchronizing SMS database with WSUS server htl-sccm.network.internal ...  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:20.567+300><thread=6348 (0x18CC)>
    sync: Starting SMS database synchronization  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:20.589+300><thread=6348 (0x18CC)>
    requested localization languages: en  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:20.610+300><thread=6348 (0x18CC)>
    Syncing updates arrived after 08/10/2013 08:02:25  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:20.661+300><thread=6348 (0x18CC)>
    Requested categories: Company=Igor Pavlov (LGPL), Company=Adobe Systems Incorporated, Company=win.rar GmbH, Company=WinZip International LLC, Company=Mozilla, Company=Local Publisher, Company=Google, Company=Skype Limited, Company=Opera Software ASA, Company=Foxit Corporation, Company=Apple Incorporated, Company=Oracle Corporation, Product=Office 2007, Product=Microsoft Lync Server 2010, Product=Forefront TMG MBE, Product=Forefront Client Security, Product=Windows Vista, Product=Exchange Server 2007, Product=Internet Security and Acceleration Server 2006, Product=Windows 8, Product=Windows XP x64 Edition, Product=System Center 2012 SP1 - App Controller, Product=Windows Internet Explorer 8 Dynamic Installer, Product=Windows XP, Product=Microsoft SQL Server 2012, Product=Forefront TMG, Product=Forefront code named Stirling Beta version, Product=Microsoft Lync 2010, Product=SQL Server 2005, Product=Windows Server 2003, Datacenter Edition, Product=SQL Server 2012 Product Updates for Setup, Product=System Center 2012 SP1 - Operation Manager, Product=Forefront Threat Management Gateway, Definition Updates for HTTP Malware Inspection, Product=Office 2010, Product=New Dictionaries for Microsoft IMEs, Product=Windows Defender, Product=Windows Vista Dynamic Installer, Product=System Center 2012 SP1 - App Controller Setup Self-update, Product=Exchange Server 2010, Product=Windows Server 2012, Product=Forefront Endpoint Protection 2010, Product=Windows XP 64-Bit Edition Version 2003, Product=Forefront Protection Category, Product=Exchange Server 2007 and Above Anti-spam, Product=Threat Management Gateway Definition Updates for Network Inspection System, Product=System Center Advisor, Product=Windows Server 2008, Product=System Center 2012 SP1 - Virtual Machine Manager, Product=SQL Server 2008 R2, Product=Windows 7, Product=SQL Server 2008, Product=SQL Server Feature Pack, Product=Windows Internet Explorer 7 Dynamic Installer, Product=TMG Firewall Client, Product=System Center Configuration Manager 2007, Product=Firewall Client for ISA Server, Product=Windows Server 2003, Product=System Center 2012 SP1 - Data Protection Manager, Product=Windows Server 2008 Server Manager Dynamic Installer, Product=Forefront Server Security Category, Product=Dictionary Updates for Microsoft IMEs, Product=Windows Server 2008 R2, ProductFamily=Skype, ProductFamily=Bing, ProductFamily=Developer Tools, Runtimes, and Redistributables, ProductFamily=Office Communications Server And Office Communicator, ProductFamily=Active Directory, ProductFamily=Virtual Server, ProductFamily=System Center Virtual Machine Manager, ProductFamily=Windows Embedded, ProductFamily=Microsoft Security Essentials, ProductFamily=Silverlight, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Service Packs, UpdateClassification=Feature Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, UpdateClassification=Critical Updates  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:23.974+300><thread=6348 (0x18CC)>
    sync: SMS synchronizing categories  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:24.010+300><thread=6348 (0x18CC)>
    sync: SMS synchronizing categories, processed 0 out of 250 items (0%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:24.920+300><thread=6348 (0x18CC)>
    sync: SMS synchronizing categories, processed 250 out of 250 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:29.398+300><thread=6348 (0x18CC)>
    sync: SMS synchronizing categories, processed 250 out of 250 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:29.419+300><thread=6348 (0x18CC)>
    sync: SMS synchronizing updates  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:29.978+300><thread=6348 (0x18CC)>
    sync: SMS performing cleanup  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:02:41.201+300><thread=6348 (0x18CC)>
    Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:05:41.887+300><thread=5944 (0x1738)>
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 14:05:41.920 2013 ISTR0="Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:05:42.124+300><thread=5944 (0x1738)>
    Sync failed. Will retry in 60 minutes  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:05:43.107+300><thread=5944 (0x1738)>
    Setting sync alert to active state on site NET  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:05:43.121+300><thread=5944 (0x1738)>
    Sync time: 0d00h05m42s  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:05:43.723+300><thread=5944 (0x1738)>
    Next scheduled sync is a regular sync at 8/10/2013 10:00:00 AM  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 09:05:43.798+300><thread=5944 (0x1738)>
    Wakeup for scheduled regular sync  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:00.156+300><thread=5944 (0x1738)>
    Starting Sync  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:00.178+300><thread=5944 (0x1738)>
    Performing sync on regular schedule  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:00.202+300><thread=5944 (0x1738)>
    Read SUPs from SCF for HTL-SCCM.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:01.121+300><thread=5944 (0x1738)>
    Found 1 SUPs  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:01.167+300><thread=5944 (0x1738)>
    Found active SUP HTL-SCCM.network.internal from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:01.182+300><thread=5944 (0x1738)>
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 15:00:01.968 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:01.968+300><thread=5944 (0x1738)>
    Synchronizing WSUS server HTL-SCCM.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:04.241+300><thread=5944 (0x1738)>
    STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 15:00:04.265 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:04.266+300><thread=5944 (0x1738)>
    Synchronizing WSUS server htl-sccm.network.internal ...  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:05.118+300><thread=7328 (0x1CA0)>
    sync: Starting WSUS synchronization  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:05.140+300><thread=7328 (0x1CA0)>
    sync: WSUS synchronizing categories  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:14.709+300><thread=7328 (0x1CA0)>
    sync: WSUS synchronizing updates  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:17.802+300><thread=7328 (0x1CA0)>
    sync: WSUS synchronizing updates, processed 10 out of 10 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:36.042+300><thread=7328 (0x1CA0)>
    Done synchronizing WSUS Server htl-sccm.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:36.064+300><thread=7328 (0x1CA0)>
    Sleeping 2 more minutes for WSUS server sync results to become available  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:00:36.085+300><thread=7328 (0x1CA0)>
    Set content version of update source {1800435A-AD61-4561-814C-4442F922187A} for site NET to 964  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:37.741+300><thread=5944 (0x1738)>
    Synchronizing SMS database with WSUS server HTL-SCCM.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:37.765+300><thread=5944 (0x1738)>
    STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 15:02:37.787 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:37.807+300><thread=5944 (0x1738)>
    Synchronizing SMS database with WSUS server htl-sccm.network.internal ...  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:38.185+300><thread=7964 (0x1F1C)>
    sync: Starting SMS database synchronization  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:38.206+300><thread=7964 (0x1F1C)>
    requested localization languages: en  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:38.227+300><thread=7964 (0x1F1C)>
    Syncing updates arrived after 08/10/2013 08:02:25  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:38.314+300><thread=7964 (0x1F1C)>
    Requested categories: Company=Igor Pavlov (LGPL), Company=Adobe Systems Incorporated, Company=win.rar GmbH, Company=WinZip International LLC, Company=Mozilla, Company=Local Publisher, Company=Google, Company=Skype Limited, Company=Opera Software ASA, Company=Foxit Corporation, Company=Apple Incorporated, Company=Oracle Corporation, Product=Office 2007, Product=Microsoft Lync Server 2010, Product=Forefront TMG MBE, Product=Forefront Client Security, Product=Windows Vista, Product=Exchange Server 2007, Product=Internet Security and Acceleration Server 2006, Product=Windows 8, Product=Windows XP x64 Edition, Product=System Center 2012 SP1 - App Controller, Product=Windows Internet Explorer 8 Dynamic Installer, Product=Windows XP, Product=Microsoft SQL Server 2012, Product=Forefront TMG, Product=Forefront code named Stirling Beta version, Product=Microsoft Lync 2010, Product=SQL Server 2005, Product=Windows Server 2003, Datacenter Edition, Product=SQL Server 2012 Product Updates for Setup, Product=System Center 2012 SP1 - Operation Manager, Product=Forefront Threat Management Gateway, Definition Updates for HTTP Malware Inspection, Product=Office 2010, Product=New Dictionaries for Microsoft IMEs, Product=Windows Defender, Product=Windows Vista Dynamic Installer, Product=System Center 2012 SP1 - App Controller Setup Self-update, Product=Exchange Server 2010, Product=Windows Server 2012, Product=Forefront Endpoint Protection 2010, Product=Windows XP 64-Bit Edition Version 2003, Product=Forefront Protection Category, Product=Exchange Server 2007 and Above Anti-spam, Product=Threat Management Gateway Definition Updates for Network Inspection System, Product=System Center Advisor, Product=Windows Server 2008, Product=System Center 2012 SP1 - Virtual Machine Manager, Product=SQL Server 2008 R2, Product=Windows 7, Product=SQL Server 2008, Product=SQL Server Feature Pack, Product=Windows Internet Explorer 7 Dynamic Installer, Product=TMG Firewall Client, Product=System Center Configuration Manager 2007, Product=Firewall Client for ISA Server, Product=Windows Server 2003, Product=System Center 2012 SP1 - Data Protection Manager, Product=Windows Server 2008 Server Manager Dynamic Installer, Product=Forefront Server Security Category, Product=Dictionary Updates for Microsoft IMEs, Product=Windows Server 2008 R2, ProductFamily=Skype, ProductFamily=Bing, ProductFamily=Developer Tools, Runtimes, and Redistributables, ProductFamily=Office Communications Server And Office Communicator, ProductFamily=Active Directory, ProductFamily=Virtual Server, ProductFamily=System Center Virtual Machine Manager, ProductFamily=Windows Embedded, ProductFamily=Microsoft Security Essentials, ProductFamily=Silverlight, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Service Packs, UpdateClassification=Feature Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, UpdateClassification=Critical Updates  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:44.781+300><thread=7964 (0x1F1C)>
    sync: SMS synchronizing categories  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:44.829+300><thread=7964 (0x1F1C)>
    sync: SMS synchronizing categories, processed 0 out of 250 items (0%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:46.229+300><thread=7964 (0x1F1C)>
    sync: SMS synchronizing categories, processed 250 out of 250 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:55.333+300><thread=7964 (0x1F1C)>
    sync: SMS synchronizing categories, processed 250 out of 250 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:55.355+300><thread=7964 (0x1F1C)>
    sync: SMS synchronizing updates  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:02:56.016+300><thread=7964 (0x1F1C)>
    sync: SMS synchronizing updates, processed 0 out of 1 items (0%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:03:15.086+300><thread=7964 (0x1F1C)>
    Synchronizing update 615f7f52-d230-496a-a4d6-a99795f7e1d9 - HTTP Malware Definition Update for Microsoft Forefront Threat Management Gateway (Antimalware 1.155.1970.0)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:03:17.849+300><thread=7964 (0x1F1C)>
    sync: SMS synchronizing updates, processed 1 out of 1 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:03:41.940+300><thread=7964 (0x1F1C)>
    sync: SMS performing cleanup  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:03:41.962+300><thread=7964 (0x1F1C)>
    Removed 5 unreferenced updates  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:06:57.335+300><thread=7964 (0x1F1C)>
    Done synchronizing SMS with WSUS Server htl-sccm.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:06:57.358+300><thread=7964 (0x1F1C)>
    Set content version of update source {1800435A-AD61-4561-814C-4442F922187A} for site NET to 965  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:06:58.694+300><thread=5944 (0x1738)>
    STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 15:06:58.717 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:06:58.718+300><thread=5944 (0x1738)>
    Sync succeeded. Setting sync alert to canceled state on site NET  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:06:58.747+300><thread=5944 (0x1738)>
    Updated 10 items in SMS database, new update source content version is 965  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:06:59.302+300><thread=5944 (0x1738)>
    Sync time: 0d00h06m58s  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:06:59.326+300><thread=5944 (0x1738)>
    Next scheduled sync is a regular sync at 8/10/2013 11:00:00 AM  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 10:06:59.491+300><thread=5944 (0x1738)>
    Wakeup for scheduled regular sync  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:01.095+300><thread=5944 (0x1738)>
    Starting Sync  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:01.109+300><thread=5944 (0x1738)>
    Performing sync on regular schedule  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:01.134+300><thread=5944 (0x1738)>
    Read SUPs from SCF for HTL-SCCM.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:01.766+300><thread=5944 (0x1738)>
    Found 1 SUPs  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:01.806+300><thread=5944 (0x1738)>
    Found active SUP HTL-SCCM.network.internal from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:01.829+300><thread=5944 (0x1738)>
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 16:00:02.028 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:02.029+300><thread=5944 (0x1738)>
    Synchronizing WSUS server HTL-SCCM.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:03.800+300><thread=5944 (0x1738)>
    STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=HTL-SCCM.network.internal SITE=NET PID=2328 TID=5944 GMTDATE=Sat Aug 10 16:00:03.818 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:03.818+300><thread=5944 (0x1738)>
    Synchronizing WSUS server htl-sccm.network.internal ...  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:04.053+300><thread=6676 (0x1A14)>
    sync: Starting WSUS synchronization  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:04.073+300><thread=6676 (0x1A14)>
    Done synchronizing WSUS Server htl-sccm.network.internal  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:12.198+300><thread=6676 (0x1A14)>
    Sleeping 2 more minutes for WSUS server sync results to become available  $$<SMS_WSUS_SYNC_MANAGER><08-10-2013 11:00:12.220+300><thread=6676 (0x1A14)>

    Saturday, August 10, 2013 4:25 PM
  • thank you for your reply;

    Yea,  KB273608 has been installed.

    Saturday, August 10, 2013 4:27 PM
  • Based on the 404 and the operation timed out messages that look pop up multiple times, I'd say you've got some kind of network issue or security software/appliance in place that only intermittently kicks in.

    Maybe you've got a proxy configured or a network security device that requires authentication?


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Semperfi4000 Wednesday, August 14, 2013 7:29 PM
    Saturday, August 10, 2013 10:20 PM
  • So, look at the 404 error [Event 12072] on HTL-SCCM server [downstream],   I looked and 12072 happens about 3 times a day..   I then looked at BRDC-WSUS [Upstream] and each time Event 12072 happens on HTL-SCCM,   

    These two events happen on BRDC-WSUS within 30 mins, each time.

    10032
    The server is failing to download some updates.
    13032
    Many client computers have not reported back to the server in the last 30 days. 3 have been detected so far.

    BRDC-WSUS was our existing WSUS server, before using SCCM SUP. 

    Saturday, August 10, 2013 10:41 PM
  • It might be fixed,  I am going to monitor it for day..   on BRDC-WSUS  Endpoint protection 2012 ,  was scanning E:\WSUS .    Once I excluded it, so far, I a have been able to manually and automatically have successfully downloads..   if this is corrected,  thank you..
    • Edited by Semperfi4000 Saturday, August 10, 2013 11:08 PM add text
    Saturday, August 10, 2013 11:07 PM
  • I also encounted errors "Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse". The sync fails 2 times before success at second retry.

    I tried to exclude the WSUS folder from antimalware scan without success.

    I don't have the 404 error encountered by SemperFi.

    I checked on our firewall, the traffic isn't blocked.

    The problem is the same using explicit proxy.

    Regards

    Friday, March 18, 2016 6:58 AM
  • You should start a new thread instead of tacking on to a nearly 3 year old one and include full snippets from log files instead of a single random error.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Friday, March 18, 2016 2:38 PM
  • Hi Semperfi4000,

    Did you finally found a solution to this? I am facing the same concern.

    Thursday, July 21, 2016 1:15 PM
  • Hello.

    I am experiencing the same issue.

    First sync fails, second sync is successful.
    Event Viewer shows error; 2148734217

    I will create a new post for this issue, but figured I would see if you found a resolution first.

    Friday, March 3, 2017 3:15 PM
  • Hello,

    we have the same problem since a long time (more than 2 years). Even a dedicated WSUS server with sup role did not bring success. The problem persists after configuring direct internet access without proxy for sccm and wsus server.
    The second sync is mostly successful.

    Environment:
    SCCM 1610 on Windows Server 2012 x64

    Log:
    Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse SMS_WSUS_SYNC_MANAGER 22.06.2017 13:44:39 728 (0x02D8)

    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SERVERNAME SITE=SITENAME PID=18244 TID=728 GMTDATE=Do Jun 22 11:44:39.034 2017 ISTR0="Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 22.06.2017 13:44:39 728 (0x02D8)


    A.Richter

    Thursday, June 22, 2017 12:24 PM
  • Are you talking about the daily (or whatever schedule is set) sync?

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, June 22, 2017 1:22 PM
  • No, not daily. Once a month the sync via SCCM is scheduled.

    A.Richter

    Thursday, June 22, 2017 1:24 PM
  • After having this issue for a while, I completely remove WSUS and SUP from the server, reinstall and reconfigure WSUS and SUP.

    WSUS Sync took several hours when working properly after many errors (Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse) now takes only 5 minutes.

    Andreas, I recommend that you do the same.

    Monday, June 26, 2017 12:07 PM
  • Im also experiencing the same thing however manual sync works.

    First sync fails, second sync successful for about a month. 

    Also noticed in consistencies within the WSUS and SUP database where by update were not shown in SUP.

    I re-installed WSUS and SUP but now see success in WSUS admin but a failure in SUP.

    I'm going to remove and re-install the system role tomorrow. 

    On the network side, doing a drop packet capture reveals no drops other than the usual UDP.

    Antivirus - reports no blocking of WSUS/SUP activity. 

    Now thinking ISP could be an aspect considering i've ruled out my own network, firewall and AV.

    cheers 

    Monday, August 13, 2018 2:04 PM
  • I've been dealing with this issue off and on for a while (currently dealing with it again). It seems to come down to poor SUSDB performance due to a lack of sufficient maintenance included with WSUS. WSUS retains so much unneeded update data, aka obsolete updates, and it has no built-in mechanism to remove all of that obsolete data automatically. Yes, there is the WSUS cleanup, but none of those jobs seem delete all of the obsolete updates. I believe "obsolete updates" includes previous revisions of updates.

    There are two stored procedures included with SUSDB; one gets obsolete updates (spGetObsoleteUpdatesToCleanup) and the other will delete the updates (spDeleteUpdate). The problem with running the spDeleteUpdate on obsolete updates is that it pretty much causes WSUS to become unavailable. Even after the job ends, SUP never seems to be able to reestablish communications with WSUS and I always just end up rebooting the server to fix SUP. So you can create a scheduled SQL job to run spDeleteUpdate, but you pretty much will need to reboot the server once it has finished. Many times the spDeleteUpdate won't even finish because it will run into a deadlock on an item. It is crap and quite annoying. I am really tired of dealing with failed syncs in SCCM. However, many times the sync does finish enough to run my Automatic Deployment Rules, which is good. It just still returns a failed sync and reruns after an hour.

    Oh, and I have been in contact with Microsoft support on this issue. There solution was to run the stored procedures to cleanup obsolete updates, as well as defrag and re-index tables afterwards. spDeleteUpdate is incredibly slow. It will literally take days to run if you never ran them. If your SUSDB is like mine, you probably have well over 10,000 obsolete updates. Each one can take approximately 20 seconds to delete.
    Tuesday, December 18, 2018 2:44 PM