Microsoft KB Archive/839879

= Event ID 16650: The account-identifier allocator failed to initialize in Windows 2000 and in Windows Server 2003 =

Article ID: 839879

Article Last Modified on 10/30/2006

-

APPLIES TO


 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows 2000 Datacenter Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Server
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

-





Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
When you try to add new users, groups, computers, mailboxes, domain controllers, or other objects to Active Directory on a Microsoft Windows Server 2003-based computer or a Windows 2000-based computer, you may receive the following error message:

Cannot create the object because directory service was unable to allocate a relative identifier.

When you restore a domain controller from a system state backup, the System log may contain the following error message:

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. 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.

You can also use the Dcdiag command together with the verbose switch to look for additional errors. 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 DCdiag /v, and then press Enter.

When you type Dcdiag /v, you may see error messages that resemble the following:

Starting test: RidManager


 * Available RID Pool for the Domain is 2355 to 1073741823


 * is the RID Master


 * DsBind with RID Master was successful


 * rIDAllocationPool is 1355 to 1854


 * rIDNextRID: 0 The DS has corrupt data: rIDPreviousAllocationPool value is not valid


 * rIDPreviousAllocationPool is 0 to 0 No rids allocated -- please check eventlog.

......................... DC01 failed test RidManager

Warning: rid set reference is deleted.

ldap_search_sW of CN=RID SetDEL:cfe0828c-8842-4cb1-a642-6d9991d0516d,CN=Deleted Objects,DC= ,DC= for rid info failed with 2: The system cannot find the file specified.

......................... DC01 failed test RidManager

Starting test: RidManager


 * Available RID Pool for the Domain is 3104 to 1073741823

Warning: FSMO Role Owner is deleted.


 * is the RID Master


 * DsBind with RID Master was successful

Warning: rid set reference is deleted.

ldap_search_sW of CN=RID SetDEL:5a128cf2-f365-47bc-a883-8ff9561ff545,CN=Deleted Objects,DC=contoso,DC=com for rid info failed with 2: The system cannot find the file specified.

......................... DC01 failed test RidManager

Starting test: KnowsOfRoleHolders

Role Rid Owner = CN=&quot;NTDS Settings DEL:fd615439-1ebb-4652-b16f-3f8517d25593&quot;,CN=dc01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=contoso,DC=com Warning: CN=&quot;NTDS Settings DEL:fd615439-1ebb-4652-b16f-3f8517d25593&quot;,CN=dc01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=contoso,DC=com is the Rid Owner, but is deleted.

You may also receive other errors in the system event log that can help you to troubleshoot the problem:

Event ID: 16647

Event Source: SAM

Description: The domain controller is starting a request for a new account-identifier pool.

Event Type: Error

Event Source: SAM Event

Category: None

Event ID: 16645

Description: The maximum account identifier allocated to this domain controller has been assigned. The domain controller has failed to obtain a new identifier pool. A possible reason for this is that the domain controller has been unable to contact the master domain controller. Account creation on this controller will fail until a new pool has been allocated. There may be network or connectivity problems in the domain, or the master domain controller may be offline or missing from the domain. Verify that the master domain controller is running and connected to the domain.



CAUSE
This problem occurs in one of the following scenarios:  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. The synchronization requirement was implemented in the Windows 2000 hotfix that is described in the following Microsoft Knowledge Base article:

307725 Backup and restore of RID Flexible Single-Master Operations domain controller causes duplicate SIDs

Note If the domain has always contained only one domain controller, the RID Master will not try to synchronize with other domain controllers. The domain controller has no knowledge of any other domain controllers. The RID pool has been exhausted, or objects in Active Directory that are related to RID allocation use incorrect values or are missing.



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:  Click Start, click Run, type cmd in the Open box, and then click OK. At the command prompt, type repadmin /showreps. You will see output that resembles 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=contoso,DC=com Default-First-Site-Name\DC02 via RPC objectGuid: 97c68f88-3864-4a12-9962-ca389937e237 Last attempt @ 2004-02-26 09:14.01 was successful.

  Type repadmin /delete to delete the replication links. Specify the naming context and the objectGUID as shown in the following examples: <pre class="fixed_text">repadmin /delete CN=Schema,CN=Configuration,DC=contoso,DC=com DC01 97c68f88-3864-4a12-9962-ca389937e237._msdcs.contoso.com /localonly repadmin /delete CN=Configuration,DC=contoso,DC=com DC01 97c68f88-3864-4a12-9962-ca389937e237._msdcs.contoso.com /localonly repadmin /delete DC=contoso,DC=com DC01 97c68f88-3864-4a12-9962-ca389937e237._msdcs.contoso.com /localonly </li> Restart the RID Master computer. The RID Master will initialize correctly.</li></ol>

Remove domain controller metadata for all other domain controllers in the domain
You can restore or connect a second domain controller to complete initial synchronization. If you cannot add a second domain controller, you must either perform a metadata cleanup on the non-existent domain controllers to remove them from the domain permanently or delete the replication links to the Active Directory naming contexts.

For more information about how to remove metadata, click the following article number to view the article in the Microsoft Knowledge Base:

216498 How to remove data in Active Directory after an unsuccessful domain controller demotion

Verify that Active Directory objects that are related to RID allocation are valid
To verify that the Active Directory objects that are related to RID allocation are valid, follow these steps: <ol> Verify that the Everyone group has the Access this computer from the network user right. The setting can be configured in the following location in the Group Policy Object Editor: Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment.</li> Install the Windows 2000 Support Tools. These tools are available in the support folder on the Windows 2000 and the Windows Server 2003 CD-ROMs. When you have installed these tools, start ADSI Edit. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> Click Start, click Run, type mmc in the Open box, and then click OK.</li> In Windows 2000, click Console, and then click Add/Remove Snap-in. In Windows Server 2003, click File, and then click Add/Remove Snap-in.</li> In the Add/Remove snap-in, click Add, click ADSIEdit, and then click Add.</li> Click Close, and then click OK.</li></ol> </li> In MMC, right-click ADSIEdit, and then click Connect to.</li> In Connections Settings, under Connection Point, click Select a well known naming context. In the drop-down list, click domain, and then click OK.</li> Expand domain, and then expand the distinguished name of the domain. For example, expand DC=, DC= .</li> Expand OU=Domain Controllers.</li> Right-click the domain controller that you want to check, and then click Properties.</li> Click the Select a property to view menu, and then click userAccountControl.</li> Verify that the value for userAccountControl is 532480. To change the userAccountControl value, click Edit on the domain controller property dialog box.</li> In the Integer Attribute Editor, type 532480 in the Value field, and then click OK.</li></ol>

Verify that the RID Master is replicating with another domain controller
If a newly promoted domain controller generates Event 16650, the domain controller may have obtained replication information from another domain controller that is not the RID Master. During promotion, the computer account for the new domain controller is modified. If these changes have not replicated to the domain controller that holds the RID master role, the request will fail when the newly promoted domain controller tries to obtain a RID pool.

To verify that the RID Master is replicating with at least one of its direct partners, follow these steps: <ol> <li>Verify that the CN=RID Set object exists.

The CN=RID Set object is in the right pane of ADSI Edit when the domain controller is selected under OU=Domain Controllers in the left pane.

If no CN=RID Set object exists, you must demote that domain controller and then promote it again to create the object.</li> <li>If the CN=RID Set object exists, make sure that the rIDSetReferences attribute on the domain controller's computer account object points to the distinguished name of the RID Set object, as shown in the following example:

CN=RID Set, CN=DC01,OU=Domain Controllers,CN=contoso,DC=local

If the rIDSetReferences attribute does not point to the distinguished name of the RID Set object, contact Microsoft Product Support Services for more information.</li></ol>

<div class="status_section">

STATUS
This behavior is by design.

<div class="references_section">