Re: 0% available RIDs in the current pool
- From: "Frederic Hurlet" <fhurlet@xxxxxxxxx>
- Date: Tue, 27 Nov 2007 09:54:45 -0500
Hi group,
Just ran a dcdiag again for fun and everything is looking good.
Starting test: RidManager
* Available RID Pool for the Domain is 2609 to 1073741823
* PDC.domainname.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 2109 to 2608
* rIDPreviousAllocationPool is 2109 to 2608
* rIDNextRID: 2111
......................... PDC passed test RidManager
Seems like leave alone is the answer...
"Frederic Hurlet" <fhurlet@xxxxxxxxx> wrote in message
news:Oj1Ga5PMIHA.4272@xxxxxxxxxxxxxxxxxxxxxxx
Hello group and experts,
Single domain with 1 DC, before had a 2nd on a virtual machine.
I let the 2nd DC offline too long. After a year being offline, started
having issues with our network. (Around 2007-09-19)
Here is part of dcdiag before I did some fixing:
REPLICATION-RECEIVED LATENCY WARNING
PDC: Current time is 2007-11-26 21:06:51.
CN=Schema,CN=Configuration,DC=OURDOMAIN,DC=local
Last replication recieved from BDC at 2006-09-17 08:46:58.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
CN=Configuration,DC=OURDOMAIN,DC=local
Last replication recieved from BDC at 2006-09-17 08:46:58.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
DC=OURDOMAIN,DC=local
Last replication recieved from BDC at 2006-09-17 08:48:20.
WARNING: This latency is over the Tombstone Lifetime of 60
days!
Fatal Error:DsGetDcName (PDC) call failed, error 1355
The Locator could not find the server.
......................... PDC failed test Advertising
......................... PDC failed test Services
......................... PDC failed test frsevent
......................... PDC failed test systemlog
......................... OURDOMAIN.local failed test FsmoCheck
What I did to fix was shutdown permanently (to be re-formattted) the
offline for a year BDC
Went through MS KB 216498 (How to remove data in Active Directory after an
unsuccessful domain controller demotion) and then followed on with MS KB
839879 (Event ID 16650: The account-identifier allocator failed to
initialize in Windows 2000 and in Windows Server 2003) and a reboot of the
only DC in single domain forest, PDC.
No errors related to Directory services in event log after bootup of PDC.
After 24 hours, all seems well, can even create new AD objects, etc.
Now, what I would like to know is should I worry about, "Warning :There is
less than 0% available RIDs in the current pool" when running dcdiag?
I still get a pass for RidManager test.
BEFORE ABOVE FIXES:
Starting test: RidManager
* Available RID Pool for the Domain is 2109 to 1073741823
* PDC.domainname.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1109 to 1608
* rIDPreviousAllocationPool is 1109 to 1608
* rIDNextRID: 1608
* Warning :Next rid pool not allocated
* Warning :There is less than 0% available RIDs in the current
pool
......................... PDC passed test RidManager
AFTER:
Starting test: RidManager
* Available RID Pool for the Domain is 2609 to 1073741823
* PDC.domainname.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 2109 to 2608
* rIDPreviousAllocationPool is 1109 to 1608
* rIDNextRID: 1608
* Warning :There is less than 0% available RIDs in the current
pool
......................... PDC passed test RidManager
Interesting that the PreviousAllocationPool is not a block just before the
current/new AllocationPool...
Interesting that rIDNextRID is the last RID from PreviousAllocationPool...
Leave alone?
Thank you
Frederic Hurlet
MCSE on W2k
CCNA
.
- References:
- 0% available RIDs in the current pool
- From: Frederic Hurlet
- 0% available RIDs in the current pool
- Prev by Date: Re: 2003 DC in 2000 Domain
- Next by Date: RE: ADMT v3 Group Migration Error
- Previous by thread: 0% available RIDs in the current pool
- Next by thread: Re: Group Policy replication
- Index(es):
Relevant Pages
|
