昨日刚刚修好的WSUS server夜里再度响起同步失败的报警
c:\program files\update services\logfiles\softwardistribution.log
2014-08-14 03:22:29.436 UTC Info w3wp.3 ServerImplementation.UpdateCache Database change occured; check if we need to update cache.
2014-08-14 03:28:00.636 UTC Warning w3wp.3 SoapUtilities.CreateException ThrowException: actor = http://nlacc00w8sd001.poc-a.dsm-group.com:8530/ReportingWebService/ReportingWebService.asmx, ID=2e732040-080c-4bef-8a69-aee7eba2f955, ErrorCode=ConfigChanged, Message=, Client=560a404a-710e-46f3-9e96-0d5019d1bb0a
2014-08-14 03:28:00.654 UTC Error w3wp.3 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.ApplicationStepManager.ResumeSteps(Exception error)
at System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
at System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)
at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)
2014-08-14 03:36:05.777 UTC Change w3wp.8 AdminDataAccess.StartSubscriptionManually Synchronization manually started
2014-08-14 03:36:09.677 UTC Info w3wp.17 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2014-08-14 03:36:09.680 UTC Info w3wp.56 ThreadEntry ThreadHelper.ThreadStart
2014-08-14 03:36:09.681 UTC Info w3wp.56 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2014-08-14 03:36:09.682 UTC Info w3wp.16 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
2014-08-14 03:36:09.787 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo:
2014-08-14 03:36:09.870 UTC Info WsusService.3 ThreadEntry ThreadHelper.ThreadStart
W3se001 上游服务怎么代理服务器又添加上去了？不会吧，凌晨三点不会有人改配置或者上change的
取消了代理和MS 同步下
同步成功为毛8月补丁还是不显示只有7月的
SQL挂了？
The client was unable to reuse a session with SPID 62, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
On 14-8-2014 3:00:44, component SMS_WSUS_SYNC_MANAGER on computer NLACC00W3SD001 reported: SMS WSUS Synchronization failed.
Message: UssCommunicationError: WebException: The underlying connection was closed: The connection was closed unexpectedly.
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context).
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction.SyncWSUS.
The operating system reported error 2148734464:
For more information, see Help and Support Center at
无法连接WSUS 数据库了啊，这wsus用的是sql
重启sql服务吧
4点重启之后再次同步数据源，还是有错。无法执行搜索？磁盘满了？SQL无法写入？一看果然D盘没有空间了，0 剩余，果然是写不了。。。
清理下终于稍微腾出一点空间了。
打开命令提示符。
键入 wuauclt.exe /resetauthorization /detectnow 以强制进行检测。
根据客户端的数量，完成初始同步可能需花费几分钟到几小时时间。 若要确认同步已完成，请在 WSUS 管理控制台中，展开“计算机”，然后单击“所有计算机”。 在“状态”窗格中，单击“任意”，然后单击“刷新”。 确认列出了您期望看到与此 WSUS 服务器同步的计算机。 必须使用迁移后时间戳刷新“Last Contact Date”（最后联系日期）：
打开命令提示符。
键入 wuauclt.exe /detectnow 以强制进行检测。
键入 wuauclt.exe /reportnow 强制进行报告，以验证“Last Contact Date”（最后联系日期）是否已更新。
8月补丁果然显示正常，但是计算机信息丢失了，过一段时间系统就会继续检测软件库存和硬件库存
component SMS_WSUS_SYNC_MANAGER on computer NLACC00W3SD001 reported: SMS WSUS,布布扣,bubuko.com
component SMS_WSUS_SYNC_MANAGER on computer NLACC00W3SD001 reported: SMS WSUS
原文：http://433266.blog.51cto.com/423266/1539845