Discussion Locked

BDC event error 5731

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

My BDC has the event5731 in event viewer. I have tried the fix from Q172302 with no luck. The event log fills up with these message every five minutes:
replication of SAM local group "RID: 0xa91" failed group does not exist

replication of SAM local group "local" failed
user already exists

Does anyone have any insight that might help me?
thanks for your time

6 replies

by ann777

Since you have already tried Q172302, I'd suggest that you try Q245123.

RID: 0x220 is the Administrator built-in account and should be identical on the PDC and the BDC.

CAUSE
This behavior can occur if the Administrator account Security IDs (SIDs) are not identical on all domain controllers.

RESOLUTION
To resolve this issue, perform a parallel installation of Windows NT Server 4.0 on the BDC, and then synchronize all the domain controllers. To do this, follow these steps:

NOTE: You can use the Getsid utility included with the Windows NT 4.0 Resource Kit to compare the SIDs for the Administrator accounts on the domain controllers.

At the relevant BDC, perform a parallel installation of Windows NT Server 4.0:

Install Windows NT Server 4.0. When you are prompted, select the new installation option. Type the drive and folder where you want to install the parallel installation, placing it in a folder other than the one that contains the original installation.

At the end of the setup process, restart the computer to the parallel installation.

Synchronize the domain controllers:

At the BDC, start Server Manager.

Click the name of the server you want to synchronize with the PDC.

On the Computer menu, click Synchronize With Primary Domain Controller.

Click OK to confirm the synchronization.

At the relevant BDC, delete the original installation of Windows\ NT Server 4.0.

At the relevant BDC, save the configuration:

Start Disk Administrator.

Insert a formatted floppy disk into drive A, and then click OK.

Saving the disk configuration to the floppy disk may take several minutes.

Click OK in the Disk Administrator dialog box.

by ann777

Also the below is from Q161569:

CAUSE
A built-in account may have been modified. For example, the administrator for the domain may have been removed from the Administrators group on the domain controller. Other changes to group memberships that can cause these errors are:

Making the Administrator's account a non-Administrator account.

Disabling the Administrator's account by clicking to select the "disable account" check box.

Setting the Administrator's account to expire.

Removing the Domain Admins global group from the Administrators local group.

Removing Administrator from the Domain Admins global group.

RESOLUTION
To resolve these problems, reverse any such modifications to built-in accounts and built-in groups.

This discussion is closed to new replies.