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.

---

I can see from running the powershell command from my adaxes web host server, that the port is open and it is able to connect via that port. Nothing on my system could be blocking the service from connecting. If you have a test envronment please see if you get the same results.

TNC "adaxes server name" -Port 54782.

The result for me shows connection succeeded.

So I believe the issue is withing the adaxes configuration. Can you help me fix a configuration issue with your product?

---

Hello,

As we mentioned previously, this cannot be an Adaxes issue. You can reach the web server, however, the web server itself cannot reach Adaxes service. That is where there is something in your environment that is blocking the connection. There is nothing in Adaxes that can do that. Unfortunately, we cannot be more specific as we are not familiar with your environment. The only thing we can suggest is try reinstalling Adaxes Web itnerface to make sure it connects to the proper Adaxes service.

---

Hello, Same error again after running updates on the IIS server and restarting. It seems the adaxes service connector breaks everytime we run updates and restart the web server. When I open the Administration console everything works fine, but when I check the web page, i get "fatal error" could not connect to adaxes server. There has got to be something else within Adaxes that is causing this issue. The program cannot be this temperatmental. Windows Updates are a must have.

---

Hello,

We totally agree with you on the fact that Windows updates are a must have. However, as we mentioned previously, there is nothing in Adaxes itself that can result in such a behavior. It always uses the very same ports and connections. It can only be something in your environment that causes the issue. For example, it can even be some software that simply takes some port(s) used by Adaxes after Windows updates are installed and the computer is restarted. As it was mentioned in the previous pat, unfortunately, we cannot be more specific as we are not familiar with your environment.

---

This is unfortunate because the only application on the server that is running is Adaxes Web. via IIS. This is a single purpose built server to run Adaxes Web. The AV is turned off and the Domain firewall is turned off. So what else could be causing this issue? Last time we had this issue we ran a repair on the Adaxes Web service via the control panel and that fixed the issue. This time no such luck. Any Idea what else we can try?

---

Hello,

The error Adaxes Service Connection Failed means only that the web interface component was unable to connect to the Adaxes service one. That is where only port 54782 is used. The only thing we can suggest from the Adaxes standpoint is recreating service connection points (SCPs) following the below steps. However, that is unlikely to cause the issue as there is definitely something just blocking the connection.

• Remove all the existing SCPs: https://www.adaxes.com/questions/209/how-to-unregister-an-adaxes-service-manually.
• Restart the Softerra Adaxes Service Windows service on all the computers where it runs.

---

Hello, Upon attempting your instructions, the "paste" function is greyed out when I attempt to select it. Why would this be? I made sure I can paste the code into a Text document, but when I attempt the paste into the search criteria section, it is greyed.

---

Hello,

As per our check, the instructions are correct. Please, post here or send us (support@adaxes.com) screenshots of all the steps you perform.

---

https://www.adaxes.com/questions/209/how-to-unregister-an-adaxes-service-manually

---

Hello,

First of all, please, try restarting Adaxes Administration console. If the issue persists, try pasting the criteria from the article into notepad, copy from there and then check whether the Paste button is active.

---

---

I got it to work and removed an old connection point, and restarted the servers web\app but that did not help.

What I did find, was I had to run a repair on the the application on the web server. Then I restarted the Server. After this I was able to get to the Web Config interface but still received the same error for the web portal. The Connection point went from showing 127.0.0.1 as the binded IP to being the actual IP of the server. I ran another repair on the application from the control panel on the adaxes web interface. This time after a restart, I was able to get to the user interface for the adaxes web console.

Its odd that this happens everytime we restart the server and update it. We normally update the LOG server first and make sure thas it accepting connections before movig onto the App server and the Web server.

Is there a better way that adaxes needs to be restarted when running windows updates. as in a different order?

We currently restart with SQL, then Application, then Web server.

---

Hello,

The order is correct and should not cause any issues at all.