locked
WSUS Synchronization error RRS feed

  • Question

  • I recently installed SP2 and now I cannto synchronize with Microsoft.   I receive the following error message:

    Please advise.

    Thanks,

    Roger

    WebException: The request failed with the error message:
    --
    <html><head><title>Object moved</title></head><body>
    <h2>Object moved to <a href="%2fmicrosoftupdate%2fv6%2ferrorinformation.aspx%3ferror%3d15">here</a>.</h2>
    </body></html>

    --.
    at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
       at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
       at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

    WSUS is running on Windows Server 2003.

    • Edited by Roger2014 Monday, February 18, 2013 12:21 AM
    Monday, February 18, 2013 12:14 AM

Answers

  • install KB2734608 --It's maybe work for you,I have the same problem with you,and I install this package,but it does not work for me
    • Edited by jun0925 Monday, February 18, 2013 12:49 AM
    • Marked as answer by Lawrence Garvin Monday, February 18, 2013 2:25 PM
    Monday, February 18, 2013 12:49 AM

All replies

  • install KB2734608 --It's maybe work for you,I have the same problem with you,and I install this package,but it does not work for me
    • Edited by jun0925 Monday, February 18, 2013 12:49 AM
    • Marked as answer by Lawrence Garvin Monday, February 18, 2013 2:25 PM
    Monday, February 18, 2013 12:49 AM
  • Hi Lawrence,

    Actually I followed the steps in http://blogs.technet.com/b/sus/archive/2012/06/20/wsus-kb272011-common-issues-encountered-and-how-to-fix-them.aspx  by uninistalling and reinstalling WSUS.  After rebooting the server, I was able to synchronize with Microsoft.  

    It looks fine so far.

    Thanks,

    Roger

    Tuesday, February 19, 2013 1:48 PM
  • Hello,

    Unfortunatley, I spoke too soon.  The following is a summary of events.  If anyone can help, please let me know.

    Summary:
    1. WSUS was running ok except some PCs were suddenly not reporting to the WSUS server
    2.  1/25/13 - Installed WSUS SP2 KB2720211.  After this, those PCs that were not previously reporting started to do so
    3. 2/17/13 - discovered I could not synchronize with Micrsoft on WSUS server
    4. 2/18-13 - based on articles found regarding known issues with KB2720211 the recommendation was to uninstall and reinstall WSUS while keeping the database intact.  After doing this & rebooting I could synchronize with Micrsoft.
    5. 2/19/13 - unfortunately, now the Windows Update Agent on PCs is not working and those pcs show the following error:
    Event Type: Error
    Event Source: Windows Update Agent
    Event Category: Software Sync
    Event ID: 16
    Date:  02/20/2013
    Time:  12:42:20 PM
    User:  N/A
    Computer: AMUSWARWTEST2
    Description:
    Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 57 69 6e 33 32 48 52 65   Win32HRe
    0008: 73 75 6c 74 3d 30 78 30   sult=0x0
    0010: 30 30 30 30 30 30 30 20   0000000
    0018: 55 70 64 61 74 65 49 44   UpdateID
    0020: 3d 7b 30 30 30 30 30 30   ={000000
    0028: 30 30 2d 30 30 30 30 2d   00-0000-
    0030: 30 30 30 30 2d 30 30 30   0000-000
    0038: 30 2d 30 30 30 30 30 30   0-000000
    0040: 30 30 30 30 30 30 7d 20   000000}
    0048: 52 65 76 69 73 69 6f 6e   Revision
    0050: 4e 75 6d 62 65 72 3d 30   Number=0
    0058: 20 00                      .     
    6. Based on this article this is supposed to update the windows update agent on computers.  http://blogs.technet.com/b/sus/archive/2012/09/04/an-update-for-windows-server-update-services-3-0-service-pack-2-is-available-kb2734608.aspx  Although this appeared to be done after first installing KB2720221.
    Does anyone have a recommendation on how to fix this so that PCs will start reporting again as they did after installing KB2720221 before it caused the problem with not synchronizing with Microsoft?  One KB fixes one problems but causes another.

    I also verified that the affected PCs/servers can ping the WSUS server and the self-update tree exists: http://WSUSServerName/selfupdate/wuident.cab

    Thanks,
    Roger

    • Edited by Roger2014 Thursday, February 21, 2013 2:38 PM
    Thursday, February 21, 2013 2:35 PM
  • Update:

    I was able to successfully install KB2734608.  Now the PCs appear to be reporting properly and are being prompted to install updates.  My problem of no Pcs communicating with the WSUS server, happened after I uninstalled WSUS while leaving the database intact and then installing KB972455. Once this was done PCs would not communicate with the WSUS server.

    The one problem that remains is an accurate picture of what updates are really needed for the various PCs.  Once the updates are approved and pushed out through our GPO, the PCs are prompted to install them. 

    However even after they are installed the WSUS console still shows as if they are needed.  If you go to a PC and click on Windows Update to check with Microsoft, the specific updates reflected in WSUS as still being needed do not show up as being needed per Microsoft.

    Does anyone know how to correct this to ensure that WSUS accurately reflects whether or not a PC truly needs a specific update?

    Thanks,
    Roger


    • Edited by Roger2014 Friday, February 22, 2013 5:21 PM
    Friday, February 22, 2013 5:19 PM
  • Thursday, March 21, 2013 9:20 AM
  • In my case I ran into this error when I was installing a new WSUS server on 2008 R2 to replace our older 2003 server.  I installed the roll and the required extras such as IIS that the wizard walked me through.

    Then during the Windows Server Update Services Configuration Wizard I got that same error while trying to do the initial setup sync with Microsoft update.

    I confirmed all routes to Microsoft update were open and working (I could browse to update.microsoft.com in the browser).  After a little thinking I realized that this was an existing server on my domain and that it was still trying to use my existing (and soon to be replaced) WSUS server which is dictated by GPO and is configured in the server's registry.

    I went to HKLM\SOFTWARE\Policies\Windows\WindowsUpdate and then changed the WUServer and WUStatusServer keys to point to http://update.microsoft.com instead of my existing, soon to be replaced, local WSUS server.

    That solved the issue.  The next time I hit that sync button it did some work for a few minutes and then went on to the next step of the initial configuration.

    Tuesday, July 9, 2013 5:17 PM
  • Then during the Windows Server Update Services Configuration Wizard I got that same error while trying to do the initial setup sync with Microsoft update.

    A known issue, discussed in several other threads includign this one. The only proven fix (and the right one even if it something else seems to work) is to install KB2734608. Either KB2720211 or KB2734608 are required updates for a WSUS v3.2 server.

    I went to HKLM\SOFTWARE\Policies\Windows\WindowsUpdate and then changed the WUServer and WUStatusServer keys to point to http://update.microsoft.com instead of my existing, soon to be replaced, local WSUS server.

    That solved the issue. The next time I hit that sync button it did some work for a few minutes and then went on to the next step of the initial configuration.

    I'm not really sure why your sync worked suddenly (although I have seen a couple instances where a second run of the wizard, without KB2734608, has worked, and it may be that KB2734608 isn't required at all, but merely a second run of the setup wizard -- I'm working on scheduling a test of this scenario), but I can tell you with absolute certainty that your success has absolutely nothing to do with reconfiguring those two registry values! :-)

    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.

    Tuesday, July 9, 2013 9:17 PM
  • thnx a lot! it helped@
    Sunday, July 21, 2013 5:38 PM
  • I am receiving the same error after a clean install of wsus on Server 2008 R2. I simply will not synchronize and produces the HTTP error above. I tried installing KB2734608. This allowed the sync to finish but my clients could no longer report in to the WSUS server. WSUS SP1 worked fine. I believe MS has some errors in the SP2. It shouldn't be this complicated.
    Friday, July 26, 2013 11:20 AM
  • As it's a fresh install, did you patch your WSUS server with the KB2720211 ?

    TiGrOu.

    Friday, July 26, 2013 11:39 AM