locked
WSUS service on Server 2012 R2 fails after installing KB4012213 - SQL Server Error "Schema Verification Failed for database SUSDB" RRS feed

  • Question

  • After installing KB4012213 stops running the WSUS service because of WID database access error.

    Error-ID 18456 in event log:

    Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database 'SUSDB'. [CLIENT: <named pipe>]

     

    The susdb database was not accessible so I run the following script.

    use master

    exec sp_resetstatus susdb

    alter database susdb set emergency 

    dbcc checkdb (susdb)

    ALTER DATABASE susdb SET SINGLE_USER WITH ROLLBACK IMMEDIATE

    dbcc checkdb (susdb, repair_allow_data_loss)

    alter database susdb set multi_user

     

    After running the sql script with server management studio 2014, can’t set the ‘susdb’ database into MULIT_USER mode.

    Error: “Schema verification failed for database 'SUSDB' ”

     

    Following error appears with every time the WID log after trying to set to Multi_User mode:

    2017-05-20 22:58:17.13 spid55      Setting database option MULTI_USER to ON for database 'SUSDB'.

    2017-05-20 22:58:17.18 spid55      Starting up database 'SUSDB'.

    2017-05-20 22:58:19.91 spid55      Error: 50000, Severity: 16, State: 1.

    2017-05-20 22:58:19.91 spid55      Verification failed

    2017-05-20 22:58:19.91 spid55      Error: 50000, Severity: 16, State: 1.

    2017-05-20 22:58:19.91 spid55      The following columns are unexpected:

        dbo.sysdiagrams.name.sys.sysname(256)

        dbo.sysdiagrams.principal_id.sys.int(4)

        dbo.sysdiagrams.diagram_id.sys.int(4)

        dbo.sysdiagrams.version.sys.int(4)

        dbo.sysdiagrams.definition.sys.varbinary(-1)

    2017-05-20 22:58:19.91 spid55      Database verification script failed for database 'SUSDB'.

    I found the above table exists now in the susdb database. Our other no R2 replica WSUS Windows server 2012 which have installed the same but with KB4012214 have not this table in that database and have not this issue either.

    The susdb database has still the “Single User” status and cannot be changed into MULIT_USER mode.

     

    Restore of the complete WID\Data\*.* folder from the date before the KB4012213 installation did not help either.

    Any help or idea?


    kailar

    Saturday, May 20, 2017 9:29 PM

Answers

  • As workaround have deleted the table dbo.sysdiagrams and this did help to set the susdb into Multi_User mode. Now the WSUS service runs again after restarting the WEB, DB, WSUSservices.

    I can't say if this was a smart method, but it works now:-(

    Nevertheless I'll be thankful for other ideas.


    kailar

    Monday, May 22, 2017 8:03 AM

All replies

  • As workaround have deleted the table dbo.sysdiagrams and this did help to set the susdb into Multi_User mode. Now the WSUS service runs again after restarting the WEB, DB, WSUSservices.

    I can't say if this was a smart method, but it works now:-(

    Nevertheless I'll be thankful for other ideas.


    kailar

    Monday, May 22, 2017 8:03 AM
  • Hi kailar,

    Glad to hear you have found a workaround to solve the issue and thanks for sharing the solution with us. Then, you may mark your reply as answer, so that the useful information will be highlighted.

    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.

    Tuesday, May 23, 2017 8:12 AM