locked
WSUS console & service can't start. "Reason: Failed to open the explicitly specified database 'SUSDB'" RRS feed

  • Question

  • 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


    Thursday, April 21, 2016 10:55 AM

Answers

All replies

  • Thursday, April 21, 2016 1:58 PM
  • Thanks. It worked.

    Evgeniy Lotosh // MCSE: Server infrastructure, MCSE: Messaging

    Thursday, April 21, 2016 3:28 PM
  • Works, thanks!
    Friday, May 20, 2016 3:39 PM
    1. If you have KB3148812 - remove it.
    2. If you have KB3159706 - remove it.

    but I read KB article and try some manual steps and that helps.

    https://support.microsoft.com/en-us/kb/3159706

    • Proposed as answer by GudrunTest Monday, June 13, 2016 2:26 PM
    Tuesday, May 24, 2016 1:40 PM
    1. If you have KB3148812 - remove it.
    2. If you have KB3159706 - remove it.

    but I read KB article and try some manual steps and that helps.

    https://support.microsoft.com/en-us/kb/3159706

    I can confirm removing KB3159706 running on Windows Server 2012R2 worked for me.

    Thanks for posting this!

    • Proposed as answer by WIFI Tirol Tuesday, June 14, 2016 1:21 PM
    Tuesday, May 24, 2016 3:38 PM
  • I have WSUS running on Server 2012r2. I did not have KB3148812 but I did have KB3159706.  Instead of removing KB3159706 I performed the manual steps listed in https://support.microsoft.com/en-us/kb/3159706 which fixed my issues.

    Basically the steps boil down to:

    1. Open an elevated Command Prompt and run "C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing
    2. Enable HTTP Activation under .NET Framework 4.5 Features in the Server Manager Add Roles and Features Wizard
    3. Restart the WSUS service

    No need to uninstall KB3159706

    • Proposed as answer by rberntson Thursday, May 26, 2016 2:11 PM
    Wednesday, May 25, 2016 4:51 PM
  • This above by ngroon is much better than uninstalling patches...
    • Edited by rberntson Thursday, May 26, 2016 2:12 PM
    Thursday, May 26, 2016 2:12 PM
  • This is the solution. Thanks.
    Tuesday, May 31, 2016 4:04 PM
  • thanks a lot !!!!!!

    You save me!!!

    Monday, June 13, 2016 1:56 PM
  • I didn't have KB3148812, but did have KB3159706.

    Instead of uninstalling I followed the steps in the link above and it fixed it. 

    Wednesday, June 15, 2016 5:14 AM
  • I did not have KB3148812 installed but did have KB3159706 installed. Uninstalled KB3159706, rebooted the server and now WSUS works fine. Thanks for the info!
    Tuesday, June 21, 2016 5:11 PM
  • I have done that and it didn't fix the problem for me. Only uninstalling the KB3159706 fixed the problem.
    Thursday, June 23, 2016 2:57 AM
  • I have WSUS running on Server 2012r2. I did not have KB3148812 but I did have KB3159706.  Instead of removing KB3159706 I performed the manual steps listed in https://support.microsoft.com/en-us/kb/3159706 which fixed my issues.

    Basically the steps boil down to:

    1. Open an elevated Command Prompt and run "C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing
    2. Enable HTTP Activation under .NET Framework 4.5 Features in the Server Manager Add Roles and Features Wizard
    3. Restart the WSUS service

    No need to uninstall KB3159706

    Its worked for me too.
    Friday, July 1, 2016 10:22 AM
  • Confirming this worked as well! :)

    I also had neither of the updates installed!

    Cheers,
    Ray


    Tuesday, July 12, 2016 10:56 AM
  • This worked for me. Uninstalling KBs didn't work.  Thanks ngroon
    Wednesday, July 20, 2016 6:02 PM
  • This worked for me.

    Many Thanks!

    Thursday, July 21, 2016 10:10 AM

  • Thanks ngroon!  This worked for me too.

    Thursday, July 21, 2016 9:56 PM
  • In my case, I didn't have either KB3148812 or KB3159706.  I ultimately, installed KB3159706, then ran those steps;

    • Open an elevated Command Prompt and run "C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing
    • Enable HTTP Activation under .NET Framework 4.5 Features in the Server Manager Add Roles and Features Wizard
    • Restart the WSUS service

    That worked for me..  spent 2 days on this and was about to wipe the installation and reinstall.  THANKS SO MUCH!!!

    Monday, July 25, 2016 5:59 PM
  • Wanted to point out KB3159706 update is required for windows 10 upgrade distribution through wsus, and so if you have checked this off in wsus you'll have to have this update installed (it will reinstall actually). So follow @ngroon steps to fix this update and get wsus working. MS should release a patch for this

    https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/

    • Proposed as answer by DonPick Saturday, August 13, 2016 11:24 PM
    Monday, August 1, 2016 6:39 PM
  • Thanks! Really Works!

    Vinícius V. A. Terçariol DT Network

    Thursday, August 4, 2016 12:25 AM
  • This is the solution... no need to uninstall anything.

    Thanks rbentson!

    Saturday, August 13, 2016 7:45 PM
  • Saturday, August 13, 2016 11:23 PM
    1. If you have KB3148812 - remove it.
    2. If you have KB3159706 - remove it.

    but I read KB article and try some manual steps and that helps.

    https://support.microsoft.com/en-us/kb/3159706


    https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Saturday, August 13, 2016 11:23 PM
    1. If you have KB3148812 - remove it.
    2. If you have KB3159706 - remove it.

    but I read KB article and try some manual steps and that helps.

    https://support.microsoft.com/en-us/kb/3159706

    I can confirm removing KB3159706 running on Windows Server 2012R2 worked for me.

    Thanks for posting this!


    https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Saturday, August 13, 2016 11:23 PM
  • If you have KB3159706 - remove it.

    This was the cause of my connection problem. Thank you for pointing it out. 
    • Proposed as answer by Eugeny Nikitin Monday, November 7, 2016 7:17 AM
    • Unproposed as answer by Eugeny Nikitin Monday, November 7, 2016 7:17 AM
    Friday, August 26, 2016 1:28 AM
  • If you have KB3159706 - remove it.

    >>>This was the cause of my connection problem. Thank you for pointing it out. 

    Ah, actually, my intention was to encourage you to *install* it (and perform the manual configuration steps detailed in the KB article), not for you to remove it.

    By removing it, you solve the immediate problem but create a problem for the future.


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Friday, August 26, 2016 11:02 AM
  • It worked for me, thanks!

    Wednesday, August 31, 2016 3:54 PM
  • Uninstalling KB3159706 is not a great solution as Windows 10 Anniversary Update requires this for deployment through WSUS. Without KB3159706, you cannot deploy Windows 10.

    Even still, uninstalling KB3159706 did not work for me.

    As for HTTP Activation, my server was already configured that way, so this fix did not work for me. Can't believe this issue has plagued people for so long without a proper patch from Microsoft.

    Friday, September 2, 2016 1:26 PM
  • I have WSUS running on Server 2012r2. I did not have KB3148812 but I did have KB3159706.  Instead of removing KB3159706 I performed the manual steps listed in https://support.microsoft.com/en-us/kb/3159706 which fixed my issues.

    Basically the steps boil down to:

    1. Open an elevated Command Prompt and run "C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing
    2. Enable HTTP Activation under .NET Framework 4.5 Features in the Server Manager Add Roles and Features Wizard
    3. Restart the WSUS service

    No need to uninstall KB3159706

    Just to add that I hit this issue with a 2012R2 server that was freshly built in the last 2 days, so looks like MS still haven't sorted this out, but the above steps have fixed it for me too.

    Thursday, September 15, 2016 3:24 PM
  • Same here.

    Fresh install and update and then WSUS stops working. 

    The steps above worked as a charm! Thanks

    Thursday, September 29, 2016 9:44 AM
  • Thanks for the solution. KB3159706 was the culprit in my case.

    -Thanks AB

    Monday, October 3, 2016 8:27 AM
  • This worked for me, thanks for saving me hours of troubleshooting.

    Ian

    Tuesday, October 18, 2016 6:56 PM
  • removing KB3159706 worked for me, thanks a lot
    Friday, November 25, 2016 10:14 AM
  • Excellent job thanks, works a treat!
    Friday, January 13, 2017 5:26 PM
  • Removing KB3159706 fixed my problem.  Thank you!
    Friday, January 13, 2017 5:35 PM
  • Excellently. Everything works correctly.
    Monday, February 13, 2017 2:39 PM
  • I second rbernston; ngroon's fix worked for me even though I'd already uninstalled KB3159706, whic didn't fix the problem (I didn't have KB3148812).

    Of course, KB3159706 has popped back up as an update so I'm installing it (again) and may well have to revert to the postinstall step. Incidentally, I only needed steps 1 & 3 from ngroon before WSUS started working.

    Friday, February 17, 2017 1:45 PM
  • I can also confirm that removing KB3159706  resolved my issues with WSUS.


    • Edited by DougWatson Wednesday, February 22, 2017 1:36 PM
    Wednesday, February 22, 2017 1:35 PM
  • This steps works fine. Solves the issue without uninstalling any patches.
    Monday, March 6, 2017 11:50 AM
  • Thanks for posting this, I had installed KB3159706 accidently in my one of the primary SCCM site server and all clients were unable to download the patches and failed to patch during scheduled maintenance window, even WSUS console was showing error "Reset Servers Node" "WSUS Service" was going in stopped state, IIS reset SQL services restart, nothing worked, servers reboot didn't work, \Windows\WID\Log\Error.log was showing "SUSDB" is unable to access login failed for associated SVC account, after uninstalling KB3159706 WSUS works like a charm, clients were able to download the patches, Thanks for providing this solution.

    Suggested manual steps to enable HTTP activation in ".Net Framework 4.5" in servers roles and features never worked for me, uninstallation of KB worked for me.

    Tuesday, April 18, 2017 10:44 AM
  • my server was generating 50GB dump logs daily and i have to run a script to clean that

    checked the updates and I did not have KB3148812 but I did have KB3159706 too

    doing steps you mentioned solved the issue immediately

    1. Open an elevated Command Prompt and run "C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing
    2. Enable HTTP Activation under .NET Framework 4.5 Features in the Server Manager Add Roles and Features Wizard
    3. Restart the WSUS service

    Thank you for that.

    Tuesday, April 25, 2017 8:34 AM
  • This procedure did worked for me, but i´m wondering why the procedure of the MS article have more steps:

    https://support.microsoft.com/en-us/help/3159706/update-enables-esd-decryption-provision-in-wsus-in-windows-server-2012-and-windows-server-2012-r2

    why the "simplified" procedure works? Why can´t i do the very sam steps in the article?

    Monday, May 22, 2017 6:03 PM
  • Perfect it works

    Thank you very much

    Andrea

    Friday, May 26, 2017 12:53 PM
  • This is solved my problem! Thank you!

    Tuesday, May 30, 2017 6:18 PM
  • thnx! worked for me
    Sunday, June 4, 2017 12:16 PM
  • first point did the thing on 2016, thanks
    Monday, December 16, 2019 3:49 PM