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
'APHKGRES02.ap.loi.net:47084'
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 (215k points)
selected by
Best answer

Hello,

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.
0

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

We upgraded to the latest version of Adaxes today but can no longer access the /AdaxesConfig web portal. Getting the error below - What do we need to do to restore access?

asked Mar 24 by sirslimjim (480 points)
0 votes
1 answer

We are currently on 2015, we would like to upgrade to the lates version. Looking for documentation on the upgrade process.

asked Feb 16 by ibmseuser (20 points)
0 votes
1 answer

I have updated adaxes from version 2021.1 to 2021.1 update 3. After that, my favorite links to the report "Password expiration" in Adaxes Administration Console stopped ... the links do not have to be recreated after an upgrade? Thanks and greetings Dominik

asked Apr 21, 2021 by pudong (600 points)
2,887 questions
2,606 answers
6,774 comments
121,145 users