Chilliflavour

It's under the 'Fix the "Failed to load data" error' link on that page, underneath the Supported Versions table.

Perfect, that fixed it! Just needed to add the 2 extra values listed under Option 1. The extra values in Options 2 & 3 were already there. Many thanks for your help 👍

Hi, As per the title, have started getting this message popping up on my ESET Protect Server after installing the 9.1.1295 update. Not sure if related but at the same time I also manually updated Apache Tomcat to 9.0.65 from an earlier 9.0.xx build, and Java from JRE 1.8.0 to JDK 17.0.4 after getting warnings in the admin console saying the components were out of out date. I didn't have this problem prior to these updates. I now get this message doing certain things in the console such as clicking the status tabs in the dashboard and drilling into the details of the clients. For the most part, repeated clicking of the OK button in the error popup fades it out a little each time until it disappears and lets me into the part I'm trying to view, such as client details or dashboard tabs, but for some functions, such as trying to run a task on a client, I click ok on the popup and it just changes to a loading popup and sits there until you click on one of the left sidebar menus , at which point it comes back to life. Any help would be appreciated. Thanks,

It's a VM so not a problem to back it up. I'll take a look at some point and see if I can get it up to SQL 2019 somehow. Thanks again for your help.

Happy to report the update has successfully installed after upgrading the ODBC driver and modifying the ESMC DB connection string as per your instructions. Thanks for all your help, it's much appreciated! Just wondering if it is possible to upgrade the SQL Server to 2019 without having to reinstall ESMC?

That might throw some light on it. I recently updated the ESMC server from WS 2012 R2 to WS 2016. As per our company security procedures I ran IIS Crypto (using the Best Practices setting) to disable TLS 1.0 & TLS 1.1 and any insecure SSL ciphers. It could be there's a SSL cipher that ESMC uses to connect to SQL which is now disabled? Are you able to tell me which ciphers are used? I've attached the list of active TLS 1.2 ciphers on the server. Regarding SQL, the DB has not been customised. It's using the version and defaults from the ESMC install. All I've done is updated SQL to the latest version, SP3 CU4.

Apologies for the delay in replying, I have been out of the office for a few days on annual leave. Please find the log attached. ra-upgrade-infrastructure.log

Thanks for the instructions. I have attached the trace log which captures another upgrade attempt. Not sure if it's relevant but I noticed the time stamps in the log are 1 hour behind the actual time. The system time on the server is correct. trace.log

Thanks for the response. The client task configuration definitely references version 7.2.1278.0 and I'm not using a custom repository server. The version of the webConsole still shows as 7.2.221.0 after the client task has completed. Could you please advise how to enable the full trace logging you describe? Thanks.

Hi all. My Security Management Center console is showing there is an update available. I run through the process via the link under the Help menu dropdown in the console. The Update Product task is scheduled which completes successfully but the update doesn't appear to have installed. The version under control panel Programs & Features is still at 7.2.1266.0 and the update notification shows up in the console again after re-opening the console or rebooting the server. Have tried the process half a dozen times and the same thing happens each time. Anyone have any thoughts? Thanks,