binary_1001010
asked on
metadata cleanup or delete replication link?
Hi guys,
Yesterady one of our server was down and we have to rebuilt the OS and restore everything from the backup. After backup was completed, i did a reboot. When the server was up and checked the eventlog, i noticed an error :
Event Type: Error
Event Source: SAM Event
Category: None
Event ID: 16650
The account-identifier allocator failed to initialize properly. The record data contains the NT error code that caused the failure. Windows 2000 will retry the initialization until it succeeds; until that time, account creation will be denied on this Domain Controller. Please look for other SAM event logs that may indicate the exact reason for the failure.
After going though the microsoft KB, it said :
RESOLUTION
Delete the replication links for the naming contexts in Windows 2000
In Windows 2000, you can restore a second domain controller to complete initial synchronization. If you cannot restore a second domain controller, you must either perform a metadata cleanup on the non-existent domain controllers or delete the replication links to the Active Directory naming contexts. If you plan to restore the other domain controllers later, you must delete the replication links instead of performing a metadata cleanup.
Before you can delete the replication links to the Active Directory naming contexts, you must identify the objectGUID value by using the Repadmin command. To do this, follow these steps:
1. Click Start, click Run, type cmd in the Open box, and then click OK.
2. At the command prompt, type repadmin /showreps. You will see output that resembles the following:
CN=Schema,CN=Configuration ,DC=contos o,DC=comDe fault-Firs t-Site-Nam e\DC02 via RPC objectGuid: 97c68f88-3864-4a12-9962-ca 389937e237 Last attempt @ 2004-02-26 09:10.03 was successful.
CN=Configuration,DC=contos o,DC=com Default-First-Site-Name\DC 02 via RPC objectGuid: 97c68f88-3864-4a12-9962-ca 389937e237 Last attempt @ 2004-02-26 09:14.43 was successful.
DC=contoso,DC=com Default-First-Site-Name\DC 02 via RPC objectGuid: 97c68f88-3864-4a12-9962-ca 389937e237 Last attempt @ 2004-02-26 09:14.01 was successful.
3. Type repadmin /delete to delete the replication links. Specify the naming context and the objectGUID as shown in the following examples:
repadmin /delete CN=Schema,CN=Configuration ,DC=contos o,DC=com DC01 97c68f88-3864-4a12-9962-ca 389937e237 ._msdcs.co ntoso.com /localonly
repadmin /delete CN=Configuration,DC=contos o,DC=com DC01 97c68f88-3864-4a12-9962-ca 389937e237 ._msdcs.co ntoso.com /localonly
repadmin /delete DC=contoso,DC=com DC01 97c68f88-3864-4a12-9962-ca 389937e237 ._msdcs.co ntoso.com /localonly
4. Restart the RID Master computer. The RID Master will initialize correctly.
(taken from http://support.microsoft.com/kb/839879 )
On the paragraph, it mentioned "If you cannot restore a second domain controller, you must either perform a metadata cleanup on the non-existent domain controllers or delete the replication links to the Active Directory naming contexts. "
So, my question is :
how do i know I have to do delete the replication link only or metacleanup only? or both?
Yesterady one of our server was down and we have to rebuilt the OS and restore everything from the backup. After backup was completed, i did a reboot. When the server was up and checked the eventlog, i noticed an error :
Event Type: Error
Event Source: SAM Event
Category: None
Event ID: 16650
The account-identifier allocator failed to initialize properly. The record data contains the NT error code that caused the failure. Windows 2000 will retry the initialization until it succeeds; until that time, account creation will be denied on this Domain Controller. Please look for other SAM event logs that may indicate the exact reason for the failure.
After going though the microsoft KB, it said :
RESOLUTION
Delete the replication links for the naming contexts in Windows 2000
In Windows 2000, you can restore a second domain controller to complete initial synchronization. If you cannot restore a second domain controller, you must either perform a metadata cleanup on the non-existent domain controllers or delete the replication links to the Active Directory naming contexts. If you plan to restore the other domain controllers later, you must delete the replication links instead of performing a metadata cleanup.
Before you can delete the replication links to the Active Directory naming contexts, you must identify the objectGUID value by using the Repadmin command. To do this, follow these steps:
1. Click Start, click Run, type cmd in the Open box, and then click OK.
2. At the command prompt, type repadmin /showreps. You will see output that resembles the following:
CN=Schema,CN=Configuration
CN=Configuration,DC=contos
DC=contoso,DC=com Default-First-Site-Name\DC
3. Type repadmin /delete to delete the replication links. Specify the naming context and the objectGUID as shown in the following examples:
repadmin /delete CN=Schema,CN=Configuration
repadmin /delete CN=Configuration,DC=contos
repadmin /delete DC=contoso,DC=com DC01 97c68f88-3864-4a12-9962-ca
4. Restart the RID Master computer. The RID Master will initialize correctly.
(taken from http://support.microsoft.com/kb/839879 )
On the paragraph, it mentioned "If you cannot restore a second domain controller, you must either perform a metadata cleanup on the non-existent domain controllers or delete the replication links to the Active Directory naming contexts. "
So, my question is :
how do i know I have to do delete the replication link only or metacleanup only? or both?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can use Active Directory Sites and Services or Replication Monitor from Support Tools. Comannd is called "Check replication topology" Or you can use command line:
"repadmin /kcc <dcservername>"
"repadmin /kcc <dcservername>"
ASKER
just to confirm, where should we delete the replication ? the DC that we just restored or the DC without any problem?
On the DC that you've restored, but it really does not matter if you delete connection objects for this particular DC on other DCs, because KCC will generate new connection objects automatically.
ASKER