Discussion Locked

dcdiag failing ridmanager test

0 helpful
0 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Greetings.

I'm working on a fairly small network that's in process of migrating to AD. The DC that has all the fsmo roles is failing part of the ridmanager test with the following error:

Starting test: RidManager
* Available RID Pool for the Domain is 2751 to 1073741823
* XXX is the RID Master
* DsBind with RID Master was successful
ldap_search_sW subtree of DC=XXX,DC=net for sam account failed with 234: More data is available.
No rids allocated -- please check eventlog.
......................... XXX failed test RidManager
Starting test: MachineAccount
ldap_search_sW failed with 234: More data is available.
ldap_search_sW subtree of DC=XXX,DC=net for sam account failed with 234: More data is available.
ldap_search_sW subtree of DC=XXX,DC=net for sam account failed with 234: More data is available.
......................... XXX failed test MachineAccount

NetDiag finds no errors, and I've run "Semantic database analysis" with the "Go Fixup" option from ntdsutil.

0 replies

No replies were posted before this discussion closed.

This discussion is closed to new replies.