Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Window 2003 R2 unable to allocate a relative identifier

Posted on 2016-09-08
16
Medium Priority
?
81 Views
Last Modified: 2016-09-08
Hi experts,

I took over a DC from the previous admin, but we had a power power failure and the DC went down.  After a few hours i was able to bring it up.  The hardware is very flaky so i decided to convert it to a VM with ESXI.  It pushed over fine, and i was able to boot into it.  

Now i get errors of "unable to allocate a relative identifier" on anything i do.  I can't add a computer to the domain, i cant create any users, users network time is completely off, etc.

Any help is welcome!
0
Comment
Question by:kabrutus
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 9
  • 7
16 Comments
 
LVL 16

Expert Comment

by:FOX
ID: 41790078
From what I am reading this may be a RID master error.   That role needs to be seized.   Is this the only domain controller in your environment?
0
 
LVL 16

Expert Comment

by:FOX
ID: 41790086
Using this guide scroll down to the section where you will SEIZE fSMO ROLE and follow the directions to seize the RID master role

ref link: https://support.microsoft.com/en-us/kb/255504
0
 

Author Comment

by:kabrutus
ID: 41790089
Yes, this is the only DC.  the other one is having hardware issuses.  this is why i pushed it to the VM
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 16

Expert Comment

by:FOX
ID: 41790099
open an elevated command prompt and run the command
netdom query fsmo


Your RID master may have got corrupted with the failed DC
The role may be pointing to the corrupted box.  Use the seize command to rehome it to this server
0
 

Author Comment

by:kabrutus
ID: 41790123
it has come up with cread.server.local which is old server decommissioned a few years ago.  I need this server to be the DC.  msgsvre.server.local  

How do i set this up as the main DC?  The old decommissioned (cread) server is long gone.
0
 
LVL 16

Expert Comment

by:FOX
ID: 41790134
Use these instructions to seize the fsmo role to this server  -Seize not transfer

ref link: https://support.microsoft.com/en-us/kb/255504

Only the Rid role was pointing to the old server?
0
 

Author Comment

by:kabrutus
ID: 41790135
All roles were pointing to cread.server.local.

None were pointing to the new VM server msgsvre.server.local

Should i seize every role?
0
 
LVL 16

Expert Comment

by:FOX
ID: 41790139
Yes, seize all of them
0
 

Author Comment

by:kabrutus
ID: 41790147
I seized them all, now i run netdom query fsmo and it now shows the correct server.  Is there anything else i should do?
0
 
LVL 16

Expert Comment

by:FOX
ID: 41790151
See if you can perform any tasks without it throwing that error it was throwing
0
 

Author Comment

by:kabrutus
ID: 41790161
It looks good.  i was able to create a user and also add another 2003 server to the domain.  Should i create this 2003 server as domain controller?  LIke that i have a backup just in case this server VM dies?
0
 
LVL 16

Expert Comment

by:FOX
ID: 41790162
No, 2003 is out of life.  Let's get up to speed for your own good

Right now you have a single point of failure.  Being that you have a VM environment I want you to spin up a 2012r2 server, fully patch it, and then follow these steps to add it as a DC to your 2003 domain.

ref link: https://blogs.technet.microsoft.com/canitpro/2013/05/05/step-by-step-adding-a-windows-server-2012-domain-controller-to-an-existing-windows-server-2003-network/
0
 
LVL 16

Accepted Solution

by:
FOX earned 2000 total points
ID: 41790165
Spin up 2012r2, fully patch it, add it as a member server to your domain, then follow the steps to promote it as a DC in to your 2003 domain.
1
 

Author Comment

by:kabrutus
ID: 41790171
Ok, i will give it a shot.  For now i will close this question.  If i have issues, i will ask a new one.  Thanks again Foxluv!
0
 

Author Closing Comment

by:kabrutus
ID: 41790172
Great support!  you are very knowledgeable!
0
 
LVL 16

Expert Comment

by:FOX
ID: 41790205
Good work
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Auditing domain password hashes is a commonly overlooked but critical requirement to ensuring secure passwords practices are followed. Methods exist to extract hashes directly for a live domain however this article describes a process to extract u…
A bad practice commonly found during an account life cycle is to set its password to an initial, insecure password. The Password Reset Tool was developed to make the password reset process easier and more secure.
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question