Adaxes unable to talk with our domain after upgrade to the newest Adaxes version?

Question

I tried two times to update our perfectly working Adaxes instance (2022.1) to the newest version. Update process doesn't show any errors. Same applies for restore of settings backup.

But each time the adaxes connection to our domain seems to be broken. Users are unable to search for any domain related objects in web interface etc.

Event log shows

Strangly permissions seems to be set correctly and also service point gets updated

Adaxes service is running fine, so there is clearly some problem with permissions/access. Thanks!

Comments

Hello,

How exactly does the issue reflect in the Adaxes Administration console and Web interface? Do users face any error messages? If so, please, provide us with screenshots. You can post them here or send to us at support@adaxes.com.

---

In web console there are no errors. Searches etc just doesn't return anything. Admin console also doesn't show any errors. Thats the reason I attached just system event logs.

---

Hello,

Thank you for specifying. To remedy the issue, please, try to do the following:

1. Remove all the existing service connection points: https://www.adaxes.com/questions/209/how-to-unregister-an-adaxes-service-manually.
2. Restart Adaxes service (this will recreate service connection points).
3. Check whether the issue persists.

If the issue is still in place, please, provide us with a screenshot of the Multi-server environment dialog. You can post it here or send to us at support@adaxes.com. For information on how to view the dialog, see https://www.adaxes.com/help/MultiServerEnvironment.

---

Will try this on saturday. Thanks

---

Unfortunately that didn't help. I've sent you support request (2023012810000018) because I need to solve this ASAP.

ServicePoint seems to be created (search code provided here finds it https://www.adaxes.com/questions/209/how-to-unregister-an-adaxes-service-manually, but system event log still shows error that it wasn't created because of insufficient rights). But the permissions are set correctly

PS: multiserver window shows just the one server where Adaxes is installed

---

Hmm according the problem with creation of the ServiceConnectionPoint it seems that it is solved now. I've added permission also to Adaxes SYSTEM container in our AD

Unfortunately the problem with web interface still persist. I am still unable to find any AD users/groups. Nor I cann se object I manage

Answer 1

Hello,

according the problem with creation of the ServiceConnectionPoint it seems that it is solved now. I've added permission also to Adaxes SYSTEM container in our AD

Thank you for the confirmation, it is much appreciated. The issue was not related to the permissions of the Adaxes service account. They were correct. The thing is that SCPs are created in the System\Softerra container in Ad domains using the permissions of the account specified for the corresponding managed domain in Adaxes. The account can and is recommended to be different from the Adaxes service account. However, if the Adaxes service account is used to register a domain in Adaxes, it will require corresponding permissions.

Unfortunately the problem with web interface still persist

As for the Web interface issue, please, make sure that the corresponding object types are allowed for displaying in the Web interface. For details on the setup, have a look at the following tutorial: https://www.adaxes.com/help/ControlObjectsDisplayedInWebInterface.