Microsoft KB Archive/288434

= Event ID: 5017 Replication Engine StartStop StartError =

Article ID: 288434

Article Last Modified on 6/13/2001

-

APPLIES TO


 * Microsoft Application Center 2000 Standard Edition

-



This article was previously published under Q288434



SUMMARY
Event ID: 5017

Source: Application Center

Description: Synchronization service could not be started

Event Type: Error

The Application Center Synchronization service could not be started on the member. This member will not be synchronized with the cluster controller until the service can be started. If the member is still serving requests, the content might become out of date. Status is %Status%: %StatusMessage%.

Meaning: The synchronization service could not be started.

Effect: If this is a cluster member, synchronization with the cluster controller will not continue until this problem is fixed. The rest of the cluster is not affected by this problem. If this is the cluster controller, no synchronization will happen on the cluster until this problem is fixed.

'Possible Causes and Solutions'

Misconfigured services: One or more of the services that Application Center depends on is misconfigured. Check the configuration by using the Services utility in Administrative Tools. The services should be configured as:

For Each Service: General - Startup type: Automatic. Log On - Log on as: Local system account; Allow service to interact with desktop = Yes

Application Center Synchronization: Recovery - Take no action (all occurrences); Reset fail count after [0] days

Application Center Log Query Helper: General - Startup type: Manual. Recovery - Take no action (all occurrences); Reset fail count after [0] days

Application Center Name Resolution: Recovery - Restart the service (all occurrences); Reset fail count after [49710] days; Restart service after [0] minutes

Application Center Cluster: Recovery - Restart (all occurrences); Reset fail count after [49710] days; Restart service after [0] minutes

IIS Admin: Recovery - Run a file (all occurrences); Log On - Allow service to interact with desktop = No. Recovery - Run a file Reset fail count after [1] days; File %System32%\Iisreset.exe; Append fail count to end of command line=Yes

Remote Procedure Call: Log On - Allow service to interact with desktop = No. Recovery - Take no action (all occurrences); Reset fail count after [0] days

Windows Management Instrumentation: Log On - Allow service to interact with desktop = No. Recovery - Restart the service (all occurrences); Reset fail count after [1] days; Restart service after [1] minutes

Also investigate:
 * Windows Event Log for failures
 * Network failures

Other Solutions (listed in order of preference):  Restart the computer. Contact Microsoft Product Support Services:

http://support.microsoft.com/directory/



Keywords: KB288434

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.