Unable to Synchronize with Replica Server Scott 10/24/2008 7:49:02 PM Since late August the replica server stopped synchronizing with the main WSUS 3.0 SP1 server. The replica server is configured identically with other replica servers which are synchronizing OK with the main server. Here are log excerpts... how do I fix this?: C:\Program Files\Update Services\LogFiles\Change.log: 2007 Microsoft Office System (KB951596) by WUS Server UpdateID:C15269A7-1779-47C4-BDC1-371317E81708 Revision Number:101 TargetGroup:All Computers 2008-08-13 04:19:35.684 UTC Downloading retried 2008-08-14 04:15:01.304 UTC WSUS configuration has been changed 2008-08-14 04:15:01.554 UTC Downloading retried 2008-08-15 04:15:01.229 UTC WSUS configuration has been changed 2008-08-15 04:15:03.479 UTC Downloading retried 2008-08-16 04:15:11.436 UTC WSUS configuration has been changed 2008-08-16 04:15:12.155 UTC Downloading retried 2008-10-24 15:09:08.570 UTC Synchronization manually started 2008-10-24 16:02:09.369 UTC Synchronization stopped 2008-10-24 19:00:59.157 UTC Synchronization manually started 2008-10-24 19:07:25.663 UTC Synchronization stopped 2008-10-24 19:09:38.191 UTC Synchronization manually started 2008-10-24 19:19:06.207 UTC Synchronization stopped 2008-10-24 19:36:55.539 UTC Synchronization manually started 2008-10-24 19:37:55.475 UTC Synchronization stopped SoftwareDistribution.log: 2008-10-24 19:19:08.223 UTC Info w3wp.20 ChangeNotificationDispatcher.InternalEventHandler Get event ConfigurationChange from dispatchmanager 2008-10-24 19:19:08.223 UTC Info w3wp.11 Client.OnConfigurationChange Creating a new ClientImplementation because the DB configuration changed 2008-10-24 19:19:09.176 UTC Info w3wp.6 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2008-10-24 19:19:09.192 UTC Info w3wp.19 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange 2008-10-24 19:19:09.192 UTC Info w3wp.5 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange 2008-10-24 19:19:09.239 UTC Info w3wp.5 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange 2008-10-24 19:19:10.035 UTC Info w3wp.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2008-10-24 19:19:10.051 UTC Info w3wp.18 ThreadEntry ThreadHelper.ThreadStart 2008-10-24 19:19:10.051 UTC Info w3wp.18 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange 2008-10-24 19:19:42.831 UTC Warning w3wp.1 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used. 2008-10-24 19:19:46.128 UTC Warning w3wp.1 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used. 2008-10-24 19:19:46.144 UTC Warning w3wp.1 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used. 2008-10-24 19:36:55.539 UTC Change w3wp.1 AdminDataAccess.StartSubscriptionManually Synchronization manually started 2008-10-24 19:36:56.164 UTC Info w3wp.6 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2008-10-24 19:36:56.180 UTC Info w3wp.17 ThreadEntry ThreadHelper.ThreadStart 2008-10-24 19:36:56.180 UTC Info w3wp.17 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange 2008-10-24 19:36:56.180 UTC Info w3wp.5 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange 2008-10-24 19:36:56.227 UTC Info w3wp.5 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange 2008-10-24 19:36:57.461 UTC Info w3wp.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2008-10-24 19:36:57.477 UTC Info w3wp.15 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange 2008-10-24 19:36:59.258 UTC Info w3wp.12 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2008-10-24 19:36:59.274 UTC Info w3wp.24 ThreadEntry ThreadHelper.ThreadStart 2008-10-24 19:36:59.274 UTC Info w3wp.24 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange 2008-10-24 19:36:59.274 UTC Info w3wp.24 ChangeNotificationDispatcher.InternalEventHandler Get event ConfigurationChange from dispatchmanager 2008-10-24 19:36:59.274 UTC Info w3wp.11 Client.OnConfigurationChange Creating a new ClientImplementation because the DB configuration changed 2008-10-24 19:37:55.475 UTC Change w3wp.1 AdminDataAccess.StopSubscription Synchronization stopped 2008-10-24 19:37:56.178 UTC Info w3wp.6 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2008-10-24 19:37:56.194 UTC Info w3wp.25 ThreadEntry ThreadHelper.ThreadStart 2008-10-24 19:37:56.194 UTC Info w3wp.25 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange

Re: Unable to Synchronize with Replica Server "Lawrence Garvin \(MVP\)" <lawrence[ at ]nospam> 10/24/2008 8:59:16 PM "Scott" <Scott[ at ]discussions.microsoft.com> wrote in message news:0EE56735-1EA6-4976-8646-68B17EB51317[ at ]microsoft.com... [Quoted Text] > Since late August the replica server stopped synchronizing with the main > WSUS > 3.0 SP1 server. The replica server is configured identically with other > replica servers which are synchronizing OK with the main server. > Here are log excerpts... how do I fix this?: > 2008-08-14 04:15:01.304 UTC WSUS configuration has been changed > 2008-08-14 04:15:01.554 UTC Downloading retried > 2008-08-15 04:15:01.229 UTC WSUS configuration has been changed > 2008-08-15 04:15:03.479 UTC Downloading retried > 2008-08-16 04:15:11.436 UTC WSUS configuration has been changed > 2008-08-16 04:15:12.155 UTC Downloading retried > 2008-10-24 15:09:08.570 UTC Synchronization manually started > 2008-10-24 16:02:09.369 UTC Synchronization stopped Well, gee, I'd start with trying to determine what changed in the "WSUS Configuration" back in August when it first started failing, and once I'd determined that, I'd =undo= that change to see if it started synchronizing again. -- Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2009) MS WSUS Website: http://www.microsoft.com/wsus My Websites: http://www.onsitechsolutions.com; http://wsusinfo.onsitechsolutions.com My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

Re: Unable to Synchronize with Replica Server Scott 10/27/2008 10:17:01 PM The configuration didn't change. It is configured the same way as other replica servers which are synchronizing successfully. Any suggestions as to what could be causing this and how to fix it? "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "Scott" <Scott[ at ]discussions.microsoft.com> wrote in message > news:0EE56735-1EA6-4976-8646-68B17EB51317[ at ]microsoft.com... > > Since late August the replica server stopped synchronizing with the main > > WSUS > > 3.0 SP1 server. The replica server is configured identically with other > > replica servers which are synchronizing OK with the main server. > > Here are log excerpts... how do I fix this?: > > > 2008-08-14 04:15:01.304 UTC WSUS configuration has been changed > > 2008-08-14 04:15:01.554 UTC Downloading retried > > 2008-08-15 04:15:01.229 UTC WSUS configuration has been changed > > 2008-08-15 04:15:03.479 UTC Downloading retried > > 2008-08-16 04:15:11.436 UTC WSUS configuration has been changed > > 2008-08-16 04:15:12.155 UTC Downloading retried > > > 2008-10-24 15:09:08.570 UTC Synchronization manually started > > 2008-10-24 16:02:09.369 UTC Synchronization stopped > > Well, gee, I'd start with trying to determine what changed in the "WSUS > Configuration" back in August when it first started failing, > and once I'd determined that, I'd =undo= that change to see if it started > synchronizing again. > > > > > -- > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > Principal/CTO, Onsite Technology Solutions, Houston, Texas > Microsoft MVP - Software Distribution (2005-2009) > > MS WSUS Website: http://www.microsoft.com/wsus > My Websites: http://www.onsitechsolutions.com; > http://wsusinfo.onsitechsolutions.com > My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin > >

Re: Unable to Synchronize with Replica Server "Lawrence Garvin \(MVP\)" <lawrence[ at ]nospam> 10/28/2008 12:30:31 AM "Scott" <Scott[ at ]discussions.microsoft.com> wrote in message news:CB07879F-41D3-41C0-AC9B-D33AA55E1EE3[ at ]microsoft.com... [Quoted Text] > The configuration didn't change. It is configured the same way as other > replica servers which are synchronizing successfully. Yes.. I understand that you *believe* the configuration has not changed... and perhaps, even, the configuration of the =WSUS Server= has not actually changed... But my 20+ years of experience tells me that the reality when something "used to work" but "now doesn't work", is that ==something changed somewhere==. The objective of the diagnostician is to identify "What Changed?" And when you identify what changed, you'll identify the cause and solution to the issue. > Any suggestions as to what could be causing this and how to fix it? Not a clue. It is impossible for me to identify, much less even begin to speculate, what might have changed to cause this, and without knowing the cause, it's impossible to determine the remediation. >> > Here are log excerpts... how do I fix this?: >> >> > 2008-08-14 04:15:01.304 UTC WSUS configuration has been changed >> > 2008-08-14 04:15:01.554 UTC Downloading retried >> > 2008-08-15 04:15:01.229 UTC WSUS configuration has been changed >> > 2008-08-15 04:15:03.479 UTC Downloading retried >> > 2008-08-16 04:15:11.436 UTC WSUS configuration has been changed >> > 2008-08-16 04:15:12.155 UTC Downloading retried Now, since this logfile is the CHANGE.LOG from the WSUS Server, and the entry on 8/14 at 0415Z, and the entry on 8/15 at 0415Z, and the entry on 8/16 at 0415Z says that the "WSUS configuration has been changed"... (which apparently triggered a "retry" of whatever was downloading...) then the only thing I can (at the moment) ask you is "WHAT changed at 0415Z on the days of 8/14, 8/15, and 8/16?" that would cause these log entries to be made? From your original post... looking at the Change.log and SoftwareDistribution.log for the synchronization [ at ] 10/24 1936Z about the only thing I can get from these log entries is "something changed". (Now, it's also possible that I'm missing something subtle in these log entries; you might consider calling PSS and opening a ticket.) 2008-10-24 19:36:55.539 UTC Synchronization manually started 2008-10-24 19:36:55.539 UTC Change w3wp.1 AdminDataAccess.StartSubscriptionManually Synchronization manually started 2008-10-24 19:36:56.164 UTC Info w3wp.6 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2008-10-24 19:36:56.180 UTC Info w3wp.17 ThreadEntry ThreadHelper.ThreadStart 2008-10-24 19:36:56.180 UTC Info w3wp.17 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange 2008-10-24 19:36:56.180 UTC Info w3wp.5 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange 2008-10-24 19:36:56.227 UTC Info w3wp.5 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange 2008-10-24 19:36:57.461 UTC Info w3wp.8 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2008-10-24 19:36:57.477 UTC Info w3wp.15 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange 2008-10-24 19:36:59.258 UTC Info w3wp.12 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2008-10-24 19:36:59.274 UTC Info w3wp.24 ThreadEntry ThreadHelper.ThreadStart 2008-10-24 19:36:59.274 UTC Info w3wp.24 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange 2008-10-24 19:36:59.274 UTC Info w3wp.24 ChangeNotificationDispatcher.InternalEventHandler Get event ConfigurationChange from dispatchmanager 2008-10-24 19:36:59.274 UTC Info w3wp.11 Client.OnConfigurationChange Creating a new ClientImplementation because the DB configuration changed 2008-10-24 19:37:55.475 UTC Change w3wp.1 AdminDataAccess.StopSubscription Synchronization stopped 2008-10-24 19:37:55.475 UTC Synchronization stopped but bottom line.... based on what you've given us.... and the suggestion that "something changed" ten weeks ago.... I don't really have much more to offer. -- Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2009) MS WSUS Website: http://www.microsoft.com/wsus My Websites: http://www.onsitechsolutions.com; http://wsusinfo.onsitechsolutions.com My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin