Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Synchronize from Microsoft updates An http error occurred

Answered Synchronize from Microsoft updates An http error occurred

  • Monday, February 04, 2013 5:29 AM
     
     
    Sign In to Vote
    1

    Unable to sync with upstream server... using 

    Synchronize from Microsoft updates

    Result: An http error occurred 

    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)

    Please advise....

     

All Replies

  • Monday, February 04, 2013 9:07 AM
     
     
    Sign In to Vote
    0

    Had the same problem today.

    After running the assistant for WSUS server configuration again synchronization worked.

    • Proposed As Answer by efgslats Friday, March 08, 2013 2:24 AM
    • Unproposed As Answer by efgslats Friday, March 08, 2013 2:24 AM
    •  
     
  • Monday, February 04, 2013 1:32 PM
     
     
    Sign In to Vote
    0

    Had the same problem today.

    After running the assistant for WSUS server configuration again synchronization worked.

    Same issue here too. Tried running the WSUS server configuration wizard and get the same error around Step 5, when it tried to connect to the upstream

    server to download the type of updates, languages, etc.

     
  • Monday, February 04, 2013 10:54 PM
     
     
    Sign In to Vote
    0
    I'm having the same problem with a new WSUS 3.0 Sp2 box that I built today.  Rerunning the configuration wizard again didn't help.
    • Edited by soloman00 Monday, February 04, 2013 10:55 PM
    •  
     
  • Monday, February 04, 2013 11:08 PM
     
     
    Sign In to Vote
    0
    Thank goodness I found this thread.  Same issue as the rest.  New Windows Server 2008 R2 installation today, trying to stand up WSUS and getting this error.  We do use a proxy server, but I'm using the same configuration that worked before to no avail.
     
  • Monday, February 04, 2013 11:45 PM
     
     
    Sign In to Vote
    0
    Having same issue, had the same issue last night too. Sad face :(
     
  • Tuesday, February 05, 2013 12:25 AM
    Moderator
     
     Answered
    Sign In to Vote
    2

    For those experiencing this issue.... have any of  you experienced the issue after installing KB2720211 or KB2734608.

    Since these all seem to be occurring on new installations ... the thought occurs to me that it might be something deficient in the 3.2.7600.226 build (that installs by default on Win2003/Win2008/Win2008R2), but may not be an issue in build 3.2.7600.251 (KB2720211) or 3.2.7600.256 (KB2734608).

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

    • Marked As Answer by Zhenguang Wednesday, February 06, 2013 2:56 PM
    •  
     
  • Tuesday, February 05, 2013 2:26 AM
     
     
    Sign In to Vote
    0
    I have v3.2.7600.251 installed and am experiencing this problem.
     
  • Tuesday, February 05, 2013 9:42 AM
     
     
    Sign In to Vote
    0

    We've 3 long-established WSUS servers here. All are on W2008R2x64 with WSUS build 3.2.7600.226. Two days ago, two stopped working with this error, one is fine. They all take the same path through the same proxy to the internet.

    One non-standard thing I have here is that all 3 use non-standard-named databases on the same SQL Server. I've had this cause me issues in the past, but it doesn't appear to be related for me at the moment.

    AW

     
  • Tuesday, February 05, 2013 11:17 AM
     
     
    Sign In to Vote
    0

    Just did an ISA server trace. One difference I'm seeing (though it doesn't attempt this every time) is the failing servers attempt to download the following:

    download.windowsupdate.com/v9/wsus/redir/wsusredir.cab?xxxxx
    download.microsoft.com/v9/wsus/redir/wsusredir.cab?xxxx
    www.update.microsoft.com/v9/wsus/redir/wsusredir.cab?xxx

    Where "xxx" is what I presume is my site-specific ID or something, it's different for each server anway, but consistent across each batch of gets.

    This is turning up in the WSUS server logs:

    2013-02-05 11:02:53.990 UTC Info WsusService.36 ServerRedirector.DownloadCab Redirector .cab file successfully retrieved from http://www.update.microsoft.com/v9/wsus/redir/wsusredir.cab?xxxx.
    2013-02-05 11:02:54.006 UTC Warning WsusService.36 ServerRedirector.UpdateMUUrls An exception ocurred while attempting to update the MU URLs: Cannot find the requested object.

    2013-02-05 11:02:54.006 UTC Warning WsusService.36 CatalogSyncAgentCore.ExecuteSyncProtocol Failed to refresh MU URL after a failed catalog sync. Exception: System.Security.Cryptography.CryptographicException: Cannot find the requested object.

       at Microsoft.UpdateServices.ServerSync.ServerRedirector.UpdateMUUrls(UpdateServerConfiguration serverConfig)
       at Microsoft.UpdateServices.ServerSync.ServerSyncLib.RefreshMUUrl(UpdateServerConfiguration serverConfig)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

    I tried to manually download the wsusredir.cabs, but no browser will complete the download.... odd.. !

    Anyone else seeing this?

    AW

     
  • Tuesday, February 05, 2013 12:02 PM
     
     
    Sign In to Vote
    0

    Same Error here...

    Installed WSUS 3.0 SP 2 yesterday on Win2008R2 x64 SP 1 and getting the same error.

     
  • Tuesday, February 05, 2013 12:27 PM
     
     
    Sign In to Vote
    0

    Installed WSUS SP2 40 minutes ago...getting the exact same error.

     
  • Tuesday, February 05, 2013 12:29 PM
     
     
    Sign In to Vote
    0

    Uh oh... Not sure if this is relevant...

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

    Notice
    Revision note, January 11, 2013
    The KB 931125 package that was posted to Windows Update and WSUS on December 11, 2012, was intended only for client SKUs. However, the package was also offered for server SKUs. Because some customers reported issues after they installed the package on servers, the KB 931125 updates for server SKUs were expired from Windows Update and WSUS. We recommend that you sync your WSUS server and approve the expiry.

    If you already applied the update on a server and are encountering issues, you should use the Fix It solution in the following article in the Microsoft Knowledge Base: 

    2801679 SSL/TLS communication problems after you install KB 931125

    I checked. Yes, we rolled this out to our entire estate. However, all 3 WSUS servers appear to have this, so I'm wondering if there's something different in the one that works...

    (edit: tried the fixit, no difference. Not really sure it's relevant to WSUS anyway..)


     
  • Tuesday, February 05, 2013 3:40 PM
     
     
    Sign In to Vote
    0

    I've been having the same issue on our WSUS 3.0 SP2 server. I found one temporary fix which seems to only help for a few days, and then I have to run the commands again.

    (change directory to C:\Program Files\Update Services\Tools)

    •wsusutil configuressl wsus.cha-llp.com
    •net stop wsusservice
    •net start wsusservice
    •net stop bits
    •net start bits
    •iisreset

    I also looked into the KB931125 angle; that update was approved but I don't see it listed in the installed updates list on our WSUS server (I don't know if it would be). I'm hesitant to make a registry change, especially since I am not seeing the event log errors listed in the article and others have reported no difference. I'm really hoping someone (i.e. Microsoft) has a more permanent fix for this. Our issue started after installing KB2720211.

    Michelle Garrah

     
  • Tuesday, February 05, 2013 4:15 PM
     
     
    Sign In to Vote
    0

    The same Error here...

    One new installation of Windows Server 2008 R2 std SP1 with all the updates.

    Michelle Garrah: your temporary fix did not work for me.

    TM

     
  • Tuesday, February 05, 2013 4:20 PM
     
     
    Sign In to Vote
    0
    I'd like to weigh in and say that I am having the same issue. Win2008R2,  SP1, fully patched. and an new install of WSUS 3.0 SP2.
     
  • Tuesday, February 05, 2013 5:17 PM
     
     
    Sign In to Vote
    0

    I disable the UAC (User Account Control) and all works here!!!

    TM

     
  • Tuesday, February 05, 2013 6:29 PM
     
     
    Sign In to Vote
    0

    Just about to head home, but found a difference between the working and not-working WSUS servers.

    Not-working server

    select muurl from tbConfigurationB
    https://www.update.microsoft.com/v6

    The other not-working server

    select muurl from tbConfigurationB
    https://www.update.microsoft.com/v6

    The working server

    select muurl from tbConfigurationB
    https://update.microsoft.com/v6

    I updated the SQL manually to set muurl on one of the non-working ones to be the same as the working one, and rebooted it. It's now apparently synchronizing... (certainly, it's not failing instantly.. but it is suspiciously slow). If anyone fancies a try of this and reporting back, feel free. Proceed at your own risk however, this is a bit dark to say the least... I'm off home to drown my sorrows. Oh, and if anyone can tell me why the new 2012 server I've built to replace these is throwing these, I'd be delighted. Proxy is ISA 2006 and it works fine with 2008 WSUS... Been googling all afternoon :(

    Content file download failed. Reason: Value does not fall within the expected range. Source File: /msdownload/update/v5/eula/xpsp2eula_nor.txt Destination File: c:\wsus\WsusContent\BD\2693E266182E16FFBF8B200A3F0AC9A1ACCAD2BD.txt.

     
  • Tuesday, February 05, 2013 7:04 PM
     
     
    Sign In to Vote
    0

    I synched again and now it works.

    No Changes done - maybe a MS Problem.

    Gz

     
  • Tuesday, February 05, 2013 7:14 PM
    Moderator
     
     
    Sign In to Vote
    0

    Just about to head home, but found a difference between the working and not-working WSUS servers.

    Not-working server

    select muurl from tbConfigurationB
    https://www.update.microsoft.com/v6

    The working server

    select muurl from tbConfigurationB
    https://update.microsoft.com/v6

    I updated the SQL manually to set muurl on one of the non-working ones to be the same as the working one, and rebooted it. It's now apparently synchronizing...

    Most interesting... could simply be a case that 'www.update.microsoft.com' went away (and wasn't supposed to).

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

     
  • Tuesday, February 05, 2013 7:17 PM
     
     
    Sign In to Vote
    0

    Working now. M$ must have fixed it.

     
  • Tuesday, February 05, 2013 8:05 PM
     
     
    Sign In to Vote
    0

    This isn't very cool - these servers went down on the 1st. Whatever's happened has cost me a day in diagnosis, and I've blown one server away to replace it with 2012. And am now stuck with that syncing, but not downloading the updates.

    To say I'm pissed-off would really be putting it mildly...

     
  • Tuesday, February 05, 2013 8:27 PM
     
     
    Sign In to Vote
    0
    Still getting "object moved" error :(
     
  • Tuesday, February 05, 2013 8:37 PM
     
     
    Sign In to Vote
    0
    Still no love for me, though it does look like a Microsoft issue.
     
  • Tuesday, February 05, 2013 8:50 PM
     
     
    Sign In to Vote
    0

    I am setting up a new WSUS 3.0 SP2 on Windows Server 2008 R2 and get the same erorr.

    I manually entered update.microsoft.com as my upstream server, and checked SSL. It took longer and I got the same error.

    Would anyone know if I should use a port different from 80 or 443?

    My thought is, that if www.update.microsoft.com isn't working, perhaps manually configuring it without the www could work.

    I'm using the default internal database so so SQL scripts for me.

    Thoughts?

     
  • Tuesday, February 05, 2013 8:50 PM
     
     
    Sign In to Vote
    0
    fwiw, I'm still having the same issue. no love here, Dr. Jones.
     
  • Tuesday, February 05, 2013 8:54 PM
     
     
    Sign In to Vote
    0

    Thos of you still having issues - please post the value of a "select muurl from tbConfigurationB". Be interesting to see if there's a correlation...

    I've now got 2012 going by poking a hole in the firewall specifically for the WSUS server. Didn't need that before, do now. My 2008 server finished synchronizing but reported 12 new updates, 1294 revised (for missing 4 days!! Suspect this is coz the muurl changed), and 377 expired.

     
  • Tuesday, February 05, 2013 9:00 PM
     
     
    Sign In to Vote
    0
    I have KB2720211 installed, with no luck. 
     
  • Tuesday, February 05, 2013 10:43 PM
     
     
    Sign In to Vote
    0
    Things appear to be getting better - it's not immediately failing.  However, now it's stuck in an endless "Synchronizing..." status.
     
  • Tuesday, February 05, 2013 10:51 PM
    Moderator
     
     Answered
    Sign In to Vote
    10
    Another option.. earlier today we were able to work around the issue by first applying KB2734608 and then running the setup wizard.

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

     
  • Tuesday, February 05, 2013 11:19 PM
     
     
    Sign In to Vote
    0
    Issue appears to be resolved.  I am now able to successfully synchronize and download updates.
     
  • Wednesday, February 06, 2013 1:43 AM
     
     Proposed Answer
    Sign In to Vote
    1
    Applying KB2734608, bouncing wuauserv, and iis (for good measure), took care of this for me. Thank you. 
    • Proposed As Answer by dyvyak Friday, February 15, 2013 12:23 PM
    •  
     
  • Wednesday, February 06, 2013 10:51 AM
     
     Proposed Answer
    Sign In to Vote
    0

    In a german Forum they posted the same problems and a solution: KB2734608 must installed on WSUS, after this, synch is working.

    Winfried

    • Proposed As Answer by dyvyak Friday, February 15, 2013 12:23 PM
    •  
     
  • Wednesday, February 06, 2013 12:19 PM
     
     
    Sign In to Vote
    0
    Jip KB2734608 does the trick, and followed the instructions on the KB itself
     
  • Wednesday, February 06, 2013 12:26 PM
     
     
    Sign In to Vote
    0

    Is it just me, or is KB2734608 not available to deploy through WSUS? It's not showing in my catalog..

    Not impressed that we have to fix a broken WSUS with an update that isn't even available through WSUS... I kinda take it on trust that I update my servers completely through WSUS, and it's still weird that none of my servers have this patch, and yet 1 still works, 1 I got to work by mangling the tbConfigurationB muurl field and 1 rebuilt to 2012...

     
  • Thursday, February 07, 2013 1:10 AM
    Moderator
     
     
    Sign In to Vote
    0

    Is it just me, or is KB2734608 not available to deploy through WSUS? It's not showing in my catalog.

    This is correct Andrew. There are manual implementation steps involved with KB2734608 that just don't make it possible to automate. Plus, to be frank, a significant majority of the installation issues with KB2720211 were a result of the update being approved via WSUS (in many cases without an awareness of what the update even was), so I think it's a Good Thing(tm) that Microsoft has made this update installable only on-demand. Also (until this moment), the update was only needed for WSUS v3 servers that would be used to patch Win8/Win2012 systems, so there wasn't a widespread need. If somebody has made a configuration change on the MU side of things, that puts an entirely different spin on this reality.

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


     
  • Thursday, February 07, 2013 7:35 PM
     
     
    Sign In to Vote
    0

    A bit more data for the list... I have 3 WSUS servers:

    • Windows Server 2008 (x86), WSUS 3.2.7600.251 (KB2720211), installed several years ago.
      I can't access the SQL database to inspect the tbConfigurationB table.
      This server is working fine.
    • Windows Server 2012 (x64), WSUS 6.2.9200.16384, installed about a month ago (02-Jan-2013).
      MUUrl in tblConfigurationB = https://fe1.update.microsoft.com/v6
      This server is working fine.
    • Windows Server 2008 R2 (x64), WSUS 3.2.7600.251 (KB2720211), installed yesterday (06-Feb-2013).
      MUUrl in tblConfigurationB = https://www.update.microsoft.com/v6
      This has the same problem described above.

    On the servers that work ok, I re-ran the WSUS config wizard and clicked "Start Connecting". That worked fine, ie the same operation that failed on the newest server.

    On the server that didn't work, I installed the update from KB2734608, taking the server to 3.2.7600.256. (I rebooted after installing the patch, as per the KB article.) After the reboot, I checked the database again, and MUUrl in tblConfigurationB = https://update.microsoft.com/v6 (ie the "www." bit disappeared). I re-ran the WSUS config wizard, and this time I could connect to the upstream server successfully.

    So, installing the patch solves the problem, but the KB article doesn't mention this issue at all. I assume that Microsoft have restructured their website recently, which kicked this whole thing off.

     
  • Thursday, February 07, 2013 8:22 PM
     
     
    Sign In to Vote
    0
    I installed KB2734608 followed by a reboot, and the synchronizations are running OK so far. I wasn't able to access the SQL database on my WSUS server either to check the tbConfigurationB MUUrl.

    Michelle Garrah

     
  • Thursday, February 07, 2013 8:41 PM
     
     
    Sign In to Vote
    0

    Am 07.02.2013 schrieb Michelle Garrah:

    I installed KB2734608 followed by a reboot, and the synchronizations are running OK so far. I wasn't able to access the SQL database on my WSUS server either to check the tbConfigurationB MUUrl.

    You can download and install the SQL Server Management Studio:
    http://www.microsoft.com/en-us/download/details.aspx?id=29062 Choose
    the right Version. You can connect only if the Studio is installed
    direct on the WSUS-Server. Use this Connection String and Windows
    Authentication: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

    Winfried

    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

     
  • Thursday, February 07, 2013 9:06 PM
     
     
    Sign In to Vote
    0
    Thank you, Winfried, that worked. The MUUrl on my WSUS server is https://update.microsoft.com/v6

    Michelle Garrah

     
  • Friday, February 08, 2013 6:56 AM
     
     
    Sign In to Vote
    0

    Hi,

    After apply KB2720211 - KB2734608 and disable UAC, the synchronization fine works !

    Thanks,

    Fabio Jr. MCP W2K3 Server

     
  • Monday, February 11, 2013 3:22 PM
     
     
    Sign In to Vote
    0
    Synchronizations still aren't working on my WSUS server. They worked for about 3 days after installing KB2734608, then failed over the weekend. My original workaround still helps, but only temporarily.

    Michelle Garrah

     
  • Monday, February 11, 2013 3:30 PM
     
     
    Sign In to Vote
    0
    I'm not sure, but I suspect we have another related problem. At about the same time our MS Directory Synchronization Tool stopped working; we use it to synchronize our employee list with Forefront Online Protection for Exchange. The automatic synch fails, but it runs successfully if I trigger it manually. 

    Michelle Garrah

     
  • Friday, February 15, 2013 12:21 PM
     
     
    Sign In to Vote
    0
    After installing KB2734608 wsus is again able to synchronize with Microsoft. Thanks for help
     
  • Saturday, February 16, 2013 8:11 PM
     
     
    Sign In to Vote
    0

    Just chiming in I also had this issue on Server 2008 R2 WSUS while setting up the role.

    I installed KB2734608, rebooted the server, and now WSUS is doing its initial synchronization without error.

    Thanks!

    • Edited by Ken Templin Saturday, February 16, 2013 9:29 PM
    •  
     
  • Wednesday, February 20, 2013 4:40 PM
     
     
    Sign In to Vote
    0

    Applied KB2734608,  allowed forced restart on Windows Server 2008 R2 SP1, synchronization completed successfully

    fast link for searchers.

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

    Architect, Microsoft Services

     
  • Friday, February 22, 2013 1:43 PM
     
     
    Sign In to Vote
    0

    This works, but a permanent solution would be ideal.

     
  • Friday, March 08, 2013 2:25 AM
     
     
    Sign In to Vote
    0
    Same issue here. It worked yesterday but I did a reinstall, and now the sync doesn't working anymore.
     
  • Friday, March 08, 2013 3:07 PM
     
     
    Sign In to Vote
    0

    The patch fixed the syncronization issue for me.

     
  • Monday, March 25, 2013 7:19 AM
     
     
    Sign In to Vote
    0

    Same issue.

    After installing kb2734608 (http://support.microsoft.com/kb/2734608) synchronization will fine work for me.


     
  • Thursday, March 28, 2013 3:33 PM
     
     
    Sign In to Vote
    0

    Yep I can confirm KB2734608 fixed this error for me

    WSUS Error - 'An HTTP error has occurred'

    Pete

    Regards Pete Long http://www.petenetlive.com

     
  • Thursday, March 28, 2013 7:08 PM
     
     
    Sign In to Vote
    0

    Had the same problem today...I've setup WSUS on a VM earlier today without any problems but because of a snafu on my end had to rebuild the VM from scratch.

    For whatever reason I ran into the same error on my second try, but KB2734608 sorted it out...hooray for Google :-)

     
  • Wednesday, April 17, 2013 5:50 PM
     
     Proposed Answer
    Sign In to Vote
    0
    Had to reinstall WSUS, wouldnt sync, Disabled UAC, rebooted, ran wizard again. all good.
    • Proposed As Answer by DljSchneider Wednesday, April 17, 2013 6:51 PM
    •  
     
  • Wednesday, April 17, 2013 6:29 PM
     
     
    Sign In to Vote
    0

    I had the same issue explained above. I have installed the hotfix KB2734608 and am still having issues downloading some update files. The Update Service appears to be syncing without issues. But I'm getting the 10032 Event ID in event viewer stating "The server is failing to download some updates."

    Is there something else I'm missing. I just upgraded to WSUS 3.0 SP2, then ran the hotfix. Running on Windows Server 2003 R2 Standard Edition, 5.2.3790 SP2 Build 3790

    Any help would be greatly appreciated!

     
  • Wednesday, April 24, 2013 3:11 PM
     
     
    Sign In to Vote
    0
    UPDATE: There were settings in our "New" firewall appliance that was blocking the server. All is good. This was still a very informative thread.
     
  • Wednesday, May 01, 2013 12:19 AM
     
     
    Sign In to Vote
    0

    This is completely anecdotal evidence, but this error seems to only
    appear on the 2nd server and on that connect from the same public IP
    address.  I'm curious if this is something others have noticed as well. 
    The first server always seems to connect, and the rest get the error. 
    Later, when the first server is done synchronizing, the 2nd server works
    but the 3rd and on do not work.

    It appears that only one server
    at the site can sync at the same time - with or without patches.  This
    leads me to believe it may be a limitation on Microsoft's end.

    Can anyone confirm or prove this to be incorrect?

    PH

     
  • Friday, May 03, 2013 3:08 AM
     
     
    Sign In to Vote
    0

    Had the same problem today.

    After running the assistant for WSUS server configuration again synchronization worked.

    Just cancelling the wizard and restaring it manually (Management->WSUS->Options->Wizard) resolved the problem for me aswell!

    <rant> After spending over an hour reinstalling my entirely broken WSUS, an "error" like this pushed my pretty close to complete insanity ;) </rant>

    • Edited by Nachtgilb Friday, May 03, 2013 3:10 AM
    •  
     
  • Wednesday, May 08, 2013 12:50 PM
     
     
    Sign In to Vote
    0
    Same issue. After installing KB2720211 I had to install KB2734608 to get synchronization working again.
     
  • Saturday, May 11, 2013 1:27 PM
     
     
    Sign In to Vote
    0

    i have faced the same problem i,m installing wsus on windows server 2008 R2 at the first time after installation this error occurred 

    i have resolved this error by canceling the auto wizard configuration n re configure it manually ( it works ) 

    however that it seems we have some problem with the synchronization we need to re-synchronize many times till it works 


    • Edited by ALI GHABSHA Saturday, May 11, 2013 1:29 PM
    •