locked
WSUS 503 service unavialable errors. RRS feed

  • Question

  • # Solarwinds® Diagnostic Tool for the WSUS Agent
    # 3/12/2015
    Windows Update Agent configuration settings
      Automatic Update:                                  Enabled 
      Options:                                           Automatically download and notify of installation 
      Use WSUS Server:                                   Enabled 
      Windows Update Server:                             http://wsus.tech.com 
      Windows Update Status Server:                      http://wsus.tech.com 
      WSUS URLs are identical:                           Identical 
      WSUS URL is valid:                                 Valid URL 
    WSUS Server Connectivity
      clientwebservice/client.asmx:                      OK 
      simpleauthwebservice/simpleauth.asmx:              OK 
      content:                                           Error: ServiceUnavailable (The remote server returned an error: (503) Server Unavailable.)
      selfupdate/iuident.cab:                            Error: ServiceUnavailable (The remote server returned an error: (503) Server Unavailable.)
      iuident.cab:                                       Error: ServiceUnavailable (The remote server returned an error: (503) Server Unavailable.)
    This WSUS server was installed and patched as a stand alone server then joined to a domain in an isolated network. Any client in the isolated network gets the 503 errors for Content and the iuident.cab. All of the clients appear in WSUS but with status of not contacting the server yet. Is there a permissions problem because of the way the server was created?
    Friday, March 13, 2015 2:14 PM

Answers

  • It was a permissions issue, but I don't understand why. The IIS app pool for the default site is using the default app pool with an identity of 'defaultapppool'. The app pool fails when WSUS client tries to connect with 80070005 error in the log (appear to be access is denied). The app pool stops after 5 of these errors are logged. When I change the app pool to use Local System account instead, this problem goes away and clients can connect and get updates.

    What caused this? Something wrong with the original setup?


    • Edited by bmcmcm Friday, March 13, 2015 5:22 PM
    • Marked as answer by Steven_Lee0510 Tuesday, April 7, 2015 8:15 AM
    Friday, March 13, 2015 5:13 PM

All replies

  • Can you restart your WSUS website in IIS and see if it helps? If it does not help, delete the WSUS website and re-install WSUS.

    Thanks,

    Umesh.S.K

    Friday, March 13, 2015 2:40 PM
  • I've restarted the server. Re-installation of WSUS is possible I guess, but I would need to preserve all of the content as the network has no access to the Internet. Is there a guide for this?
    Friday, March 13, 2015 2:48 PM
  • You need to backup the WSUS content. Please check the below links. In the second link follow the steps to backup WSUS and its metadata.

    https://technet.microsoft.com/en-us/library/dd939904%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

    http://blogs.technet.com/b/sus/archive/2009/07/02/how-to-move-wsus-from-one-server-to-another.aspx

    Thanks,

    Umesh.S.K

    Friday, March 13, 2015 3:10 PM
  • It was a permissions issue, but I don't understand why. The IIS app pool for the default site is using the default app pool with an identity of 'defaultapppool'. The app pool fails when WSUS client tries to connect with 80070005 error in the log (appear to be access is denied). The app pool stops after 5 of these errors are logged. When I change the app pool to use Local System account instead, this problem goes away and clients can connect and get updates.

    What caused this? Something wrong with the original setup?


    • Edited by bmcmcm Friday, March 13, 2015 5:22 PM
    • Marked as answer by Steven_Lee0510 Tuesday, April 7, 2015 8:15 AM
    Friday, March 13, 2015 5:13 PM