WSUS post install failed on 2016 Essential server DC

Ralph Westland 1 Reputation point
2021-10-14T07:39:42.01+00:00

After run post install for WSUS on a Server essential 2016 DC server we receive database errors:
ClientConnectionId:ef156204-4956-4309-8cd4-0b7d2c353c62
Error Number:3605,State:1,Class:16
Fatal Error: Schema verification failed for database ‘SUSDB’.
ALTER DATABASE statement failed.
Failed to restart the current database. The current database is switched to master.

SQL query to set database to Master is failed with same error

I removed WSUS, reboot server, Removed WID en reboot server.
Removed all folders of WSUS en WID
Framework 4.7 is not installed
Reinstalled WID en reboot server
Installed WSUS en reboot server
Run post install task en receive the database error

On server server 2016 DC it is running without any problems, only this server give troubles.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,053 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rita Hu -MSFT 9,626 Reputation points
    2021-10-15T02:03:56.443+00:00

    Hello,

    Thanks for your posting on Q&A.

    Please follow the below steps one by one to remove the WSUS completely. There will be something wrong to reinstall the WSUS role if we haven't remove complete:

    To remove WSUS completely, you need to:

    1. Remove the following server roles and features through Server Manager:

    Roles: Windows Server Update Server

    features: Windows Server Update Services Tools(at Remote Server Administration Tools -> Role Administration Tools)

    Follow the wizard prompts to complete the deletion. Then restart the server.
    2. After the server is restarted, manually delete the folder or file of the following path:

    C:\WSUS (this depends on where you choose to install WSUS)

    C:\Program Files\Update Services
    3. Delete database files

    If you use SQL Server Management Studio to delete a database, you can try as follow.

    In Object Explorer, connect to an instance of the SQL Server Database Engine, and then expand that instance. Expand Databases, right-click the database to delete, and then click Delete. Confirm the correct database is selected, and then click OK.

    If you use a WID database, it is recommended to delete the following path folders:

    C:\Windows\WID
    4. In the IIS Information Services (IIS) Manager, manually remove the WSUS Administration site. Then restart the server.

    Or, you can also consider using the Powershell command Remove-WebSite -Name "WSUS Administration" for deletion.

    Please follow the above steps one more time and reinstall the WSUS role. Please share the error logs with us if the issue stays.

    Hope the above will be helpful.

    Regards,
    Rita

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  2. Ralph Westland 1 Reputation point
    2021-10-15T06:52:10.933+00:00

    This installation140803-tmp1f70.txt removal was done several times but still the error as seen in the attached log

  3. Ralph Westland 1 Reputation point
    2021-10-19T15:16:37.44+00:00

    SMSS version 2016 is installed on the server.
    We use the WID database

    Databse deleted, WSUS removed, server reboot.
    WID removed en server reboot
    Folders Windows\wid removed and program files\update server removed.

    Clean install WID and reboot
    Clean install WSUS and reboot
    Post install via powershell.
    Error :
    Fatal Error: Schema verification failed for database ‘SUSDB’.
    ALTER DATABASE statement failed.
    Failed to restart the current database. The current database is switched to master.

    Via SQL query try to set SUSDB database to multi user, failed

    It seems to be a WID problem