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

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.