The Directory service was unable to allocate a relative identifier

Jackfor None 1 Reputation point

We have two AD in our network . We set one of the for WSUS .Everything was working fine until i uninstalled wsus to clear directory and change path because of size issues. Next time i installed WSUS in AD and when launched POST Launch script or start WSUS then it asks for folder path to be set where downloaded files will be kept. I get an error "The Directory service was unable to allocate a relative identifier" .The detail log is attached138494-img-20211005-090834.jpg

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,430 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Limitless Technology 39,501 Reputation points


    Thank you for your question.

    The results say the DC with the RID master role has been deleted. Assuming the DC that held this role has been removed and cannot be brought back, you need to seize the role. Best to seize onto the DC that holds the PDC Emulator role

    We have a similar subject with a problem similar to this, I recommend that you consult it to better understand how to solve it, go to it on the links below:

    On the other note , I will suggest you to keep WSUS on separate server or VM from AD.

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments

  2. Gary Reynolds 9,406 Reputation points

    Hi @Jackfor None

    You can confirm which DC is the current RID master by checking out this article sites-dc-list, the DC that has the RID master role will have an R next to it in the Roles column.

    Then have a look at rid-pool which will show the current RID pools per DC and you can confirm that there are spare RIDs in the pools. If the pools have been depleted then you should be having issues creating objects on this affect DC and the event log will have errors associated to object creation.

    You can confirm if this the problem by creating a new object on the DC to see if you get an error from the ADUC.


    0 comments No comments