Discussion Locked

NETLOGON EVENTS TOO MANY IN EVENT VIEWER

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a PDC/BDC environment. I am using OPEN FILE MANAGER, POWERSYNC4.5s and
SEAGATE for Replications and backups. Servers are being used as data stores. I am
not running any CLIENT/SERVER apps. I have an ACCESS Database (backend) that is
open 24x7 for read and writes. Application is on the desktop.

I replicate logical drives (except C: boot) from PDC to BDC several times a day
so if the PDC goes to lunch, if necessary I can promote the BDC and am back in
business fairly quickly.
The problem I appear to be having is that I get too many NETLOGON events in the
EVENT VIEWER. Indications are that the NETLOGON.CHG file on the PDC may be
corrupt. According to error code I.D. 5705 I should stop the NETLOGON service,
delete the NETLOGON.CHG file and restart the service.

However I cannot delete the NETLOGON.CHG file. When I try to delete it, I get a
message that the file is in use.

Any recommendations?

.

4 replies

by longmwa

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

NOTE: Make sure that the permissions on the %SystemRoot% folder include
"System Full Control" or the Netlogon.chg file will not be re-created, and
partial synchronization errors will continue.

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.

by mwdavid

Should have thought of this myself. However, this is not the resolution to the problem. The problem was related to too many AUDIT requests. When I reduced the number of AUDITS and cleared the EVENT VIEWER the problem went away.

This discussion is closed to new replies.