Our WSUS server (Windows Server 2012 R2) hanged when it was installing updates on itself. I rebooted it in a harsh way, it started normally and finished installing the updates. However, now I can't start the WSUS management console due to a connection error. The WSUS server service itself doesn't start as well.
The Application server contains multiple events 18456, source MSSQL$MICROSOFT##WID, message "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database 'SUSDB'. [CLIENT: <named pipe>]" If I try to connect to the server using SQL Server Management Studio, it displays the following error:
"Cannot connect to \\.\pipe\MICROSOFT##WID\tsql\query. Login failed for user 'MY-LOGIN'. (Microsoft SQL Server, Error: 18456)"
The Application even log contains the same event mentioned above, only the message is different: "Login failed for user 'MY-LOGIN'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT:<named pipe>]".
If I restart the Windows Internal Database service, it starts normally and doesn't throw any errors in the Application log. Among other things, it successfully mounts the SUSDB database. No other errors (including DCOM errors) can be found in the log.
Seems that security setting on the WID engine are damaged. Any ideas how to fix them? Besides reinstalling the server, of course? :)
Evgeniy Lotosh // MCSE: Server infrastructure, MCSE: Messaging