Errors: 7053 & 7032 RRS feed

  • Question

  • Hey

    I just applied an update to my WSUS server (KB4034681 and KB890830) and i now get Event errors 7053 and 7032. WSUS fails to loads and gives the option to reset the node, which again fails.

    After doing a wsustil.exe post install service, it kicked up this:

    Post install is starting
    Fatal Error: A network-related or
    shing a connection to SQL Server.
    . Verify that the instance name is
    allow remote connections. (provide
     open a connection to SQL Server)

    Restarting the server still doesn't work.

    Any ideas?


    Tuesday, August 29, 2017 3:01 PM

All replies

  • I hope you will find this helpful...


    Please click on "Mark as Answer" and “Vote as Helpful” on the post that helps you, this can be beneficial to other community members.

    Tuesday, August 29, 2017 3:04 PM
  • Hi Mark,

    First, I'd suggest you try to remove that updates to see if the issue persists .

    Have you use a separate SQL server for WSUS Server ?

    Also please check the registry key settings which mentioned in the following article :



    Best Regards,


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

    Wednesday, August 30, 2017 9:00 AM
  • As mentioned in the Spiceworks link, my script usually fixes this problem. Version 3.0 is now out too, so here's the info of what it does.

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


    What it does:

    1. Add WSUS Index Optimization to the database to increase the speed of many database operations in WSUS by approximately 1000-1500 times faster.
    2. Remove all Drivers from the WSUS Database (Default; Optional).
    3. Shrink your WSUSContent folder's size by declining multiple types of updates including by default any superseded updates, preview updates, expired updates, Itanium updates, and beta updates. Optional extras: Language Packs, IE7, IE8, IE9, IE10, Embedded, NonEnglishUpdates, ComputerUpdates32bit, WinXP.
    4. Remove declined updates from the WSUS Database.
    5. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    6. Compress Update Revisions.
    7. Remove Obsolete Updates.
    8. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    9. Application Pool Memory Configuration to display the current private memory limit and easily set it to any configurable amount including 0 for unlimited. This is a manual execution only.
    10. Checks to see if you have a dirty database, and if you do, fixes it. This is primarily for Server 2012 WSUS, and is a manual execution only.
    11. Run the Recommended SQL database Maintenance script on the actual SQL database.
    12. 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 so don't over think it. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment (email settings only if you are accepting all the defaults), simply run:

    .\Clean-WSUS.ps1 -FirstRun

    If you wish to view or increase the Application Pool Memory Configuration, or run the Dirty Database Check, 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.

    Adam Marshall, MCSE: Security

    • Proposed as answer by Elton_Ji Friday, September 15, 2017 8:58 AM
    Saturday, September 2, 2017 2:07 AM