Jump to content

Login failed: Connection has failed with state 'Not connected'


Recommended Posts



Our server has been working all week until it needed to be rebooted due to a windows update. Now we cannot access the server. 

I tried looking at KB articles, but it is of no help. 


On a side note, we have found V6 incredibly difficult to work with compared to v5. Even after almost a year we thought all these bugs would be polished out but during the week ALL our workstations froze and we had to install an obscure hotfix from 2012. We have around 30 licences and are really reconsidering ESET after this latest misfortune where now we cannot even log into the server anymore. V5 was very smooth and we had no problems running it for years. 

Link to comment
Share on other sites

  • Administrators

Regarding the error connecting to database, make sure that SQL Server Database Engine is set to "Mixed mode (SQL Server and Windows Authentication)". See the screen shot at hxxp://openhosting.com/images/setup3.pngfor instance.

As for the hotfix, it's necessary to install it to prevent a bug in Windows Filtering Platform from manifesting (when filtering application protocols by Endpoint or when agent communicates with an ERAS server). We'll remove some performance improvements in the next service release of ERAS that have been incorporated recently and turned out to cause the WFP bug to manifest.

Link to comment
Share on other sites

  • 1 year later...

Here we are near the end of 2017 and this is still an issue. For 3 plus years this Linux-based ERA deployment has been a nightmare.

From 6.1 to 6.2, 6.2 to 6.3, and so on has never fixed this issue. Whoever made the decision to deploy this product is seriously in need of a career change.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...