locked
wsus configuration manager failed to configure upstream server settings on wsus server RRS feed

  • Question

  • Hello,

    I am receiving the following error in SCCM 2012......

    "wsus configuration manager failed to configure upstream server settings on wsus server"

    I have had a quick search for this issue but am struggling to find any results more recent than 2007 so am concerned the suggested fixes will no longer be relevant.

    We use SCCM 2012 v1602, WSUS v3 SP2 & SCOM 2012R2

    I am also receiving the following alert in SCOM....

    "WSUS Pool - Application pool worker process is unresponsive"

    I believe ports are correctly configured but am happy to check again if needed.

    Is anyone able to offer any advice on this issue?

    Please let me know if any further information or log files are required to diagnose.

    Thanks

    John

    Wednesday, July 5, 2017 5:01 PM

Answers

  • Have you simply started the AppPool again in IIS?

    Have you raised the queue length limit for the apppool?

    Reference: https://blogs.msdn.microsoft.com/the_secure_infrastructure_guy/2015/09/02/windows-server-2012-r2-wsus-issue-clients-cause-the-wsus-app-pool-to-become-unresponsive-with-http-503/

    Have you increased the private memory limit on the AppPool?

    Reference: http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/

    Have you cleaned up the WSUS database?

    Reference: https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, July 5, 2017 5:24 PM

All replies

  • Thought I would provide some information on error logs from SCCM server.......

    Error 5002 - Application pool 'WsusPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

    Error 5013 - A process serving application pool 'WsusPool' exceeded time limits during shut down. The process id was '8676'.

    Wednesday, July 5, 2017 5:21 PM
  • Hello

    See this aticle :

    http://scug.be/blogs/sccm/archive/2009/07/10/sccm-2007-wsus-issues-configuration-manager-failed-to-configure-upstream-settings-on-wsus-server-xxxx.aspx


    Regards, Regin Ravi

    Wednesday, July 5, 2017 5:21 PM
  • Have you simply started the AppPool again in IIS?

    Have you raised the queue length limit for the apppool?

    Reference: https://blogs.msdn.microsoft.com/the_secure_infrastructure_guy/2015/09/02/windows-server-2012-r2-wsus-issue-clients-cause-the-wsus-app-pool-to-become-unresponsive-with-http-503/

    Have you increased the private memory limit on the AppPool?

    Reference: http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/

    Have you cleaned up the WSUS database?

    Reference: https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, July 5, 2017 5:24 PM
  • Thank you for your response Jason, I will run through your suggestions and post the outcome.

    Regards

    John

    Thursday, July 6, 2017 7:48 AM
  • Thanks Jason, the steps which resolved my issue were increasing memory limit and queue length. WSUS is no longer failing.

    Thanks again

    John

    Thursday, July 13, 2017 3:33 PM