WSUS Broken - Database Confusion RRS feed

  • Question

  • Running System Center 2012 for Endpoint Protection and Windows Updates.

    Single 100GB HDD filled up quickly with updates.

    Added larger HDD.

    Stopped necessary services.

    Detached SUSDB from within Management Studio.

    Manually copied susdb mdf and ldf files to dir on new HDD.

    Reattached to Management Studio.

    *WSUS in MMC will not connect. (Error Below)

    I'm able to log into $MICROSOFT##SSEE..... SUSDB was there, but was in an error state, pointing to old location. I brought it offline and detached it. 

    Not able to attach it to $MICROSOFT##SSEE: File already in use. Probably because it's attached to the Server SQL instance.

    The end goal is to continue retrieving updates from Microsoft and serve them out through SCCM.

    ** I'm not too familiar with SQL and database management in general, so I don't have a great understanding of how WSUS and SCCM work together. Does WSUS server as the underlying mechanism for retrieving and storing updates and SCCM merely displays those updates as available?

    ** Is it possible to recover from this without a total rebuild?


    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.


    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.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       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.PooledStream.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.


    Stack Trace:
       at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
       at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
       at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()
    Thursday, April 11, 2013 5:30 PM


  • Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?

    There will be security setting that will need to be applied to the database files after you move them. To be honest the fast way to fix this is to re-install WSUS.

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    • Proposed as answer by Garth JonesMVP Saturday, January 31, 2015 7:00 PM
    • Marked as answer by Garth JonesMVP Saturday, February 7, 2015 3:27 PM
    Saturday, January 17, 2015 3:59 PM