JoeSimms

Ok - thanks for clarifying, i thought the server was supported on v10 but now understand that it is not I appreciate that we'll need to move to either VM/Cloud - ideally i'd like to get the ESMC running again meantime so we can get pending updates completed which were planned for during this holiday break then look to migrate in a more planned fashion over the coming weeks

Hi Yes - it’s running SP1 and I rechecked both of them are installed

Thanks I will need to look at this - but i'm trying to get this working for now to allow updates to be pushed out to clients and monitoring to continue for them - then look at cloud etc... v10 appears to support 2008r2 - i've checked prerequisites for it and should be OK ? The installer says it is not a supported O/S when i try and run the upgrade.

I've tried all of them - all versions listed on the Eset site for download v11/v10/v9 will not install on 2008R2 I'm stuck with 2008R2 / v7.2 and no upgrade path currently (appreciate my fault for leaving it to this point! ) I've tried an in-place u/g to 2012R2 to then allow upgrade to a supported version, but that was unsuccessful Thanks

I've tried to do that today - unfortunately so far i'm not able to The ESMC 7.2 is running on a 2008R2 box - i've downloaded the oldest version that I can see on ESET site ( v9 ) but this is blocked from installing on this OS I don't have access to a 7.2 installer to try to install this on a new server with a supported OS and then move database across before updating that to a supported version such as v11 Thanks

em000_64.zip I've uploaded it as a ZIP file (unsure if that is what you were requesting in previous message?) Thanks Joe.

Thanks I've looked at properties of em000_64.dll and that seems to be the case Entrust Extended Validation Code Signing CA = EVCS1 expired on 08/12/23 Is it possible to get an updated em000_64.dll or an alternative solution to this problem ? Thanks Joe .s

I think it is some limitation in v7.2 and appears date related I've tested it offline and online - so i don't believe it looks like anything is being blocked, but that could be possible ? If i restart my server running ESMC with a system date of 8/12/23 - it works OK whether online or running offline - when i move the date to 9/12/23 or later and restart my server, then ESMC and Agent fails to start. I'm testing it currently by changing date/time on server after booting it with an earlier date to get the services running - i don't know how long it will stay online though

Hi, Thanks for the quick reply - no both agent and server are running v7.2 ( appreciate the out of support issues ) but just trying to get this working today to support the existing clients - then allow us to progress to a supported version. I can't understand why it just stopped working - from the logs it failed with this loader error around 9pm on 15/12/23 when system was running OK. A system restart made no change, ESMC and Agent both fail to start A repair of the application fails as it can't start the service at the end (same "unable to update loader" error) and then rolls the installation back. We had a working image on a cloned server drive from several months ago - when that failed as well when we booted that we tried the clock rollback and that allowed us to started both services OK - hence my worry we've hit some limit/date lock. We have server running offline during this testing so it's not talking to any end users when date/time reset. Thanks

Unfortunately I am seeing the same issue - I appreciate it's a legacy system but for several reasons it's not been updated. Our server stopped working on the 15th of December - same error you are seeing and as with you, on a server that has been untouched. I've not managed to resolve it after several days - and even restoring a backup still shows same problem. What we have seen today is that resetting the server date/time back allows the ESMC server to start. I've checked and all certificates in use are current also. I can't see any obvious reason for the date/time reset to make it work