The directory service was unable to allocate a relative identifier
Posted on 2012-09-21
I created a 'sandbox' for someone to do some server upgrade testing a couple weeks ago. This is something I do a couple of times a year and the first time it gave me this error. Basically, I take a clone of a DOMAIN CONTROLLER and a set of MEMBER SERVERS and place them in a sandbox network that cant see anything else. When I did this three weeks ago, I was able to attach the MEMBER SERVERS to the DC with no issue. Now I needed to add a NEW MEMBER SERVER to the sandbox, but am unable to attach him to the domain. When I try to create a new COMPUTER in AD manually, I get the error above.
I realize that you cant 'restore' a DC into a network directly, but since this was merely a snapshot of a DC that was brought up in a SANBOX, why am I getting different results than before? I trashed the sanbox DC and re-cloned the production DC back into the sanbox but still have the same issue.
This error returns google results poiting to RID master FSMO roles. My SANBOX DC holds all roles, but his replication parter is not available in the SANDBOX. I dont understand why the sandbox would need a replation parter -- I would assume that if DC#2/replication partner dies in production, DC#1 would continue to function, so why cant a clone function by itself in the sandbox?