locked
WSUS Console does not connect to database after wsusutil movecontent RRS feed

  • Question

  • After running the command to move my content to a new directory "wsusutil movecontent G:\Content\ G:\move.log" the WSUS console opens but after a minute it errors that it cannot connect to the database.

    My SQL instance (remote SQL server to WSUS) is running at full CPU.

    The move.log shows the following:

    2014-08-21T07:49:57 Successfully stopped WsusService.
    2014-08-21T07:49:57 Beginning content file location change to G:\Content\
    2014-08-21T08:15:46 Successfully copied content files.
    2014-08-21T08:15:46 Successfully copied application files.
    2014-08-21T08:15:46 Successfully changed WUS configuration.
    2014-08-21T08:15:47 Successfully changed IIS virtual directory path.
    2014-08-21T08:15:47 Successfully removed existing local content network shares.
    2014-08-21T08:15:47 Successfully created local content network shares.
    2014-08-21T08:15:47 Successfully changed registry value for content store directory.
    2014-08-21T08:15:47 Successfully changed content file location.
    2014-08-21T08:15:50 Successfully started WsusService.
    2014-08-21T08:15:50 Content integrity check and repair...
    2014-08-21T08:15:50 Initiated content integrity check and repair.

    On the WSUS server I found some log files and this is an extract of the SoftwareDistribution.log:

    2014-08-21 07:49:56.459 UTC Info wsusutil.1 ThreadEntry Application.Main
    2014-08-21 07:49:56.459 UTC Info wsusutil.1 WsusServiceUtility.Stop Stopping WsusService
    2014-08-21 07:49:56.474 UTC Info WsusService.14 ThreadEntry _ThreadPoolWaitCallback.PerformWaitCallback
    2014-08-21 07:49:56.474 UTC Info WsusService.14 SusService.OnStop EventId=502,Type=Information,Category=WsusService,Message=Update Services Service Has Stopped
    2014-08-21 07:49:57.474 UTC Info wsusutil.1 WsusServiceUtility.Stop WsusService successfully stopped.
    2014-08-21 07:49:57.474 UTC Info wsusutil.1 ContentManager.LogMessage Beginning content file location change to G:\Content\
    2014-08-21 07:54:21.017 UTC Info w3wp.14 ThreadEntry _ThreadPoolWaitCallback.PerformWaitCallback
    2014-08-21 07:54:21.033 UTC Warning w3wp.14 DBConnection.OnReceivingInfoMessage  The join order has been enforced because a local join hint is used.
    2014-08-21 08:15:46.906 UTC Change wsusutil.1 AdminDataAccess.ExecuteSPSetConfiguration WSUS configuration has been changed
    2014-08-21 08:15:47.859 UTC Info wsusutil.1 ContentManager.LogMessage Successfully changed content file location.
    2014-08-21 08:15:47.874 UTC Info wsusutil.1 WsusServiceUtility.Start Starting WsusService
    2014-08-21 08:15:50.124 UTC Info wsusutil.1 WsusServiceUtility.Start WsusService successfully started.
    2014-08-21 08:15:50.124 UTC Info wsusutil.1 ContentManager.LogMessage Content integrity check and repair...
    2014-08-21 08:15:50.218 UTC Info wsusutil.1 ContentManager.LogMessage Initiated content integrity check and repair.
    2014-08-21 08:15:50.234 UTC Info WsusService.5 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:15:50.249 UTC Info WsusService.5 SusService.SusServiceStartUpThreadProc WSUS Server Version: 3.2.7600.251
    2014-08-21 08:15:50.593 UTC Info WsusService.5 SusService.CleanUpIntermediateFileDownload CleanupIntermediateFileDownload
    2014-08-21 08:15:50.859 UTC Info WsusService.5 BitsCleanupHelper.CleanupJobsInBits Cancelled BITS job b1838a88-6668-450e-ae43-0b0eaed1ea03
    2014-08-21 08:15:50.874 UTC Info WsusService.5 BitsCleanupHelper.CleanupJobsInBits Cancelled BITS job d62e0ee8-b02b-4bde-b0dc-0f1c23f9c0da
    2014-08-21 08:15:50.890 UTC Info WsusService.5 BitsCleanupHelper.CleanupJobsInBits Cancelled BITS job 1570c257-2421-4d85-8a9c-10bfd5ce0dfd
    2014-08-21 08:15:50.890 UTC Info WsusService.5 BitsCleanupHelper.CleanupJobsInBits Cancelled BITS job b92cc245-b283-492b-b01f-1bf17041dbda
    2014-08-21 08:15:50.921 UTC Info WsusService.5 BitsCleanupHelper.CleanupJobsInBits Cancelled BITS job a3badcfe-802e-41ab-a30f-6d0995725d04
    2014-08-21 08:15:50.921 UTC Info WsusService.5 BitsCleanupHelper.CleanupJobsInBits Cancelled BITS job b87ba29a-16d8-4ee0-89cb-6fb23d949c33
    2014-08-21 08:15:50.937 UTC Info WsusService.5 BitsCleanupHelper.CleanupJobsInBits Cancelled BITS job 9b1d3823-40b8-4249-8fa5-7ab58fed739f
    2014-08-21 08:15:50.953 UTC Info WsusService.5 BitsCleanupHelper.CleanupJobsInBits Cancelled BITS job 564054d9-8be2-4cb3-ba16-831cf1b0cd14
    2014-08-21 08:15:50.968 UTC Info WsusService.5 BitsCleanupHelper.CleanupJobsInBits Cancelled BITS job 9136126b-9846-421f-8f4c-bcc524bc9241
    2014-08-21 08:15:50.984 UTC Info WsusService.5 BitsCleanupHelper.CleanupJobsInBits Cancelled BITS job 5b5e6ddd-50bd-4d36-96df-f47ffa0bca39
    2014-08-21 08:15:52.312 UTC Info WsusService.7 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:15:52.312 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo: Startup
    2014-08-21 08:15:52.312 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ContentSyncAgent, EventInfo: Startup
    2014-08-21 08:15:52.312 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: StateMachineReset, EventInfo: Startup
    2014-08-21 08:15:52.328 UTC Info WsusService.8 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:15:52.328 UTC Info WsusService.8 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent
    2014-08-21 08:15:52.328 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: RollupAgent, EventInfo: Startup
    2014-08-21 08:15:52.328 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: EmailNotificationAgent, EventInfo: Startup
    2014-08-21 08:15:52.328 UTC Info WsusService.8 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ContentSyncAgent
    2014-08-21 08:15:52.343 UTC Info WsusService.4 ThreadEntry _TimerCallback.PerformTimerCallback
    2014-08-21 08:15:52.343 UTC Info WsusService.4 EventLogEventReporter.ReportEvent EventId=424,Type=Error,Category=WsusService,Message=The content synchronization agent did not respond within the expected timeout.
    2014-08-21 08:15:52.343 UTC Info WsusService.8 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: StateMachineReset
    2014-08-21 08:15:52.343 UTC Info WsusService.12 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:15:52.343 UTC Info WsusService.12 ResetStateMachineAgent.WakeUpWorkerThreadProc State Machine Reset Agent Starting
    2014-08-21 08:15:52.359 UTC Info WsusService.8 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: RollupAgent
    2014-08-21 08:15:52.437 UTC Info WsusService.10 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:15:52.437 UTC Info WsusService.10 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-08-21 08:15:52.437 UTC Info WsusService.10 EventLogEventReporter.ReportEvent EventId=361,Type=Information,Category=Synchronization,Message=Content synchronization started.
    2014-08-21 08:15:52.437 UTC Info WsusService.8 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: EmailNotificationAgent
    2014-08-21 08:15:52.453 UTC Info WsusService.9 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:15:52.453 UTC Info WsusService.9 CatalogSyncAgent.HandleCatalogSyncStateCorrection Handling systemStartup work...
    2014-08-21 08:15:52.468 UTC Info WsusService.9 CatalogSyncAgent.HandleCatalogSyncStateCorrection Finished systemStartup work.
    2014-08-21 08:15:52.484 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2014-08-21 08:15:52.484 UTC Info WsusService.16 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:15:52.484 UTC Info WsusService.16 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2014-08-21 08:15:52.500 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2014-08-21 08:15:52.515 UTC Info WsusService.9 CatalogSyncAgent.UpdateServerHealthStatusBasedOnError ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running
    2014-08-21 08:15:52.515 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2014-08-21 08:15:52.515 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2014-08-21 08:15:52.531 UTC Info WsusService.15 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:15:52.531 UTC Info WsusService.15 EmailNotificationAgent.WakeUpWorkerThreadProc Email Notification Agent Starting
    2014-08-21 08:15:52.531 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2014-08-21 08:15:52.640 UTC Info WsusService.5 SusService.SusServiceStartUpThreadProc EventId=501,Type=Information,Category=WsusService,Message=Update Services Service Started
    2014-08-21 08:15:52.718 UTC Info WsusService.15 EmailNotificationAgent.WakeUpWorkerThreadProc Email Notification Agent Finished
    2014-08-21 08:15:53.750 UTC Info WsusService.10 ContentSyncAgent.WakeUpWorkerThreadProc ServerHealth: Updating Server Health for Component: ContentSyncAgent Running, Marking as Running
    2014-08-21 08:16:07.281 UTC Info w3wp.30 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:16:07.281 UTC Info w3wp.30 ClientImplementation..ctor Initializing ClientWebService ProcessID = 4896, Process Start Time = 21/08/2014 08:20:55, Product Version = 3.2.7600.251
    2014-08-21 08:16:07.281 UTC Info w3wp.30 CabUtilities.CheckCertificateSignature File cert verification failed for c:\Program Files\Update Services\autest.cab with 2147942402
    2014-08-21 08:16:07.281 UTC Info w3wp.30 WsusTestKeys.AreTestKeysAllowed Server test key check: test keys are NOT allowed
    2014-08-21 08:16:07.281 UTC Info w3wp.30 CabUtilities.CheckCertificateSignature File cert verification failed for c:\Program Files\Update Services\autest.cab with 2147942402
    2014-08-21 08:16:07.281 UTC Info w3wp.30 WsusTestKeys.AreTestKeysAllowed Server test key check: test keys are NOT allowed
    2014-08-21 08:16:07.328 UTC Info w3wp.30 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
    2014-08-21 08:17:22.643 UTC Info w3wp.32 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-08-21 08:17:22.643 UTC Info w3wp.32 SimpleAuth..ctor Initializing SimpleAuth WebService ProcessID = 4896, Process Start Time = 21/08/2014 08:20:55, Product Version = 3.2.7600.251
    2014-08-21 08:17:22.768 UTC Info w3wp.32 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
    2014-08-21 08:17:22.909 UTC Info w3wp.20 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:17:22.909 UTC Info w3wp.20 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-08-21 08:17:22.940 UTC Info w3wp.20 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
    2014-08-21 08:18:24.396 UTC Info WsusService.14 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:18:24.396 UTC Error WsusService.14 HealthMonitoringTasks.ExecuteSubtask Health Monitoring Thread caught an exception: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteGetSingleResult()
       at Microsoft.UpdateServices.Internal.SingleValueSPHandler.ExecuteStoredProcedure(DBConnection connection)
       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)
       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.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-08-21 08:18:25.271 UTC Info w3wp.13 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-08-21 08:18:25.271 UTC Info w3wp.13 WebService..cctor Initializing Reporting WebService ProcessID = 4896, Process Start Time = 21/08/2014 08:20:55, Product Version = 3.2.7600.251
    2014-08-21 08:18:28.630 UTC Info w3wp.13 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-08-21 08:18:28.646 UTC Info w3wp.13 ApiRemoting..cctor Initializing ApiRemoting WebServiceProcessID = 4896, Process Start Time = 21/08/2014 08:20:55, Product Version = 3.2.7600.251
    2014-08-21 08:18:32.693 UTC Info WsusService.14 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-08-21 08:18:33.256 UTC Info w3wp.13 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-08-21 08:18:33.256 UTC Info w3wp.13 ServerImplementation..ctor Initializing ServerSyncWebService ProcessID = 4896, Process Start Time = 21/08/2014 08:20:55, Product Version = 3.2.7600.251
    2014-08-21 08:20:12.963 UTC Error WsusService.14 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.HttpWebClientProtocol.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.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-08-21 08:20:13.870 UTC Info w3wp.27 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-08-21 08:20:13.885 UTC Info w3wp.27 DssAuthWebServiceImplementation..ctor Initializing DssAuthWebService ProcessID = 4896, Process Start Time = 21/08/2014 08:20:55, Product Version = 3.2.7600.251
    2014-08-21 08:20:13.901 UTC Info w3wp.27 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
    2014-08-21 08:20:14.088 UTC Info WsusService.4 SusService.OnStop EventId=502,Type=Information,Category=WsusService,Message=Update Services Service Has Stopped
    2014-08-21 08:20:14.838 UTC Info WsusService.5 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:20:14.838 UTC Info WsusService.5 SusService.SusServiceStartUpThreadProc WSUS Server Version: 3.2.7600.251
    2014-08-21 08:20:14.963 UTC Info WsusService.5 SusService.CleanUpIntermediateFileDownload CleanupIntermediateFileDownload
    2014-08-21 08:20:16.323 UTC Info w3wp.13 RevisionIdCache.UpdateCategoryAndRevisionIdCache Fetching the category and revision id change for cache from database
    2014-08-21 08:20:16.354 UTC Info w3wp.25 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:20:16.354 UTC Info w3wp.25 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2014-08-21 08:20:16.354 UTC Info w3wp.23 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:20:16.354 UTC Info w3wp.23 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2014-08-21 08:20:16.354 UTC Info w3wp.20 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-08-21 08:20:16.354 UTC Info w3wp.25 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2014-08-21 08:20:16.354 UTC Info w3wp.25 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2014-08-21 08:20:16.354 UTC Info w3wp.25 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2014-08-21 08:20:16.354 UTC Info w3wp.25 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2014-08-21 08:20:16.417 UTC Info w3wp.20 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
    2014-08-21 08:20:16.807 UTC Info WsusService.5 SusService.SusServiceStartUpThreadProc EventId=501,Type=Information,Category=WsusService,Message=Update Services Service Started
    2014-08-21 08:20:16.885 UTC Info WsusService.7 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:20:16.885 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo: Startup
    2014-08-21 08:20:16.885 UTC Info WsusService.11 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:20:16.885 UTC Info WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent
    2014-08-21 08:20:16.901 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ContentSyncAgent, EventInfo: Startup
    2014-08-21 08:20:16.901 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: StateMachineReset, EventInfo: Startup
    2014-08-21 08:20:16.901 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: RollupAgent, EventInfo: Startup
    2014-08-21 08:20:16.901 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: EmailNotificationAgent, EventInfo: Startup
    2014-08-21 08:20:16.901 UTC Info WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ContentSyncAgent
    2014-08-21 08:20:16.917 UTC Info WsusService.12 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:20:16.917 UTC Info WsusService.12 CatalogSyncAgent.HandleCatalogSyncStateCorrection Handling systemStartup work...
    2014-08-21 08:20:16.917 UTC Info WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: StateMachineReset
    2014-08-21 08:20:16.932 UTC Info WsusService.15 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:20:16.932 UTC Info WsusService.15 ResetStateMachineAgent.WakeUpWorkerThreadProc State Machine Reset Agent Starting
    2014-08-21 08:20:16.932 UTC Info WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: RollupAgent
    2014-08-21 08:20:16.948 UTC Info WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: EmailNotificationAgent
    2014-08-21 08:20:16.948 UTC Info WsusService.15 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.WaitOne(Int64 timeout, Boolean exitContext)
       at Microsoft.UpdateServices.Internal.WaitHandleUtilities.WaitOneIgnoreAbandoned(WaitHandle waitHandle, Int32 timeout)
    2014-08-21 08:20:16.948 UTC Info WsusService.12 CatalogSyncAgent.HandleCatalogSyncStateCorrection Finished systemStartup work.
    2014-08-21 08:20:16.963 UTC Info WsusService.17 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:20:16.963 UTC Info WsusService.17 EmailNotificationAgent.WakeUpWorkerThreadProc Email Notification Agent Starting
    2014-08-21 08:20:16.979 UTC Info WsusService.14 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:20:16.979 UTC Info WsusService.14 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-08-21 08:20:17.010 UTC Info WsusService.12 CatalogSyncAgent.UpdateServerHealthStatusBasedOnError ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running
    2014-08-21 08:20:17.026 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2014-08-21 08:20:17.042 UTC Info WsusService.18 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:20:17.042 UTC Info WsusService.18 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2014-08-21 08:20:17.057 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2014-08-21 08:20:17.057 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2014-08-21 08:20:17.057 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2014-08-21 08:20:17.057 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2014-08-21 08:20:17.073 UTC Info WsusService.17 EmailNotificationAgent.WakeUpWorkerThreadProc Email Notification Agent Finished
    2014-08-21 08:20:17.120 UTC Info WsusService.14 EventLogEventReporter.ReportEvent EventId=361,Type=Information,Category=Synchronization,Message=Content synchronization started.
    2014-08-21 08:20:17.292 UTC Info WsusService.14 ContentSyncAgent.WakeUpWorkerThreadProc ServerHealth: Updating Server Health for Component: ContentSyncAgent Running, Marking as Running
    2014-08-21 08:20:26.198 UTC Info w3wp.13 RevisionIdCache.UpdateCategoryCache Refreshing the category cache
    2014-08-21 08:20:26.214 UTC Info w3wp.13 RevisionIdCache.UpdateRevisionCache Refreshing the revision cache
    2014-08-21 08:20:26.808 UTC Info w3wp.13 DependencyCache.RefreshThreadStart read 147486 UpdateIDs from DB in 250 ms
    2014-08-21 08:20:26.808 UTC Info w3wp.13 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: DeploymentChange
    2014-08-21 08:20:26.823 UTC Info w3wp.13 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
    2014-08-21 08:20:26.933 UTC Info w3wp.13 CabUtilities.CheckCertificateSignature File cert verification failed for c:\Program Files\Update Services\autest.cab with 2147942402
    2014-08-21 08:20:26.933 UTC Info w3wp.13 WsusTestKeys.AreTestKeysAllowed Server test key check: test keys are NOT allowed
    2014-08-21 08:20:26.933 UTC Info w3wp.13 CabUtilities.CheckCertificateSignature File cert verification failed for c:\Program Files\Update Services\autest.cab with 2147942402
    2014-08-21 08:20:26.933 UTC Info w3wp.13 WsusTestKeys.AreTestKeysAllowed Server test key check: test keys are NOT allowed
    2014-08-21 08:20:26.948 UTC Info w3wp.7 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:20:26.948 UTC Info w3wp.7 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: DeploymentChange
    2014-08-21 08:20:26.948 UTC Info w3wp.7 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-08-21 08:20:26.948 UTC Info w3wp.7 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: LanguageChange
    2014-08-21 08:20:26.948 UTC Info w3wp.7 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: FileLocationChange
    2014-08-21 08:20:26.948 UTC Info w3wp.7 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: HardwareIDChange
    2014-08-21 08:22:48.111 UTC Info WsusService.8 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:22:48.111 UTC Error WsusService.8 HealthMonitoringTasks.ExecuteSubtask Health Monitoring Thread caught an exception: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteGetSingleResult()
       at Microsoft.UpdateServices.Internal.SingleValueSPHandler.ExecuteStoredProcedure(DBConnection connection)
       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)
       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.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-08-21 08:22:53.627 UTC Info WsusService.8 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-08-21 08:25:34.400 UTC Info w3wp.27 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-08-21 08:25:34.400 UTC Warning w3wp.27 AdminDataAccess.AcquireSynchronizationMutex Unable to acquire database synchronization mutex.
    2014-08-21 08:25:34.400 UTC Warning w3wp.27 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user DOMAIN\Administrator, IP Address fe80::75d2:2eef:1e4c:9965%11, 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)
    2014-08-21 08:28:44.002 UTC Info w3wp.32 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-08-21 08:28:44.002 UTC Warning w3wp.32 AdminDataAccess.AcquireSynchronizationMutex Unable to acquire database synchronization mutex.
    2014-08-21 08:28:44.002 UTC Warning w3wp.32 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user DOMAIN\Administrator, IP Address fe80::75d2:2eef:1e4c:9965%11, 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)
    2014-08-21 08:28:48.080 UTC Info w3wp.26 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-08-21 08:28:48.080 UTC Info w3wp.26 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-08-21 08:28:48.236 UTC Info w3wp.26 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
    2014-08-21 08:28:48.377 UTC Warning w3wp.26 SoapUtilities.CreateException ThrowException: actor = http://10.20.30.20/ReportingWebService/ReportingWebService.asmx, ID=ff507417-97d0-4ba1-b279-68c235a7ec42, ErrorCode=ConfigChanged, Message=, Client=373242c1-86ce-4377-97a1-92651d9a3b4b
    2014-08-21 08:28:48.377 UTC Error w3wp.26 WebService.ReportEventBatch Exception occured in ReportEventBatch: Fault occurred
       at Microsoft.UpdateServices.Internal.Reporting.WebService.ReportEventBatch(Cookie cookie, DateTime clientTime, ReportingEvent[] eventBatch)
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target, Object[] values)
       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.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 managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    2014-08-21 08:30:18.428 UTC Error w3wp.30 ClientImplementation..ctor Error in ClientImplementation constructor: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout)
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ReadOneRow()
       at Microsoft.UpdateServices.Internal.DataAccess.GetRevisionInfo(String spName, Int64 changeNumber, ArrayList deletedDeployments)
       at Microsoft.UpdateServices.Internal.DataAccessCache..ctor(ClientImplementation client)
       at Microsoft.UpdateServices.Internal.DataAccessCache.GetCache(ClientImplementation client)
       at Microsoft.UpdateServices.Internal.ClientImplementation..ctor(NotifyEventHandler handler, HttpContext httpContext). Seconds spent in constructor: 851.0370752.
       at Microsoft.UpdateServices.Internal.ClientImplementation..ctor(NotifyEventHandler handler, HttpContext httpContext)
       at Microsoft.UpdateServices.Internal.Client.CreateClientImplementationThread()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-08-21 08:30:18.428 UTC Warning w3wp.30 SoapUtilities.CreateException ThrowException: actor = ?, ID=7c2565c6-2119-40cc-9183-d35a1f271eea, ErrorCode=InternalServerError, Message=, Client=?
    2014-08-21 08:30:18.428 UTC Error w3wp.30 Client.CreateClientImplementationThread Error in CreateClientImplementationThread: System.Web.Services.Protocols.SoapException: Fault occurred
       at Microsoft.UpdateServices.Internal.SoapUtilities.ThrowException(ErrorCode errorCode, Exception e, Int32 eventLogEntryId, String[] clientIds, Boolean logToEventLog)
       at Microsoft.UpdateServices.Internal.ClientImplementation..ctor(NotifyEventHandler handler, HttpContext httpContext)
       at Microsoft.UpdateServices.Internal.Client.CreateClientImplementationThread()
       at Microsoft.UpdateServices.Internal.Client.CreateClientImplementationThread()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-08-21 08:30:37.101 UTC Error WsusService.7 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-08-21 08:30:41.382 UTC Error w3wp.25 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-08-21 08:30:41.851 UTC Info w3wp.23 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:30:41.851 UTC Error w3wp.23 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-08-21 08:32:27.184 UTC Info w3wp.8 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-08-21 08:32:27.184 UTC Warning w3wp.8 AdminDataAccess.AcquireSynchronizationMutex Unable to acquire database synchronization mutex.
    2014-08-21 08:32:27.184 UTC Warning w3wp.8 SoapExceptionProcessor.SerializeAndThrow Discarding stack trace for user DOMAIN\Administrator, IP Address fe80::75d2:2eef:1e4c:9965%11, 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)
    2014-08-21 08:35:24.784 UTC Error WsusService.8 HealthMonitoringTasks.ExecuteSubtask Health Monitoring Thread caught an exception: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteGetSingleResult()
       at Microsoft.UpdateServices.Internal.SingleValueSPHandler.ExecuteStoredProcedure(DBConnection connection)
       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)
       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.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-08-21 08:39:03.106 UTC Info w3wp.22 ThreadEntry ThreadHelper.ThreadStart
    2014-08-21 08:39:03.106 UTC Error w3wp.22 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-08-21 08:40:57.127 UTC Error WsusService.7 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-08-21 08:41:01.408 UTC Error w3wp.25 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-08-21 08:41:01.877 UTC Error w3wp.23 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()

    The errors at the end of this log are repeated ever since. I left it last week as I thought it might take a few days to update the database after the movecontent change (plus I was on holiday) and have since restarted both SQL and WSUS servers.

    Any ideas (other than re-install)?

    Chris


    • Edited by Tippers Tuesday, September 2, 2014 12:08 PM Edit
    Tuesday, September 2, 2014 12:01 PM

Answers

  • I suggest a WSUS Reset (which will re-verify all update states and mark needed updates for re-downloading) or rebuilding the WSUS server in this case.

    I took this post to mean 'do a wsus reset after installing the new instance (but kept the old WSUS content store) to save re-downloading the required updates again'

    Doing a 'reset' after installing a new instance to clean out any unneeded files carried forward in the content store is definitely a useful exercise, provided one surgically selects the updates to be approved.

    It would, however, be a pointless exercise after enabling and running the Default Automatic Approval rule.

    Then... <sigh> You enabled the Default Automatic Approval rule and ran it. Well, at least now we know how you got 4000+ approved updates! You caught and declined some of them, but still downloaded over 30GB of updates, which tells me that you still have a couple thousand approved updates which is 2x-3x more than you actually need.

    What is the point of the Default Rule then?

    Mostly.. it's an *EXAMPLE* of how to use the rules; it's certainly not intended as a suggestion of how to operate a WSUS server. Firstly, consider why you're implementing a WSUS server, and then ponder whether "approving everything" is consistent with why WSUS is being implemented.

    Of course, you also have to understand that this example was designed back in 2005 when there were barely a thousand Critical and Security Updates in the entire catalog, and most of them were actually still valid updates. The impact of approving a thousand updates in a catalog of a few thousand is exponentially different from approving a few thousand in a catalog of ten thousand.

    One must adjust accordingly now that there's nine years of content in the catalog.

    Why does it approve superceded updates?

    I'll get flamed for this answer by others.... but the only answer I got for you is: Because it does.

    There are many LEGIT reasons why an admin might want to have an active approval on a superseded update, but NOT YET have an approval on the current update. One need only look at the litany of defective updates released by the Office team over the past six months to understand this purpose.

    I will point out however, that in order to get the rule to approve those superseded updates, you have to *explicitly* choose to RUN that rule on the thousands of updates already synchronized. Since you cannot engage the AutoApproval rule on the initial synchronization, and the AutoApproval rule only applies to *NEW* content. The issue is not with the rule itself, but rather with the decision to intentionally apply it to the legacy content already present on the server.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Alex Lv Friday, October 3, 2014 10:09 AM
    Tuesday, September 16, 2014 7:50 PM

All replies

  • Hi Tippers,

    On wsus server, browse to HKLM\SOFTWARE\Microsoft\UpdateServices\Server\Setup\ContentDir and check if the path is the new path.

    Tuesday, September 2, 2014 1:56 PM
  • It reads G:\Content\ which is the path I moved everything to.
    Tuesday, September 2, 2014 1:57 PM
  • before trying to re-install wsus, you can try to run wsusutil reset.
    Tuesday, September 2, 2014 2:15 PM
  • I've just tried that this afternoon.  The command completes without any messages and after a few minutes the load on the SQL server returns.  Very similar situation to this: http://social.technet.microsoft.com/Forums/windowsserver/en-US/864682e0-5e7f-4438-8d26-f29a164517e7/all-sorts-of-timeouts-in-wsus?forum=winserverwsus

    Tuesday, September 2, 2014 2:25 PM
  • is G:\Content shared?

    check if the NT Authority\Network Service account have have Full Control permission granted to G:\Content.

    Tuesday, September 2, 2014 3:56 PM
  • No it's not shared.

    When the movecontent was done Network Service did not have any permissions on this directory.  I then added it with read permissions and restarted the Update Services service.  I have now changed it to Full Control and restarted Update Services but the SQL Server instance is still running flat out and I can't connect when the Update Services service is running.

    If the Update Services service is stopped the console connects.

    Tuesday, September 2, 2014 4:20 PM
  • can you check if the LocalContentCacheLocation on wsus db is correct?

    run this query from sql management studio:

    SELECT LocalContentCacheLocation FROM [SUSDB].[dbo].[tbConfigurationB]


    • Edited by Matteo C Tuesday, September 2, 2014 4:46 PM
    Tuesday, September 2, 2014 4:45 PM
  • It shows G:\Content\WsusContent\ which is correct and valid path.
    Tuesday, September 2, 2014 5:25 PM
  • After running the command to move my content to a new directory "wsusutil movecontent G:\Content\ G:\move.log" the WSUS console opens but after a minute it errors that it cannot connect to the database.

    Unless you've been suffering through this problem for the past two weeks before seeking assistance, I'm inclined to think that your timeout errors are purely coincidental with the moving of your content store.

    Even if you have been suffering for a couple of weeks, I'm still disinclined to think that moving the content store is the cause.

    Perhaps this article will help?

    WSUS Timeout Errors - When? and Why?, Eliminating and Avoiding

    Then there's also the speculation on why you needed to move the content store, which is almost always a symptom of the administrative issues described in the article. :-)


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.


    Tuesday, September 2, 2014 5:59 PM
  • The problems were not present before I ran the movecontent on 21/8. I then left the servers to do their work after the command as I read it might take some time to complete the background work. I was on holiday last week so it's only this week when I have returned to review the issue. Before I ran the movecontent command, the content store ran out of space when I approved some updates. It downloaded about 3Gb of 10Gb when the space ran out so I ran the Server Cleanup Wizard. It freed some space and downloaded a further 2Gb before running out again. I then ran the movecontent command so I presume this is my first mistake as the download job had not completed. Now I can see the download status in the Wsus console when the Update Services service is not running and the job is still pending/trying to complete.
    Tuesday, September 2, 2014 7:33 PM
  • So this morning I have restored the SUSDB database from a backup before I ran movecontent on 21/8.  I manually changed the content path back to the original location in the registry, IIS virtual directory, the shared folders (with permissions) and moved all content back.  When I started the Update Services service again I was able to connect to the WSUS console and the clients were connecting in.

    I then extended the original drive size to allow the downloads to complete and then did a fresh backup of the database.

    Now that my WSUS installation is working (but in the old location) I tried the movecontent again (having created a new directory with the NETWORK SERVICE having Full Control but once the process has finished the SQL errors are back (in SoftwareDistribution.log) and the thing runs at 25% CPU.  I can't connect to the WSUS console either.

    Wednesday, September 3, 2014 1:14 PM
  • This is the SoftwareDistribution.log file since the movecontent was done:

    2014-09-03 12:28:22.472 UTC Change wsusutil.1 AdminDataAccess.ExecuteSPSetConfiguration WSUS configuration has been changed
    2014-09-03 12:28:23.566 UTC Info wsusutil.1 ContentManager.LogMessage Successfully changed content file location.
    2014-09-03 12:28:23.566 UTC Info wsusutil.1 WsusServiceUtility.Start Starting WsusService
    2014-09-03 12:28:25.378 UTC Info WsusService.5 ThreadEntry ThreadHelper.ThreadStart
    2014-09-03 12:28:25.378 UTC Info WsusService.5 SusService.SusServiceStartUpThreadProc WSUS Server Version: 3.2.7600.251
    2014-09-03 12:28:25.503 UTC Info wsusutil.1 WsusServiceUtility.Start WsusService successfully started.
    2014-09-03 12:28:25.503 UTC Info wsusutil.1 ContentManager.LogMessage Content integrity check and repair...
    2014-09-03 12:28:25.519 UTC Info wsusutil.1 ContentManager.LogMessage Initiated content integrity check and repair.
    2014-09-03 12:28:25.722 UTC Info WsusService.5 SusService.CleanUpIntermediateFileDownload CleanupIntermediateFileDownload
    2014-09-03 12:28:26.394 UTC Info WsusService.7 ThreadEntry ThreadHelper.ThreadStart
    2014-09-03 12:28:26.394 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo: Startup
    2014-09-03 12:28:26.394 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ContentSyncAgent, EventInfo: Startup
    2014-09-03 12:28:26.394 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: StateMachineReset, EventInfo: Startup
    2014-09-03 12:28:26.394 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: RollupAgent, EventInfo: Startup
    2014-09-03 12:28:26.394 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: EmailNotificationAgent, EventInfo: Startup
    2014-09-03 12:28:26.394 UTC Info WsusService.8 ThreadEntry ThreadHelper.ThreadStart
    2014-09-03 12:28:26.394 UTC Info WsusService.8 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent
    2014-09-03 12:28:26.409 UTC Info WsusService.8 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ContentSyncAgent
    2014-09-03 12:28:26.409 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2014-09-03 12:28:26.425 UTC Info WsusService.8 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: StateMachineReset
    2014-09-03 12:28:26.425 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2014-09-03 12:28:26.425 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2014-09-03 12:28:26.425 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2014-09-03 12:28:26.425 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2014-09-03 12:28:26.441 UTC Info WsusService.12 ThreadEntry ThreadHelper.ThreadStart
    2014-09-03 12:28:26.441 UTC Info WsusService.12 ResetStateMachineAgent.WakeUpWorkerThreadProc State Machine Reset Agent Starting
    2014-09-03 12:28:26.441 UTC Info WsusService.8 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: RollupAgent
    2014-09-03 12:28:26.456 UTC Info WsusService.11 ThreadEntry ThreadHelper.ThreadStart
    2014-09-03 12:28:26.472 UTC Info WsusService.11 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-09-03 12:28:26.472 UTC Info WsusService.9 ThreadEntry ThreadHelper.ThreadStart
    2014-09-03 12:28:26.472 UTC Info WsusService.9 CatalogSyncAgent.HandleCatalogSyncStateCorrection Handling systemStartup work...
    2014-09-03 12:28:26.472 UTC Info WsusService.9 CatalogSyncAgent.HandleCatalogSyncStateCorrection Finished systemStartup work.
    2014-09-03 12:28:26.488 UTC Info WsusService.8 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: EmailNotificationAgent
    2014-09-03 12:28:26.503 UTC Info WsusService.9 CatalogSyncAgent.UpdateServerHealthStatusBasedOnError ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running
    2014-09-03 12:28:26.519 UTC Info WsusService.8 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2014-09-03 12:28:26.534 UTC Info WsusService.15 ThreadEntry ThreadHelper.ThreadStart
    2014-09-03 12:28:26.534 UTC Info WsusService.15 EmailNotificationAgent.WakeUpWorkerThreadProc Email Notification Agent Starting
    2014-09-03 12:28:26.581 UTC Info WsusService.11 EventLogEventReporter.ReportEvent EventId=361,Type=Information,Category=Synchronization,Message=Content synchronization started.
    2014-09-03 12:28:26.659 UTC Info WsusService.15 EmailNotificationAgent.WakeUpWorkerThreadProc Email Notification Agent Finished
    2014-09-03 12:28:26.691 UTC Info WsusService.5 SusService.SusServiceStartUpThreadProc EventId=501,Type=Information,Category=WsusService,Message=Update Services Service Started
    2014-09-03 12:28:27.691 UTC Info WsusService.11 ContentSyncAgent.WakeUpWorkerThreadProc ServerHealth: Updating Server Health for Component: ContentSyncAgent Running, Marking as Running
    2014-09-03 12:30:58.383 UTC Info WsusService.14 ThreadEntry ThreadHelper.ThreadStart
    2014-09-03 12:30:58.383 UTC Error WsusService.14 HealthMonitoringTasks.ExecuteSubtask Health Monitoring Thread caught an exception: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteGetSingleResult()
       at Microsoft.UpdateServices.Internal.SingleValueSPHandler.ExecuteStoredProcedure(DBConnection connection)
       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)
       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.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-09-03 12:31:00.258 UTC Info w3wp.50 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-09-03 12:31:00.258 UTC Info w3wp.50 WebService..cctor Initializing Reporting WebService ProcessID = 3584, Process Start Time = 03/09/2014 09:58:37, Product Version = 3.2.7600.251
    2014-09-03 12:31:04.039 UTC Info w3wp.83 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-09-03 12:31:04.039 UTC Info w3wp.83 ApiRemoting..cctor Initializing ApiRemoting WebServiceProcessID = 3584, Process Start Time = 03/09/2014 09:58:37, Product Version = 3.2.7600.251
    2014-09-03 12:31:08.211 UTC Info WsusService.14 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-09-03 12:31:08.805 UTC Info w3wp.50 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-09-03 12:31:08.805 UTC Info w3wp.50 ServerImplementation..ctor Initializing ServerSyncWebService ProcessID = 3584, Process Start Time = 03/09/2014 09:58:37, Product Version = 3.2.7600.251
    2014-09-03 12:32:48.574 UTC Error WsusService.14 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.HttpWebClientProtocol.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.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-09-03 12:32:49.715 UTC Info w3wp.83 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-09-03 12:32:49.715 UTC Info w3wp.83 SimpleAuth..ctor Initializing SimpleAuth WebService ProcessID = 3584, Process Start Time = 03/09/2014 09:58:37, Product Version = 3.2.7600.251
    2014-09-03 12:32:49.824 UTC Info w3wp.83 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
    2014-09-03 12:32:49.933 UTC Info w3wp.35 ThreadEntry ThreadHelper.ThreadStart
    2014-09-03 12:32:49.933 UTC Info w3wp.35 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-09-03 12:32:49.933 UTC Info w3wp.35 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
    2014-09-03 12:32:50.371 UTC Info w3wp.83 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-09-03 12:32:50.371 UTC Info w3wp.83 DssAuthWebServiceImplementation..ctor Initializing DssAuthWebService ProcessID = 3584, Process Start Time = 03/09/2014 09:58:37, Product Version = 3.2.7600.251
    2014-09-03 12:32:50.387 UTC Info w3wp.83 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
    2014-09-03 12:33:38.826 UTC Error w3wp.50 ServerImplementation..ctor Error in ServerImplementation constructor: System.Threading.ThreadAbortException: Thread was being aborted.
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       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, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
       at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
       at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
       at System.Activator.CreateInstance(Type type, Boolean nonPublic)
       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.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 managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    2014-09-03 12:33:38.841 UTC Warning w3wp.50 SoapUtilities.CreateException ThrowException: actor = http://serversvm10/ServerSyncWebService/serversyncwebservice.asmx, ID=4894e820-5b7d-451d-8351-10076fcbd9fc, ErrorCode=InternalServerError, Message=, Client=?
    2014-09-03 12:35:45.767 UTC Info w3wp.83 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-09-03 12:35:45.767 UTC Info w3wp.83 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-09-03 12:35:45.798 UTC Info w3wp.83 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
    2014-09-03 12:35:45.908 UTC Warning w3wp.83 SoapUtilities.CreateException ThrowException: actor = http://serversvm10/ReportingWebService/ReportingWebService.asmx, ID=15fd1c56-5255-4752-ab28-82022e2f9bb9, ErrorCode=ConfigChanged, Message=, Client=173a5108-e7f2-4435-b508-d4da9c12c1b7
    2014-09-03 12:35:45.908 UTC Error w3wp.83 WebService.ReportEventBatch Exception occured in ReportEventBatch: Fault occurred
       at Microsoft.UpdateServices.Internal.Reporting.WebService.ReportEventBatch(Cookie cookie, DateTime clientTime, ReportingEvent[] eventBatch)
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target, Object[] values)
       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.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 managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    2014-09-03 12:36:32.847 UTC Warning w3wp.50 SoapUtilities.CreateException ThrowException: actor = http://serversvm10.domain.local/ReportingWebService/ReportingWebService.asmx, ID=335771b7-ab98-45b8-9a54-f19b65b7be49, ErrorCode=ConfigChanged, Message=, Client=9b58663a-6487-4486-a833-2ca484cbdca1
    2014-09-03 12:36:32.847 UTC Error w3wp.50 WebService.ReportEventBatch Exception occured in ReportEventBatch: Fault occurred
       at Microsoft.UpdateServices.Internal.Reporting.WebService.ReportEventBatch(Cookie cookie, DateTime clientTime, ReportingEvent[] eventBatch)
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target, Object[] values)
       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.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 managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    2014-09-03 12:38:56.445 UTC Error WsusService.7 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-09-03 12:43:04.994 UTC Info w3wp.43 ThreadEntry ThreadHelper.ThreadStart
    2014-09-03 12:43:04.994 UTC Error w3wp.43 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-09-03 12:45:20.670 UTC Error WsusService.14 HealthMonitoringTasks.ExecuteSubtask Health Monitoring Thread caught an exception: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteGetSingleResult()
       at Microsoft.UpdateServices.Internal.SingleValueSPHandler.ExecuteStoredProcedure(DBConnection connection)
       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)
       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.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-09-03 12:45:20.686 UTC Info w3wp.50 ServerImplementation..ctor Initializing ServerSyncWebService ProcessID = 3584, Process Start Time = 03/09/2014 09:58:37, Product Version = 3.2.7600.251
    2014-09-03 12:46:00.796 UTC Info w3wp.27 ThreadEntry ThreadHelper.ThreadStart
    2014-09-03 12:46:00.796 UTC Error w3wp.27 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-09-03 12:46:16.219 UTC Warning w3wp.83 SoapUtilities.CreateException ThrowException: actor = http://serversvm10/ReportingWebService/ReportingWebService.asmx, ID=86acd43e-d089-407e-a014-775591ede28d, ErrorCode=ConfigChanged, Message=, Client=173a5108-e7f2-4435-b508-d4da9c12c1b7
    2014-09-03 12:46:16.219 UTC Error w3wp.83 WebService.ReportEventBatch Exception occured in ReportEventBatch: Fault occurred
       at Microsoft.UpdateServices.Internal.Reporting.WebService.ReportEventBatch(Cookie cookie, DateTime clientTime, ReportingEvent[] eventBatch)
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target, Object[] values)
       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.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 managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    2014-09-03 12:47:00.736 UTC Error WsusService.14 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.HttpWebClientProtocol.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.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-09-03 12:47:50.691 UTC Error w3wp.50 ServerImplementation..ctor Error in ServerImplementation constructor: System.Threading.ThreadAbortException: Thread was being aborted.
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       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, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
       at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
       at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
       at System.Activator.CreateInstance(Type type, Boolean nonPublic)
       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.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 managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    2014-09-03 12:47:50.706 UTC Warning w3wp.50 SoapUtilities.CreateException ThrowException: actor = http://serversvm10/ServerSyncWebService/serversyncwebservice.asmx, ID=f3cf896e-c360-4e40-bac4-586945dd0283, ErrorCode=InternalServerError, Message=, Client=?
    2014-09-03 12:49:16.475 UTC Error WsusService.7 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-09-03 12:53:25.014 UTC Error w3wp.43 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-09-03 12:56:20.816 UTC Error w3wp.27 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-09-03 12:59:30.882 UTC Error WsusService.14 HealthMonitoringTasks.ExecuteSubtask Health Monitoring Thread caught an exception: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteGetSingleResult()
       at Microsoft.UpdateServices.Internal.SingleValueSPHandler.ExecuteStoredProcedure(DBConnection connection)
       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)
       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.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-09-03 12:59:30.898 UTC Info w3wp.83 ThreadEntry PipelineRuntime.ProcessRequestNotification
    2014-09-03 12:59:30.898 UTC Info w3wp.83 ServerImplementation..ctor Initializing ServerSyncWebService ProcessID = 3584, Process Start Time = 03/09/2014 09:58:37, Product Version = 3.2.7600.251
    2014-09-03 12:59:36.507 UTC Error WsusService.7 SusEventDispatcher.DispatchManagerDatabasePollingThreadProc SusEventDispatcher got exception while polling database. Polling will continue: Excpetion details: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       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()
       at Microsoft.UpdateServices.Internal.SusEventDispatcher.DispatchManagerDatabasePollingThreadProc()
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    2014-09-03 12:59:55.774 UTC Warning w3wp.50 SoapUtilities.CreateException ThrowException: actor = http://serversvm10.domain.local/ReportingWebService/ReportingWebService.asmx, ID=b64cd49b-a908-47c7-aee4-decba99df188, ErrorCode=ConfigChanged, Message=, Client=9b58663a-6487-4486-a833-2ca484cbdca1
    2014-09-03 12:59:55.774 UTC Error w3wp.50 WebService.ReportEventBatch Exception occured in ReportEventBatch: Fault occurred
       at Microsoft.UpdateServices.Internal.Reporting.WebService.ReportEventBatch(Cookie cookie, DateTime clientTime, ReportingEvent[] eventBatch)
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target, Object[] values)
       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.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 managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    2014-09-03 12:59:55.914 UTC Warning w3wp.50 SoapUtilities.CreateException ThrowException: actor = http://serversvm10.domain.local/ReportingWebService/ReportingWebService.asmx, ID=3eb3b734-9087-401b-bd44-d0b2e2edb647, ErrorCode=ConfigChanged, Message=, Client=9b58663a-6487-4486-a833-2ca484cbdca1
    2014-09-03 12:59:55.930 UTC Error w3wp.50 WebService.ReportEventBatch Exception occured in ReportEventBatch: Fault occurred
       at Microsoft.UpdateServices.Internal.Reporting.WebService.ReportEventBatch(Cookie cookie, DateTime clientTime, ReportingEvent[] eventBatch)
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target, Object[] values)
       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.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 managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
       at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
    2014-09-03 13:01:10.948 UTC Error WsusService.14 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.HttpWebClientProtocol.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.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()

    Wednesday, September 3, 2014 1:27 PM
  • Before I ran the movecontent command, the content store ran out of space when I approved some updates.

    Bingo!

    And the content store and database were both on the same volume, probably Drive C: (the default)? Have you considered the possibility that running out of space on the volume has corrupted the WSUS database? This is a common occurrence in this scenario.

    then ran the movecontent command so I presume this is my first mistake as the download job had not completed.

    That should not have impacted the situation. BITS downloads to a temporary storage area and the hands off to the WSUSService. The WSUSService puts the file in whatever location it thinks is the current content store. If the content store is full, the WSUSService refuses the file (as you've observed). HOWEVER... if the database was corrupted, then the reconciliation that occurs after the movecontent could well have failed, hung, or caused further damage.

    Now I can see the download status in the Wsus console when the Update Services service is not running and the job is still pending/trying to complete.

    Yeah.. with the Update Services service "not running" that job ain't never gonna complete. :-)

    The downloads will remain in the queue until they are successfully completed (which cannot happen until the service is operational), or BITS is able to identify an actual download failure.

    But, to the more basic point .... the location, condition, or size of the content store has absolutely nothing to do with TIMEOUT errors. Those are between the console, webservices, and database.

    Also, there are two types of timeout errors.

    • Type 1: Caused when the console IS connected to the database and times out as a result of an operation in progress.
    • Type 2: Caused when the console cannot connect to the database.

    Now knowing that you overflowed the volume, not once, but apparently at least twice, I'd say that "Type 2" is much more likely the scenario at play here.

    You might give serious consideration to just calling it a day and rebuilding the WSUS installation with a known-healthy database. (You can keep the files you've already downloaded, although I suspect you probably don't need about 2/3 of them anyway.)


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, September 3, 2014 2:09 PM
  • I guess you're replying to my post last night!

    FYI, no the content store is not on the C drive and the database is a separate SQL server altogether.

    I don't think the restored database is corrupt else I wouldn't be able to connect to it now (and have the WSUS server working again).  See my latest post for where I am up to now.

    Wednesday, September 3, 2014 2:13 PM
  • I guess you're replying to my post last night!
    I'm replying to the post from 9/2 at 7:33pm. The one I quoted from. Until the question of "running out of space" and a possible corrupted database were resolved nothing else really mattered.

    the database is a separate SQL server ltogether.

    Good deal! :)

    I don't think the restored database is corrupt

    Restored Database????

    Restored from a backup taken WHEN?

    See my latest post for where I am up to now.

    I'm not sure where your "latest post" is.. but it's not in this thread.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.


    Friday, September 5, 2014 2:30 AM
  • Now that my WSUS installation is working (but in the old location) I tried the movecontent again (having created a new directory with the NETWORK SERVICE having Full Control but once the process has finished the SQL errors are back (in SoftwareDistribution.log) and the thing runs at 25% CPU.

    This is actually normal behavior (except the timeouts)... after you do a 'movecontent', a reconciliation is performed. As documented (back when the catalog had only a few thousand updates), that task could take a few hours. Today, depending on the server, it could take a few days!

    So answer me some questions, please:

    • How many total updates are on this WSUS server?
    • How many Approved updates are on this WSUS server?
    • How much physical disk space is consumed by the ~\WSUSContent folder?

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, September 5, 2014 2:35 AM
  • I didn't have a SQL backup but I did have a snapshot of the database in the VM backup on that date so I restored it, altered the paths back in the aforementioned places and started the Update Services service and the console worked again.

    I have extended the drive holding the updates to allow them to complete (before they didn't complete downloading due to insufficient space) but I still need to move it to another drive.  This is because I don't want to replicate the WSUS content to our DR site.

    In answer to your questions:

    1.  Total updates (from Update > All Updates) 15,315
    2. Approved updates 4278
    3. Physical disk space consumed 76.1Gb

    I have run the Server Cleanup Wizard and followed the steps in your article about declining fully installed superceded updates.  I also only have English language updates selected and the necessary Products and Classifications (excluding Drivers).

    I understand there will be a period where the database has to update after the movecontent but I previously left it for a week and it still hadn't completed.  Our hardware and resources allocated to the SQL server are not that slow!!!

    If there is corruption in the database, can I run some queries to check?  There are currently no file downloads happening yet the tbFileDownloadProgress table shows four entries. For each entry the TotalBytes is the same as the BytesDownloaded.

    Friday, September 5, 2014 10:55 AM
  • Can you look in the SUSDB and see if any stored procedures are running presently?
    Friday, September 5, 2014 11:48 PM
  • I have run the Server Cleanup Wizard and followed the steps in your article about declining fully installed superceded updates.

    And yet, you still have over 4000 approved updates consuming 76GB of disk space.

    Methinks there's probably another 3000+ superseded/notNeeded updates that can have approvals removed.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Saturday, September 6, 2014 4:14 PM
  • I have declined more superceded updates (regardless of installed count) and that has reduced the number of approved updates to 2100 and the content store size to 35Gb.

    I have done a SQL backup of the database and run the movecontent again while having SQL Profiler running.

    Once the movecontent completes and starts up the Update Services service again, there is a 12 minute period in the SoftwareDistribution.log where no exceptions are logged.  Then I get the following:

    2014-09-08 15:28:49.996 UTC	Error	WsusService.13	HealthMonitoringTasks.ExecuteSubtask	Health Monitoring Thread caught an exception: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteGetSingleResult()
       at Microsoft.UpdateServices.Internal.SingleValueSPHandler.ExecuteStoredProcedure(DBConnection connection)
       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)
       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.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()

    In terms of looking for the running stored procedure, I can see lots of activity in the SQL Profiler trace at that time but a lot of it is repetitive and it's hard to identitfy excatly what goes wrong and where. Any pointers on what to look for or where in the tables there might be data errors?

    Monday, September 8, 2014 4:04 PM
  • Once the movecontent completes and starts up the Update Services service again, there is a 12 minute period in the SoftwareDistribution.log where no exceptions are logged.  Then I get the following:

    (Please do not post log segments as CODE blocks. It makes the logfile exceptionally difficult to read.)

    As for the log entry after ~12 minutes, my guess would be that this is a standard HealthMonitoringSystem check, and it's failing with a timeout. Most likely because the WSUS server is still performing the post-movecontent file reconciliation, and the database is too busy to respond. It could be several hours after a movecontent before the reconciliation is completed, even more so since you still have thousands of approved updates and 35GB of files.

    Today it's now 36 hours later from the above log entry, are the timeouts still occurring?


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, September 10, 2014 4:15 PM
  • Once I got the same error again I reverted to the backup version of the database and manually put the path back so I had a working WSUS installation. Given that when I initially posed this question I had left the SQL server for a week to complete the post movecontent file reconciliation (admittedly it had 4000 approved updates) wouldn't that indicate it is stuck somewhere? I can't recall the number of updates or even the version of WSUS, but when I did the movecontent previously I don't remember it taking days, perhaps just hours. I'm leaning towards doing a re-install of WSUS to fix this as I need to get the path changed in the next week.
    • Edited by Tippers Wednesday, September 10, 2014 7:15 PM
    Wednesday, September 10, 2014 7:15 PM
  • (admittedly it had 4000 approved updates) wouldn't that indicate it is stuck somewhere?

    *stuck* somewhere... No. Performing a task that may take several *days* to complete due the complexity of having 4000 approved updates in the database... Absolutely.

    but when I did the movecontent previously I don't remember it taking days, perhaps just hours

    And when did you do this previous 'movecontent'? How many approved updates were there? What was the number/size of files in the content store?

    I'm leaning towards doing a re-install of WSUS to fix this as I need to get the path changed in the next week.

    This is always a viable option, provided you change how you administer approvals and maintain the server. :-)

    In many cases it takes less time to build a new, properly configured server, with minimally approved updates, than it does to "fix" the existing one.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Thursday, September 11, 2014 1:49 AM
  • I suggest a WSUS Reset (which will re-verify all update states and mark needed updates for re-downloading) or rebuilding the WSUS server in this case.
    Thursday, September 11, 2014 6:08 PM
  • I suggest a WSUS Reset (which will re-verify all update states and mark needed updates for re-downloading) or rebuilding the WSUS server in this case.

    Presumably doing a 'reset' (pursuant to doing the 'movecontent') is why his environment was "stuck" in the first place.

    Given our recent conversations, I'm particularly concerned that anybody would even recommend launching a RESET against a machine that has THOUSANDS of approved updates. :-(


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.


    Saturday, September 13, 2014 1:42 AM
  • I didn't do a reset, I deleted the content files and once the new install had completed I set about approving the updates again.

    To do this I enabled the Default Approval rule and then ran it.  As soon as this had completed the console reported that it wanted to download 81Gb of updates so I quickly went through and declined any superceded updates and it only downloaded around 30Gb of updates.  Once the clients had checked in again (over the next 24 hours) I ran the Server Cleanup wizard.

    I am including updates for Windows XP, Vista and 7 and Server 2003, 2008 and 2008 R2.  Offfice versions 2003 to 2010 and Exchange 2010 and SQL server 2008.  I am not including Drivers but all other categories.  The console still reports 3300+ approved updates and I don't see a way to get this down further.

    I know you'll say XP and Office 2003 are not support so there is no point including them and to a point you are correct.  Once I have got the remaining client up-to-date I can remove this (and no I cannot remove it from our network as we have a legacy piece of software which only runs XP - that's another story which I am working on).

    Monday, September 15, 2014 10:15 AM
  • I didn't do a reset, I deleted the content files and once the new install had completed I set about approving the updates again.

    In your original post (9/2 1701GMT), you reported running a 'wsusutil movecontent' on 8/21. THAT command launches a 'reset' as part of the reconciliation of having moved the content.

    In a subsequent post, 9/2 2120GMT the 'reset' was obviously still running -- 12 days later, potentially complicated by the fact that incorrect ACLs were configured, but not actually fixed until September 2nd.

    Then, on 9/3 you restored the SUSDB from a pre-8/21 update and made manual changes (it would have been preferable to use 'wsusutil movecontent -skipcopy' because it's impossible to know whether your manual changes caught everything that needed to be changed. Nonetheless, it seems that you were able to restore functionality to the server, ostensibly in the state it existed somewhat prior to the original 'movecontent' performed on 8/21.

    Then you launched another 'movecontent' on 9/3, apparently without having addressed any of the possible causes, or necessary remediations, for the abject failure of the original movecontent launched two weeks earlier.

    Then, on 9/5 we get some additional relevant information to this scenario:

    • You have 15,315 updates on this WSUS server.
    • You have 4,278 approved updates on this WSUS server.
    • Your content store is 76.1GB in size.

    On 9/8 you reduced the number of approved updates to 2,100 (still 3x what it should be), and 35GB of disk space (also 3x what it should be).

    **NOW** you tell us that you

    deleted the content files and once the new install had completed I set about approving the updates again

    Would it be accurate to simply that statement to say that you installed a *NEW* WSUS instance?

    Then... <sigh> You enabled the Default Automatic Approval rule and ran it. Well, at least now we know how you got 4000+ approved updates! You caught and declined some of them, but still downloaded over 30GB of updates, which tells me that you still have a couple thousand approved updates which is 2x-3x more than you actually need.

    I don't know what else to say here, dude. I provided you a link back on 9/2 to a 4000+ word blog series that describes everything you should need to know and do, to address this issue, and nowhere in there does it say to "install a new server and run the Default AutoApproval rule".

    To put this in perspective... I have almost exactly the same products and classifications on my LAB WSUS server that you have on yours (I'm not syncing Office 2003, but I do have extra versions of SQL Server). I have 8,829 synchronized updates, of which 997 are approved. My ~\WSUSContent folder consumes 18.6GB of space. Oh yeah.. and I haven't actually approved/deployed any updates in a couple of months. Of those 997 approved updates, 219 are superseded and will actually be declined in the very near term once the replacement updates get deployed. That leaves about 778 updates with actual (needed) approvals. (Which is <10% of the total number of updates, and has been, over several years, my general observation for a healthy number of approved updates on a WSUS server.)

    The console still reports 3300+ approved updates and I don't see a way to get this down further.

    If you follow the guidance in the blog series I provided the link for, and create the Custom View to see the Superseded updates with approvals, I'm sure you'll find at least a couple thousand that don't need to have approvals.

    Hint: Windows 7/Windows Server 2008 R2 Service Pack 1 did not explicitly list superseded updates, so you'll have to use a bit of creative evaluation here. Consider that pretty much any W7/WS2008R2 update dated prior to 2011 was probably included in (and superseded by) SP1. That will account for a few hundred... but not a couple thousand.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.


    Tuesday, September 16, 2014 3:03 AM
  • I suggest a WSUS Reset (which will re-verify all update states and mark needed updates for re-downloading) or rebuilding the WSUS server in this case.

    I took this post to mean 'do a wsus reset after installing the new instance (but kept the old WSUS content store) to save re-downloading the required updates again' hence my reply stating that I started from scratch.  My reply did not relate to the attempts to salvage the old WSUS instance.

    Crossed wires there.

    Then... <sigh> You enabled the Default Automatic Approval rule and ran it. Well, at least now we know how you got 4000+ approved updates! You caught and declined some of them, but still downloaded over 30GB of updates, which tells me that you still have a couple thousand approved updates which is 2x-3x more than you actually need.

    What is the point of the Default Rule then?

    Why does it approve superceded updates?

    I'll look into the updates for Windows 7/Windows Server 2008 R2 post SP1 and see how many are still Approved.

    If you follow the guidance in the blog series I provided the link for, and create the Custom View to see the Superseded updates with approvals, I'm sure you'll find at least a couple thousand that don't need to have approvals.

    I have followed two posts titled "Removing Unneeded Update Approvals" and "Too Many Updates" before I posted my previous message.

    I now have a working WSUS instance and a little more understanding about how I need to manage the approvals and updates in the future (for which I am grateful).  I'll try and find more updates to filter out and bring the number of approved updates down to below 10% of the total (which is 10280 synchronised).

    Tuesday, September 16, 2014 1:09 PM
  • Hi Trippers, is this problem still pending or resolved?
    Tuesday, September 16, 2014 2:01 PM
  • I suggest a WSUS Reset (which will re-verify all update states and mark needed updates for re-downloading) or rebuilding the WSUS server in this case.

    I took this post to mean 'do a wsus reset after installing the new instance (but kept the old WSUS content store) to save re-downloading the required updates again'

    Doing a 'reset' after installing a new instance to clean out any unneeded files carried forward in the content store is definitely a useful exercise, provided one surgically selects the updates to be approved.

    It would, however, be a pointless exercise after enabling and running the Default Automatic Approval rule.

    Then... <sigh> You enabled the Default Automatic Approval rule and ran it. Well, at least now we know how you got 4000+ approved updates! You caught and declined some of them, but still downloaded over 30GB of updates, which tells me that you still have a couple thousand approved updates which is 2x-3x more than you actually need.

    What is the point of the Default Rule then?

    Mostly.. it's an *EXAMPLE* of how to use the rules; it's certainly not intended as a suggestion of how to operate a WSUS server. Firstly, consider why you're implementing a WSUS server, and then ponder whether "approving everything" is consistent with why WSUS is being implemented.

    Of course, you also have to understand that this example was designed back in 2005 when there were barely a thousand Critical and Security Updates in the entire catalog, and most of them were actually still valid updates. The impact of approving a thousand updates in a catalog of a few thousand is exponentially different from approving a few thousand in a catalog of ten thousand.

    One must adjust accordingly now that there's nine years of content in the catalog.

    Why does it approve superceded updates?

    I'll get flamed for this answer by others.... but the only answer I got for you is: Because it does.

    There are many LEGIT reasons why an admin might want to have an active approval on a superseded update, but NOT YET have an approval on the current update. One need only look at the litany of defective updates released by the Office team over the past six months to understand this purpose.

    I will point out however, that in order to get the rule to approve those superseded updates, you have to *explicitly* choose to RUN that rule on the thousands of updates already synchronized. Since you cannot engage the AutoApproval rule on the initial synchronization, and the AutoApproval rule only applies to *NEW* content. The issue is not with the rule itself, but rather with the decision to intentionally apply it to the legacy content already present on the server.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Alex Lv Friday, October 3, 2014 10:09 AM
    Tuesday, September 16, 2014 7:50 PM
  • No further help required thanks.
    Friday, October 3, 2014 4:27 PM