When tryin to add a new server to a current shared configuration, i get a "Failed to Connect to Service Configuration Server", Username or Password wrong. I checked the password, it's correct and i can log on with that account and also the service is running in that context on the server i want to join the shared configuration. The servers are in the same network and no windows firewall is running. I also tried it with domain\username and username@domain, both with the same error. 2025-10-14 10_02_50-.png

Any ideas on that?

ago by (170 points)

1 Answer

ago by (306k points)
0 votes

Hello,

First of all, make sure that all the ports used by Adaxes are open for the computer where the new Adaxes service will be installed. For details, see https://www.adaxes.com/questions/20/what-ports-does-adaxes-use.

Also, you need to make sure that all the ports for AD LDS (used as Adaxes backend) replication are also open. For details on the ports, have a look at the following Microsoft article: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd772723(v=ws.10)?redirectedfrom=MSDN.

Pay attention that not only firewall, but some third-party software (e.g. protection one) can block or consume the ports.

Finally, make sure that the account you specify during the installation is not a member of the Protected users group.

ago by (170 points)
0

I will check that. The user is at least not a member of the Protected User group. And just to be more specific, the server i try to add in the shared configuration, has previsiously already been an Adaxes Server. I just uninstalled Adaxes before to install the new Updates and re-add this server again in the shared configuration.

ago by (170 points)
0

I figured out what the problem is. We also did install Windows Updates with our Adaxes Update Process. This made us dive into an error described here:

https://learn.microsoft.com/en-us/answers/questions/5545056/%2824h2%29-build-26100-5074-%28kb5064081%29-release-previe

https://learn.microsoft.com/de-de/answers/questions/5543276/kein-rdp-oder-file-share-mehr-nach-letzten-windows

It's found in KB5064081, KB5064401, KB5065426 and leads to an lsasrv event id 6167.

After uninstalling the KB everything works as expected. Thanks for your assistance.

Related questions

During the upgrade of the second server with version 2021.1, shared installation selected, the process stops in "pending authorization" not allowing the process to complete ... to find Adaxes services that are waiting for authorization." Any suggest? Thanks

asked Mar 18, 2021 by Simone.Vailati (500 points)
0 votes
1 answer

We have not deployed the Password SelfService out yet, but I am making my help desk guys use the password reset tools when they lock themselves out. ... .SelfPasswordResetFormViewPresenter.GetNearestService() --- End of inner exception stack trace ---

asked Apr 1, 2013 by jiambor (1.2k 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, 2023 by awooten (80 points)
0 votes
1 answer

Is the further clarification on how to join the Adaxes service to the configuration set during a multi-sever upgrade

asked Nov 16, 2022 by itsupport (20 points)
0 votes
1 answer

Subject: Connecting to a Foreign Domain Without a Trust Relationship Hello Adaxes Support, I am trying to connect to a domain that has no trust relationship and is not part ... my (unknown) domain? Thanks in advance for your help! Best regards, Idkom Helpdesk

asked Mar 19 by IDKOM (40 points)
0 votes
1 answer