Petri.com forums Home Forums Start Page Forums Frequently Asked Questions FAQ Member List Members List
Go Back   Petri IT Knowledgebase Forums > Microsoft Networking Services > Active Directory
Petri.com is happy to award RicklesP the title of Most Valuable Member !!!
Register Calendar Calendar Search Petri IT Knowledgebase Forums Search Todays Posts Today's Posts Mark Forums Read
Notices

The directory service was unable to allocate a relative identifier

The directory service was unable to allocate a relative identifier

this thread has 1 replies and has been viewed 1551 times

Closed Thread
 
Thread Tools Search this Thread Display Modes
  #1  
Old 12th April 2012, 21:13
thestriver thestriver is offline
Casual
Casual
 
 Join Date: Apr 2012
  6 month star 12 month star
 Posts: 1
 Reputation: thestriver is on a distinguished road (10)
Default The directory service was unable to allocate a relative identifier

We are in the process of creating our AD DR env of our PROD env on a separate subnet as we don't want the DR env to talk to the PROD env.

PROD Env: Forest functional level is W2k3 and all DC's are w2k3 and are all Vmware VM's.

We have created a DR env on another subnet with similar umber of VM's for similar number of Dc's in the prod env.

Next, we restored the ntbackup of the DC in the prod env that had all the roles, except GC, on one of the VM's in the DR env.

Went into DSRM and restored the backup non-authoritatively.

Then, before rebooting, set the burflags to D4 to make it the AD DB authoritative.

Note: We have an internal policy here that specifically asks us to first do non-authoritative restore then use either ntdsutil or via burflags to set to Authoritative.

Rebooted this VM into normal mode. Then, went into ncpa.cpl to set the DR env IP address'. DNS was set to look at itself as this was the first DC in the domain.

Then, started DNS server and started Netlogon from paused state.

Created a new subnet for the site as the DR network is different compared to prod. Now, This first DC is functioning as expected.

Now, when I try to add a ADC...it gives the following error towards the end of the dcpromo process:

"The directory service was unable to allocate a relative identifier"

I tried to first add the VM to the domain...but same error.

I have gone through the following MS articles to no use as this is a DR site with no connection to the Prod network.

KB's: 839879 822053

Would appreciate expert comments on how to proceed...

Thanks in advance.
  #2  
Old 13th April 2012, 19:54
Ossian Ossian is online now
Administrator
 
 Join Date: Nov 2003
  6 month star 12 month star
 Location: Bonnie Scotland
 Posts: 16,888
  Send a message via Skype™ to Ossian
 Reputation: Ossian has a brilliant futureOssian has a brilliant futureOssian has a brilliant futureOssian has a brilliant futureOssian has a brilliant futureOssian has a brilliant futureOssian has a brilliant futureOssian has a brilliant futureOssian has a brilliant futureOssian has a brilliant futureOssian has a brilliant future (1596)
Default Re: The directory service was unable to allocate a relative identifier

Can you confirm you have checked the DR DC has all the FSMOs?
__________________
Tom Jones
MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
PhD, MSc, FIAP, MIITT
IT Trainer / Consultant
Ossian Ltd
Scotland

** Remember to give credit where credit is due and leave reputation points where appropriate **
Closed Thread


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
The directory service was unable to allocate a relative identifier vbjr Windows Server 2000 / 2003 / 2003 R2 4 8th April 2011 01:42
Unable to connect to Win 2003 service manager from win 2008 service manager charlsteve Windows Server 2008 / 2008 R2 0 7th April 2010 08:36
Can't assign a relative ID maxtor-be Active Directory 2 17th October 2009 17:11
Homedirectory\Profilepath relative to site aviwollman Active Directory 2 26th December 2007 17:10
The server was unable to allocate from the system nonpaged pool tulik23 Windows Server 2000 / 2003 / 2003 R2 1 1st October 2007 01:09


All times are GMT +3. The time now is 09:56.

Steel Blue 3.5.4 vBulletin Style ©2006 vBEnhanced
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
 

Valid XHTML 1.0!   Valid CSS!

Copyright 2005 Daniel Petri