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
Convert UCHAR[] to System::string
AccesVB: Button that closes report
Making custom PowerPoint template the default for all users
Problems when running VB.NET app as a scheduled task
Need clarification on SMS to SCCM side by side upgrade
Excel interop
URGENT - 2003 Server - this system does not permit you to logon interactivally
SBS 2008: Cannot enable shadow clopies
Windows XP - Strange Connection Issues (ping but can't browse)
Excel vba: post 30 based on prev EE post - Using VBA to place a Y axis title