Computing.Net > Forums > Windows NT > Partial Sync Requests

Partial Sync Requests

Reply to Message Icon

Original Message
Name: Paul
Date: May 31, 2002 at 03:55:01 Pacific
Subject: Partial Sync Requests
Comment:

I have noticed within our PDC's Event Log that every 5 mins, a number of events are being logged. These events are not errors but 'Information Events - 5711'. I think that there maybe a problem in that it seems that these partial syncs. could be in some sort of loop?

Does this scenario sound familiar to anyone or does anyone know of any utilities for checking that database(s)?

These events also seem to coninue over night!


Report Offensive Message For Removal


Response Number 1
Name: XP DOC
Date: May 31, 2002 at 03:59:39 Pacific
Subject: Partial Sync Requests
Reply: (edit)

Event ID: 5711
Source NETLOGON
Type Information
Description The partial synchronization request from the server CORPEX01 completed successfully. 1 changes(s) has(have) been returned to the caller.
Comments Indicates a successful synchronization between domain controllers.


Report Offensive Follow Up For Removal

Response Number 2
Name: Mike
Date: July 1, 2002 at 09:14:50 Pacific
Subject: Partial Sync Requests
Reply: (edit)

I am getting the same event mesages.
My server is also locking down every night and needs to be rebooted. ??????


Report Offensive Follow Up For Removal

Response Number 3
Name: Mike
Date: July 1, 2002 at 09:29:53 Pacific
Subject: Partial Sync Requests
Reply: (edit)

Found an article guys.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q191828

CAUSE
A component of Systems Management Server called Climonnt.exe is trying to log on to the SMS shares on your network using an incorrect or expired password.

Normally, the CLIMONNT process will wake up one time every 24 hours and try to connect to the SMS shares on the network using the credentials of the currently logged-on user. The problem occurs when a user's password has been changed or has expired, but the user has not logged off. The problem can also occur if a user's password is changed on one computer but the user is logged on with the old password on at least one other computer.

In either scenario, the CLIMONNT process will awaken and try to connect to an SMS share using an old password. Since the password is incorrect, Windows NT will deny the connection. CLIMONNT then attempts to connect to other SMS shares that may be configured. It fails again. When all SMS shares have been tried unsuccessfully, CLIMONNT will pause for 60 seconds, and then start the entire process again, using the first SMS share. If an account lockout policy is in effect on the domain, the user's account will be locked out.

This problem can also cause the LSASS process on the Windows NT primary domain controller to spike.

For additional information, please see the following article in the Microsoft Knowledge Base:


Report Offensive Follow Up For Removal







Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Partial Sync Requests

Comments:

 


  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 
Data Recovery Software