ConfigMgr 2012 Support Tip: WSUS sync fails with HTTP 503 errors


~ Eric Ellis | Senior Support Escalation Engineer

FIX

Here in product support we’ve seen a recent uptick in issues related to WSUS/ConfigMgr sync problems after the last Patch Tuesday, so I wanted to take a minute to mention the issue here, as well as how you can resolve it in case you happen to see it.

The typical scenario is that a customer is running System Center Configuration Manager 2007 (ConfigMgr 2007) or System Center 2012 Configuration Manager (ConfigMgr 2012 or ConfigMgr 2012 R2) and is unable to synchronize their Software Update Point with their WSUS server. A review of the component status messages for the SMS_WSUS_SYNC_MANAGER component on the primary site server reveals errors related to WSUS synchronization which are similar to the following: 

Message ID: 6703
WSUS Synchronization failed. 
Message: The request failed with HTTP status 503: Service Unavailable.
Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer.

When you attempt to open Update Services on the WSUS server you receive the following error:

Error: Connection Error
An error occurred trying to connect to the WSUS server. This error can happen for a number of reasons. Please contact your network administrator if the problem persists. Click the Reset Server Node to connect to the server again.

In addition to the above, attempts to access the URL for the WSUS Administration website (i.e., http://CM12CAS:8530) fails with the error:

HTTP Error 503. The service is unavailable

In this situation, the most likely cause is that the WsusPool Application Pool in IIS is in a stopped state, as shown below.

image

Also, the Private Memory Limit (KB) for the Application Pool is probably set to the default value of 1843200 KB.

image

If you encounter this problem, increase the Private Memory Limit to 4GB (4000000 KB) and restart the Application Pool. To increase the Private Memory Limit, select the WsusPool Application Pool and click Advanced Settings under Edit Application Pool. Then set the Private Memory Limit to 4GB (4000000 KB).

After the Application Pool has been restarted, monitor the SMS_WSUS_SYNC_MANAGER component status, wcm.log and wsyncmgr.log for failures. Please note that it may be necessary to increase the Private Memory Limit to 8GB (8000000 KB) or higher depending on the environment.

More Information

When encountering this issue, the WCM.log from the primary site server will contain numerous entries similar to the following:

3/17/2015 11:31:31 AM Attempting connection to WSUS server: serverName, port: 8530, useSSL: False
3/17/2015 11:31:31 AM System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)
3/17/2015 11:31:31 AM Remote configuration failed on WSUS Server.
3/17/2015 11:31:31 AM STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=serverName.contoso.com SITE=CAS PID=1884 TID=2920 GMTDATE=Tue Mar 17 16:31:31.602 2015 ISTR0="serverName" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
3/17/2015 11:31:31 AM Setting new configuration state to 3 (WSUS_CONFIG_FAILED)

Also, the wsyncmgr.log from the primary site server will contain numerous entries similar to the ones below:

3/17/2015 11:28:41 AM Synchronizing WSUS server serverName
3/17/2015 11:28:41 AM STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CM12TeamCAS.cm12Team.LC SITE=CAS PID=1884 TID=2636 GMTDATE=Tue Mar 17 16:28:41.645 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
3/17/2015 11:28:43 AM Sync failed: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer
3/17/2015 11:28:43 AM STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=serverName SITE=CAS PID=1884 TID=2636 GMTDATE=Tue Mar 17 16:28:43.021 2015 ISTR0="Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer" ISTR1="The request failed with HTTP status 503: Service Unavailable" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
3/17/2015 11:28:43 AM Sync failed. Will retry in 60 minutes

Eric Ellis | Senior Support Escalation Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ 
Data Protection Manager Team blog: http://blogs.technet.com/dpm/ 
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ 
Operations Manager Team blog: http://blogs.technet.com/momteam/ 
Service Manager Team blog: http://blogs.technet.com/b/servicemanager 
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv
The Surface Team blog: http://blogs.technet.com/b/surface/
The Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/


Comments (35)
  1. Anonymous says:

    Thanks for sharing! Increasing Memory Limit solved it!

  2. Anonymous says:

    perfect.

  3. Finny says:

    thanks Eric, good info.

  4. JK says:

    Thank you, thank you… We had the same issue, this solved it…!!!

  5. Jeff K. says:

    Our org. had this issue, thank you so much for posting this.

  6. Oscar P says:

    I had the same problem, I spent hours checking logs and searching the internet. Finally I find this website and my live is on track again. Thanks for your help

  7. RB says:

    Thanks for sharing — this fixed my issue as well.

  8. travis c. says:

    perfect solution.

  9. Jay Valente says:

    You are the man, thanks for all you guys do, great fix.

  10. Matt says:

    Had this issue pop up. Worked like a champ.

  11. Henrik says:

    Thanks, solved the problem 🙂

  12. J.C. Hornbeck Thanks for your effort
    this worked well in my case

  13. Eric Thanks for your effort
    this worked for my case

  14. Thanks we had the exact same issue and it was still happening after the server’s restart: we resolved starting the application pool in IIS. After starting it the WCM, SYNCMGR and CTRL logs returned to normal behavior and the component monitoring turned
    green.

    P.S. in our case the memory limit is set to 0 (I guess means no limit).

  15. Davi Bittencourt says:

    Thanks! Worked. Simple solution.

  16. christophe says:

    Thank you. It worked for me 😉

  17. Ricky says:

    Thanks for that! Dead on was my issue

  18. Perry says:

    Many thanks, Saved us a lot of time.

  19. ReedK24 says:

    Thanks! worked great

  20. sbrown515 says:

    OMG!!!! I feel like Oscar P, my life is back on track again!!! Thank you. I went ahead and bumped my memory up to 8 GB and rebooted the box before I saw it working, but, it’s alive again! Thank you!

  21. Dave says:

    Thanks a lot, this seems to be the fixed. Took a while to find this article unfortunately.

  22. dinesh says:

    Thank you so much, it help me to resolve the issue

  23. JShoe says:

    Been looking at this issue for couple days. Thank you for posting this and saving me another couple.

  24. Jay Robbins says:

    I also had an issue with a fresh install of server 2012R2 and not being able to finish post install tasks. In my case the problem was due to connection limit. For some reason, by default, it was set to 0. Many web sites out there instruct users to delete the web site as a solution.

    A better solution. If you go to the advanced settings of the Wsus Admin web site and expand the Limits section. Max Connections may be set to 0. Set this to something like….100 and it will fix the issue. Fixed it for me and didn’t have to nuke the web page.

  25. Björn Ingi Björnsson says:

    Nice, thank you very much!

  26. [AgK] says:

    Excellent – Thankyou – this had me baffled

  27. I change the private memory but I am still facing the problem

  28. bigjoe says:

    I have the same error in WCM.log, WSUS pool worker is running and has plenty (unlimited) memory.
    In the process of transferring SUP/WSUS to a separate server, I now have two SUPs/WSUS running.

    …The request failed with HTTP status 503: Service Unavailable.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)…

    Is there any other network traffic involved besides the http call on port 8530. (RPC call, WMI ? ) that would require opening extra ports on firewalls?

  29. Jim Williams says:

    Many thanks; this fixed the problem for me too.

  30. Simon says:

    Thank you. This can solve my problem.

  31. Ran Vijay Bharti says:

    This worked like a charm. Thanks for sharing.

  32. Anonymous says:

    thanks perfect solution

  33. Stephen Mills says:

    Thumbs up for this.

    It has fixed my problems so far, thank you.

  34. Albert says:

    Many thanks. This solution works for me.

Comments are closed.

Skip to main content