Netlogon Synchronization Errors

Last reviewed: March 5, 1998
Article ID: Q173882
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.51 and 4.0
  • Microsoft Windows NT Server versions 3.51 and 4.0

SUMMARY

Netlogon creates many errors that are recorded in the event log, which eventually fills or wraps the log.

MORE INFORMATION

The Netlogon.chg file is located on all domain controllers, but is used only by the primary domain controlloer (PDC) to keep track of changes made to the security databases. All changes to the security databases are recorded in this log file, along with the serial number of the change. Each of the three security databases maintains a separate serial number, which is incremented once for each change. When a backup domain controller (BDC) requests a particular change from the PDC, the PDC checks the change log to determine which changes need to be sent.

Specific Events and Errors

The following events may be recorded on the BDC:

   Event ID: 5717
   Source: NETLOGON
   Type: Information
   The full synchronization replication of the LSA database from the
   primary domain controller \\<DOMAIN CONTROLLER> completed successfully.

   Event ID: 5716
   Source: NETLOGON
   Type: Warning
   The partial synchronization replication of the SAM database from the
   primary domain controller <DOMAIN CONTROLLER> failed with the following
   error:

      <THERE IS NO ERROR REPORTED>

   The Data section contains c0000134 (Words) or 34 01 00 c0 (Bytes.); the
   c0000134 indicates STATUS_SYNCHRONIZATION_REQUIRED.

The following events may be reported on the PDC:

   Event ID: 5713
   Source: NETLOGON
   Type: Information
   The full synchronization request from the server <SERVERNAME> completed
   successfully. <X> object(s) has(have) been returned to the caller.

   Event ID: 5712
   Source: NETLOGON
   Type: Warning
   The partial synchronization request from the server <SERVERNAME> failed
   with the following error:

      <THERE IS NO ERROR REPORTED>

Trying to promote a BDC to a PDC may cause the following pop-up window message to stay on the screen indefinitely:

   "Synchronizing <BDC> with its primary"

The following event log error may be generated:

   Event ID: 5705
   Source: NETLOGON
   Type: Error
   The change log cache maintained by the Netlogon Service for database
   changes is corrupted. The Netlogon service is resetting the change log.

These events can be caused when Windows NT fails to update the %SystemRoot%\Netlogon.chg file on the PDC. This may occur for any of the following reasons:
  • The Read-Only attribute could be set.
  • The netlogon.chg file could be corrupted.
  • The permissions for the system account could be insufficient for that file; they should be at least RWXD.

Resolving the Problem

If the Netlogon.chg file has been corrupted, it may be necessary to delete or rename the file. However, this file is always in use by the system.

To delete (reset) Netlogon.chg on an NTFS partition, use the following steps:

  1. Set the permissions so that the %SystemRoot%\Netlogon.chg file has No Access for the System account.

  2. Restart the system and delete the file when it comes up

  3. Restart again. The file will be recreated at startup.

To delete (reset) Netlogon.chg on a FAT partition, use the following steps:

  1. Start the system using MS-DOS, and then delete the %SystemRoot%\Netlogon.chg file.

  2. Restart using Windows NT. The file will be recreated at startup.


Additional query words: continuous repeated alternate
server user manager forever 340100c0 warning informational blue yellow 4 A
Keywords : ntdomain ntfilesys NTSrvWkst kbnetwork
Version : WinNT:3.51,4.0
Platform : winnt
Hardware : x86
Issue type : kbinfo


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 5, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.