My WSUS Console will no longer connect and allow me to administer WSUS. I continue to get «Error: Database Error» or «Error: Connection Error». I have tried may different suggestions that are out there including the MMC WSUS
File delete and the WSUSUtil post install command. The console was working last Thursday. I was not back in the console till Wednesday which is when I discovered the problem. We run updates every Wednesday morning. I don’t know if updates are running on the
servers and workstations. Below are the error text from the MMC Console and below those two errors is a snippet of the events in the WSUS SoftwareDistribution log file.
«Error: Database Error»:
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.ExecuteSPGetUpdateCount(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState) at Microsoft.UpdateServices.UI.SnapIn.Pages.ComputersListPage.GetListRows()
«Error: Connection Error»:
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. System.Net.WebException -- The operation has timed out Source System.Web.Services Stack Trace: at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse(WebRequest webRequest) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateServerStatus(Int32 updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, Int32 publicationState, Int32 propertiesToGet) at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetUpdateServerStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState, UpdateServerStatusPropertiesToGet propertiesToGet) at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, UpdateScope updatesToInclude, ComputerTargetScope computersToInclude, UpdateServerStatusPropertiesToGet propertiesToGet) at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetReplicaStatus(UpdateSources updateSources) at Microsoft.UpdateServices.UI.AdminApiAccess.CachedObject.RefreshCache() at Microsoft.UpdateServices.UI.AdminApiAccess.CachedObject.GetFromCache() at Microsoft.UpdateServices.UI.SnapIn.Pages.ServerSummaryPage.backgroundWorker_DoWork(Object sender, DoWorkEventArgs e)
SoftwareDistribution.Log
2017-05-04 14:12:37.486 UTC Warning w3wp.304 SoapUtilities.CreateException ThrowException: actor = http://dc1-sl:8530/ServerSyncWebService/serversyncwebservice.asmx, ID=f72689dd-ee3e-46d4-b3bb-d656a46b060e, ErrorCode=InternalServerError, Message=, Client=? 2017-05-04 14:13:27.510 UTC Error WsusService.9 HmtWebServices.CheckClientWebService Client WebService WebException:System.Net.WebException: The operation has timed out at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.UpdateServices.Internal.ClientWebService.Client.Ping(Int32 pingLevel) at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckClientWebService(EventLoggingType type, HealthEventLogger logger) at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckClientWebService(EventLoggingType type, HealthEventLogger logger) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.ExecuteSubtask(HealthMonitoringSubtask subtask, EventLoggingType type, HealthEventLogger logger) at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.Execute(EventLoggingType type) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.Execute(EventLoggingType type) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.Execute(Boolean waitIfNecessary, EventLoggingType loggingType) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.PeriodicTask() at Microsoft.UpdateServices.Internal.HealthMonitoring.PeriodicTaskExecuter.ThreadStart() 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() 2017-05-04 14:14:18.122 UTC Error WsusService.8 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException (0x80131904): A transport-level error has occurred when receiving results from the server. (provider: Named Pipes Provider, error: 0 - The pipe has been ended.) ---> System.ComponentModel.Win32Exception (0x80004005): The pipe has been ended at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e) at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteReader() at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPGetChangeTrackingInformation(Int64 lastChangeNumber, DateTime lastTimeWeChecked) at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc() ClientConnectionId:d8e42a83-793f-4bfc-9260-3e8f7b64a723 Error Number:109,State:0,Class:20 at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc() 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() 2017-05-04 14:14:18.122 UTC Error w3wp.9 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException (0x80131904): A transport-level error has occurred when receiving results from the server. (provider: Named Pipes Provider, error: 0 - The pipe has been ended.) ---> System.ComponentModel.Win32Exception (0x80004005): The pipe has been ended at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e) at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteReader() at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPGetChangeTrackingInformation(Int64 lastChangeNumber, DateTime lastTimeWeChecked) at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc() ClientConnectionId:ad85f038-1cf4-4e86-8be3-28a21dea8d00 Error Number:109,State:0,Class:20 at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc() 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() 2017-05-04 14:14:18.122 UTC Error WsusService.16 DataAccess.DumpStateMachineLog DumpStateMachineLog encountered an error at Microsoft.UpdateServices.Internal.DataAccess.DumpStateMachineLog() at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPResetStateMachineAndReEvaluate() at Microsoft.UpdateServices.Internal.ResetStateMachineAgent.WakeUpWorkerThreadProc() 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() 2017-05-04 14:14:18.122 UTC Error WsusService.16 DataAccess.DumpStateMachineLog System.InvalidOperationException: ExecuteReader requires an open and available Connection. The connection's current state is closed. at System.Data.SqlClient.SqlCommand.ValidateCommand(String method, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteReader() at Microsoft.UpdateServices.Internal.DataAccess.DumpStateMachineLog() at Microsoft.UpdateServices.Internal.DataAccess.DumpStateMachineLog() at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPResetStateMachineAndReEvaluate() at Microsoft.UpdateServices.Internal.ResetStateMachineAgent.WakeUpWorkerThreadProc() 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() 2017-05-04 14:14:18.122 UTC Error WsusService.16 ResetStateMachineAgent.ProcessSqlException dataAccess.ExecuteSPResetStateMachineAndReEvaluate(): SqlException.Number: 109; SqlException.State: 0; Message: A transport-level error has occurred when receiving results from the server. (provider: Named Pipes Provider, error: 0 - The pipe has been ended.) at Microsoft.UpdateServices.Internal.ResetStateMachineAgent.ProcessSqlException(Int32& numRetry, Int32 sqlExceptionNumber, String errorMessage) at Microsoft.UpdateServices.Internal.ResetStateMachineAgent.WakeUpWorkerThreadProc() 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() 2017-05-04 14:14:45.615 UTC Info WsusService.6 ThreadEntry ThreadHelper.ThreadStart 2017-05-04 14:14:45.615 UTC Info WsusService.6 SusService.SusServiceStartUpThreadProc WSUS Server Version: 6.3.9600.18324 2017-05-04 14:14:54.043 UTC Info WsusService.6 SusService.CleanUpIntermediateFileDownload CleanupIntermediateFileDownload 2017-05-04 14:14:54.585 UTC Info WsusService.6 SusService.SusServiceStartUpThreadProc EventId=501,Type=Information,Category=WsusService,Message=Update Services Service Started 2017-05-04 14:14:54.609 UTC Info WsusService.8 ThreadEntry ThreadHelper.ThreadStart 2017-05-04 14:14:54.609 UTC Info WsusService.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo: Startup 2017-05-04 14:14:54.610 UTC Info WsusService.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ContentSyncAgent, EventInfo: Startup 2017-05-04 14:14:54.610 UTC Info WsusService.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: StateMachineReset, EventInfo: Startup 2017-05-04 14:14:54.610 UTC Info WsusService.13 ThreadEntry ThreadHelper.ThreadStart 2017-05-04 14:14:54.610 UTC Info WsusService.13 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent 2017-05-04 14:14:54.611 UTC Info WsusService.13 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ContentSyncAgent 2017-05-04 14:14:54.611 UTC Info WsusService.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: RollupAgent, EventInfo: Startup 2017-05-04 14:14:54.611 UTC Info WsusService.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: EmailNotificationAgent, EventInfo: Startup 2017-05-04 14:14:54.611 UTC Info WsusService.13 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: StateMachineReset 2017-05-04 14:14:54.612 UTC Info WsusService.13 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: RollupAgent 2017-05-04 14:14:54.612 UTC Info WsusService.16 ThreadEntry ThreadHelper.ThreadStart 2017-05-04 14:14:54.613 UTC Info WsusService.16 ResetStateMachineAgent.WakeUpWorkerThreadProc State Machine Reset Agent Starting 2017-05-04 14:14:54.614 UTC Info WsusService.16 WaitHandleUtilities.WaitOneIgnoreAbandoned AbandonedMutexException received while waiting for mutex. Will ignore and continue as normal. Exception = System.Threading.AbandonedMutexException: The wait completed due to an abandoned mutex. at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext) at Microsoft.UpdateServices.Internal.WaitHandleUtilities.WaitOneIgnoreAbandoned(WaitHandle waitHandle, Int32 timeout) 2017-05-04 14:14:54.616 UTC Info WsusService.14 ThreadEntry ThreadHelper.ThreadStart 2017-05-04 14:14:54.616 UTC Info WsusService.14 CatalogSyncAgent.HandleCatalogSyncStateCorrection Handling systemStartup work... 2017-05-04 14:14:54.616 UTC Info WsusService.13 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: EmailNotificationAgent 2017-05-04 14:14:54.617 UTC Info WsusService.19 ThreadEntry ThreadHelper.ThreadStart 2017-05-04 14:14:54.618 UTC Info WsusService.19 EmailNotificationAgent.WakeUpWorkerThreadProc Email Notification Agent Starting 2017-05-04 14:14:54.628 UTC Info WsusService.15 ThreadEntry ThreadHelper.ThreadStart 2017-05-04 14:14:54.628 UTC Info WsusService.15 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange 2017-05-04 14:14:54.637 UTC Info WsusService.14 CatalogSyncAgent.WakeUpWorkerThreadProc Finished systemStartup work. 2017-05-04 14:14:54.654 UTC Info WsusService.20 ThreadEntry ThreadHelper.ThreadStart 2017-05-04 14:14:54.654 UTC Info WsusService.20 WsusTestKeys.PerformCheck autest.cab signature is invalid 2017-05-04 14:14:54.654 UTC Info WsusService.20 WsusTestKeys.AreTestKeysAllowed Server test key check: test keys are NOT allowed 2017-05-04 14:14:54.655 UTC Info WsusService.20 WsusTestKeys.PerformCheck autest.cab signature is invalid 2017-05-04 14:14:54.655 UTC Info WsusService.20 WsusTestKeys.AreTestKeysAllowed Server test key check: test keys are NOT allowed 2017-05-04 14:14:54.656 UTC Info WsusService.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2017-05-04 14:14:54.656 UTC Info WsusService.21 ThreadEntry ThreadHelper.ThreadStart 2017-05-04 14:14:54.656 UTC Info WsusService.21 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange 2017-05-04 14:14:54.658 UTC Info WsusService.19 EmailNotificationAgent.WakeUpWorkerThreadProc Email Notification Agent Finished 2017-05-04 14:14:54.659 UTC Info WsusService.15 EventLogEventReporter.ReportEvent EventId=361,Type=Information,Category=Synchronization,Message=Content synchronization started. 2017-05-04 14:14:54.660 UTC Info WsusService.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange 2017-05-04 14:14:54.661 UTC Info WsusService.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange 2017-05-04 14:14:54.662 UTC Info WsusService.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange 2017-05-04 14:14:54.663 UTC Info WsusService.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange 2017-05-04 14:14:54.664 UTC Info WsusService.20 CatalogSyncAgentCore.SyncUpdatesOutsideSubscription sync'ing 0 updates with catalog site flag 2017-05-04 14:14:54.678 UTC Info WsusService.20 EventLogEventReporter.ReportEvent EventId=381,Type=Information,Category=Synchronization,Message=A scheduled synchronization was started. 2017-05-04 14:14:54.898 UTC Info WsusService.20 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site 2017-05-04 14:14:54.907 UTC Warning WsusService.15 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used. 2017-05-04 14:14:54.907 UTC Info WsusService.15 ContentSyncAgent.WakeUpWorkerThreadProc ServerHealth: Updating Server Health for Component: ContentSyncAgent Running, Marking as Running 2017-05-04 14:14:54.919 UTC Info WsusService.20 ServerSyncLib.GetWebServiceProxyInternal Found config says USS is MU site 2017-05-04 14:14:54.925 UTC Info WsusService.20 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange 2017-05-04 14:14:55.003 UTC Info WsusService.20 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site 2017-05-04 14:14:55.010 UTC Info WsusService.20 CatalogSyncAgentCore.ExecuteSyncProtocol Server ID is b954f634-f971-4fc8-8d89-eb87d01a2be3 2017-05-04 14:14:55.067 UTC Info WsusService.20 SusService.ValidateServerCertificate CheckValidationResult Succeeds: CertOK 2017-05-04 14:14:55.068 UTC Info WsusService.20 ServerCertificateValidator.IsHostAllowedException Requested host: fe2.update.microsoft.com 2017-05-04 14:14:55.068 UTC Info WsusService.20 ServerCertificateValidator.VerifyServerCertificate SSL validation succeeded. 2017-05-04 14:14:55.179 UTC Info WsusService.20 CatalogSyncAgentCore.SyncConfigUpdatesFromUSS Category Sync: Filter: <filter SyncAnchor="40049984,2017-04-27 17:14:37.807" GetConfig="1"></filter> 2017-05-04 14:14:55.662 UTC Info WsusService.9 ThreadEntry ThreadHelper.ThreadStart 2017-05-04 14:14:55.662 UTC Warning WsusService.9 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used. 2017-05-04 14:14:56.579 UTC Info WsusService.20 CatalogSyncAgentCore.SyncConfigUpdatesFromUSS Need 5 config updates, 5 are new 2017-05-04 14:14:59.030 UTC Info w3wp.9 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2017-05-04 14:14:59.031 UTC Info w3wp.309 ThreadEntry ThreadHelper.ThreadStart 2017-05-04 14:14:59.031 UTC Info w3wp.309 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange 2017-05-04 14:14:59.031 UTC Info w3wp.8 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange 2017-05-04 14:14:59.039 UTC Info w3wp.8 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site 2017-05-04 14:14:59.670 UTC Info WsusService.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2017-05-04 14:14:59.671 UTC Info WsusService.23 ThreadEntry ThreadHelper.ThreadStart 2017-05-04 14:14:59.671 UTC Info WsusService.23 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange 2017-05-04 14:14:59.679 UTC Info WsusService.23 ServerCertificateValidator.ConfigChangedHandler Update server configuration has changed. Sync against MU: True 2017-05-04 14:15:17.100 UTC Info w3wp.303 ThreadEntry PipelineRuntime.ProcessRequestNotification 2017-05-04 14:15:17.100 UTC Warning w3wp.303 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used. 2017-05-04 14:15:19.795 UTC Warning w3wp.303 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used. 2017-05-04 14:15:19.795 UTC Warning w3wp.303 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used. 2017-05-04 14:15:19.795 UTC Warning w3wp.303 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used. 2017-05-04 14:17:30.415 UTC Error WsusService.9 HealthMonitoringTasks.ExecuteSubtask Health Monitoring Thread caught an exception: System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e) at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteGetSingleResult() at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds) at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPSingleValue(String spName, DBParameterCollection args, Int32 queryTimeoutInSeconds) at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetFailedToDownloadUpdatesCount() at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtCore.CheckForContentSyncFailures(EventLoggingType type, HealthEventLogger logger) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.ExecuteSubtask(HealthMonitoringSubtask subtask, EventLoggingType type, HealthEventLogger logger) ClientConnectionId:69ee97e8-99c8-4ae1-a6db-1a52ecfc5845 Error Number:-2,State:0,Class:11 at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.ExecuteSubtask(HealthMonitoringSubtask subtask, EventLoggingType type, HealthEventLogger logger) at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtCore.Execute(EventLoggingType type) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.Execute(EventLoggingType type) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.Execute(Boolean waitIfNecessary, EventLoggingType loggingType) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.PeriodicTask() at Microsoft.UpdateServices.Internal.HealthMonitoring.PeriodicTaskExecuter.ThreadStart() 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() 2017-05-04 14:17:31.716 UTC Info w3wp.316 ThreadEntry PipelineRuntime.ProcessRequestNotification 2017-05-04 14:17:31.716 UTC Info w3wp.316 ServerImplementation..ctor Initializing ServerSyncWebService ProcessID = 18164, Process Start Time = 5/4/2017 8:46:18 AM, Product Version = 6.3.9600.18324 2017-05-04 14:17:49.830 UTC Warning w3wp.303 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user <DOMAIN><User>, IP Address xxx.xxx.xxx.xxx, exception System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e) at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteGetSingleResult() at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds) at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPSingleValue(String spName, DBParameterCollection args, Int32 queryTimeoutInSeconds) at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetUpdateCount(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState) at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateCount(String updateScopeXml, String preferredCulture, Int32 publicationState) ClientConnectionId:f8c0eafd-1b4c-4c1e-a3a5-21c3ab3c1916 Error Number:-2,State:0,Class:11 2017-05-04 14:17:55.105 UTC Info w3wp.315 ThreadEntry PipelineRuntime.ProcessRequestNotification 2017-05-04 14:17:55.106 UTC Warning w3wp.315 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user <DOMAIN>Administrator, IP Address xxx.xxx.xxx.xxx, exception System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e) at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteGetSingleResult() at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds) at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPSingleValue(String spName, DBParameterCollection args, Int32 queryTimeoutInSeconds) at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetUpdateCount(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState) at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateCount(String updateScopeXml, String preferredCulture, Int32 publicationState) ClientConnectionId:e92549a1-faf2-4a81-a866-2e3aced2d0f2 Error Number:-2,State:0,Class:11 2017-05-04 14:19:11.727 UTC Error WsusService.9 HmtWebServices.CheckServerSyncWebService ServerSync WebService WebException:System.Net.WebException: The operation has timed out at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.Ping(Int32 pingLevel) at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckServerSyncWebService(EventLoggingType type, HealthEventLogger logger) at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckServerSyncWebService(EventLoggingType type, HealthEventLogger logger) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.ExecuteSubtask(HealthMonitoringSubtask subtask, EventLoggingType type, HealthEventLogger logger) at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.Execute(EventLoggingType type) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.Execute(EventLoggingType type) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.Execute(Boolean waitIfNecessary, EventLoggingType loggingType) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.PeriodicTask() at Microsoft.UpdateServices.Internal.HealthMonitoring.PeriodicTaskExecuter.ThreadStart() 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() 2017-05-04 14:20:01.710 UTC Error w3wp.316 ServerImplementation..ctor Error in ServerImplementation constructor: System.Threading.ThreadAbortException: Thread was being aborted. at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Microsoft.UpdateServices.Internal.ClassFactory.GetSingletonInstance(String propertyName, Type type) at Microsoft.UpdateServices.Internal.ServerImplementation..ctor() at Microsoft.UpdateServices.Internal.ServerImplementation..ctor() at Microsoft.UpdateServices.Internal.ServerSyncProxy..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) 2017-05-04 14:20:01.712 UTC Warning w3wp.316 SoapUtilities.CreateException ThrowException: actor = http://dc1-sl:8530/ServerSyncWebService/serversyncwebservice.asmx, ID=e190465a-21e3-4f64-b23c-5eec48f6eff2, ErrorCode=InternalServerError, Message=, Client=? 2017-05-04 14:20:07.393 UTC Info w3wp.298 ThreadEntry PipelineRuntime.ProcessRequestNotification 2017-05-04 14:20:07.393 UTC Warning w3wp.298 AdminDataAccess.AcquireSynchronizationMutex Unable to acquire database synchronization mutex. 2017-05-04 14:20:07.394 UTC Warning w3wp.298 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user <DOMAIN><User>, IP Address xxx.xxx.xxx.xxx, exception System.TimeoutException: The operation has timed out. at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.AcquireSynchronizationMutex() at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetUpdateServerStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState, UpdateServerStatusPropertiesToGet propertiesToGet) at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateServerStatus(Int32 updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, Int32 publicationState, Int32 propertiesToGet) 2017-05-04 14:20:11.640 UTC Info w3wp.307 ThreadEntry PipelineRuntime.ProcessRequestNotification 2017-05-04 14:20:11.641 UTC Warning w3wp.307 AdminDataAccess.AcquireSynchronizationMutex Unable to acquire database synchronization mutex. 2017-05-04 14:20:11.642 UTC Warning w3wp.307 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user <DOMAIN>Administrator, IP Address xxx.xxx.xxx.xxx, exception System.TimeoutException: The operation has timed out. at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.AcquireSynchronizationMutex() at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetUpdateServerStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState, UpdateServerStatusPropertiesToGet propertiesToGet) at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateServerStatus(Int32 updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, Int32 publicationState, Int32 propertiesToGet) 2017-05-04 14:20:15.250 UTC Info w3wp.310 ThreadEntry PipelineRuntime.ProcessRequestNotification 2017-05-04 14:20:15.250 UTC Warning w3wp.310 AdminDataAccess.AcquireSynchronizationMutex Unable to acquire database synchronization mutex. 2017-05-04 14:20:15.251 UTC Warning w3wp.310 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user <DOMAIN><User>, IP Address xxx.xxx.xxx.xxx, exception System.TimeoutException: The operation has timed out. at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.AcquireSynchronizationMutex() at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetUpdateServerStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState, UpdateServerStatusPropertiesToGet propertiesToGet) at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateServerStatus(Int32 updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, Int32 publicationState, Int32 propertiesToGet) 2017-05-04 14:20:15.781 UTC Info w3wp.257 ThreadEntry PipelineRuntime.ProcessRequestNotification 2017-05-04 14:20:15.781 UTC Warning w3wp.257 AdminDataAccess.AcquireSynchronizationMutex Unable to acquire database synchronization mutex. 2017-05-04 14:20:15.782 UTC Warning w3wp.257 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user <DOMAIN>Administrator, IP Address xxx.xxx.xxx.xxx, exception System.TimeoutException: The operation has timed out. at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.AcquireSynchronizationMutex() at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetUpdateServerStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState, UpdateServerStatusPropertiesToGet propertiesToGet) at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateServerStatus(Int32 updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, Int32 publicationState, Int32 propertiesToGet) 2017-05-04 14:20:51.775 UTC Error WsusService.9 HmtWebServices.CheckClientWebService Client WebService WebException:System.Net.WebException: The operation has timed out at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.UpdateServices.Internal.ClientWebService.Client.Ping(Int32 pingLevel) at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckClientWebService(EventLoggingType type, HealthEventLogger logger) at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckClientWebService(EventLoggingType type, HealthEventLogger logger) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.ExecuteSubtask(HealthMonitoringSubtask subtask, EventLoggingType type, HealthEventLogger logger) at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.Execute(EventLoggingType type) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.Execute(EventLoggingType type) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.Execute(Boolean waitIfNecessary, EventLoggingType loggingType) at Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.PeriodicTask() at Microsoft.UpdateServices.Internal.HealthMonitoring.PeriodicTaskExecuter.ThreadStart() 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() 2017-05-04 14:22:34.714 UTC Info w3wp.316 ThreadEntry PipelineRuntime.ProcessRequestNotification 2017-05-04 14:22:34.714 UTC Warning w3wp.316 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user <DOMAIN><User>, IP Address xxx.xxx.xxx.xxx, exception System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e) at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteGetSingleResult() at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds) at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPSingleValue(String spName, DBParameterCollection args, Int32 queryTimeoutInSeconds) at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetUpdateCount(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState) at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateCount(String updateScopeXml, String preferredCulture, Int32 publicationState) ClientConnectionId:f8c0eafd-1b4c-4c1e-a3a5-21c3ab3c1916 Error Number:-2,State:0,Class:11 2017-05-04 14:24:32.831 UTC Info w3wp.326 ThreadEntry PipelineRuntime.ProcessRequestNotification 2017-05-04 14:24:32.831 UTC Warning w3wp.326 AdminDataAccess.AcquireSynchronizationMutex Unable to acquire database synchronization mutex. 2017-05-04 14:24:32.832 UTC Warning w3wp.326 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user <DOMAIN>Administrator, IP Address xxx.xxx.xxx.xxx, exception System.TimeoutException: The operation has timed out. at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.AcquireSynchronizationMutex() at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetUpdateServerStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState, UpdateServerStatusPropertiesToGet propertiesToGet) at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateServerStatus(Int32 updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, Int32 publicationState, Int32 propertiesToGet) 2017-05-04 14:24:58.153 UTC Info w3wp.327 ThreadEntry PipelineRuntime.ProcessRequestNotification 2017-05-04 14:24:58.153 UTC Warning w3wp.327 AdminDataAccess.AcquireSynchronizationMutex Unable to acquire database synchronization mutex. 2017-05-04 14:24:58.154 UTC Warning w3wp.327 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user <DOMAIN><User>, IP Address xxx.xxx.xxx.xxx, exception System.TimeoutException: The operation has timed out. at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.AcquireSynchronizationMutex() at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetUpdateServerStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState, UpdateServerStatusPropertiesToGet propertiesToGet) at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateServerStatus(Int32 updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, Int32 publicationState, Int32 propertiesToGet) 2017-05-04 14:25:01.495 UTC Info w3wp.334 ThreadEntry PipelineRuntime.ProcessRequestNotification 2017-05-04 14:25:01.495 UTC Warning w3wp.334 AdminDataAccess.AcquireSynchronizationMutex Unable to acquire database synchronization mutex. 2017-05-04 14:25:01.496 UTC Warning w3wp.334 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user <DOMAIN><User>, IP Address xxx.xxx.xxx.xxx, exception System.TimeoutException: The operation has timed out. at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.AcquireSynchronizationMutex() at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetUpdateServerStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState, UpdateServerStatusPropertiesToGet propertiesToGet) at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdateServerStatus(Int32 updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, Int32 publicationState, Int32 propertiesToGet) 2017-05-04 14:25:18.967 UTC Error w3wp.9 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e) at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteReader() at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPGetChangeTrackingInformation(Int64 lastChangeNumber, DateTime lastTimeWeChecked) at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc() ClientConnectionId:1035788e-e3f5-44d8-94d8-30c85258a363 Error Number:-2,State:0,Class:11 at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc() 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() 2017-05-04 14:25:19.609 UTC Error WsusService.8 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e) at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteReader() at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPGetChangeTrackingInformation(Int64 lastChangeNumber, DateTime lastTimeWeChecked) at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc() ClientConnectionId:7e86832b-02fe-4305-b940-3166e8f01769 Error Number:-2,State:0,Class:11 at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc() 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()
I’m getting Database errors when using the Update Services console on Windows Server 2008 R2. Synchronizations fails and I get the same
Database error if I try to do the Clean Up Wizard.
In Event Viewer I’m seeing:
The description for Event ID 824 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
incorrect pageid (expected 1:259197; actual 0:0)
read
(1:259197)
5
0x0000007e8fa000
e:WSUS\UpdateServicesDbFilesSUSDB.mdf
The specified resource type cannot be found in the image file
Anybody have any suggestions or is it looking like I’m going to have to uninstall and reinstall the WSUS role/DB?
check
Best Answer
OverDrive
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
mace
WSUS Expert
-
check
392
Best Answers -
thumb_up
557
Helpful Votes
Your DB id pooched. It’s corrupted. To run the fixes would result in data loss. As it’s only WSUS…
You’re best off removing WSUS/WID and re-installing it and starting fresh.
Remove the roles, reboot, Delete the databases in C:WindowsWIDData (beyond master, model, tempdb, and msdb — you should see only SUSDB if WSUS is the only database within the WID. If it is, remove all the databases)
Install WSUS again, and setup from scratch. Then use my script to keep it clean.
1 found this helpful
thumb_up
thumb_down
View Best Answer in replies below
Read these next…
Can’t communicate with scanner
Hardware
Hello everyone,I have a client that uses Kodak ScanMate i940 scanners at their desks. They recently got a new computer that we prepped and put on their domain. This new computer is recognizing the scanner but it is unusable with the error «can’t communica…
Different MAC address, same computer name — multiple DHCP leases
Windows
I’m noticing a lot more now that our Wifi DHCP scopes are filled by the same computer name, but with different mac addresses. I know there’s a feature in Windows 10 called Random hardware addresses, but that setting is off. Is there anything else that cou…
Snap! — No-Password Logins, Solar Powered Water Filter, Glitch in the Matrix?
Spiceworks Originals
Your daily dose of tech news, in brief.
Welcome to the Snap!
Flashback: February 9, 1996: Introduction of the Bandai Pippin (Read more HERE.)
Bonus Flashback: February 9, 1990: Galileo Probe does a Venus Flyby (Read more HERE.)
You nee…
Roku TV being used as Wallboard Issues
Hardware
Helping someone out at their shop. They have 4 large Roku screens and 2 laptops with dual HDMI ports for video. They are viewing static website business dashboards and PowerPoint. At first all 4 screens connected to wireless, worked for a while but with a…
Charging for SSO
Security
We have SSO set up with around 5 or 6 solution providers via our M365. Not one of them charges for this, they just sent us the documentation.I identified another online service in use by one of our departments which would benefit from using SSO for staff …
Содержание
- Wsus error database error
- Asked by:
- Question
- All replies
- Resolve WSUS Database Error Timeouts
- Problem:
- Symptoms:
- Reason:
- Background:
- Solution:
- References:
- Related Articles
- 3 Comments
- Wsus error database error
- Asked by:
- Question
- All replies
- WSUS Database Error
- Popular Topics in WSUS
- 15 Replies
- Wsus error database error
- Answered by:
- Question
Wsus error database error
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
I am very new to wsus, any how i configured everything and implemented and using Windows internal database(WID). But frequently getting connection error and some times getting database error. I got some scripts while browsing web but not getting how to run those scripts. Can any one kindly guide me to come out of this issue.
Further to your issue, I want to confirm if you encountered a connection error like the screenshot below.
We could increase physical & virtual memory limit of WsusPool (in IIS Application Pool). Please follow the steps below, so that you can increase it to 8388608KB.
2. Check if there occurs Windows Update Error in event log. (Login failed for user ‘NT AUTHORITYNETWORK SERVICE’.) For this error, you may install Windows update KB3148812 or KB3159706 on your WSUS server.
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com
We wonder whether your issue has been resolved.
If it has, I would appreciate if you could mark my replies as answer if they help and post your solutions to share with others having the same problem.
If it has not, please feel free to contact us for further assistance.
Thanks.
Источник
Resolve WSUS Database Error Timeouts
Problem:
Symptoms:
WSUS runs slow. WSUS IIS App pool crashes and stops. WSUS problem requires administrator to reset server node in order to function again. Clients cannot download WSUS updates when APP pool is down.
Reason:
Background:
Kent Agerlund does a good job describing the problem on his blog. Agerlund also provides a solution using a SQL script. However, Agerlund’s fix does not work for all WSUS implementations. The script only works with the full version of SQL -not the Windows Internal Database. For example:
The specified option ‘Ad Hoc Distributed Queries’ is not supported by this edition of SQL Server
Solution:
Talented programmer, SAK, updates the script to work with WSUS 2012 running a Windows Internal Database version of SQL:
- SQL script to identify obsolete updates on WSUS server:
USE [SUSDB]
GO
DECLARE @return_value int
EXEC @return_value = [dbo].[spGetObsoleteUpdatesToCleanup]
GO - SQL script to delete all obsolete updates on WSUS. N.B., the script provides feedback messages, after each update ID is deleted.
References:
Related Articles
Thank You!
I came from Kent Agerlunds Blog, this does not worked for me.
But your Comment, you had the same Problem brought me to your Site. 🙂
Hi! SBS2011 / WSUS 3.2, neither of these scripts do anything. They both complete, but report 0 lines. I have 80,000 unneeded updates I’m still trying to get rid of, thanks!
Start planning to get off SBS2011 — running a system that’s only in extended support for another two years is just opening yourself to trouble.
Try this script from the comments in the original «house of cards» article to force the WSUS cleanup to work recursively rather than trying the low-level DB scripts. It will be slower but might get you there.
Источник
Wsus error database error
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
My WSUS Console will no longer connect and allow me to administer WSUS. I continue to get «Error: Database Error» or «Error: Connection Error». I have tried may different suggestions that are out there including the MMC WSUS File delete and the WSUSUtil post install command. The console was working last Thursday. I was not back in the console till Wednesday which is when I discovered the problem. We run updates every Wednesday morning. I don’t know if updates are running on the servers and workstations. Below are the error text from the MMC Console and below those two errors is a snippet of the events in the WSUS SoftwareDistribution log file.
«Error: Database Error»:
«Error: Connection Error»:
SoftwareDistribution.Log
My script will fix your issue.
Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need.
1. Remove all Drivers from the WSUS Database.
2. Shrink your WSUSContent folder’s size by declining superseded updates.
3. Remove declined updates from the WSUS Database.
4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
5. Compress Update Revisions.
6. Remove Obsolete Updates.
7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.
9. Run the Recommended SQL database Maintenance script on the actual SQL database.
10. Run the Server Cleanup Wizard.
It will email the report out to you or save it to a file, or both.
Although the script is lengthy, it has been made to be super easy to setup and use. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment, simply run:
If you wish to view or increase the Application Pool Memory Configuration, you must run it with the required switch. See Get-Help .Clean-WSUS.ps1 -Examples
If you’re having trouble, there’s also a -HelpMe option that will create a log so you can send it to me for support.
Источник
WSUS Database Error
I’m getting Database errors when using the Update Services console on Windows Server 2008 R2. Synchronizations fails and I get the same Database error if I try to do the Clean Up Wizard.
In Event Viewer I’m seeing:
The description for Event ID 824 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
incorrect pageid (expected 1:259197; actual 0:0)
read
(1:259197)
5
0x0000007e8fa000
e:WSUS\UpdateServicesDbFilesSUSDB.mdf
The specified resource type cannot be found in the image file
Anybody have any suggestions or is it looking like I’m going to have to uninstall and reinstall the WSUS role/DB?
Thanks in advanced.
Popular Topics in WSUS
- check 388 Best Answers
- thumb_up 552 Helpful Votes
Your DB id pooched. It’s corrupted. To run the fixes would result in data loss. As it’s only WSUS.
You’re best off removing WSUS/WID and re-installing it and starting fresh.
Remove the roles, reboot, Delete the databases in C:WindowsWIDData (beyond master, model, tempdb, and msdb — you should see only SUSDB if WSUS is the only database within the WID. If it is, remove all the databases)
Install WSUS again, and setup from scratch. Then use my script to keep it clean.
- check 388 Best Answers
- thumb_up 551 Helpful Votes
Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need.
1. Remove all Drivers from the WSUS Database.
2. Shrink your WSUSContent folder’s size by declining superseded updates.
3. Remove declined updates from the WSUS Database.
4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
5. Compress Update Revisions.
6. Remove Obsolete Updates.
7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.
9. Run the Recommended SQL database Maintenance script on the actual SQL database.
10. Run the Server Cleanup Wizard.
It will email the report out to you or save it to a file, or both.
Although the script is lengthy, it has been made to be super easy to setup and use. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment, simply run:
If you wish to view or increase the Application Pool Memory Configuration, you must run it with the required switch. See Get-Help .Clean-WSUS.ps1 -Examples
If you’re having trouble, there’s also a -HelpMe option that will create a log so you can send it to me for support.
Источник
Wsus error database error
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
Hi there. I’ve done a fair amount of research and attempted multiple suggestions from other threads about this issue but nothing has worked so I’m hoping someone can provide me with some information about the Database Error message I’m getting when running Server Cleanup Wizard in WSUS version 6.3.9600.18838. I can run all the options except the first one and get this error when running it. Help would really be appreciated. Thanks.
FIRST ERROR in EVENT LOG
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 — Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
SECOND ERROR in EVENT LOG
The description for Event ID 0 from source WSusCertServer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
Источник
This is caused because the partition doesn´t have enough diskspace.
I will show you how to solve this error doing the following steps.
- Stop UpdateService
- Cleanup some update files located in WSUSContent ( It must be enough , so a log file for the cleanup could be created on the WSUS partition. In my case the log file was about 2 GB)
- Start UpdateService
- Run the Cleanup Wizard
- After this run the following command:
C:Program FilesUpdate ServicesTools>wsusutil.exe reset
The command “wsusutil.exe reset” tells WSUS to check each update in the database, and verify that the content is present in the WSUSContent folder. As it finds that the content is not present in the folder, it executes a BITS job to download the content from Microsoft. This process takes quite a bit of time and runs in the background.
How do you know when the process is complete?
The size of the WSUSContent folder is no longer growing, but to be sure check the SoftwareDistribution.log.
C:Program FilesUpdate ServicesLogFilesSoftwareDistribution.log
If you start the “wsusutil.exe reset” command, you should see a line towards the bottom of the log which looks like this:
WsusService.14 ExecutionContext.runTryCode State Machine Reset Agent Starting
… after a while you should see this-> …
WsusService.14 ExecutionContext.runTryCode State Machine Reset Agent Finished
So, that’s all in this blog. I will meet you soon with next stuff .Have a nice day !!!
Recommended contents
How to Check the Active Directory Database Integrity
Disabling and Enabling the Outbound Replication
DFS Replication Service Stopped Replication
What is Strict Replication Consistency
The replication operation failed because of a schema mismatch between the servers involved
Troubleshooting ad replication error 8418 the replication operation failed because of a schema mismatch between the servers
How to export replication information in txt file
Repadmin Replsummary
Enabling the outbound replication
Disabling and enabling replication on schema master domain controller
How to enable strict replication consistency
How to prevent lingering objects replication in active directory
AD replication process overview
How to force active directory replication
Change notification in replication process
How to check replication partner for a specific domain controller
dcdiag test replications
DFS Replication Event
Unidirectional replication
Guys please don’t forget to like and share the post. You can also share the feedback on below windows techno email id.
If you have any questions feel free to contact us on [email protected] also follow us on [email protected] to get updates about new blog posts.
I am an Active Directory Consultant. I have around eight years experiences in IT field. Presently, I am working with reputed IT Company as an Active Directory Consultant.
I am dedicated and enthusiastic information technology expert who always ready to resolve any technical problem. I am maintaining this blog from last three years. This blog includes more than 450 articles.
These are mainly about windows active directory and azure active directory service however I have also started to publish the articles on windows server issues as well.In free time I likes to Travel, watch interesting videos, learn about new technologies.
If you guys need any further help on subject matters, feel free to contact me on 𝙖𝙙𝙢𝙞𝙣@𝙬𝙞𝙣𝙙𝙤𝙬𝙨𝙩𝙚𝙘𝙝𝙣𝙤.𝙘𝙤𝙢
and also subscribe our Facebook page as well website for latest article.
𝖍𝖙𝖙𝖕𝖘://𝖜𝖜𝖜.𝖋𝖆𝖈𝖊𝖇𝖔𝖔𝖐.𝖈𝖔𝖒/𝖜𝖎𝖓𝖉𝖔𝖜𝖘𝖙𝖊𝖈𝖍𝖓𝖔/
Back to top button
When running the WSUS Server Cleanup Wizard from the MMC snap-in, it can occur that you receive the following WSUS database error:
Error: Database Error
An error occurred when trying to perform a database operation. This can happen if the database is very busy, if the database service is stopped, if the connection to the database is lost, of if the Post-Installation task is not completed successfully. Please contact your system administrator if the problem persists.
Click Reset Server Node to try to connect to the server again.
If you haven’t performed the cleanup in a long time, then this can happen. So you might decide to read through the manual of the wsusutil.exe tool where you think that the deleteunneededrevisions switch will resolve all your problems, however, it seems that the wsusutil.exe parameter deleteunneededrevisions doesn’t exist on WSUS 3.1.
Luckily, you can achieve the same thing using powershell. The advantages here are:
- If you have used this powershell script once, you can use the Server Cleanup Wizard from the GUI again.
- You can schedule the execution of this powershell script using Task Scheduler (for example once every month).
- On my WSUS server, I had about 600GB of updates. After running this script, almost 2000 updates were compressed, saving almost 200GB of disk space!
If you save the contents of the powershell script to «WSUSCleanup.ps1», then you can execute this script as follows from a DOS Command Prompt window: powershell -file «WSUSCleanup.ps1»
Make sure that you open the DOS Command Prompt as administrator!
The script itself is only 11 lines long (13 if you include comments):
# WSUSCleanup.ps1
[reflection.assembly]::LoadWithPartialName(«Microsoft.UpdateServices.Administration»)` | out-null
$wsus = [Microsoft.UpdateServices.Administration.AdminProxy]::GetUpdateServer();
$cleanupScope = new-object Microsoft.UpdateServices.Administration.CleanupScope;
$cleanupScope.DeclineSupersededUpdates = $true
$cleanupScope.DeclineExpiredUpdates = $true
$cleanupScope.CleanupObsoleteUpdates = $true
$cleanupScope.CompressUpdates = $true
$cleanupScope.CleanupObsoleteComputers = $true
$cleanupScope.CleanupUnneededContentFiles = $true
$cleanupManager = $wsus.GetCleanupManager();
$cleanupManager.PerformCleanup($cleanupScope);
# Script END
The output of the script looked as follows when I ran it the first time:
C:scripts>powershell -file «WSUSCleanup.ps1»
SupersededUpdatesDeclined : 0
ExpiredUpdatesDeclined : 0
ObsoleteUpdatesDeleted : 3
UpdatesCompressed : 1953
ObsoleteComputersDeleted : 0
DiskSpaceFreed : 168707192502
Tags:
- WSUS
- Windows
- Infrastructure security
- PowerShell
Related articles
Pages
You might also be interested in…
I just upgraded our WSUS server from WSUS 2.0 to WSUS 3.0 SP2. After performing the upgrade I ran the Cleanup Wizard. All boxes were checked except for «Computers not contacting the server». It ran for several hours and finally errored out with the Database Error below. At that point I ran the Cleanup Wizard again but only did one option at a time. Superseded Updates, Expired Updates, and Unneeded update Files each run fine and finish in less than a minute. However, if I try to clean Unused updates and update revisions I get the Database Error after about two minutes. I checked the event log after the Database Error and I’m getting event ID 7042 (full details below). The only products I have selected are Office and Windows. My WSUS folder is 27GB and my WsusDatabase folder is 5GB. WSUS seems to be using the Internal Database.
Error: Database Error
An error occurred when trying to perform a database operation. This can happen if the database is very busy, if the database service is topped, or if the connection to the database is lost. Please contact your systems administrator if the problem persists. Click Reset Server Node to try to connect to the server again. «Reset Server Node»
Source: Windows Server Update
Type: Warning
Event ID: 7042
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 System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at System.Windows.Forms.Control.Invoke(Delegate method)
at Microsoft.UpdateServices.UI.SnapIn.Wizards.ServerCleanup.ServerCleanupWizard.OnCleanupComplete(Object sender, PerformCleanupCompletedEventArgs e)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp
Open in new window
Problem
When attempting to perform a WSUS Server Cleanup on the WSUS Server always getting a error and have to ‘Reset Server Node’.
Checking the Event Viewer showed the following error;
Log Name: Application
Source: Windows Server Update Services
Date: 23/12/2016 9:42:55 AM
Event ID: 7042
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Server.domain.local
Description:
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 System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at Microsoft.UpdateServices.UI.SnapIn.Wizards.ServerCleanup.ServerCleanupWizard.OnCleanupComplete(Object sender, PerformCleanupCompletedEventArgs e)
Event Xml:
7042
3
0
0x80000000000000
122805
Application
Server.domain.local
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 System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at Microsoft.UpdateServices.UI.SnapIn.Wizards.ServerCleanup.ServerCleanupWizard.OnCleanupComplete(Object sender, PerformCleanupCompletedEventArgs e)
Resolution
I have found there are two ways to resolve this issue;
Firstly…
For those less experienced in SQL, here is the process:
1. Enable “named pipes” access for the Microsoft##WID database. Access wasn’t enabled on mine initially.
2. Open SSMS (SQL Server Management Studio and enter “\.pipeMICROSOFT##WIDtsqlquery” under server name.
3. Click “options” and select “Named Pipes” under “Network protocol” under the “Connection Properties” tab
4. Click “connect”
5. Execute a query for:
USE SUSDB
GO
exec spGetObsoleteUpdatesToCleanup
You will see a list of obsolete updates pop up. Take note of these UpdateID’s.
6. Execute “exec spDeleteUpdate @localUpdateID=000000” where 000000=UpdateID
Another option is to increase the timeout on the sql server.
Extend Timeout (f.e. for Cleanup-Wizard)
Connect to SQL via: Extend Timeout (f.e. for Cleanup-Wizard)
Connect to SQL via: \.pipeMICROSOFT##WIDtsqlquery
Right click on \.pipeMICROSOFT##WIDtsqlquery (first in the row on the left)
Select Properties
Select Connections
Set timeout from default 600 to 1200 (or greater, avoid 0 as this is unlimited and not best practise).
Categories: Event Viewer, Microsoft, Server 2012, Windows Server, Windows Update, WSUS
Tags: 7042, Cleanup, Error, Event ID, Microsoft, SQL, timeout, WSUS