locked
WSUS console can't connect to server after system crash RRS feed

  • Question

  • You guys got my first problem solved with setting up this server, and everything was working well, until the host computer crashed a couple of weeks ago.  Since then, when I open the WSUS administrative console, it can't connect to the server.  I'm not sure how to even evaluate the problem.  My inclination is to reinstall the whole business, but I sense that that is a cowardly approach, and I had better confess my ignorance and try to repair the existing installation.

    Miriam S

    Monday, May 2, 2016 8:46 PM

Answers

  • Hi Mrs Schechter,

    >I am about to give up and re-install WSUS, as my boss has changed her mind about waiting until summer to start over.  Number one, if I just remove the role from the server, will that delete the defective database, or should I manually delete the database, or maybe the whole folder?

    To remove the original WSUS role, you may use "Remove Roles and Features" to remove WSUS role. After removing WSUS server, manually delete the original database. If you use WID, then delete files "SUSDB.mdf" and "SUSDB_log.ldf" located in C:\Windows\WID\Data. If you use external SQL server, contact SQL expects to learn how to remove the WSUS database.

    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.

    • Marked as answer by Mrs Schechter Wednesday, May 11, 2016 3:09 PM
    Tuesday, May 10, 2016 6:37 AM

All replies

  • it could be related to KB3148812 installed on the WSUS ?

    https://blogs.technet.microsoft.com/wsus/2016/04/22/what-you-need-to-know-about-kb3148812-part-two/


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

    Monday, May 2, 2016 8:58 PM
  • Hi Schechter,

    As DonPick pointed out, check if you have updated your WSUS server recently and installed the KB, there is an known issue for KB3148812, if yes, uninstall the KB and test if it could work.

    If the issue is not related with that KB, the log of WSUS can help troubleshooting which located in C:\program files\update services\logfiles.

    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.

    Tuesday, May 3, 2016 5:02 AM
  • The Update History doesn't show this KB.  I do see errors in this log file.  I will post a part of it.

    2016-05-03 12:41:14.437 UTC Warning w3wp.216 SoapUtilities.CreateException ThrowException: actor = http://smith-update:8530/SimpleAuthWebService/SimpleAuth.asmx, ID=c9a34500-d39e-4a6e-b3cc-b01c09ce6cdf, ErrorCode=InternalServerError, Message=, Client=?
    2016-05-03 12:41:14.437 UTC Info w3wp.173 SimpleAuth..ctor Initializing SimpleAuth WebService ProcessID = 1820, Process Start Time = 5/2/2016 3:15:08 PM, Product Version = 6.3.9600.16384
    2016-05-03 12:41:28.207 UTC Error w3wp.173 SimpleAuthImplementation..ctor Exception in SimpleAuth constructor: System.Threading.ThreadAbortException: Thread was being aborted.
       at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout)
       at System.Threading.Thread.Sleep(Int32 millisecondsTimeout)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
       at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
       at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect(String connectionString)
       at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds)
       at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPMultipleResultSets(String spName, DBParameterCollection args, Type[] resultTypes)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetConfiguration()
       at Microsoft.UpdateServices.Internal.SimpleAuthImplementation..ctor(ConfigChangeHandler handler)
       at Microsoft.UpdateServices.Internal.SimpleAuthImplementation..ctor(ConfigChangeHandler handler)
       at Microsoft.UpdateServices.Internal.SimpleAuth..ctor()
       at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
       at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
       at System.Activator.CreateInstance(Type type, Boolean nonPublic)
       at System.Activator.CreateInstance(Type type)
       at System.Web.Services.Protocols.ServerProtocol.CreateServerInstance()
       at System.Web.Services.Protocols.SoapServerProtocol.CreateServerInstance()
       at System.Web.Services.Protocols.WebServiceHandler.Invoke()
       at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
       at System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context)
       at System.Web.Script.Services.ScriptHandlerFactory.HandlerWrapper.ProcessRequest(HttpContext context)
       at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
       at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
       at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
       at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
       at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    2016-05-03 12:41:28.207 UTC Warning w3wp.173 SoapUtilities.CreateException ThrowException: actor = http://smith-update:8530/SimpleAuthWebService/SimpleAuth.asmx, ID=8d70bc01-101c-4e14-be98-15bd8febb723, ErrorCode=InternalServerError, Message=, Client=?
    2016-05-03 12:41:28.207 UTC Info w3wp.208 SimpleAuth..ctor Initializing SimpleAuth WebService ProcessID = 1820, Process Start Time = 5/2/2016 3:15:08 PM, Product Version = 6.3.9600.16384
    2016-05-03 12:41:44.097 UTC Error w3wp.208 SimpleAuthImplementation..ctor Exception in SimpleAuth constructor: System.Threading.ThreadAbortException: Thread was being aborted.
       at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout)
       at System.Threading.Thread.Sleep(Int32 millisecondsTimeout)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
       at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
       at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect(String connectionString)
       at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds)
       at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPMultipleResultSets(String spName, DBParameterCollection args, Type[] resultTypes)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetConfiguration()
       at Microsoft.UpdateServices.Internal.SimpleAuthImplementation..ctor(ConfigChangeHandler handler)
       at Microsoft.UpdateServices.Internal.SimpleAuthImplementation..ctor(ConfigChangeHandler handler)
       at Microsoft.UpdateServices.Internal.SimpleAuth..ctor()
       at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
       at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
       at System.Activator.CreateInstance(Type type, Boolean nonPublic)
       at System.Activator.CreateInstance(Type type)
       at System.Web.Services.Protocols.ServerProtocol.CreateServerInstance()
       at System.Web.Services.Protocols.SoapServerProtocol.CreateServerInstance()
       at System.Web.Services.Protocols.WebServiceHandler.Invoke()
       at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
       at System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context)
       at System.Web.Script.Services.ScriptHandlerFactory.HandlerWrapper.ProcessRequest(HttpContext context)
       at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
       at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
       at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
       at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
       at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    2016-05-03 12:41:44.097 UTC Warning w3wp.208 SoapUtilities.CreateException ThrowException: actor = http://smith-update:8530/SimpleAuthWebService/SimpleAuth.asmx, ID=ddfc20fc-b823-42c6-8df4-d78735e4bd21, ErrorCode=InternalServerError, Message=, Client=?
    2016-05-03 12:41:44.097 UTC Info w3wp.178 SimpleAuth..ctor Initializing SimpleAuth WebService ProcessID = 1820, Process Start Time = 5/2/2016 3:15:08 PM, Product Version = 6.3.9600.16384
    2016-05-03 12:42:10.129 UTC Error WsusService.5 SusService.SusServiceStartUpThreadProc WUS Service failed during startup processing, sleeping before retry - Error Details: System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
       at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
       at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect(String connectionString)
       at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPUpdateServerHealthStatus(String componentName, Boolean isRunning)
       at Microsoft.UpdateServices.EventSystem.SusService.SusServiceStartUpThreadProc()
    ClientConnectionId:00000000-0000-0000-0000-000000000000
    Error Number:2,State:0,Class:20, Retry Count: 8
       at Microsoft.UpdateServices.EventSystem.SusService.SusServiceStartUpThreadProc()
       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.Threading.ThreadHelper.ThreadStart()


    Miriam S

    Tuesday, May 3, 2016 12:46 PM
  • 2016-05-03 12:42:10.129 UTC Error
    WsusService.5 SusService.SusServiceStartUpThreadProc
    WUS Service failed during startup processing, sleeping before retry - Error Details: System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server.
    The server was not found or was not accessible.
    Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
    it seems that the WID (Windows Internal Database) SQL server service, is unavailable, after this crash.
    The WSUS webservice is attempting to connect to the SQL database service and is failing to connect.
    The SQL service, or the underlying database, may be damaged by the crash. It may be possible to repair the database integrity using SQL tools, or, it may be simpler to restore from a backup, or reinstall the SUSDB?

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

    Tuesday, May 3, 2016 9:13 PM
  • Hi Mrs Schechter,

    Or before performing DonPick's suggestion, you may check if reindex WSUS database could help:

    https://technet.microsoft.com/en-us/library/dd939795(v=ws.10).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.

    Wednesday, May 4, 2016 9:35 AM
  • Thanks for your quick responses. Do you think that the death of the database is the cause of the many ASP.net errors, also?

           

    Event code: 3001 
    Event message: The request has been aborted. 
    Event time: 5/4/2016 9:58:47 AM 
    Event time (UTC): 5/4/2016 1:58:47 PM 
    Event ID: d0110420448647129c7fbd5d35c34df5 
    Event sequence: 10171 
    Event occurrence: 4976 
    Event detail code: 0 

    Application information: 
        Application domain: /LM/W3SVC/1629168005/ROOT/SimpleAuthWebService-1-131067945182284958 
        Trust level: Full 
        Application Virtual Path: /SimpleAuthWebService 
        Application Path: C:\Program Files\Update Services\WebServices\SimpleAuthWebService\ 
        Machine name: SMITH-UPDATE 

    Process information: 
        Process ID: 1732 
        Process name: w3wp.exe 
        Account name: NT AUTHORITY\NETWORK SERVICE 

    Exception information: 
        Exception type: HttpException 
        Exception message: Request timed out.



    Request information: 
        Request URL: http://smith-update:8530/SimpleAuthWebService/SimpleAuth.asmx 
        Request path: /SimpleAuthWebService/SimpleAuth.asmx 
        User host address: 192.168.1.147 
        User:  
        Is authenticated: False 
        Authentication Type:  
        Thread account name: NT AUTHORITY\NETWORK SERVICE 

    Thread information: 
        Thread ID: 286 
        Thread account name: NT AUTHORITY\NETWORK SERVICE 
        Is impersonating: False 
        Stack trace: 

     Also, for the MSSQL$MICROSOFT##WID error

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


    Miriam S

    Wednesday, May 4, 2016 2:05 PM
  • Another question;

    I tried running a script to reindex the DB. and SQLCMD exited with this result

    Sqlcmd: Error: Microsoft ODBC Driver 11 for SQL Server : Named Pipes Provider: C
    ould not open a connection to SQL Server [2]. .
    Sqlcmd: Error: Microsoft ODBC Driver 11 for SQL Server : Login timeout expired.
    Sqlcmd: Error: Microsoft ODBC Driver 11 for SQL Server : A network-related or in
    stance-specific error has occurred while establishing a connection to SQL Server
    . Server is not found or not accessible. Check if instance name is correct and i
    f SQL Server is configured to allow remote connections. For more information see
     SQL Server Books Online..

    Do you think this means that the database is beyond repair, or just that I don't have the script properly configured?


    Miriam S

    Wednesday, May 4, 2016 3:07 PM
  • Hi Mrs Schechter,

    Does your WSUS server 2012 or 2012 R2?

    If yes, check if your steps are all correct:

    1.Download and install the following tools:

    Microsoft Command Line Utilities 11 for SQL Server:

    https://www.microsoft.com/en-us/download/details.aspx?id=36433

    ODBC driver 11 for SQL:

    https://www.microsoft.com/en-us/download/details.aspx?id=36434

    2. In CMD, direct to SQLCMD.exe path using command:

    cd C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn

    3. Cope the script and store it locally:

    https://gallery.technet.microsoft.com/scriptcenter/6f8cde49-5c52-4abd-9820-f1d270ddea61#content

    4. In CMD, run the following command:

    SQLCMD -E -S np:\\.\pipe\MICROSOFT##WID\tsql\query -i <script location>

    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, May 9, 2016 2:46 AM
  • Good Morning

    Thanks for your reply.  I did do all of these things, and in addition I followed two suggestions made by other readers, namely 

    

    I had to edit that sql file to add the line "SET QUOTED_IDENTIFIER ON;" and I added that line just below the line "SET NOCOUNT ON;" so it is the 4th line in the script. Now my SQL maintenance script runs to completion without errors!

    and

    --Second, go to the SQLCMD.exe path cd C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn --Then run the following command: SQLCMD -E -S np:\\.\pipe\MICROSOFT##WID\tsql\query -i <script location> As you can see, the SQL WID instance name changed in 2012, and the sql changed to tsql. No other changes needed, the WSUS 3 maintenance script works just fine.

    I am about to give up and re-install WSUS, as my boss has changed her mind about waiting until summer to start over. Number one, if I just remove the role from the server, will that delete the defective database, or should I manually delete the database, or maybe the whole folder?

    Thanks for your help.



    Miriam S

    Monday, May 9, 2016 2:44 PM
  • Hi Mrs Schechter,

    >I am about to give up and re-install WSUS, as my boss has changed her mind about waiting until summer to start over.  Number one, if I just remove the role from the server, will that delete the defective database, or should I manually delete the database, or maybe the whole folder?

    To remove the original WSUS role, you may use "Remove Roles and Features" to remove WSUS role. After removing WSUS server, manually delete the original database. If you use WID, then delete files "SUSDB.mdf" and "SUSDB_log.ldf" located in C:\Windows\WID\Data. If you use external SQL server, contact SQL expects to learn how to remove the WSUS database.

    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.

    • Marked as answer by Mrs Schechter Wednesday, May 11, 2016 3:09 PM
    Tuesday, May 10, 2016 6:37 AM