Normales Thema Workaround für Sync-Problem (Gelesen: 3063 mal)
Manuel1889
WSUS Neuling
Offline


I Love WSUS!

Beiträge: 9
Mitglied seit: 09.10.08
Workaround für Sync-Problem
23.10.08 um 07:21:54
Beitrag drucken  
Hallo

Ich wollte den Workaround für das Sync-Problem durchführen.
Ich habe jetzt einen 2. server aufgesetzt, WSUS mit der Option Repliaktserver installiert, aber dei beiden syncen nicht miteinander.
der alte Server erkennt den neuen unter downstreamserver aber die beiden syncen einfach nicht. Eine verbindung besteht, da wenn ich auch dem neuen die einstellungen ändere sehe ich dieses sofort auf dem alten.

Bitte um HILFE!

Danke
  
Zum Seitenanfang
 
Sunny
Microsoft MVP
*****
Offline



Beiträge: 13250
Mitglied seit: 11.02.07
Geschlecht: männlich
Re: Workaround für Sync-Problem
Antwort #1 - 23.10.08 um 08:32:54
Beitrag drucken  
Welche Version vom WSUS hast Du denn auf beiden Seite? Und was steht in der SoftwareDistribution.log? Die Log findest Du im Programmverzeichnis vom WSUS.
  
Zum Seitenanfang
 
Manuel1889
WSUS Neuling
Offline


I Love WSUS!

Beiträge: 9
Mitglied seit: 09.10.08
Re: Workaround für Sync-Problem
Antwort #2 - 23.10.08 um 08:40:33
Beitrag drucken  
Erstmal danke für die Schnelle antwort.

WSUS 3.0

Log:
2008-10-23 06:37:11.168 UTC      Info      w3wp.12      Client.OnConfigurationChange      Creating a new ClientImplementation because the DB configuration changed
2008-10-23 06:37:11.184 UTC      Info      w3wp.12      WebServiceCommunicationHelper.GetProxyConfiguration      Use Proxy: server17:8080
2008-10-23 06:37:11.200 UTC      Info      w3wp.12      WebServiceCommunicationHelper.GetProxyConfiguration      Using Proxy Credentials: dhlconnect : ****
2008-10-23 06:37:11.200 UTC      Info      w3wp.12      AuthorizationManager.GetUpstreamServerUriHeader      Found config says USS is MU site
2008-10-23 06:37:11.371 UTC      Info      w3wp.5      SusEventDispatcher.TriggerEvent      TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2008-10-23 06:37:11.371 UTC      Info      w3wp.137      ThreadEntry      ThreadHelper.ThreadStart
2008-10-23 06:37:11.371 UTC      Info      w3wp.137      SusEventDispatcher.DispatchManagerWorkerThreadProc      DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2008-10-23 06:37:11.371 UTC      Info      w3wp.8      SusEventDispatcher.RegisterEventHandler      RegisterEventHandler called for NotificationEventName: ConfigurationChange
2008-10-23 06:37:11.403 UTC      Info      w3wp.8      WebServiceCommunicationHelper.GetProxyConfiguration      Use Proxy: server17:8080
2008-10-23 06:37:11.403 UTC      Info      w3wp.8      WebServiceCommunicationHelper.GetProxyConfiguration      Using Proxy Credentials: dhlconnect : ****
2008-10-23 06:37:11.403 UTC      Info      w3wp.8      AuthorizationManager.GetUpstreamServerUriHeader      Found config says USS is MU site
2008-10-23 06:37:11.418 UTC      Info      w3wp.8      SusEventDispatcher.RegisterEventHandler      RegisterEventHandler called for NotificationEventName: ConfigurationChange
2008-10-23 06:37:11.434 UTC      Info      w3wp.8      WebServiceCommunicationHelper.GetProxyConfiguration      Use Proxy: server17:8080
2008-10-23 06:37:11.434 UTC      Info      w3wp.8      WebServiceCommunicationHelper.GetProxyConfiguration      Using Proxy Credentials: dhlconnect : ****
2008-10-23 06:37:11.434 UTC      Info      w3wp.8      AuthorizationManager.GetUpstreamServerUriHeader      Found config says USS is MU site
2008-10-23 06:37:15.309 UTC      Info      WsusService.16      SusEventDispatcher.TriggerEvent      TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2008-10-23 06:37:15.309 UTC      Info      WsusService.108      ThreadEntry      ThreadHelper.ThreadStart
2008-10-23 06:37:15.309 UTC      Info      WsusService.108      SusEventDispatcher.DispatchManagerWorkerThreadProc      DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2008-10-23 06:37:15.715 UTC      Change      w3wp.1      AdminDataAccess.StopSubscription      Synchronization stopped
2008-10-23 06:37:20.403 UTC      Info      WsusService.16      SusEventDispatcher.TriggerEvent      TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo:
2008-10-23 06:37:20.824 UTC      Info      WsusService.128      ThreadEntry      ThreadHelper.ThreadStart
2008-10-23 06:37:20.824 UTC      Info      WsusService.128      SusEventDispatcher.DispatchManagerWorkerThreadProc      DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent
2008-10-23 06:37:20.824 UTC      Info      WsusService.122      ThreadEntry      ThreadHelper.ThreadStart
2008-10-23 06:37:20.824 UTC      Info      WsusService.122      CatalogSyncAgent.WaitUntilSyncFinishedOrCancelled      Found WakeUp event while doing sync.
2008-10-23 06:37:21.043 UTC      Info      WsusService.122      CatalogSyncAgent.WaitUntilSyncFinishedOrCancelled      Found subscription 1 status=5
2008-10-23 06:37:23.652 UTC      Warning      WsusService.131      CatalogSyncAgentCore.ExecuteSyncProtocol      User cancelled - Microsoft.UpdateServices.ServerSync.CatalogSyncCancelException
   bei Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CheckUserCancelEvent(In
t32 waitMs)
   bei Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boo
lean allowRedirect)
2008-10-23 06:37:23.652 UTC      Info      WsusService.131      CatalogSyncAgentCore.UpdateSyncResultAndGenerateReportingEvent      CatalogSyncThreadProcess: report subscription User cancelled
2008-10-23 06:37:23.652 UTC      Info      WsusService.131      EventLogEventReporter.ReportEvent      EventId=387,Type=Information,Category=Synchronization,Message=Synchronisierung wurde beendet.
2008-10-23 06:37:23.684 UTC      Change      WsusService.122      CatalogSyncAgentCore.Cancel      Catalog Sync is canceled
2008-10-23 06:37:23.684 UTC      Info      WsusService.122      CatalogSyncAgent.SetSubscriptionStateWithRetry      Firing event Cancelled...
2008-10-23 06:37:23.699 UTC      Info      WsusService.122      CatalogSyncAgent.WakeUpWorkerThreadProc      Found no more jobs. CatalogSyncAgent quits but will run rollup before terminating ...
2008-10-23 06:37:23.715 UTC      Info      WsusService.122      CatalogSyncAgent.UpdateServerHealthStatusBasedOnError      ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running
2008-10-23 06:37:25.606 UTC      Info      WsusService.16      SusEventDispatcher.TriggerEvent      TriggerEvent called for NotificationEventName: RollupAgent, EventInfo:
2008-10-23 06:37:25.606 UTC      Info      WsusService.85      ThreadEntry      ThreadHelper.ThreadStart
2008-10-23 06:37:25.606 UTC      Info      WsusService.85      SusEventDispatcher.DispatchManagerWorkerThreadProc      DispatchManager Worker Thread Processing NotificationEvent: RollupAgent
2008-10-23 06:37:25.621 UTC      Info      WsusService.16      SusEventDispatcher.TriggerEvent      TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2008-10-23 06:37:25.621 UTC      Info      WsusService.85      SusEventDispatcher.DispatchManagerWorkerThreadProc      DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2008-10-23 06:37:25.668 UTC      Info      WsusService.45      ThreadEntry      ThreadHelper.ThreadStart
2008-10-23 06:37:25.684 UTC      Info      WsusService.45      RollupEventReporter.BuildReportingServiceUrl      Found config says USS is MU site
2008-10-23 06:37:25.684 UTC      Info      WsusService.45      WebServiceCommunicationHelper.GetProxyConfiguration      Use Proxy: server17:8080
2008-10-23 06:37:25.684 UTC      Info      WsusService.45      WebServiceCommunicationHelper.GetProxyConfiguration      Using Proxy Credentials: dhlconnect : ****
2008-10-23 06:37:25.918 UTC      Info      WsusService.45      MicrosoftUpdateRollup.ReportEvents      Rolling up 2 events.
2008-10-23 06:37:26.262 UTC      Info      w3wp.7      SusEventDispatcher.TriggerEvent      TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2008-10-23 06:37:26.277 UTC      Info      w3wp.115      ThreadEntry      ThreadHelper.ThreadStart
2008-10-23 06:37:26.277 UTC      Info      w3wp.115      SusEventDispatcher.DispatchManagerWorkerThreadProc      DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2008-10-23 06:37:26.387 UTC      Info      w3wp.115      WebServiceCommunicationHelper.GetProxyConfiguration      Use Proxy: server17:8080
2008-10-23 06:37:26.402 UTC      Info      w3wp.115      WebServiceCommunicationHelper.GetProxyConfiguration      Using Proxy Credentials: dhlconnect : ****
2008-10-23 06:37:26.418 UTC      Info      w3wp.115      AuthorizationManager.GetUpstreamServerUriHeader      Found config says USS is MU site
2008-10-23 06:37:26.465 UTC      Info      w3wp.14      SusEventDispatcher.TriggerEvent      TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2008-10-23 06:37:26.465 UTC      Info      w3wp.134      ThreadEntry      ThreadHelper.ThreadStart
2008-10-23 06:37:26.465 UTC      Info      w3wp.134      SusEventDispatcher.DispatchManagerWorkerThreadProc      DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2008-10-23 06:37:26.465 UTC      Info      w3wp.134      ChangeNotificationDispatcher.InternalEventHandler      Get event ConfigurationChange from dispatchmanager
2008-10-23 06:37:26.481 UTC      Info      w3wp.5      SusEventDispatcher.TriggerEvent      TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2008-10-23 06:37:26.481 UTC      Info      w3wp.12      Client.OnConfigurationChange      Creating a new ClientImplementation because the DB configuration changed
2008-10-23 06:37:26.481 UTC      Info      w3wp.129      ThreadEntry      ThreadHelper.ThreadStart
2008-10-23 06:37:26.481 UTC      Info      w3wp.129      SusEventDispatcher.DispatchManagerWorkerThreadProc      DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2008-10-23 06:37:26.481 UTC      Info      w3wp.8      SusEventDispatcher.RegisterEventHandler      RegisterEventHandler called for NotificationEventName: ConfigurationChange
2008-10-23 06:37:26.527 UTC      Info      w3wp.12      WebServiceCommunicationHelper.GetProxyConfiguration      Use Proxy: server17:8080
2008-10-23 06:37:26.527 UTC      Info      w3wp.12      WebServiceCommunicationHelper.GetProxyConfiguration      Using Proxy Credentials: dhlconnect : ****
2008-10-23 06:37:26.527 UTC      Info      w3wp.12      AuthorizationManager.GetUpstreamServerUriHeader      Found config says USS is MU site
2008-10-23 06:37:26.527 UTC      Info      w3wp.8      WebServiceCommunicationHelper.GetProxyConfiguration      Use Proxy: server17:8080
2008-10-23 06:37:26.543 UTC      Info      w3wp.8      WebServiceCommunicationHelper.GetProxyConfiguration      Using Proxy Credentials: dhlconnect : ****
2008-10-23 06:37:26.543 UTC      Info      w3wp.8      AuthorizationManager.GetUpstreamServerUriHeader      Found config says USS is MU site
2008-10-23 06:37:26.574 UTC      Info      w3wp.8      SusEventDispatcher.RegisterEventHandler      RegisterEventHandler called for NotificationEventName: ConfigurationChange
2008-10-23 06:37:26.606 UTC      Info      w3wp.8      WebServiceCommunicationHelper.GetProxyConfiguration      Use Proxy: server17:8080
2008-10-23 06:37:26.606 UTC      Info      w3wp.8      WebServiceCommunicationHelper.GetProxyConfiguration      Using Proxy Credentials: dhlconnect : ****
2008-10-23 06:37:26.606 UTC      Info      w3wp.8      AuthorizationManager.GetUpstreamServerUriHeader      Found config says USS is MU site
2008-10-23 06:37:29.559 UTC      Info      WsusService.45      SusService.ValidateServerCertificate      CheckValidationResult Succeeds: CertOK
2008-10-23 06:37:30.746 UTC      Info      WsusService.45      RollupEventReader.SetLastRollupComplete      Finished Rollup.  Setting time anchor in local DB as 23.10.2008 06:37:10
  
Zum Seitenanfang
 
Sunny
Microsoft MVP
*****
Offline



Beiträge: 13250
Mitglied seit: 11.02.07
Geschlecht: männlich
Re: Workaround für Sync-Problem
Antwort #3 - 23.10.08 um 08:56:58
Beitrag drucken  
Brauchst Du den Proxy auch innerhalb des LANs? Sind beide Server bereits WSUS 3.0 SP1?

BTW: Weshalb führst Du nicht den anderen/einfacheren Workaround aus?
BTW2: Du postest im Forum für den WSUS 2.0. Zwinkernd
  
Zum Seitenanfang
 
Manuel1889
WSUS Neuling
Offline


I Love WSUS!

Beiträge: 9
Mitglied seit: 09.10.08
Re: Workaround für Sync-Problem
Antwort #4 - 23.10.08 um 09:05:23
Beitrag drucken  
welchen anderen?
den mit der sprache am SQL-Server ändern?
  
Zum Seitenanfang
 
Sunny
Microsoft MVP
*****
Offline



Beiträge: 13250
Mitglied seit: 11.02.07
Geschlecht: männlich
Re: Workaround für Sync-Problem
Antwort #5 - 23.10.08 um 09:25:53
Beitrag drucken  
Manuel1889 schrieb on 23.10.08 um 09:05:23:
den mit der sprache am SQL-Server ändern?


Genau den, sollte in 1 Minute erledigt sein. Wenn man die Installation vom Management Studio nicht berücksichtigt.
  
Zum Seitenanfang
 
Manuel1889
WSUS Neuling
Offline


I Love WSUS!

Beiträge: 9
Mitglied seit: 09.10.08
Re: Workaround für Sync-Problem
Antwort #6 - 23.10.08 um 09:49:13
Beitrag drucken  
habe ich schon gemacht, funktioniert nicht.
  
Zum Seitenanfang
 
Sunny
Microsoft MVP
*****
Offline



Beiträge: 13250
Mitglied seit: 11.02.07
Geschlecht: männlich
Re: Workaround für Sync-Problem
Antwort #7 - 23.10.08 um 10:07:05
Beitrag drucken  
Manuel1889 schrieb on 23.10.08 um 09:49:13:
habe ich schon gemacht, funktioniert nicht.


OK, mit dieser sehr aussagekräftigen Fehlermeldung ist bei mir erst mal Schluß.
  
Zum Seitenanfang
 
Manuel1889
WSUS Neuling
Offline


I Love WSUS!

Beiträge: 9
Mitglied seit: 09.10.08
Re: Workaround für Sync-Problem
Antwort #8 - 23.10.08 um 12:45:41
Beitrag drucken  
ist dir diese fehlermeldung nicht aussagekräftig genug?

Ich wollte den Workaround für das Sync-Problem durchführen.
Ich habe jetzt einen 2. server aufgesetzt, WSUS mit der Option Repliaktserver installiert, aber dei beiden syncen nicht miteinander.
der alte Server erkennt den neuen unter downstreamserver aber die beiden syncen einfach nicht. Eine verbindung besteht, da wenn ich auch dem neuen die einstellungen ändere sehe ich dieses sofort auf dem alten.
  
Zum Seitenanfang
 
Bookmarks: Facebook Google Google+ Linked in Twitter Yahoo
 



Nutzungsbedingungen | Datenschutz
Kontakt | RSS | Feedback | Impressum
Facebook | News einsenden