Microsoft
Software
Hardware
Network
Question : "The Directory Service was unable to allocate a relative identifier." when adding machines to AD
"The Directory Service was unable to allocate a relative identifier."
Oh jeepers I think I might have got a tad out of my depth with this one :( Seriously worried, about this one. Let me give you a bit of background history...
- I virtualised a Domain controller.
- Rebuilt the hardware with a fresh copy of Server 2008
- Imported the virtual machine and put it on line, everything was working great.
- I migrated the roles across as per advice below, Think I left both as writable DC's if its relevant I dont know?
http://www.experts-exchang
e.com/Soft
ware/Serve
r_Software
/
File_Serv
ers/Active
_Directory
/Q_2482694
3.html
- Performed a restore of the new DC using Symantec System restore and now...
"The Directory Service was unable to allocate a relative identifier."
I am unable to add at least one machine to the new domain, and I strongly suspect I wont be able to join any for that matter. I am also suddenly unable to join a Linux based NAS to which I suspect is related.
I might need a bit of hand holding with this one I am afraid
Answer : "The Directory Service was unable to allocate a relative identifier." when adding machines to AD
This has been resolved with a system restore. Bit of a sledge hammer to crack a wallnut but still :(
Random Solutions
Validate front end server configuration error
WSUS Update not installing
Comparable Objects
Convert date from mm/dd/yyyy to yyyymmdd
PerformancePoint error - Cannot connect to data source
VS2008: fatal error LNK1112: module machine type 'THUMB' conflicts with target machine type 'ARM'
How do I add a 2008 Domain Controller to a 2003 Server network?
combining sql
Can you store public folders on an external hard drive in exchange server 2003
Windows SharePoint Services 3 Event ID 8214