Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
WSUS3.0 SP2 on w2k8r2 stopped syncing, a firewall issue or else?

Answered WSUS3.0 SP2 on w2k8r2 stopped syncing, a firewall issue or else?

  • Monday, March 18, 2013 9:11 PM
     
     
    Sign In to Vote
    0

    After March 13th updates to servers I noticed WSUS 3.0 SP2 (on w2k8R2) is no longer able to sync for updates. It actually shows the last successfull attempt on March 13th and then no more (all failed), not really sure what did it.

    here is the error in from WSUS console:

    TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. ---> System.Net.WebException: The request failed with HTTP status 400: Bad Request.
    at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args)
       at Microsoft.UpdateServices.ServerSync.ServerSyncLib.GetWebServiceProxyInternal(UpdateServerConfiguration serverConfig, WebServiceCommunicationHelper webServiceHelper, Boolean useCompressionProxy)
       at Microsoft.UpdateServices.ServerSync.ServerSyncLib.GetWebServiceCompressionProxy(UpdateServerConfiguration serverConfig, WebServiceCommunicationHelper webServiceHelper)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.RetrieveSubscriptionData()
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

    in firewall both WSUS related rules are allowed, all clients can connect for updates (over SSL) without trouble, same goes for remote admin consoles (working in plain and SSL mode both).

    It sounds like it sends a bad HTTP request (error 400), but why? what am I missing here?

    I tried installing KB2734608, but it didn't help in resolving the sync fail problem. it still persists.

    just to rule out Firewall issues, I disabled it and it still fails, so re-enabled it back on since it is unrelated.

    any ideas?

    EDIT:

    last server updates installed on March 13th were:

    KB2791765

    KB2806748

    KB2809289

    KB2807986

    KB890830

    • Edited by fenixus Monday, March 18, 2013 9:19 PM
    •  
     

All Replies

  • Monday, March 18, 2013 10:26 PM
     
     Answered
    Sign In to Vote
    0
    installed KB2720211 and after restart it started working! :)
     
  • Wednesday, March 20, 2013 7:48 PM
     
     
    Sign In to Vote
    0

    and bummer

    WSUS reports all clients perfectly fine over both plain mode and SSL mode (tested both ways), but so far I found 2 clients (1x new win7x64 fresh install, other an old 2008 32-bit server recently switched over to WSUS) that will NOT download new updates from it no matter what ... I am stumped. at this point I don't even know if WSUS somehow failed (even though all seems to be green, working OK, clients reporting, etc.) or it's rather IIS7 which is playing some authorization tricks on me... so fed up with that.

    The error being reported in Windows Updates box on clients (when I start I in GUI) says the error is 80244016. The error doesn't show up until after I click Install to pull the detected updates from WSUS (and only from WSUS).

    windowsupdate.log on problem win7 client states also a different error 0x80070020 (package download failed) and that eventually ends up as 0x80244016, reporting works correctly though.

    I also checked IIS7 failed request tracing logs on server and it seems to be reporting those problematic clients with status 500 whenever they try to actually download any (detected) packages ... why?

    tried resetting BITS on those clients, restarting them multiple times to no avail.

    decided to update those clients straight from MS WU website and it's going OK so far. will see if then they will "comply" with WSUS3.0 SP2 on windows 2008 R2.

    what gets me really worried is that I don't know if this WSUS server refuses to work with any clients that want to download updates (e.g. will know that after next patch Tuesday) or it's just those 2 newly registered clients causing trouble (missing some compatibility update)...

     
  • Wednesday, March 20, 2013 8:18 PM
     
     
    Sign In to Vote
    0

    and another update

    after updates were installed (successfully) from MS WU website and restart, clients still couldn't install anything from WSUS (same error). so I went more drastic about it:

    a) deleted problematic (reported as failed) clients from WSUS admin console

    b) restarted those computers

    c) forcefully re-registered using command "wuauclt /resetauthorization /detectnow"

    and BAM! clients were able to successfully pull the rest of updates from WSUS ... however they haven't reported yet though LOL, hopefully they will ...

    ... I actually spent the whole miserable day on making those 2 clients work with my WSUS ... since I have a solution now, I just hope I won't have to repeat that on each of domain members after next Patch Tuesday huh.

    hoping this little thread helps others going through same miserable troubleshooting to make the darned WSUS co-operate with the rest of environment,.,..

     
  • 4 hours 36 minutes ago
    Moderator
     
     
    Sign In to Vote
    0

    I found 2 clients (1x new win7x64 fresh install, other an old 2008 32-bit server recently switched over to WSUS) that will NOT download new updates from it no matter what

    A totally separate issue not related to the original server synchronization issue. Applying available patches KB2720211 or KB2734608 is the proper remediation for unpatched WSUS servers that fail synchronization.

    The error being reported in Windows Updates box on clients (when I start I in GUI) says the error is 80244016.

    This error is an HTTP 400 error .. the URL of the request to the WSUS Server is defective..

    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.


     
  • 3 hours 57 minutes ago
     
     
    Sign In to Vote
    0

    I found 2 clients (1x new win7x64 fresh install, other an old 2008 32-bit server recently switched over to WSUS) that will NOT download new updates from it no matter what

    A totally separate issue not related to the original server synchronization issue. Applying available patches KB2720211 or KB2734608 is the proper remediation for unpatched WSUS servers that fail synchronization.

    The error being reported in Windows Updates box on clients (when I start I in GUI) says the error is 80244016.

    This error is an HTTP 400 error .. the URL of the request to the WSUS Server is defective..

    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.


    actually the issue WAS related somehow to recent switch to WSUS. the URL was set in GPO and was correct for the whole domain (around 40 boxes), but still those 2 clients wouldn't pull updates, but all others assigned to WSUS earlier would.

    I checked their WSUS URLs in registry on 2 problematic boxes, and they were correct and they were having normal connectivity, no firewall issues. The patches you mentioned had not much to do with it ... and I believe they were actually applied ...

    The solution was as I wrote, to delete them from WSUS server and reset authorization, that's all. all started working fine since. never a problem again.


    • Edited by fenixus 3 hours 56 minutes ago
    • Edited by fenixus 3 hours 55 minutes ago
    •