| Event Id | 16647 |
| Source | SAM |
| Description | The domain controller is starting a request for a new account-identifier pool. |
| Event Information | According to Microsoft: CAUSE: 1. When the relative ID (RID) Master is restored from backup, it tries to synchronize with other domain controllers to verify that there are no other RID Masters online. However, the synchronization process fails if there are no domain controllers available to synchronize with, or if replication is not working. 2. The RID pool has been exhausted, or objects in Active Directory that are related to RID allocation use incorrect values or are missing. RESOLUTION: To bypass the initial synchronization requirements when the affected domain contains Windows Server 2003 domain controllers, transfer the RID operations role to a Windows Server 2003 domain controller and then seize the RID operations master role to the current role owner. Seizing the FSMO role back to itself on a Windows Server 2003 domain controller bypasses the initial synchronization requirements that are required to enable the RID operations master until the role holder is restarted. 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, delete the replication links instead of performing a metadata cleanup. 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 is similar to the following: CN=Schema,CN=Configuration,DC=contoso,DC=comDefault-First-Site-Name\DC02 via RPC objectGuid: 97c68f88-3864-4a12-9962-ca389937e237 Last attempt @ 2004-02-26 09:10.03 was successful. CN=Configuration,DC=contoso,DC=com Default-First-Site-Name\DC02 via RPC objectGuid: 97c68f88-3864-4a12-9962-ca389937e237 Last attempt @ 2004-02-26 09:14.43 was successful. DC |
| Reference Links | The account-identifier allocator failed to initialize in Windows 2000 and in Windows Server 2003 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.