locked
Repeatedly cannot connect to database RRS feed

  • Question

  • The 2012 R2 WSUS server keeps having failures connecting to the database (default WID) every few days after we ran WSUS maintenance a few weeks ago.

    After someone notices clients aren't updating, restarting the WSUS server usually fixes it, but how can we find the cause so we can get it stable again?

    The server has KB3159706 and we have already ran the manual post installation steps listed in the KB article.


    • Edited by Kalimanne Tuesday, March 21, 2017 3:12 PM
    Tuesday, March 21, 2017 3:11 PM

Answers

All replies

  • Hi Kalimanne,

    >The 2012 R2 WSUS server keeps having failures connecting to the database (default WID) every few days after we ran WSUS maintenance a few weeks ago.

    What is the detailed things did you do to do WSUS maintenance, do you re-index WSUS database?

    Besides, please check if you checked "Drivers" in "Products and Classifications", it's not recommended to check "Drivers".

    Also check WSUS event log to see, if there is any errors.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, March 22, 2017 6:42 AM
  • Yes, I reindexed the database using the instructions and script from this page:

    https://gallery.technet.microsoft.com/scriptcenter/6f8cde49-5c52-4abd-9820-f1d270ddea61#content

    There is sometimes very heavy CPU use from "IIS Worker Process."

    Whenever WSUS fails, the application event log has this error:

    The WSUS content directory is not accessible.
    System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
      at System.Net.HttpWebRequest.GetResponse()
      at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)

    Wednesday, March 22, 2017 5:00 PM
  • It just failed again.

    The event logs says:

    The WSUS administration console was unable to connect to the WSUS Server via the remote API. 

    Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

    System.Net.WebException -- The request failed with HTTP status 503: Service Unavailable.

    Source
    Microsoft.UpdateServices.Administration

    Stack Trace:
       at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

    Wednesday, March 22, 2017 11:09 PM
  • Hi Kalimanne,

    Please also increase the Private Memory Limit of the WSUS site in IIS:

    After then, restart WSUS console.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Thursday, March 23, 2017 3:20 AM
  • Hi Kalimanne,

    Just to check if the above reply could be of help? If yes, you may mark useful reply as answer, if not, welcome to feedback.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, April 5, 2017 8:07 AM