none
Still having problems after installing 3159706 RRS feed

  • Question

  • I’m still having problems with this.

    KB3148812 had been installed and WSUS stopped working, clients were unable to check for updates. Did some research and uninstalled it.

    Later installed 3159706 via Windows Update – no restart notification displayed but WSUS was still not starting (saw a ‘Reset server node’ message which did not work). Rebooted, Server Manager flagged WSUS Service as not started on restart, but a refresh showed it was started. Ran WSUS, but saw same message.

    Copied error and followed recommendation to delete wsus file at %appdata%\Microsoft\MMC\. WSUS now starts, but the server was not listed. Chose to connect to the server but an error message about SQL not running was displayed (port is correct: 8530). All SQL services seem to be running.

    Any suggestions, please?

    Thanks

    --

    Here's the error from the console:

    **********************************************************************

    The WSUS administration console was unable to connect to the WSUS Server via the remote API.

    Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

    The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,

    Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.


    System.IO.IOException -- The handshake failed due to an unexpected packet format.

    Source
    System

    Stack Trace:
       at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
       at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
       at System.Net.ConnectStream.WriteHeaders(Boolean async)
    ** this exception was nested inside of the following exception **


    System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.

    Source
    Microsoft.UpdateServices.Administration

    Stack Trace:
       at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
       at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

    **********************************************************************

    Friday, May 6, 2016 10:15 AM

Answers

  • I’m still having problems with this.

    KB3148812 had been installed and WSUS stopped working, clients were unable to check for updates. Did some research and uninstalled it.

    Later installed 3159706 via Windows Update – no restart notification displayed but WSUS was still not starting (saw a ‘Reset server node’ message which did not work). Rebooted, Server Manager flagged WSUS Service as not started on restart, but a refresh showed it was started. Ran WSUS, but saw same message.

    Copied error and followed recommendation to delete wsus file at %appdata%\Microsoft\MMC\. WSUS now starts, but the server was not listed. Chose to connect to the server but an error message about SQL not running was displayed (port is correct: 8530). All SQL services seem to be running.

    Any suggestions, please?

    Thanks

    --

    Here's the error from the console:

    **********************************************************************

    The WSUS administration console was unable to connect to the WSUS Server via the remote API.

    This error results from not running the post-install command.  Since you installed from Windows Update, you might have missed the guidance: https://support.microsoft.com/en-us/kb/3159706

    Note that the installation is not complete until these manual steps have been performed. 

    • Marked as answer by Mark-Blood Monday, May 9, 2016 7:44 AM
    Friday, May 6, 2016 9:45 PM
    Moderator

All replies

  • More info:

    I have just checked the Application log after trying to start WSUS and noticed the same event that led to the info about the initial update problems:

    Event: 18456 Source: MSSQL$MICROSOFT##WID

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

    --

    Full event info:

    Log Name:      Application
    Source:        MSSQL$MICROSOFT##WID
    Date:          06/05/2016 11:55:13
    Event ID:      18456
    Task Category: Logon
    Level:         Information
    Keywords:      Classic,Audit Failure
    User:          NETWORK SERVICE
    Computer:      Janus.htlincs.local
    Description:
    Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database 'SUSDB'. [CLIENT: <named pipe>]
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSSQL$MICROSOFT##WID" />
        <EventID Qualifiers="49152">18456</EventID>
        <Level>0</Level>
        <Task>4</Task>
        <Keywords>0x90000000000000</Keywords>
        <TimeCreated SystemTime="2016-05-06T10:55:13.000000000Z" />
        <EventRecordID>165594</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Janus.htlincs.local</Computer>
        <Security UserID="S-1-5-20" />
      </System>
      <EventData>
        <Data>NT AUTHORITY\NETWORK SERVICE</Data>
        <Data> Reason: Failed to open the explicitly specified database 'SUSDB'.</Data>
        <Data> [CLIENT: &lt;named pipe&gt;]</Data>
        <Binary>184800000E000000150000004A0041004E00550053005C004D004900430052004F0053004F0046005400230023005700490044000000070000006D00610073007400650072000000</Binary>
      </EventData>
    </Event>

    Friday, May 6, 2016 11:11 AM

  •  I have run into the exact same issue. Its the same as KB3148812. I had to uninstall kb3159706 to resolve the problem. Do not install the latest fix!
    Friday, May 6, 2016 1:08 PM
  • I’m still having problems with this.

    KB3148812 had been installed and WSUS stopped working, clients were unable to check for updates. Did some research and uninstalled it.

    Later installed 3159706 via Windows Update – no restart notification displayed but WSUS was still not starting (saw a ‘Reset server node’ message which did not work). Rebooted, Server Manager flagged WSUS Service as not started on restart, but a refresh showed it was started. Ran WSUS, but saw same message.

    Copied error and followed recommendation to delete wsus file at %appdata%\Microsoft\MMC\. WSUS now starts, but the server was not listed. Chose to connect to the server but an error message about SQL not running was displayed (port is correct: 8530). All SQL services seem to be running.

    Any suggestions, please?

    Thanks

    --

    Here's the error from the console:

    **********************************************************************

    The WSUS administration console was unable to connect to the WSUS Server via the remote API.

    This error results from not running the post-install command.  Since you installed from Windows Update, you might have missed the guidance: https://support.microsoft.com/en-us/kb/3159706

    Note that the installation is not complete until these manual steps have been performed. 

    • Marked as answer by Mark-Blood Monday, May 9, 2016 7:44 AM
    Friday, May 6, 2016 9:45 PM
    Moderator
  • KB3148812 had a specific defect that was broadly affecting customers who installed it; as such, we recommended that it be uninstalled while we worked out a fix.  KB3159706 is that fix, and it should not be skipped or uninstalled as a long-term resolution for the symptoms described in this thread.

    These failures are expected until you've run the steps described in https://support.microsoft.com/en-us/kb/3159706.

    Friday, May 6, 2016 9:48 PM
    Moderator
  • Hi all,

    After installing 3159706 I still have the same issues and I have run the WSUSUtil postinstall /servicing command.

    Got into the console but it failed again after a short while.

    Errors in WSUS log.

    The last catalog synchronization attempt was unsuccessful.

    The Reporting Web Service is not working.

    The Reporting Web Service is not working.

    The Server Synchronization Web Service is not working.

    The Client Web Service is not working.

    The SimpleAuth Web Service is not working.

    The DSS Authentication Web Service is not working.

    The WSUS content directory is not accessible.
    System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
    at System.Net.HttpWebRequest.GetResponse()
    at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)

    The WSUS administration console was unable to connect to the WSUS Server via the remote API.
    Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
    The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
    Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.System.IO.IOException -- The handshake failed due to an unexpected packet format.
    Source
    System


    Jens Ole Kragh, MCITP Server/Client, MCTS, MCT, Microsoft TechNet Influent Denmark,Blog: http://jensolekragh.wordpress.com/

    Saturday, May 7, 2016 6:57 AM
  • OK - after deleting the %appdata%\Microsoft\MMC file, the MMC said that postinstall wasn't run, when I tried to connect to the server from the WSUS MMC. (it was run with success earlier)

    I then ran wsusutil postinstall SQL_INSTANCE_NAME=servername CONTENT_DIR=E:\WSUS

    I get "Fatal error: The object identifier does not represent a valid object. (Exception from HRESULT: 0x800710D8)

    It seems like an IIS problem ?

    WSUS postinstall log:

    2016-05-07 09:05:43  Start: ConfigureWebsite
    2016-05-07 09:05:44  Configuring website on port 8530
    2016-05-07 09:06:32  System.Runtime.InteropServices.COMException (0x800710D8): The object identifier does not represent a valid object. (Exception from HRESULT: 0x800710D8)

    at Microsoft.Web.Administration.Interop.IAppHostMethodInstance.Execute()
       at Microsoft.Web.Administration.ConfigurationElement.ExecuteMethod(String methodName)
       at Microsoft.Web.Administration.ApplicationPool.Recycle()
       at Microsoft.UpdateServices.Administration.UseCustomWebSite.CreateWebsite(Int32 newPortNumber)
       at Microsoft.UpdateServices.Administration.PostInstall.ConfigureWebsite(Int32 portNumber)
       at Microsoft.UpdateServices.Administration.PostInstall.Run()
       at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)


    Jens Ole Kragh, MCITP Server/Client, MCTS, MCT, Microsoft TechNet Influent Denmark,Blog: http://jensolekragh.wordpress.com/


    Saturday, May 7, 2016 7:24 AM
  • KB3148812 had a specific defect that was broadly affecting customers who installed it; as such, we recommended that it be uninstalled while we worked out a fix.  KB3159706 is that fix, and it should not be skipped or uninstalled as a long-term resolution for the symptoms described in this thread.

    These failures are expected until you've run the steps described in https://support.microsoft.com/en-us/kb/3159706.

    Thank you, Steve - ran the post-install task. The http activation service was already checked. Restarted the WSUS service and everything sprang back into life.

    Cheers!

    Monday, May 9, 2016 7:43 AM
  • You have got to be f&*()ing kidding me!!  A run of windows updates causes WSUS to fail unless manual steps are taken to fix it.  What utter moron allowed this to happen?  Somebody needs to be fired.  I have dozens of clients that will need to have these manual fixes done.  This is totally and absolutely unacceptable.  Pull this patch until it works properly without intervention!!!!!

    Old enough to know better, young enough to try anyway

    Wednesday, May 11, 2016 1:23 AM
  • We're working on it, Mordock.  WSUS used to be serviced as a separate product, using service packs that performed this reconfiguration as part of the update.  When the role moved in-box starting with Windows Server 2012, that process detail might have been overlooked, resulting in such post-installation tasks.

    Unfortunately, this is the way the product is today, but our team is prioritizing a smoother experience going forward.  If possible, we will not ship another WSUS update until this scenario is improved. Note that we can only automate modifications to WSUS itself: IIS configurations will still have to be done manually, as there's no clean way to automate this.

    Wednesday, May 11, 2016 6:16 AM
    Moderator
  • I have dozens of clients that will need to have these manual fixes done

    Can you share more about these clients that require manual intervention?  It should only be the WSUS server(s) that needs anything.  It's manual and a nuisance, sure, but it isn't dozens of clients... what's happening in your environment?
    Wednesday, May 11, 2016 6:18 AM
    Moderator
  • On many of the WSUS servers I support, the steps for 3159706 have worked and have successfully restored functionality. However, on one WSUS server the console is still broken. 3148812 was uninstalled last week, and 3159706 was installed today. HTTP activation was added successfully. The wsusutil postinstall command runs for about two seconds (it usually takes a minute or two) and indicates completion, but the console is still broken. Event logs filled with 507 and 7053 errors. Very disconcerting. Please advise.

    UPDATE: when I try to run the the command Jens lists above (wsusutil postinstall specify sql instance and content dir) it runs for a while then gives this error:

    Fatal Error: Failed to start and configure the WSUS service


    Doug Kinzinger, MCSE


    Wednesday, May 11, 2016 3:35 PM
  • KB3148812 had a specific defect that was broadly affecting customers who installed it; as such, we recommended that it be uninstalled while we worked out a fix.  KB3159706 is that fix, and it should not be skipped or uninstalled as a long-term resolution for the symptoms described in this thread.

    These failures are expected until you've run the steps described in https://support.microsoft.com/en-us/kb/3159706.

    Running the manual steps fixed the issue for me
    Thursday, May 12, 2016 2:00 AM
  • KB3148812 had a specific defect that was broadly affecting customers who installed it; as such, we recommended that it be uninstalled while we worked out a fix.  KB3159706 is that fix, and it should not be skipped or uninstalled as a long-term resolution for the symptoms described in this thread.

    These failures are expected until you've run the steps described in https://support.microsoft.com/en-us/kb/3159706.

    Not everyone is too familiar with WsusUtil. To make life easier you could add this crucial information to the article (output from WsusUtil.exe help postinstall):

    EXAMPLES

    Run postinstall for a WSUS server using the WID role and the default content directory:

        wsusutil postinstall

    Run postinstall for a WSUS server using the WID role to store downloaded update files in the directory C:\WSUS:

        wsusutil postinstall CONTENT_DIR=C:\WSUS

    Run postinstall for a WSUS server using the Database role, where the SQL Serveris installed on machine MYSQLSRV:

        wsustil postinstall SQL_INSTANCE_NAME=MYSQLSRV

    Run postinstall for a WSUS server using the Database role, where the SQL Server is installed on the same machine as the WSUS server and update files will be stored in the C:\WSUS directory:

        wsusutil postinstall SQL_INSTANCE_NAME=localhost CONTENT_DIR=C:\WSUS


    Rolf Lidvall, Swedish Radio (Ltd)

    Thursday, May 12, 2016 8:35 AM
  • Not everyone is too familiar with WsusUtil. To make life easier you could add this crucial information to the article (output from WsusUtil.exe help postinstall):

    EXAMPLES

    Run postinstall for a WSUS server using the WID role and the default content directory:

        wsusutil postinstall

    Run postinstall for a WSUS server using the WID role to store downloaded update files in the directory C:\WSUS:

        wsusutil postinstall CONTENT_DIR=C:\WSUS

    Run postinstall for a WSUS server using the Database role, where the SQL Serveris installed on machine MYSQLSRV:

        wsustil postinstall SQL_INSTANCE_NAME=MYSQLSRV

    Run postinstall for a WSUS server using the Database role, where the SQL Server is installed on the same machine as the WSUS server and update files will be stored in the C:\WSUS directory:

        wsusutil postinstall SQL_INSTANCE_NAME=localhost CONTENT_DIR=C:\WSUS


    Rolf Lidvall, Swedish Radio (Ltd)

    Do you still have to add the /servicing to the command? I also cannot find any documentation about the servicing switch.

    One thing I find odd is that when you have SCCM they explicitly tell you not to configure WSUS from WSUS itself but let SCCM do it for you. This KB goes against all these recommendations... *sigh*

    Thursday, May 12, 2016 8:41 AM
  • We installed 3159706, and did the post install manual steps https://support.microsoft.com/en-us/kb/3159706, the WSUS console is working, but clients is reporting error 80244008 and 8024401F, even from the WSUS server itself...?

    Any ideas?


    HUBH

    Friday, May 13, 2016 9:01 AM
  • We installed 3159706, and did the post install manual steps https://support.microsoft.com/en-us/kb/3159706, the WSUS console is working, but clients is reporting error 80244008 and 8024401F, even from the WSUS server itself...?

    Any ideas?


    HUBH

    Same situation here, did you resolve this? All my clients/servers now reporting 8024401F when attempting to check for updates... unbelievable.
    Wednesday, May 18, 2016 2:54 PM
  • It appears you only need to make changes to the web.config file if your WSUS server is SSL enabled, which mine isn't... doh

    Reverted the changes and now everything is working again, did you miss this too HUBH?

    • Proposed as answer by danbro92 Thursday, August 18, 2016 10:59 AM
    Thursday, May 19, 2016 7:38 AM
  • I have installed this patch and run the post-installation command.  HTTP activation was already checked so I didn't have to do anything there.  I rebooted and was at least able to get the Update Services console open, but every time I try to check on my client computers or on updates available that I need to approve, I get timeouts connecting to the database.  I'm using WID Database for my WSUS installation.  It tells me to try restarting SQL, but since I'm using a WID database, SQL isn't installed.  Here's the error message I get:

    The WSUS administration console was unable to connect to the WSUS Server Database.
        
    Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL.
        

    System.Data.SqlClient.SqlException -- Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    The statement has been terminated.

    Source
    .Net SqlClient Data Provider

    Stack Trace:
       at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetSummariesPerUpdate(String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
       at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetSummariesPerUpdate(UpdateScope updatesToInclude, ComputerTargetScope computersToInclude)
       at Microsoft.UpdateServices.UI.AdminApiAccess.BulkUpdatePropertiesCache.GetUpdateSummaries(UpdateScope updateScope, ComputerTargetScope computerTargetScope)
       at Microsoft.UpdateServices.UI.AdminApiAccess.BulkUpdatePropertiesCache.GetAndCacheUpdates(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope)
       at Microsoft.UpdateServices.UI.SnapIn.Pages.UpdatesListPage.GetListRows()


    Thursday, May 19, 2016 5:19 PM
  • Have you checked your system logs for WID authentication errors etc? If there are any errors post them.
    Thursday, May 19, 2016 7:43 PM
  • Hi Guys,

    I had lot's of issues with Clients throwing the known error messages when contacting the WSUS.

    Í also tried to the post install steps mentioned in the KB.

    Now, I finally found a solution and this might be especially interesting to Microsoft:

    File:
    C:\Program Files\Update Services\WebServices\ClientWebService\Web.Config

    Last 5 lines Before:

            <!-- Requires AspNetCompatibility mode -->
            <serviceHostingEnvironment aspNetCompatibilityEnabled="true" />
    	multipleSiteBindingsEnabled="true" />
           </system.serviceModel>
    </configuration>

    I instantly spotted the false line-break / double end characters.
    So, I corrected the lines:

            <!-- Requires AspNetCompatibility mode -->
            <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />
           </system.serviceModel>
    </configuration>

    Guess what?

    After a WSUS Restart, all is working beautifully again.

    Basically, the KB article says that you should add the final parameter to the line, however in our case it was already present but with a false code. If you're clever, you may find this out easily, but I thought I would still point it out here.

    • Proposed as answer by BundyH Friday, June 3, 2016 8:09 AM
    Friday, May 20, 2016 2:32 PM
  • Steve,

    I've tried patching and performing the post-install steps 4 times and failed 4 times.  I've rolled back the server and the database each time and tried to do clean, and it always fails. When I run the post-install script, the logs just shows the following:

    2016-05-24 13:24:45  Postinstall started
    2016-05-24 13:24:45  Detected role services: Api, UI, Services
    2016-05-24 13:24:45  Start: LoadSettingsForServicing
    2016-05-24 13:24:45  End: LoadSettingsForServicing
    2016-05-24 13:24:45  Stopping service WSUSService
    2016-05-24 13:24:46  Stopping service W3SVC
    2016-05-24 13:24:47  Starting service W3SVC
    2016-05-24 13:24:47  Starting service WSUSService
    2016-05-24 13:24:48  Postinstall completed

    After I perform all steps, I still just get the "Reset Server Node" error in the console.  I don't know where to go from here, but I've put about 10 hours into this process, and am about ready to give up.  (Rolling back the DB and VM does bring WSUS back online, but this patch just will not work for me).  Any suggestions?


    Janssen Jones - Virtual Machine MVP -http://www.janssenjones.com - Please remember to mark answers as answers. :)

    Tuesday, May 24, 2016 5:29 PM
  • I'm having a similar problem. I've run the post install a few times, tried with and without the modified web.config file.  Everything broke after April batch of updates run a bit late as I am on maternity leave and not replaced, so I'm doing this over VPN with a baby crying at me too!  Would like to be done with it!

    I have been getting the reset server node error and have this in event viewer repeatedly: Information 25/05/2016 14:20:39 MSSQL$MICROSOFT##WID 18456 Ouverture de session  (logon) detail is

    Échec de l'ouverture de session de l'utilisateur 'AUTORITE NT\SERVICE RÉSEAU'. Raison : impossible d'ouvrir la base de données spécifiée explicitement 'SUSDB'. [CLIENT : <named pipe>]  (log on failed...impossible to open the database SUSDB)

    I've tried adding permissions to the serveur logon as service in one of my gpos, and I have a new error saying it can't find the SID...Avertissement 25/05/2016 14:20:01 SceCli 1202 Aucun 

    I checked the log and found Windows is not able to map  MSSQL$MICROSOFT##WID to an SID

    Windows Update log has the following:

    2016-05-25 14:23:04:956 1140 1ff0 PT WARNING: Cached cookie has expired or new PID is available
    2016-05-25 14:23:04:956 1140 1ff0 EP Got WSUS SimpleTargeting URL: "http://Srv-003-pc:8530"
    2016-05-25 14:23:04:956 1140 1ff0 PT Initializing simple targeting cookie, clientId = a31aab67-b583-4de6-86b9-650641714c89, target group = , DNS name = MYSERVER
    2016-05-25 14:23:04:956 1140 1ff0 PT   Server URL = http://Srv-003-pc:8530/SimpleAuthWebService/SimpleAuth.asmx
    2016-05-25 14:23:05:467 1140 1ff0 WS WARNING: Nws Failure: errorCode=0x803d0013
    2016-05-25 14:23:05:467 1140 1ff0 WS WARNING: Le corps du message reçu contenait une erreur. (msg body contains error)
    2016-05-25 14:23:05:467 1140 1ff0 WS WARNING: Soap fault info:
    2016-05-25 14:23:05:467 1140 1ff0 WS WARNING: reason: System.Web.Services.Protocols.SoapException: Fault occurred
       à Microsoft.UpdateServices.Internal.SimpleAuth..ctor()
    2016-05-25 14:23:05:467 1140 1ff0 WS WARNING: code: Server
    2016-05-25 14:23:05:467 1140 1ff0 WS WARNING: detail: <detail><ErrorCode>InternalServerError</ErrorCode><Message></Message><ID>051f7593-ab6b-47f2-86ca-87539c71ffb3</ID><Method>"</detail">http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie"</Method></detail>
    2016-05-25 14:23:05:467 1140 1ff0 WS FATAL: OnCallFailure(hrCall, m_error) failed with hr=0x80244007
    2016-05-25 14:23:05:467 1140 1ff0 WS FATAL: NwsCallWithProxyRetry<Functor>( Functor(_clientId, _targetGroupName, _dnsName, &_result)) failed with hr=0x80244007
    2016-05-25 14:23:05:467 1140 1ff0 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244007
    2016-05-25 14:23:05:467 1140 1ff0 PT WARNING: PopulateAuthCookies failed: 0x80244007
    2016-05-25 14:23:05:467 1140 1ff0 PT WARNING: RefreshCookie failed: 0x80244007
    2016-05-25 14:23:05:467 1140 1ff0 PT WARNING: RefreshPTState failed: 0x80244007
    2016-05-25 14:23:05:467 1140 1ff0 PT WARNING: PTError: 0x80244007
    2016-05-25 14:23:05:467 1140 1ff0 Report WARNING: Reporter failed to upload events with hr = 80244007.

    Any ideas out there? If I remove the wsus role and readd it will the problem be corrected?


    • Edited by KCSPI76 Wednesday, May 25, 2016 12:33 PM
    Wednesday, May 25, 2016 12:32 PM
  • I have done a considerable amount of testing on this.  I installed a brand new Server 2012 R2 Standard machine and installed every Windows update except 3159706.  I was able to get SSL working and download and approve as many updates as I wanted (20000+ updates and 300+GB) and distribute them to clients.

    As soon as I install KB3159706 the console stops working.  I did follow all the postinstall instructions correctly.

    I have tried this twice now on 2 separate server builds from scratch just to confirm that it is always the 3159706 update that kills things no matter how careful I am to follow the installation instructions properly.

    Uninstallation of the update does not solve anything.  The server remains broken even with it removed.

    Sunday, May 29, 2016 3:39 PM
  • I believe the same update was to blame for my issues. What I finally did (after trying all the stuff Microsoft said as far as post install tasks) was remove the WSUS role, restart, re-add the wsus role (pointing to previous content location), then launch the automatic post install which of course failed.

    Then I followed this:

    https://gyorgybalassy.wordpress.com/2013/08/10/installing-wsus-on-windows-server-2012/

    I did not have to drop the database but I added the permissions to the folders and GPO as specified and modified the XML file with my WSUS content location. Has been working since then.

    Monday, May 30, 2016 7:57 AM
  • Hi,

    please take a look at this thread. I had the same problem/problems. Changing the Wsuspool settings have helped me at 2 customer sites.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/4b74ed13-37a2-430f-a92b-02876f002952/still-problems-after-installing-kb3159706-wsuspool?forum=winserverwsus


    Jens Ole Kragh, MCITP Server/Client, MCTS, MCT, Microsoft TechNet Influent Denmark,Blog: http://jensolekragh.wordpress.com/


    Monday, May 30, 2016 8:01 AM
  • Thank you AndréDE, worked for us!
    Friday, June 3, 2016 8:10 AM
  • Thanks for the update. I ran into the same error and was not able to connect to the WSUS with SQL error.

    I uninstalled KB 3159706 and restarted the server and it worked and everything came back like magic.


    Joe

    Wednesday, June 29, 2016 3:40 AM
  • i ran into the same Problems.

    KB3148812 was not installed. KB3159706 was installed via Windows Updates.
    WSUS was not starting, console did not connect.

    i did the post-install command and activated the HTTP-Activation from .Net Framework.
    after restart of the WSUS Service the console opens and it seems it works.

    thanks a lot guys!


    Patrick

    Tuesday, July 5, 2016 3:46 PM
  • i had the same problem.

    KB3148812 was not installed. KB3159706 was installed.
    WSUS was not starting, console did not connect.

    after just uninstalling KB3159706 and restarting the server my issue was resolved

    • Proposed as answer by Nawaz Khan Saturday, August 6, 2016 5:30 PM
    Saturday, August 6, 2016 5:30 PM
  • Not everyone is too familiar with WsusUtil. To make life easier you could add this crucial information to the article (output from WsusUtil.exe help postinstall):

    EXAMPLES

    Run postinstall for a WSUS server using the WID role and the default content directory:

        wsusutil postinstall

    Run postinstall for a WSUS server using the WID role to store downloaded update files in the directory C:\WSUS:

        wsusutil postinstall CONTENT_DIR=C:\WSUS

    Run postinstall for a WSUS server using the Database role, where the SQL Serveris installed on machine MYSQLSRV:

        wsustil postinstall SQL_INSTANCE_NAME=MYSQLSRV

    Run postinstall for a WSUS server using the Database role, where the SQL Server is installed on the same machine as the WSUS server and update files will be stored in the C:\WSUS directory:

        wsusutil postinstall SQL_INSTANCE_NAME=localhost CONTENT_DIR=C:\WSUS


    Rolf Lidvall, Swedish Radio (Ltd)

    Do you still have to add the /servicing to the command? I also cannot find any documentation about the servicing switch.

    One thing I find odd is that when you have SCCM they explicitly tell you not to configure WSUS from WSUS itself but let SCCM do it for you. This KB goes against all these recommendations... *sigh*

    Can't believe this is such a difficult patch...

    Tried following the KB, but just get a reset node message launching WSUS. Running the postinstall stuff, the logs indicate it can't update the database.  Using your tip, It went much further, but fails trying to reference the internal SQL database, rather then my external SUSDB.  

    2016-08-11 12:27:53  Install type is: Fresh
    2016-08-11 12:27:53  Creating database...
    2016-08-11 12:27:54  Msg 5170, Level 16, State 1, Server \\.\pipe\Microsoft##WID\tsql\query,  Line 2
    Cannot create file 'C:\Windows\WID\Data\SUSDB.mdf' because it already exists. Change the file path or the file name, and retry the operation.Msg 1802, Level 16, State 4, Server \\.\pipe\Microsoft##WID\tsql\query,  Line 2
    CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
    2016-08-11 12:27:54  Microsoft.UpdateServices.Administration.CommandException: Database creation failed
       at Microsoft.UpdateServices.Administration.ConfigureDB.CreateDatabase()
       at Microsoft.UpdateServices.Administration.ConfigureDB.Configure()
       at Microsoft.UpdateServices.Administration.PostInstall.Run()
       at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)

    Suggestions? 

    Thanks!

    Steve


    Thursday, August 11, 2016 4:36 PM
  • I confirmed my old SUSDB is in the default folder, but my active SQL database is on my D: drive.  Here's the whole log specifying the paths: wsusutil postinstall SQL_INSTANCE_NAME=localhost CONTENT_DIR=C:\WSUS

    2016-08-11 12:27:39  Postinstall started
    2016-08-11 12:27:39  Detected role services: Api, UI, WidDatabase, Services
    2016-08-11 12:27:39  Start: LoadSettingsFromParameters
    2016-08-11 12:27:39  Content local is: True
    2016-08-11 12:27:39  Content directory is: D:\WSUS
    2016-08-11 12:27:39  SQL instname is: localhost
    2016-08-11 12:27:39  End: LoadSettingsFromParameters
    2016-08-11 12:27:39  Start: Run
    2016-08-11 12:27:39  Configuring content directory...
    2016-08-11 12:27:39  Configuring groups...
    2016-08-11 12:27:39  Starting group configuration for WSUS Administrators...
    2016-08-11 12:27:39  Found group in regsitry, attempting to use it...
    2016-08-11 12:27:44  Writing group to registry...
    2016-08-11 12:27:44  Finished group creation
    2016-08-11 12:27:44  Starting group configuration for WSUS Reporters...
    2016-08-11 12:27:44  Found group in regsitry, attempting to use it...
    2016-08-11 12:27:44  Writing group to registry...
    2016-08-11 12:27:44  Finished group creation
    2016-08-11 12:27:44  Configuring permissions...
    2016-08-11 12:27:44  Fetching content directory...
    2016-08-11 12:27:44  Fetching ContentDir from registry store
    2016-08-11 12:27:44  Value is D:\WSUS
    2016-08-11 12:27:44  Fetching group SIDs...
    2016-08-11 12:27:44  Fetching WsusAdministratorsSid from registry store
    2016-08-11 12:27:44  Value is S-1-5-21-3393413916-3626962682-111359008-1025
    2016-08-11 12:27:44  Fetching WsusReportersSid from registry store
    2016-08-11 12:27:44  Value is S-1-5-21-3393413916-3626962682-111359008-1026
    2016-08-11 12:27:44  Creating group principals...
    2016-08-11 12:27:44  Granting directory permissions...
    2016-08-11 12:27:44  Granting permissions on content directory...
    2016-08-11 12:27:53  Granting registry permissions...
    2016-08-11 12:27:53  Granting registry permissions...
    2016-08-11 12:27:53  Granting registry permissions...
    2016-08-11 12:27:53  Configuring shares...
    2016-08-11 12:27:53  Configuring network shares...
    2016-08-11 12:27:53  Fetching content directory...
    2016-08-11 12:27:53  Fetching ContentDir from registry store
    2016-08-11 12:27:53  Value is D:\WSUS
    2016-08-11 12:27:53  Fetching WSUS admin SID...
    2016-08-11 12:27:53  Fetching WsusAdministratorsSid from registry store
    2016-08-11 12:27:53  Value is S-1-5-21-3393413916-3626962682-111359008-1025
    2016-08-11 12:27:53  Content directory is local, creating content shares...
    2016-08-11 12:27:53  Creating share "UpdateServicesPackages" with path "D:\WSUS\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
    2016-08-11 12:27:53  Deleting existing share...
    2016-08-11 12:27:53  Creating share...
    2016-08-11 12:27:53  Share successfully created
    2016-08-11 12:27:53  Creating share "WsusContent" with path "D:\WSUS\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
    2016-08-11 12:27:53  Creating share...
    2016-08-11 12:27:53  Share successfully created
    2016-08-11 12:27:53  Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
    2016-08-11 12:27:53  Deleting existing share...
    2016-08-11 12:27:53  Creating share...
    2016-08-11 12:27:53  Share successfully created
    2016-08-11 12:27:53  Finished creating content shares
    2016-08-11 12:27:53  Configuring WID database...
    2016-08-11 12:27:53  Configuring the database...
    2016-08-11 12:27:53  Establishing DB connection...
    2016-08-11 12:27:53  Checking to see if database exists...
    2016-08-11 12:27:53  Database does not exist
    2016-08-11 12:27:53  Loading install type query...
    2016-08-11 12:27:53  DECLARE @currentScriptVersion   int
    DECLARE @currentDBVersion       int
    IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
    BEGIN
        SELECT 1
    END
    ELSE
    BEGIN
        SET @currentScriptVersion = (9200 + 21847)
        SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
        IF @currentDBVersion < 926
        BEGIN
            SELECT 3
        END
        ELSE IF @currentDBVersion < @currentScriptVersion
        BEGIN
            SELECT 2
        END
        ELSE IF @currentDBVersion = @currentScriptVersion
        BEGIN
            SELECT 0
        END
        ELSE
        BEGIN
            SELECT 4
        END
    END

    2016-08-11 12:27:53  Install type is: Fresh
    2016-08-11 12:27:53  Creating database...
    2016-08-11 12:27:54  Msg 5170, Level 16, State 1, Server \\.\pipe\Microsoft##WID\tsql\query,  Line 2
    Cannot create file 'C:\Windows\WID\Data\SUSDB.mdf' because it already exists. Change the file path or the file name, and retry the operation.Msg 1802, Level 16, State 4, Server \\.\pipe\Microsoft##WID\tsql\query,  Line 2
    CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
    2016-08-11 12:27:54  Microsoft.UpdateServices.Administration.CommandException: Database creation failed
       at Microsoft.UpdateServices.Administration.ConfigureDB.CreateDatabase()
       at Microsoft.UpdateServices.Administration.ConfigureDB.Configure()
       at Microsoft.UpdateServices.Administration.PostInstall.Run()
       at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)


    Thursday, August 11, 2016 4:45 PM
  • So I did a bit more digging, and found the WID feature was still installed. I removed that, and reran the postinstall. both specifying the paths, and with the KB's service switch.  Still couldn't load the console, and found WSUS service was stopped.  Started, and retried console.  Still no luck. 

    Rebooted and no change.

    The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists, 

    Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.

    Event log throwing event ID 7053:

    System.NullReferenceException -- Object reference not set to an instance of an object.

    Source
    Microsoft.UpdateServices.UI.SnapIn

    Stack Trace:
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ResetScopeNode()

    Thursday, August 11, 2016 5:08 PM
  • FYI, running the stock KB postinstall give this log:

    2016-08-11 13:10:27  Postinstall started
    2016-08-11 13:10:27  Detected role services: Api, UI, Services
    2016-08-11 13:10:27  Start: LoadSettingsForServicing
    2016-08-11 13:10:27  End: LoadSettingsForServicing
    2016-08-11 13:10:27  Postinstall completed

    Running the postinstall with the paths errors out : Fatal Error: Failed to start and configure the WSUS service

    2016-08-11 13:24:04  Postinstall started
    2016-08-11 13:24:04  Detected role services: Api, UI, Services
    2016-08-11 13:24:04  Start: LoadSettingsFromParameters
    2016-08-11 13:24:04  Content local is: True
    2016-08-11 13:24:04  Content directory is: D:\WSUS
    2016-08-11 13:24:04  SQL instname is: localhost
    2016-08-11 13:24:04  End: LoadSettingsFromParameters
    2016-08-11 13:24:04  Start: Run
    2016-08-11 13:24:04  Configuring content directory...
    2016-08-11 13:24:04  Configuring groups...
    2016-08-11 13:24:04  Starting group configuration for WSUS Administrators...
    2016-08-11 13:24:04  Found group in regsitry, attempting to use it...
    2016-08-11 13:24:09  Writing group to registry...
    2016-08-11 13:24:09  Finished group creation
    2016-08-11 13:24:09  Starting group configuration for WSUS Reporters...
    2016-08-11 13:24:09  Found group in regsitry, attempting to use it...
    2016-08-11 13:24:09  Writing group to registry...
    2016-08-11 13:24:09  Finished group creation
    2016-08-11 13:24:09  Configuring permissions...
    2016-08-11 13:24:09  Fetching content directory...
    2016-08-11 13:24:09  Fetching ContentDir from registry store
    2016-08-11 13:24:09  Value is D:\WSUS
    2016-08-11 13:24:09  Fetching group SIDs...
    2016-08-11 13:24:09  Fetching WsusAdministratorsSid from registry store
    2016-08-11 13:24:09  Value is S-1-5-21-3393413916-3626962682-111359008-1025
    2016-08-11 13:24:09  Fetching WsusReportersSid from registry store
    2016-08-11 13:24:09  Value is S-1-5-21-3393413916-3626962682-111359008-1026
    2016-08-11 13:24:09  Creating group principals...
    2016-08-11 13:24:09  Granting directory permissions...
    2016-08-11 13:24:09  Granting permissions on content directory...
    2016-08-11 13:24:17  Granting registry permissions...
    2016-08-11 13:24:17  Granting registry permissions...
    2016-08-11 13:24:17  Granting registry permissions...
    2016-08-11 13:24:17  Configuring shares...
    2016-08-11 13:24:17  Configuring network shares...
    2016-08-11 13:24:17  Fetching content directory...
    2016-08-11 13:24:17  Fetching ContentDir from registry store
    2016-08-11 13:24:17  Value is D:\WSUS
    2016-08-11 13:24:17  Fetching WSUS admin SID...
    2016-08-11 13:24:17  Fetching WsusAdministratorsSid from registry store
    2016-08-11 13:24:17  Value is S-1-5-21-3393413916-3626962682-111359008-1025
    2016-08-11 13:24:17  Content directory is local, creating content shares...
    2016-08-11 13:24:18  Creating share "UpdateServicesPackages" with path "D:\WSUS\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
    2016-08-11 13:24:18  Deleting existing share...
    2016-08-11 13:24:18  Creating share...
    2016-08-11 13:24:18  Share successfully created
    2016-08-11 13:24:18  Creating share "WsusContent" with path "D:\WSUS\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
    2016-08-11 13:24:18  Deleting existing share...
    2016-08-11 13:24:18  Creating share...
    2016-08-11 13:24:18  Share successfully created
    2016-08-11 13:24:18  Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
    2016-08-11 13:24:18  Deleting existing share...
    2016-08-11 13:24:18  Creating share...
    2016-08-11 13:24:18  Share successfully created
    2016-08-11 13:24:18  Finished creating content shares
    2016-08-11 13:24:18  Configuring IIS...
    2016-08-11 13:24:18  Start: ConfigureWebsite
    2016-08-11 13:24:18  Configuring website on port 8530
    2016-08-11 13:25:13  2016-08-11 13:24:33  Info      IISCustomAction    Performing Setup Action, Command /Install 
    2016-08-11 13:25:11  Info      IISCustomAction    Command /Install Succeeded

    2016-08-11 13:25:13  End: ConfigureWebsite
    2016-08-11 13:25:13  Configuring performance counters...
    2016-08-11 13:25:13  Configuring Stats.NET perf counter...
    2016-08-11 13:25:13  Configuring reporting perf counter...
    2016-08-11 13:25:13  Configuring client webservice perf counter...
    2016-08-11 13:25:13  Configuring server sync webservice perf counter...
    2016-08-11 13:25:13  Configuring API remoting perf counter...
    2016-08-11 13:25:13  Bringing services online...
    2016-08-11 13:25:13  StartServer starting...
    2016-08-11 13:25:13  Generating encryption key to write to the registry...
    2016-08-11 13:25:13  Generating encryption key to write to the database...
    2016-08-11 13:25:13  Generation of encryption key to save to the database failed. Error=System.IndexOutOfRangeException: Index was outside the bounds of the array.
       at Microsoft.UpdateServices.Internal.DatabaseAccess.GenericReadableRow.GetInt32(Int32 index)
       at Microsoft.UpdateServices.Internal.ConfigurationTableRow.ReadRow(IDataRecord record)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetConfiguration()
       at Microsoft.UpdateServices.Internal.BaseApi.UpdateServerConfiguration.Load()
       at Microsoft.UpdateServices.Setup.StartServer.StartServer.GenerateNewDatabaseEncryptionKey()
    2016-08-11 13:25:13  StartServer encountered errors. Exception=Index was outside the bounds of the array.
    2016-08-11 13:25:13  Microsoft.UpdateServices.Administration.CommandException: Failed to start and configure the WSUS service
       at Microsoft.UpdateServices.Administration.PostInstall.Run()
       at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)

    Thursday, August 11, 2016 5:27 PM
  • Well, removed the WID database from featured, ZIP'd the files in the old folder, rebooted, Same error. 

    Uninstalled the KB patch, rebooted.  WSUS works.

    Reinstalled, reran the postinstall stuff, doesn't work.  

    Uninstalled for now - hopefully someone can shed some light on this. 


    Thursday, August 11, 2016 7:06 PM
  • Same problem went through all the steps

    WSUS DB is sitting on a SQL Database and not on a WID

    Are the wusutil commands in the KB article 3159706 for WID databases only!?

    Friday, August 12, 2016 9:05 PM
  • No one at Microsoft knows.  Or they're not telling.  Or they don't care.  Shame on you for using another Microsoft product and probably following a TechNet article to do it.  Now it's not supported... HAHAHAHAAHA.  We lose.
    Friday, August 19, 2016 8:00 PM
  • KB3148812 was not installed. KB3159706 was installed.  Uninstalled KB3159706 and everything is back to normal.  Come on M$, get it together!  Why is this still an issue months later??
    Wednesday, August 24, 2016 4:34 PM
  • KB3148812 was not installed. KB3159706 was installed.  Uninstalled KB3159706 and everything is back to normal.  Come on M$, get it together!  Why is this still an issue months later??
    Yeah, I'm still having an issue too. This is unacceptable. I've done the post install steps and it STILL DOESN'T WORK. I am using an external SQL database for the SUSDB. I think this is the common factor in those who are still having issues. 
    Wednesday, August 24, 2016 5:23 PM
  • So initially I caught the fact that KB3159706 breaks a functioning WSUS server. (KB 3148812 was already uninstalled) It did mine. I uninstalled the update and my WSUS server begins functioning again.

    So I decided to try the KB3159706 update again, several weeks later, because I know eventually I will need ESD decrypt capabilities on my WSUS.

    I am now about three hours into this evolution. KB3159706 did not work. The manual steps left me with a non functional WSUS server. I following the steps exactly, but something went wrong somewhere. Uninstalled KB3159706 again. Did not return my functional WSUS server. Eventually uninstalled WSUS, tried to reinstall. WID database was still there. Uninstalled WID and deleted database. Reinstalled WSUS and proceeded to reconfigure to attempt to get back to the initial configuration and functionality. Lesson learned. Wait until the issue surrounding KB3159706 have been resolved. They obviously haven’t been resolved.

    At one point I would up with a database that couldn’t be read.

    2016-08-25 10:51:12 Microsoft.UpdateServices.Administration.CommandException: The schema version of the database is from a newer version of WSUS than currently installed. You must either patch your WSUS server to at least

    Thursday, August 25, 2016 7:04 PM
  • So initially I caught the fact that KB3159706 breaks a functioning WSUS server. (KB 3148812 was already uninstalled) It did mine. I uninstalled the update and my WSUS server begins functioning again.

    So I decided to try the KB3159706 update again, several weeks later, because I know eventually I will need ESD decrypt capabilities on my WSUS.

    I am now about three hours into this evolution. KB3159706 did not work. The manual steps left me with a non functional WSUS server. I following the steps exactly, but something went wrong somewhere. Uninstalled KB3159706 again. Did not return my functional WSUS server. Eventually uninstalled WSUS, tried to reinstall. WID database was still there. Uninstalled WID and deleted database. Reinstalled WSUS and proceeded to reconfigure to attempt to get back to the initial configuration and functionality. Lesson learned. Wait until the issue surrounding KB3159706 have been resolved. They obviously haven’t been resolved.

    I don't think M$ is interested in fixing it. I've been told to open a support case but I'm not giving them $500 more of my companies money because they can't release a working patch. 
    Thursday, August 25, 2016 9:24 PM
  • For those of us using SQL Server, I have a solution!!!  I wrote a how-to on it, which you can find here:

    https://community.spiceworks.com/how_to/132301-fix-wsus-using-sql-server-after-kb3159706-broke-it

    Because of the nature of this issue and the many people like myself left frustrated by this situation, I will be posting it in a few different threads.  I apologize in advance if this comes across as spam to some people.

    Wednesday, August 31, 2016 8:18 PM
  • For an IT consultant who services multiple customer sites, "Clients" may refer to those customers who need to be visited in order to repair their WSUS deployments. - I agree with Mordock, this was a pretty big fail... I am still getting calls from customers whose WSUS deployments have been offline (several months) since this update was pushed out and they've tried everything (including rebuilding their WSUS server multiple times) to fix it before calling a pricey consultant to help them figure it out. - Support information, debugging flags, and communication for situations like need to be greatly improved, especially when "there is no other way". The symptoms for this failure issue are not immediately evident, I was only able to determine this by connecting to WID and searching for issues that would cause SUSDB to be 'recovery pending'. The WSUS service needs to do some of it's own debugging (independent of database connectivity) when you push breaking changes, and the eventlog errors need to be much clearer. Your release management and QA folks need a spanking for this one.
    Thursday, September 8, 2016 4:25 PM