Igor Kramarsich 3 Posted November 15, 2018 Share Posted November 15, 2018 Hello, I start ESET Security Management Center upgrade to last 7.0.577.0 version, from previous 7.0 version. Something go wrong. I receive on ESET Security Management Center info about upgrade and start it. Made all backup and then update. Receive new windows and again click update. After this I close for mistake browser. But see that update go. Both folder agent and server is update. After some time try to open console but receive error. See that Tomcat not start again so start it. After this receive blank page in firefox and in Internet explorer (server is windows server 2008) give me error 404. Then I made also server restart, but again blank page. Looking in program list I see ESCM version 7.0.577.0 is installed What I can do now? Link to comment Share on other sites More sharing options...
ESET Staff MartinK 376 Posted November 15, 2018 ESET Staff Share Posted November 15, 2018 I would recommend to follow steps for manual Webconsole installation as from description it seems that something might have gone wrong during Webconsole upgrade. Could you verify there is no directory named "era" in Tomcat's webapps directory, most probably located in C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\webapps\ ? Link to comment Share on other sites More sharing options...
Igor Kramarsich 3 Posted November 16, 2018 Author Share Posted November 16, 2018 Thanks for replay. In Webapps folder was two folder era.bak and era.new. Last one I rename in era and now all work Link to comment Share on other sites More sharing options...
ESET Staff MartinK 376 Posted November 16, 2018 ESET Staff Share Posted November 16, 2018 5 hours ago, Igor Kramarsich said: Thanks for replay. In Webapps folder was two folder era.bak and era.new. Last one I rename in era and now all work Should be working now properly. There is no other operation being made between renaming of directories, but it is very suspicious that era.new was not renamed to era ... most probably some kind of I/O or permissions error occurred during hat operation. Link to comment Share on other sites More sharing options...
Recommended Posts