,
A few days ago I encountered the error “Login failed: Connection has failed with state “Not Connected” when trying to connect to ESET PROTECT management console. After solving the problem, I decided to write this guide for anyone else facing the same problem.
The error “Login failed: Connection has failed with state ‘Not connected'” occurs because the ESET PROTECT Web Console cannot connect to the ESET PROTECT Server or the ESET PROTECT database to authenticate the login request.
The mentioned problem may occur when the Apache Tomcat or the SQL Server service or the ESET PROTECT Server service is not running, or because the ESET PROTECT database is corrupted.
How to FIX: ‘Login failed: Connection has failed with state “Not connected”‘ in ESET Protect web console.
To solve the ESET PROTECT error “Login failed: Connection has failed with state ‘Not connected’ follow the below methods in order.
Method 1. Restart Required ESET PROTECT Services.
As mentioned above, one of the reasons for the error “login failed” with the status “not connected” in ESET Protect, is that the necessary services required for the console to function are not running. More specifically, ESET PROTECT needs the following three (3) services to function:
- ESET PROTECT Server (EraServerSvc)
- Apache Tomcat 7.0 (Tomcat7)
- SQL Server (ERASQL)
So, navigate to Windows services console (services.msc) and verify that all the above services are running and the startup type is Automatic. Now according the result, do the following:
- If any of the above services are not running, verify that the “Startup type” is Automatic and then Start the service.
- If all the above services are running, do the following in order:
1. Restart the ESET PROTECT Server service first. Then refresh the ESET PROTECT Web Console by pressing F5 and check if you can log in. If you can log in, you’re done here. If not, continue below.
2. Proceed and restart the required services for the ESET Protect in this order (important).
- SQL Service (ERASQL)
- Apache Tomcat 7.0 (Tomcat7)
- ESET PROTECT Server (EraServerSvc)
3. Wait 4-5 minutes and then refresh the ESET PROTECT Web Console (press F5) and try to log in. If you can login without any error, you’re done here. If not, continue to next method. *
* Note: Before continuing below, it is recommended to restart the server (if you can), and then to check again if the problem persists.
Method 2. Allow Required Ports for ESET PROTECT web console in Windows Firewall.
1. Open Windows Firewall and verify in the Inbound rules that ESET Security Management traffic is allowed on ports 443, 2222 and 2223 and that these ports are not being used by other services or applications:
Method 3. FIX ESET PROTECT “Not connected” status by restarting ERASQL Server.
In most cases the mentioned problem is fixed by simply restarting the ESET Remote Administrator SQL Server (aka “ERASQL Server”).
1. Open the Microsoft SQL Server Management Studio (SSMS) and restart the ERASQL (SQL Server).
2. Wait 3-4 minutes and then expand the Databases section and check if the “era_db” database is listed with or without an error. Then according the result, do the following:
- If the “era_db” database is listed without an error try to login to ESET WEB Console. If you still can’t login, follow the steps in this ESET article to uninstall and re-install Web Console using the “All-in-one installer”.
- If the “era_db” is listed with the “Recovery Pending” error, ensure first that the disk containing the database files has sufficient free space* and then continue to next step.*
* Note: If there is not enough free space on the disk containing the “era_db” database, then delete or move some files to another disk, and then restart the ERASQL (SQL Server).
Method 4. FIX “era_db Recovery Pending” state by reattaching the database.
1. Make sure the “era_db” MDF & LDF files exist in the following location and then continue below:
- C:Program FilesMicrosoft SQL ServerMSSQLxx.ERASQLINSTANCEIDMSSQLDATA
2. Right-click on “era-db” database and select Tasks > Take Offline. Then, click OK in the ‘Take Database Offline’ window
3. Then, right-click again on the “era-db” database and select Tasks > Detach. Click OK in the ‘Detach Database Offline’ window.
4. Now right-click on Databases and select Attach.
5. In the Attach Databases window, click Add.
6. In ‘Locate Database Files’ window, select the era_db database and click OK and then OK again to attach the database. *
* Note: If you cannot attach the database and you receive the error “Cannot detach a suspect or recovery pending database. It must be repaired or dropped“, follow the instructions in step-7 in this article to repair the database..
7. Now, restart the ERASQL (SQL Server).
8. Finally, open the Windows services (services.msc) and restart the below services in order:
- Apache Tomcat 7.0 (Tomcat7)
- ESET PROTECT Server (EraServerSvc)
9. Wait 4-5 minutes, refresh the ESET PROTECT Web Console (press F5) and try to log in.
Method 5. FIX ESET PROTECT “login failed with status ‘not connected” by examining the logs.
The final method to fix the “login failed – status: not connected” error in ESET PROTECT console, is to examine the server logs for any error messages or warnings that could provide more insight into the problem. To do that:
1. Open File Explorer and navigate to the following location:
- C:ProgramDataESETRemoteAdministratorServerEraServerApplicationDataLogs
2. Open the trace.txt file and look for any logs that indicate connection failures or other issues like the one in screenshot below.*
* Note: The error in the screenshot indicates that the “era-db” database file is either missing or corrupted. In this case, make sure the “era-db.mdf” file exists and if so, try to restore the database from backup (if you have one) or uninstall and reinstall ESET Web Console using the “All-in-one installer”.
“Cannot open database “era_db” requested by the login. The login failed (4060).”
That’s it! Which method worked for you?
Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.
