Fatal Error after restarting my IIS server

Question

The Adaxes web server running on IIS recently stopped working after a reboot. Nothing has changed, it was a routine restart no updates were installed, After the web server came back up, I get an error message when going to the "http://servername/adaxes#/signin" this happens even when I am on the IIS server itself attempting to browse to the webpage from, IIS.

Fatal Error: Adaxes Service Connection Failed

I can login to the Adaxes Console on the Application server, but from any web interface, it shows this error. Any help would be appreciated.

Answer 1

Hello,

The issue is not related to Adaxes itself, it is just about the Web interface connecting to the service. Most probably, there is something in your environment blocking the connection. For details on the ports used by Adaxes, see https://www.adaxes.com/questions/20/what-ports-does-adaxes-use. Make sure none of them are blocked neither by firewall, nor by any protection software.

Comments

So you are saying I need all those ports open from the web server? I believe these ports are all open from the application server where Adaxes is running.

What port specifically need to be opened on the IIS server?

is there a log I can look at to see what port is being block on the IIS server?

389 LDAP - to connect to Active Directory 636 LDAP (SSL) - to connect to Active Directory via SSL 3268 LDAP - to connect to AD Global Catalog 3269 LDAP (SSL) - to connect to AD Global Catalog via SSL 88 Kerberos - for authentication 135 RPC - to resolve AD user names Dynamic RPC ports* - to communicate with Active Directory

---

Hello,

What port specifically need to be opened on the IIS server?

Have a look at section Adaxes Clients of the article.

is there a log I can look at to see what port is being block on the IIS server?

Unfortunately, there is no such log.

389 LDAP - to connect to Active Directory 636 LDAP (SSL) - to connect to Active Directory via SSL 3268 LDAP - to connect to AD Global Catalog 3269 LDAP (SSL) - to connect to AD Global Catalog via SSL 88 Kerberos - for authentication 135 RPC - to resolve AD user names Dynamic RPC ports* - to communicate with Active Directory

The ports are required for the computer where Adaxes service runs. If you have Adaxes Web tienrface on a separate computer only the ports from section Adaxes Clients need to be open.

---

I have checked, the firewall and all the ports are open that need to be. I even tried turning off the firewall just to see if that was the issue. It was not. I do not believe anything is blocking adaxes. Do you have any other tips? I have tried a repair of the web service to no avail.

---

Hello,

Whenever a client application cannot connect to Adaxes service, the only option is that there is something in the environment blocking the connection. You mentioned that it only started after restarting IIS. As such, nothing changed in terms of Adaxes configuration. It can only be something in your environment. It can also be not a port blocked, but taken by another software.

---

Here is the error I am getting in event viewer....

Failed to get the Web Interface configuration due to the following error: Softerra.Adaxes.Adsi.Exceptions.SelectNearestServiceException: Adaxes service connection failed. at Softerra.Adaxes.Web.Infrastructure.Common.NoCredentialDirectoryObjectProvider.GetAdaxesService() at Softerra.Adaxes.Web.Infrastructure.Common.DirectoryObjectProvider.GetWellKnownObject[T](WellKnownDirectoryObject alias) at Softerra.Adaxes.Web.App.Configuration.UseCommonSignInSettingsModifier.GetCommonSignInConfig() at Softerra.Adaxes.Web.App.Configuration.UseCommonSignInSettingsModifier.ModifierChangesTracker.IsUpToDate(Object stateSnapshot) at Softerra.Adaxes.Web.Core.AdaxesConfiguration.WebInterface.Provider.WebUIConfigurationProvider.IsModifiersCacheUpToDate(WebUIConfigurationModifiersCache lastKnownCache, WebUIConfigurationModifiersCache& newCache) at Softerra.Adaxes.Web.Core.AdaxesConfiguration.WebInterface.Provider.WebUIConfigurationProvider.CheckModifiersCache(Boolean forceCheckCache) at Softerra.Adaxes.Web.Core.AdaxesConfiguration.WebInterface.Provider.WebUIConfigurationProvider.GetConfiguration(String configurationName, GetConfigurationOptions options) at Softerra.Adaxes.Web.App.Core.Controllers.HomeController.Index(String configurationName)

---

Hello,

The error is expected as long as the Web interface failed to connect to Adaxes service. It is all about port 54782. Either some software is blocking it or have taken it.