locked
WSUS MMC connection error RRS feed

  • Question

  • Hi,

    after a reboot (April updates installation) the WSUS MMC on our 2012r2 server, returns a connection error.

    At boot time the services are all started correctly without any error or warning. Sometimes when we try to start the MMC, an event 7031 (The WSUS Service service terminated unexpectedly ......) is logged in the System Event log, but every time we try to start the MMC an event 7032 (The WSUS administration console was unable to connect to the WSUS Server via the remote API....) is logged in the application log and there are also a lot of event ids 18456 (Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database 'SUSDB'. [CLIENT: <named pipe>]).

    From the IIS side, as far as I can check, telnetting on port 8530 gives a response but the website is not loading.

    Already tried or checked:

    - KB2720211 can give this kind of error but it is not installed on our server

    - Allow service to interact with desktop check box (https://social.technet.microsoft.com/Forums/windowsserver/en-US/d24fe704-1a3d-431d-82b5-d6d004a96ff7/connection-error-wsus-console?forum=winserverwsus )

    - checking/changing the .Net Framework version (https://jamessummerlin.com/2012/08/28/wsus-connection-error/ ) and ( http://www.dell.com/support/article/mk/en/mkdhs1/SLN286548/en )

    Every other article found on the web, ends up by a reinstalling WSUS (!!); has anyone a better suggestion ?

    If reinstalling WSUS is the only way to solve the problem, we would like to keep our settings (groups, downloads, approval settings, .....) and avoid to re-download all the updates; is it possible ?

    Thank you in advance,

    Best Regards,

    Eric

    Saturday, April 23, 2016 8:38 AM

Answers

  • Am 23.04.2016 schrieb Eric.Jaminet:

    after a reboot (April updates installation) the WSUS MMC on our 2012r2 server, 
    returns a connection error.

    At boot time the services are all started correctly without any error or warning. Sometimes when we try to start the MMC, an event 7031 (The WSUS Service service terminated unexpectedly ......) is logged in the System Event log, but every time we try to start the MMC an event 7032 (The WSUS administration console was unable to connect to the WSUS Server via the remote API....) is logged in the application log and there are also a lot of event ids 18456 (Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database 'SUSDB'. [CLIENT: <named pipe>]).

    Deinstall KB3148812 on your WSUS.

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    • Marked as answer by Eric.Jaminet Sunday, April 24, 2016 8:36 AM
    Saturday, April 23, 2016 2:24 PM
  • Winfried is spot on.  Look at MS's latest info about KB3148812:

    http://blogs.technet.com/b/wsus/archive/2016/04/22/what-you-need-to-know-about-kb3148812-part-two.aspx

    I can verify that I updated my WSUS server yesterday and the issue appeared as described.  I uninstalled KB3148812 (per both Winfried and MS's recommendation (link above)) and I'm good to go.

    The KB is designed to prep WSUS for the anniversary update to Windows 10 coming in May.  There is no immediate need to install the broken update as it does not fix any security flaws.  MS will put out a working version before the May date.


    • Edited by Fregi Ventum Saturday, April 23, 2016 2:52 PM
    • Marked as answer by Eric.Jaminet Sunday, April 24, 2016 8:42 AM
    Saturday, April 23, 2016 2:47 PM
  • Hi guys,

    I confirm; after removing KB3148812, WSUS MMC is working back as expected.

    Tanks to both.

    Eric

    Sunday, April 24, 2016 8:42 AM

All replies

  • Am 23.04.2016 schrieb Eric.Jaminet:

    after a reboot (April updates installation) the WSUS MMC on our 2012r2 server, 
    returns a connection error.

    At boot time the services are all started correctly without any error or warning. Sometimes when we try to start the MMC, an event 7031 (The WSUS Service service terminated unexpectedly ......) is logged in the System Event log, but every time we try to start the MMC an event 7032 (The WSUS administration console was unable to connect to the WSUS Server via the remote API....) is logged in the application log and there are also a lot of event ids 18456 (Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database 'SUSDB'. [CLIENT: <named pipe>]).

    Deinstall KB3148812 on your WSUS.

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    • Marked as answer by Eric.Jaminet Sunday, April 24, 2016 8:36 AM
    Saturday, April 23, 2016 2:24 PM
  • Winfried is spot on.  Look at MS's latest info about KB3148812:

    http://blogs.technet.com/b/wsus/archive/2016/04/22/what-you-need-to-know-about-kb3148812-part-two.aspx

    I can verify that I updated my WSUS server yesterday and the issue appeared as described.  I uninstalled KB3148812 (per both Winfried and MS's recommendation (link above)) and I'm good to go.

    The KB is designed to prep WSUS for the anniversary update to Windows 10 coming in May.  There is no immediate need to install the broken update as it does not fix any security flaws.  MS will put out a working version before the May date.


    • Edited by Fregi Ventum Saturday, April 23, 2016 2:52 PM
    • Marked as answer by Eric.Jaminet Sunday, April 24, 2016 8:42 AM
    Saturday, April 23, 2016 2:47 PM
  • Hi guys,

    I confirm; after removing KB3148812, WSUS MMC is working back as expected.

    Tanks to both.

    Eric

    Sunday, April 24, 2016 8:42 AM
  • Hi guys,

    It is a known issue:

    http://blogs.technet.com/b/wsus/archive/2016/04/20/known-issues-with-kb3148812.aspx

    Best Regards,

    Anne


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

    Monday, April 25, 2016 2:54 AM