none
WSUS sync failure after KB2720211

    Question

  • WSUS 3.0 SP2 build 3.2.7600.226 on W2008 R2 Sp1 server, just added the 2720211 update. Sync fails, manual or scheduled. Sync is direct to MS with no proxy involved.

    Sync logs error below - with the 404 suggesting if can't connect to MS server(s).

    The only event logged from WSUS is 10022.

    Stopped/started WSUS and BITS services, restarted server

    A second WSUS server - without the 2720211 update - syncs fine

    Any ideas?

    TIA, Paul C

    "Error type is unknown

    TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. ---> System.Net.WebException: The request failed with HTTP status 404: Not Found.
    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)"

    Tuesday, June 12, 2012 11:35 AM

Answers

  • Hi all,

    404 error from OP fixed!

    Reassociate SSL settings with 'wsusutil configuressl your.full.fqdn.servername' - assuming server name is used for the web site and the ssl cert matches.

    Note: while using SSL on the problem server on 443 it was NOT set as required on any of the IIS component sites, e.g.  ApiRemoting30, just controlled via the group policy settings.

    Cheers, Paul C

    Thursday, June 14, 2012 9:47 AM
  • Yes, issue

    "TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. ---> System.Net.WebException: The request failed with HTTP status 404: Not Found."

    is fixed.

    wsusutil configuressl
    restart wsusservice
    restart bits
    iisreset

    Sync from Microsoft update is now working for me.

    Cheers,
    Paul C

    Thursday, June 14, 2012 10:39 AM
  • My problem is now fixed thanks to a long session with MS remoted in. It appears that the new patch has a side effect of activating some prior security configuration stuff that WSUS had previously effectively ignored). MS ended up following the majority of KB896861 which resolved my issue.

    Thursday, June 14, 2012 11:11 AM

All replies

  • I applied the latest update (2720211) for the WSUS server (3.0 SP2 Build 3.2.7600.226) and I now see this issue, with the same error message, as well. My server OS is Windows 2003 SE SP2.
    This was the only change made to the server, and WSUS is now non-operational. 

    According to the Application Log:  
    The DSS Authentication Web Service is not working.
    The SimpleAuth Web Service is not working.
    The Client Web Service is not working.
    The API Remoting Web Service is not working.
    The Reporting Web Service is not working.
    Self-update is not working.

    According to the System Log:
    The WinHTTP Web Proxy Auto-Discovery Service suspended operation.

    I am able to run Windows Update on this server, so there is no network issue (such as a change firewall) evident. 

    This is my only WSUS server.

    Thank you for reading and thinking about this. Any help would be appreciated.

    Bruce



    Tuesday, June 12, 2012 1:53 PM
  • For comparison I've

    installed WSUS 3.0 SP2 on a spare server.
    configured WSUS for 1 product only
    successfully tested sync
    added the 2720211 update
    restarted
    successfully tested sync

    My 'problem' server also has the web service errors BUT it is configured for SSL and all clients are reporting and getting updates. Those errors have been logged for years. It is only the sync that has failed with the new 10022 error logged.

    Paul C

    Tuesday, June 12, 2012 2:04 PM
  • I attempted to go to the MS windows update server at http://65.55.184.155

    It redirected me here:  http://support.microsoft.com/kb/2497281

    Tuesday, June 12, 2012 2:27 PM
  • Hi Bruce,

    thanks for the link but I can't see any relevance to the issue.

    All clients are connecting, reporting and getting their updates as expected.

    Only sync between the WSUS server and Microsoft is failing........

    Paul C

    Tuesday, June 12, 2012 2:56 PM
  • Hi Paul,

    I'm grasping at straws and following any lead I can get. I agree the probem is WSUS to MS, so I tried to manually connect and was redirected. If the redirection is happening for WSUS, then that IS the problem (I think). I agree with you.

    Thanks

    Bruce



    Tuesday, June 12, 2012 3:11 PM
  • I just wanted to add another data point as I'm seeing similar behavior.  Since applying KB2720211 to my WSUS Server (WSUS 3.0 SP2 on Windows 2008R2) I am unable to sync to Microsoft Update.  The error I'm getting is:

    TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. ---> System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
    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)

    This is with a direct connection - no proxy is in use.  All clients are reporting into the WSUS server fine and the replicas are talking to it fine, the ONLY problem is that the WSUS server cannot sync from Microsoft Update.

    Tuesday, June 12, 2012 6:07 PM
  • Hi,

    Have you tried to uninstall this KB2720211 on your WSUS thru the control panel/programs and features?If the uninstallation doesn't work,pls let me know.

    Regards,
    Clarence
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contacttnmff@microsoft.com.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, June 13, 2012 3:39 AM
  • Clarence,

    KB2720211 does not support uninstallation through the Control Panel.

    Wednesday, June 13, 2012 3:59 AM
  • Hi, Clarence!

    I have the same problem of connectivity to MS Update thru proxy, not directly, such as Bruce_Klines after installing KB2720211 on my WSUS server (3.0 SP2 Build 3.2.7600.226) running on Windows 2003 SE SP2.

    The error is:

    TypeInitializationException: Инициализатор типа "Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy" выдал исключение. ---> System.Net.WebException: Сбой запроса с состоянием HTTP 404: Not Found.
    в Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args)
       в Microsoft.UpdateServices.ServerSync.ServerSyncLib.GetWebServiceProxyInternal(UpdateServerConfiguration serverConfig, WebServiceCommunicationHelper webServiceHelper, Boolean useCompressionProxy)
       в Microsoft.UpdateServices.ServerSync.ServerSyncLib.GetWebServiceCompressionProxy(UpdateServerConfiguration serverConfig, WebServiceCommunicationHelper webServiceHelper)
       в Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.RetrieveSubscriptionData()
       в Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

    Thru the Control Panel I can't uninstall this update.

    May be this is a Microsoft problem, because my another WSUS, connecting to master WSUS, not to Microsoft, after installing this update, work well.

    Thanks

    Michael



    Wednesday, June 13, 2012 5:36 AM
  • I have uninstalled KB2720211 and now have to re setup the service. Will give a update once the server has completed a manual sync. Also while preserving the database, when it came time to do the re-install of WSUS it told me that the current database is corrupt and I will have to create a new one.
    • Edited by AlexZamora Wednesday, June 13, 2012 8:06 AM
    Wednesday, June 13, 2012 8:00 AM
  • I have uninstalled KB2720211
    How can you uninstall this update?
    Wednesday, June 13, 2012 9:03 AM
  • you can't (that I know of), that's why this is so bad
    Wednesday, June 13, 2012 12:24 PM
  • Have just almost exactly the same error myself, only difference is mine claims http 401 even when using a proxy that does not require authentication! No other changes to my config for many months until KB2720211 came along! I have just logged a support call with MS so will see what transpires.

    Wednesday, June 13, 2012 12:51 PM
  • Hey all i got the same issue since KB2720211. I was able to remove the update through programs and features. But still my WSUS is bust.
    Wednesday, June 13, 2012 3:13 PM
  • I had similar issue, but with code
    TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. ---> System.Net.WebException: The request failed with HTTP status 403: Forbidden.

    So i went to http://social.technet.microsoft.com/Forums/en-GB/winserverwsus/thread/e918a191-ef6d-4c4b-b83a-7a4ae20a5217 made all the things - and still no luck.
    Then uninstalled whole WSUS, installed again - and it began to work. (i have configured it to work in SSL way).
    Then, again installed this KB2720211 and it stopped to sync with that error.

    I went to IIS and removed an SSL require - and it began to work back. So i put SSL on all except the website called: ServerSyncWebService inside of Default .
    So maybe this site or component in it somehow related to the issue.
    • Edited by warpil Wednesday, June 13, 2012 4:41 PM
    Wednesday, June 13, 2012 4:28 PM
  • OK Warpil

    Could you walk me through "I went to IIS and removed an SSL require - and it began to work back. So i put SSL on all except the website called: ServerSyncWebService inside of Default ."

    Are you saying you started with ssl enabled some how in IIS?

    Wednesday, June 13, 2012 8:51 PM
  • Yes. There is guide in WSUS , that explains how to enable SSL on WSUS, so with all options as described there - it doesnt work.

    So i open IIS, go to default website (this is my scheme of WSUS, it use default website and ports), then choosing inside of website ServerSyncWebService , and in SSL options i remove the require SSL connection. And then apply.

    And yes, i reinstalled WSUS, enabled SSL options and then installed this KB2720211 .. and after it stopped working =)

    Wednesday, June 13, 2012 9:39 PM
  • Hi everyone,

    The following thread seems to have the same issue with this thread.Pls try to use the following suggestion to see whether the issue can be resolved.

    http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/32b7bdac-be20-4d93-ac17-1d9fb3bbdfd8

    Whether it is resolved or not, pls let me know.

    Thanks.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, June 14, 2012 2:18 AM
  • Issue had already been escalated to Microsoft Product Support Tea. Presently there is no resolution except to reinstall WSUS

    Regards

    Muhammad Adil

    Senior SME- SCS Pro Team

    • Proposed as answer by Adil Muhammad Thursday, June 14, 2012 4:46 AM
    Thursday, June 14, 2012 4:46 AM
  • The following thread seems to have the same issue with this thread.

    Hi, Clarence!

    I think this discussion is not exactly what I need.

    My WSUS databases in good condition. I can maintance it, clients are connected to the server normaly.

    There is only no sync to the Microsoft Update server.

    Any ideas?

    Thursday, June 14, 2012 5:07 AM
  • TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. ---> System.Net.WebException: The request failed with HTTP status 403: Forbidden.
    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)

    Didn't changed or installed anything new. Just began to not syncing again =___=

    ok.
    At the end - i did restart,so it restarted all server and then it stopped to work.
    So, i began to search again and found, that ApiRemote30 site (while it SSL) - the application fails with 403. I've tested this couple of times and its reproduceable. So, meanwhile this site is not require SSL and i success to sync.
    • Edited by warpil Thursday, June 14, 2012 8:55 AM
    Thursday, June 14, 2012 8:20 AM
  • Hi all,

    404 error from OP fixed!

    Reassociate SSL settings with 'wsusutil configuressl your.full.fqdn.servername' - assuming server name is used for the web site and the ssl cert matches.

    Note: while using SSL on the problem server on 443 it was NOT set as required on any of the IIS component sites, e.g.  ApiRemoting30, just controlled via the group policy settings.

    Cheers, Paul C

    Thursday, June 14, 2012 9:47 AM
  • So do you mean everything's fine now?

    Thanks
    Zero

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, June 14, 2012 10:25 AM
  • Yes, issue

    "TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. ---> System.Net.WebException: The request failed with HTTP status 404: Not Found."

    is fixed.

    wsusutil configuressl
    restart wsusservice
    restart bits
    iisreset

    Sync from Microsoft update is now working for me.

    Cheers,
    Paul C

    Thursday, June 14, 2012 10:39 AM
  • Glad to hear that.

    Thanks
    Zero

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, June 14, 2012 10:41 AM
  • My problem is now fixed thanks to a long session with MS remoted in. It appears that the new patch has a side effect of activating some prior security configuration stuff that WSUS had previously effectively ignored). MS ended up following the majority of KB896861 which resolved my issue.

    Thursday, June 14, 2012 11:11 AM
  • Thanks for this Paul. I am now at least able to get into my console now. Just got to get the sync working with MS now. 
    Thursday, June 14, 2012 1:22 PM
  • Following KB896861 posted by msbugger on 2008 using the 2003 instructions worked for me.
    Thursday, June 14, 2012 1:57 PM
  • Not to worry ran the command again and restarted everything. And is now syncing perfectly.
    Thursday, June 14, 2012 2:01 PM
  • Yes, issue

    "TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. ---> System.Net.WebException: The request failed with HTTP status 404: Not Found."

    is fixed.

    wsusutil configuressl
    restart wsusservice
    restart bits
    iisreset

    Sync from Microsoft update is now working for me.

    Cheers,
    Paul C

    I'm happy for you.

    But in my case it doesn't work. :(

    Also does not work and the decision of the KB896861.

    More ideas?


    Friday, June 15, 2012 5:14 AM
  • Not to worry ran the command again and restarted everything. And is now syncing perfectly.
    What the command I need to run again?
    • Proposed as answer by Lucio Sarti Friday, June 15, 2012 7:31 AM
    • Unproposed as answer by Lucio Sarti Friday, June 15, 2012 7:31 AM
    Friday, June 15, 2012 5:15 AM
  • I had the same problem with my WSUS on Windows 2008 R2.

    The command I used are:

    • wsusutil configuressl
    • net stop wsusservice
    • net start wsusservice
    • net stop bits
    • net start bits
    • iisreset

    WSUS now is syncing perfectly.

    Friday, June 15, 2012 7:34 AM
  • I had trouble with the install, so I followed info other threads. my WSUS config and database appear to be gone.

    and the if i remove and attempt to reinstall, I have to blow everything away for the install to succeed

    has anyone seen this?


    Bruce Walters

    Sunday, June 17, 2012 8:38 AM
  • The description for this update

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

    suggests that "you'd better stop [this and that] before applying the update". So presumably if you just let WU install it, nlb, iisreset, wsusservice et al are stopped automatically? Did this not happen for you folks having problems?

    Sunday, June 17, 2012 4:10 PM
  • Found this link:http://social.technet.microsoft.com/Forums/en-CA/winserverwsus/thread/e918a191-ef6d-4c4b-b83a-7a4ae20a5217?prof=required

    It mentions a resolution, One of my colleague tried it on a machine where WSUS was installed on a SBS box and it fixed the issue!

    Have forwarded the steps to Product Support Team.

     

    Regards

    Muhammad Adil

    Senior SME- ConfigMgr Pro Team

    Tuesday, June 19, 2012 5:58 AM
  • I think you have changed the time of domain controller so  a wsus server aldo required a porper restart to run smothly. this command will refresh the WSUS

    Open a command window.

    Type sc config bits start= auto

    Type net stop bits && net start bits

    Type net stop wsusservice && net start wsusservice

    Start WSUS 3.0: Click Start, click Administrative Tools, then click Microsoft Windows Server Update Services v3.0.

    Click Synchronization Results.

    In the Action pane, click Synchronize Now.

    it will work

    Tuesday, June 19, 2012 12:41 PM
  • I think you have changed the time of domain controller so  a wsus server aldo required a porper restart to run smothly. this command will refresh the WSUS

    Open a command window.

    Type sc config bits start= auto

    Type net stop bits && net start bits

    Type net stop wsusservice && net start wsusservice

    Start WSUS 3.0: Click Start, click Administrative Tools, then click Microsoft Windows Server Update Services v3.0.

    Click Synchronization Results.

    In the Action pane, click Synchronize Now.

    it will work

    Don't work in my case...

    Wednesday, June 20, 2012 1:29 PM
  • Call 1-800-Microsoft if you are still having issues and state you have issues with KB2720211.  If you have any issues getting a free call, email me at susan-at-msmvps.com
    Wednesday, June 27, 2012 7:53 PM
  • Calling Microsoft is the only option that worked. As of last night, My WSUS system is fully functional, and I have learned some configuration tips that made reconfiguring the system a breaze (just ask them). Many thanks to James Alwaris at Microsoft.

    Bruce Walters

    Wednesday, June 27, 2012 8:16 PM
  • I had the same problem with my WSUS on Windows 2008 R2.

    The command I used are:

    • wsusutil configuressl
    • net stop wsusservice
    • net start wsusservice
    • net stop bits
    • net start bits
    • iisreset

    WSUS now is syncing perfectly.

    The above resolved my issues after the patch on Windows 2008 SP2.  "Update Services" service was having issues starting at all and even if it did start a vast number of errors were thrown into the application event log.  After applying the above steps, successfuly sync!!

    Log Name:      Application
    Source:        Windows Server Update Services
    Date:          7/17/2012 9:04:11 PM
    Event ID:      10020
    Task Category: 7
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      Server.domain.com
    Description:
    Catalog synchronization is working correctly.

    Wednesday, July 18, 2012 1:11 AM
  • The answer above fixed my issue, cheers.

    I thought it was to do with GPO setings i was applying to my systems to comply with PCI DSS.

    Tuesday, July 24, 2012 12:56 PM
  • Hi this problem fix

    On Command Line (CMD) -> cd "%PROGRAMFILES%\Update Services\Tools"

    1.- wsusutil configuressl your.full.fqdn.servername  (Example: srv1.contoso.local)
    2.- restart wsusservice
    3.- restart bits
    4.- iisreset

    Two sync and fix problem.

    Wednesday, December 19, 2012 7:52 PM
  • Hi this problem fix

    On Command Line (CMD) -> cd "%PROGRAMFILES%\Update Services\Tools"

    1.- wsusutil configuressl your.full.fqdn.servername  (Example: srv1.contoso.local)
    2.- restart wsusservice
    3.- restart bits
    4.- iisreset

    Two sync and fix problem.

    I can confirm that this resolved my issues on an SBS 2011 box - good work.
    Saturday, January 19, 2013 7:44 PM
  • I attempted to go to the MS windows update server at 65.55.184.155

    It redirected me here:  support.microsoft.com/kb/2497281

    So, are you saying that this likely is the reason why the synchronization is failing?

    I am trying to synchronize Windows Server Update Services 3.0 SP1 on a Windows Server 2003 Enterprise SP2 machine.

    I currently have IIS 6.0, .NET Framework 2.0, and Report Viewer 2005 Redistributable.

    I am getting the error that was stated in the original post, and I'm hoping that someone can give me a set of detailed walkthroughs on how to fix this issue.

    Thanks in advance,

    Brent.


    Thursday, April 11, 2013 8:10 PM
  • I am trying to synchronize Windows Server Update Services 3.0 SP1 on a Windows Server 2003 Enterprise SP2 machine.

    You cannot install KB2720211 on a WSUS3SP1 system, and KB2720211 is the topic of this thread.

    First you need to upgrade your WSUS server to Service Pack 2 (released October 2009).

    Then you can install KB2720211, KB2734608 -or- KB2828185 as you see fit for your particular environmental needs.


    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.

    Wednesday, May 29, 2013 5:41 PM
  • Hi this problem fix

    On Command Line (CMD) -> cd "%PROGRAMFILES%\Update Services\Tools"

    1.- wsusutil configuressl your.full.fqdn.servername  (Example: srv1.contoso.local)
    2.- restart wsusservice
    3.- restart bits
    4.- iisreset

    Two sync and fix problem.

    This fixed the issue for us on a VMWare Windows Server 2003 Standard Edition (32-bit).

    Had applied patch KB2734608, which broke our WSUS Server. Then had to reinstall everything.

    After some problems with installing KB2720211, finally managed to get the patch installed.

    Then sync to Microsoft Update kept failing, the quoted solution fixed it for us.

    Thank you very much.

    Friday, June 28, 2013 7:35 AM
  • Paul your method fixed my WSUS updates.

    Thanks a ton

    Cheers

    Aman

    Friday, July 05, 2013 7:37 PM
  • That fixed my issue. Thanks for the info.

    Robert

    Monday, July 15, 2013 7:41 PM