TheSkymanDC 4 Posted August 21, 2018 Share Posted August 21, 2018 After what looks to be a successful upgrade to V7 I am no longer able to log into the RA console. The error is Login failed: Connection has failed with state 'Not connected' Any ideas? Thanks! Link to comment Share on other sites More sharing options...
ESET Staff MartinK 383 Posted August 21, 2018 ESET Staff Share Posted August 21, 2018 11 minutes ago, TheSkymanDC said: After what looks to be a successful upgrade to V7 I am no longer able to log into the RA console. The error is Login failed: Connection has failed with state 'Not connected' Any ideas? Thanks! This error means that ESMC Server service is not running. Could you verify that and possibly try to restart it? If it won't help, could you please check relevant trace.log for possible errors? Was it actually working after upgrade, or it stopped working during upgrade? Link to comment Share on other sites More sharing options...
TheSkymanDC 4 Posted August 21, 2018 Author Share Posted August 21, 2018 OK - ESMC Server was not started. Set to Delayed Start. Started the service but still can't log in. Trying to find trace.log. Link to comment Share on other sites More sharing options...
TheSkymanDC 4 Posted August 21, 2018 Author Share Posted August 21, 2018 Here are all the trace.log files I can find. trace (1).log trace (2).log trace (3).log trace.log Link to comment Share on other sites More sharing options...
TheSkymanDC 4 Posted August 21, 2018 Author Share Posted August 21, 2018 Now I see I'm getting this error: Link to comment Share on other sites More sharing options...
ESET Staff MartinK 383 Posted August 21, 2018 ESET Staff Share Posted August 21, 2018 So it seems ESMC servers is not running properly. There is nothing suspicious visible in trace log - could you please check whether there are any minidumps generated in directory: c:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Dumps\ or it's subdirectories? If so, please send me at least one dmp file for verification as private message (PM) as it might contain sensitive data. Link to comment Share on other sites More sharing options...
TheSkymanDC 4 Posted August 21, 2018 Author Share Posted August 21, 2018 (edited) Here you go. Thanks! Looks like there are plenty more. Edited August 23, 2018 by TheSkymanDC Link to comment Share on other sites More sharing options...
ESET Staff MartinK 383 Posted August 22, 2018 ESET Staff Share Posted August 22, 2018 Thanks for clarifying this issue. Please use temporary hotfix for this issue, in attached file you will find replacement modules for Windows and basic instructions. Once applied, ESMC should be working correctly. NotificationValidationFix_ESMC7.0.66.1.zip Link to comment Share on other sites More sharing options...
TheSkymanDC 4 Posted August 22, 2018 Author Share Posted August 22, 2018 That worked! Thanks Martin! Link to comment Share on other sites More sharing options...
ESET Staff MartinK 383 Posted August 22, 2018 ESET Staff Share Posted August 22, 2018 12 minutes ago, TheSkymanDC said: That worked! Thanks Martin! Btw. it was related to new notifications validation mechanisms. It seems, that at least one of your notifications is referencing dynamic group that no longer exists -> now you should see it as invalid. Link to comment Share on other sites More sharing options...
TheSkymanDC 4 Posted August 22, 2018 Author Share Posted August 22, 2018 OK - I don't see that but I'll keep looking. Link to comment Share on other sites More sharing options...
TheSkymanDC 4 Posted August 22, 2018 Author Share Posted August 22, 2018 Found it! Link to comment Share on other sites More sharing options...
.thumb.jpg.d0dae4df7d520793aba4b217c88691a6.jpg)
Recommended Posts