Unable to allocate a relative identifier


i have mixed domain 2003 sp2 standard primary domain controller , 2008 r2 secondary domain conroller both running dns.  frs service got turned off on 2003 pdc server , 2 servers got serverely out of date on replication.  pdc saw 2008 server beyond tombstone date , not replicate when restarted frs.  in trying fix ended having authoritative restore on pdc , restore group policies backup.  has pdc working ok "unable allocate relative indentifier" when try add new machine domain.  2003 pdc still not replicating 2008 dc.  shows pdc holds fsmo roles can't validate without replication.  question two-fold.  can demote 2008 server , allow pdc validate itself?  don't know if system let me demote has tried it?  have 1 other 2003 server on domain promote third dc.  allow pdc validate when replicated new third dc?  don't want have blow whole thing , start on though small domain few systems in it.  , advice appreciated.

kg

if server has reached tombstone life cycle period demote promote best bet.


cannot demote faulty dc gracefully need forcefull removal.you need ran dcpromo/force removal , ran matadata cleanup on other dc(healthy) remove instance of faulty dc ad database , dns.

once done can promote server adc.

if faulty dc fsmo role holder need seize fsmo on other dc.

reference link
forcefull removal of dc:http://support.microsoft.com/kb/332199
metadata cleanup:http://www.petri.co.il/delete_failed_dcs_from_ad.htm
seize fsmo role:http://www.petri.co.il/seizing_fsmo_roles.htm

can refer below link more details:
http://social.technet.microsoft.com/forums/en-us/winserverds/thread/482439af-901f-4f99-9d00-435dfb5038a0


best regards,

sandesh dubey.

mcse|mcsa:messaging|mcts|mcitp:enterprise adminitrator | blog

disclaimer: posting provided "as is" no warranties or guarantees , , confers no rights.



Windows Server  >  Directory Services



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file