locked
WSUS console connectivity to database issue RRS feed

  • Question

  • Until very recently, the WSUS (v3.0 SP2) on my 2008 R2 server was working well. Recently, I've been having issues with the MMC console connection to the database. 

    The error that I pasted to the clipboard is:

    The WSUS administration console was unable to connect to the WSUS Server Database.
       
    Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL.

    System.Data.SqlClient.SqlException -- Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    The statement has been terminated.

    Source
    .Net SqlClient Data Provider

    Stack Trace:
       at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetSummariesPerUpdate(String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
       at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetSummariesPerUpdate(UpdateScope updatesToInclude, ComputerTargetScope computersToInclude)
       at Microsoft.UpdateServices.UI.AdminApiAccess.BulkUpdatePropertiesCache.GetUpdateSummaries(UpdateScope updateScope, ComputerTargetScope computerTargetScope)
       at Microsoft.UpdateServices.UI.AdminApiAccess.BulkUpdatePropertiesCache.GetAndCacheUpdates(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope)
       at Microsoft.UpdateServices.UI.SnapIn.Pages.UpdatesListPage.GetListRows()

    Any suggestions would be appreciated

    Friday, April 7, 2017 11:14 AM

All replies

  • Am 07.04.2017 schrieb AndyK52:


    The WSUS administration console was unable to connect to the WSUS Server Database.
        Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL.

    System.Data.SqlClient.SqlException -- Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    The statement has been terminated.

    Did you a complete restart from your Server? If yes, pls run a server
    clean up Script.
    https://gallery.technet.microsoft.com/scriptcenter/WSUS-Clean-Powershell-102f8fc6
    first time it could be take a long time. After the script was running
    try to open the MSC again.

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Friday, April 7, 2017 4:16 PM
  • Hi AndyK52,

    1. What is the database do you use for the WSUS server, WID or external SQL server?

    2. What is the version of the WSUS server, if it's not the latest one, please install the related KB to upgrade the WSUS server:

    WSUS version:
    WSUS 3.0 (SP2): Build 3.2.7600.226
    WSUS 3.0 (SP2) + KB2720211: Build 3.2.7600.251
    WSUS 3.0 (SP2) + KB2734608: Build 3.2.7600.256
    WSUS 3.0 (SP2) + KB2828185: Build 3.2.7600.262
    WSUS 3.0 (SP2) + KB2938066: Build 3.2.7600.274

    3. Did you do any change to the WSUS server before the issue occurs?

    4. Please re-index WSUS database on the WSUS server, check if it could help:

    https://technet.microsoft.com/en-us/library/dd939795(v=ws.10).aspx

    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.

    Monday, April 10, 2017 2:16 AM
  • Hi,

    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 19, 2017 2:47 AM
  • Check out my Cleanup Script. It's very comprehensive and is made to be a set and forget system.

    Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need.

    http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus

    What it does:

    1. Remove all Drivers from the WSUS Database.
    2. Shrink your WSUSContent folder's size by declining superseded updates.
    3. Remove declined updates from the WSUS Database.
    4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    5. Compress Update Revisions.
    6. Remove Obsolete Updates.
    7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.
    9. Run the Recommended SQL database Maintenance script on the actual SQL database.
    10. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment, simply run:

    .\Clean-WSUS.ps1 -FirstRun

    and then

    .\Clean-WSUS.ps1 -InstallTask

    If you wish to view or increase the Application Pool Memory Configuration, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.

    Sunday, May 14, 2017 12:51 AM