0 votes

Hi all,

I tried to update one of my adaxes server(EUMSQILM21.eu.loi.net:2014.1>2014.1) and I got following error :

Failed to connect to the schema master role owner
The server is not operational.

This server was deleted by local IT guys (without my advice) and without uninstall Adaxes service several months ago.

I made further upgrade since this server was deleted without problem.

Thanks for your help

by (730 points)

1 Answer

0 votes
by (216k points)
selected by
Best answer


It looks like the Adaxes service that was deleted was the schema master role owner of the AD LDS instance that your Adaxes services use as backend. Since it was not uninstalled properly, the role has not been transferred to another Adaxes service.

To remedy the issue, you need to transfer the schema master role manually. For information on how to do this, see the following article by Microsot: http://technet.microsoft.com/en-us/libr ... 10%29.aspx.

Important Notice: since only Adaxes default service administrator can manage the settings of the AD LDS instance used as Adaxes backend, you need to launch the MMC console with credentials of Adaxes default service administrator (the user that you specified when installing Adaxes).

On the 1st step of the article, you'll need to connect to the AD LDS instance used by Adaxes. For information no how to connect, see the following article: http://technet.microsoft.com/en-us/libr ... 10%29.aspx. On Step 10, you need to supply the name and the port of the AD LDS instance used by Adaxes. To find out the name and the port:

  1. Launch Adaxes Administration Console.
  2. In the Console Tree, right-click one of your existing Adaxes services and click Properties.
  3. The DNS name of your Adaxes service and the port used by Adaxes backend will be displayed on the General tab. You need to supply them when connecting to the backend with the Active Directory Schema snap-in.

Hi guys,

First of all, thanks so much for your useful help.

Since my previous FSMO was not accessible anymore, I had to follow these steps : http://technet.microsoft.com/en-us/libr ... s.10).aspx
to seize schema master role.

If it could help other admins in need ... :)

Best regards

Related questions

0 votes
1 answer

HI. I'm trying to upgrade to 2017.2 and have hit an issue. I have uninstalled Adaxes from our 'DR' server and attempted to install the latest version (note I have ... the server name, and also the servername with the Adaxes port i.e. servername:12345. Thanks

asked Dec 10, 2017 by firegoblin (1.6k points)
0 votes
0 answers

Hi, we recently upgraded to version 2013.1. Everything was working fine. We have multiple websites and noticed, that on custom websites, newly created Active Directory filters do ... THE OU object does not exist". It is a know error? Thanks Regards, Andreas

asked May 30, 2013 by andreasaster (20 points)
0 votes
1 answer

Send Mail with integrated mail sending function isn´t working anymore with SSL after Upgrade to 2023.2. The error code is "Send Mail with integrated mail sending function isn´t ... is working if SSL is not enabled. Does someone else have the same problem?

asked Sep 11 by robin.christmann (160 points)
0 votes
1 answer

We are attempting to update from 2021.1 version 3.14.20916.0 to the most current version - 3.14.21404.0. We have two servers in a multiserver configuration once ... Adaxes Service reverts to the previous server that no longer exists and displays the error.

asked Sep 1 by awooten (40 points)
0 votes
1 answer

The individualmodule for PnP if upgraded to 2.2 in non PowerShell 7 breaks in Adaxers. Previous versions of Powershell will not allow the 2.2 PnP version to connect which is ... to make this work but if it is deprecated by MS, then we will lose functionality.

asked Aug 16 by nick.boehm (20 points)
3,222 questions
2,924 answers
533,017 users