2021.1 Upgrade - Can't Add New Server to Shared Configuration

Question

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 of which we have backed up the config and uninstalled Adaxes from in order to proceed with the upgrade.

When we attempted to install the new version, however, we received this error:

The two current servers recently replaced two older Adaxes servers and it appears that the original servers may not have been deprovisioned properly.

Following the directions in this thread from support and the OP we were able to seize the roles (schema master and naming master) for the one, primary server that is still running.

We attempted the installation again, however, we received a different error: .

When specifying the Adaxes server to share the config with we're shown the correct server, however, when we go to click "Next" the Adaxes Service reverts to the previous server that no longer exists and displays the error.

Answer 1

Hello,

Most probably the issue is caused by the stale service connection points (SCPs) left after server replacements. To remedy the issue, please, try removing all the existing SCPs and restart the existing Adaxes service. Once done, check whether the issue persists. For information on how to remove the SCPs, have a look at the following FAQ article: https://www.adaxes.com/questions/209/how-to-unregister-an-adaxes-service-manually.

Comments

Our search looks a little different but I was able to build the same search criteria in the advanced tab. Unfortunately the only server that shows up is the current running server that we seized the roles on yesterday.

I don't see any sign of the decommisioned server anywhere.

---

Hello,

As per your reference, you currently have only one instance of Adaxes service. As such, there should be only 2 service connection points (SCPs). Your screenshot has 6 SCPs and they do not seem to be correct. Please, remove all the existing SCPs and restart Adaxes service. This will recreate the proper SCPs.

---

If they don't show up in the search how do I go about deleting them?

When using the criteria specified -

Service-Connection-Point Keywords equals '1.3.6.1.4.1.15741.2.3.1'

on the advance tab of the search (I didn't see anywhere to paste the JSON in my search) the only server that is returned is our currently running Adaxes instance.

---

Hello,

You need to delete the service connection points found when you follow the steps from the article. The SCPs are incorrect and that seems to be the root cause of the issue. As we mentioned in the previous post, your search returns 6 SCPs while there should only be 2.