No trabalho, atualmente temos um controlador de domínio, POLLY. Este DC é o mestre do RID. No entanto, costumava haver dois outros CDs, PAULA e PETTY. Estes são ambos offline (e muito longe), mas eles aparecem na configuração POLLYs. Estranhamente, o POLLY tem o mesmo IP que o PETTY.
Quando tento adicionar um novo usuário a Usuários e computadores do Active Directory , recebo a seguinte mensagem de erro:
Windows cannot create the object because the Directory Service was unable to allocate a relative identifier.
Isso é estranho, já que o POLLY (nosso único DC) é o mestre do RID.
Aqui está a saída de dcdiag :
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.Doing initial required tests
Testing server: Standardname-des-ersten-Standorts\POLLY
Starting test: Connectivity
......................... POLLY passed test ConnectivityDoing primary tests
Testing server: Standardname-des-ersten-Standorts\POLLY
Starting test: Replications
REPLICATION-RECEIVED LATENCY WARNING
POLLY: Current time is 2012-01-11 09:18:28.
DC=ForestDnsZones,DC=europa-institut,DC=com
Last replication recieved from PETTY at 2004-08-12 17:48:21.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
DC=DomainDnsZones,DC=europa-institut,DC=com
Last replication recieved from PETTY at 2004-08-13 10:50:52.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
CN=Schema,CN=Configuration,DC=europa-institut,DC=com
Last replication recieved from PETTY at 2004-08-12 17:48:20.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from PAULA at 2004-08-25 01:05:28.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
CN=Configuration,DC=europa-institut,DC=com
Last replication recieved from PETTY at 2004-08-13 10:54:37.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from PAULA at 2004-08-25 01:05:19.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
DC=europa-institut,DC=com
Last replication recieved from PETTY at 2004-08-13 11:04:57.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from PAULA at 2004-08-25 01:09:36.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
......................... POLLY passed test Replications
Starting test: NCSecDesc
......................... POLLY passed test NCSecDesc
Starting test: NetLogons
......................... POLLY passed test NetLogons
Starting test: Advertising
......................... POLLY passed test Advertising
Starting test: KnowsOfRoleHolders
......................... POLLY passed test KnowsOfRoleHolders
Starting test: RidManager
......................... POLLY passed test RidManager
Starting test: MachineAccount
......................... POLLY passed test MachineAccount
Starting test: Services
......................... POLLY passed test Services
Starting test: ObjectsReplicated
......................... POLLY passed test ObjectsReplicated
Starting test: frssysvol
......................... POLLY passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after theSYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems.
......................... POLLY failed test frsevent
Starting test: kccevent
......................... POLLY passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x40000004
Time Generated: 01/11/2012 08:47:35
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 01/11/2012 09:05:49
(Event String could not be retrieved)
......................... POLLY failed test systemlog
Starting test: VerifyReferences
......................... POLLY passed test VerifyReferencesRunning partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDomRunning partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDomRunning partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDomRunning partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDomRunning partition tests on : europa-institut
Starting test: CrossRefValidation
......................... europa-institut passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... europa-institut passed test CheckSDRefDomRunning enterprise tests on : europa-institut.com
Starting test: Intersite
......................... europa-institut.com passed test Intersite
Starting test: FsmoCheck
......................... europa-institut.com passed test FsmoCheck
E aqui está a saída de repadmin /showrepl :
repadmin running command /showrepl against server localhost
Standardname-des-ersten-Standorts\POLLY
DC Options: IS_GC
Site Options: (none)
DC object GUID: 3c57a0b6-7047-4b42-a3d1-e5eed7513cbe
DC invocationID: 5194142b-3179-4cff-b17e-77af398b8007
O que preciso fazer para adicionar novos usuários?
Primeiro, faça um backup de dados do estado do sistema no seu DC, apenas no caso. Em seguida, execute a limpeza de metadados para remover todos os vestígios de DCs que desapareceram. Aqui está um bom tutorial: link Depois disso, execute dcdiag novamente e nos informe se o problema persistir.