Jump to content
Bart31

ESET File security 7.0.12018.0 on RDS2016 crashes services

Recommended Posts

Just now, Marcos said:

You obviously have a good version of the CE module 1745.13. Are you having issues with it as well? Even after a server restart?

I've had to restart the box to get you this screen capture. The server will start having problems around 14:00 tomorrow. I can allow you access to the server for a look if you like, as staff have now gone home.   

Share this post


Link to post
Share on other sites
1 hour ago, Marcos said:

Check "C:\Program Files\ESET\ESET File Security\Modules\em036_64\1237\em036_64.dll". The number 1237 is important as it means version 1745.13 which is in fact the version that was on update servers before.

the version is: 1236

Share this post


Link to post
Share on other sites
6 minutes ago, Erlend said:

the version is: 1236

I have that same version in that folder from 09:50 this morning. So I'm guessing we don't have a fix.

Share this post


Link to post
Share on other sites

I wonder how we could roll back the em036 module to before the 28th at 10am. If we can't work something out I suppose it's time to uninstall ESET. Possibly use another product until this has been corrected.

Share this post


Link to post
Share on other sites
1 hour ago, Marcos said:

Check "C:\Program Files\ESET\ESET File Security\Modules\em036_64\1237\em036_64.dll". The number 1237 is important as it means version 1745.13 which is in fact the version that was on update servers before.

one more thing, do you have a internal system to make local support in different countries aware of these kind of issues?

i contacted ESET support in Norway, and they needed to check and get back to me.

Share this post


Link to post
Share on other sites
1 hour ago, JasonKE said:

I wonder how we could roll back the em036 module to before the 28th at 10am. If we can't work something out I suppose it's time to uninstall ESET. Possibly use another product until this has been corrected.

We already rolled it back. Just make sure that you have v1745.13 installed. Doesn't EFSW update the module to this version after a server reboot?

Share this post


Link to post
Share on other sites

Hi Marcos,

We have multiple clients that have a terminal server and yes, the configuration module is updated back to  v1745.13 after a server reboot but then ESET seems to try to update again and the status in ESET admin console shows that it's updating however, any subsequent logins after that update begins seem to experience the same windows explorer problems.

I am unable to cancel the update at this point, and seem to have to resort to turning off (not shutting down, but powering off) the affected virtual server and powering it back on again because if I try to log out at this point or restart, it will again hang on the "Please Wait for the system Event Notification Service"

Boomtang

 

Share this post


Link to post
Share on other sites

It is weird that the issue occurs also with the CE module 1745.13. Would it be possible to get a complete memory dump (or active memory dump on newer OS's) from the state when the system is unresponsive? For instructions, please refer to https://support.eset.com/kb380/.

Share this post


Link to post
Share on other sites
Same problem under a RDS 2012 R2 ! 

Would you have a solution?


 
Edited by dfourt

Share this post


Link to post
Share on other sites

Last Friday, all systems updated automaticly back to 1745.13 version and have not had any problems anymore.

In all cases, the network was using ESMC (no local installations).

 

Share this post


Link to post
Share on other sites
1 hour ago, dfourt said:

Same problem under a RDS 2012 R2 ! 
Would you have a solution?

What version of the Configuration Engine module do you have?

Share this post


Link to post
Share on other sites
Required to uninstall it from the server.
I even tried to install the old version of ESFW but the same.
On other non-RDS servers on which I made the update, I have version 1811.6 of October 26, 2019

Share this post


Link to post
Share on other sites

I'd suggest raising a support ticket with your local customer care since the issue seems to be completely different than the one discussed in this topic. Most likely a complete memory dump from the point when the issue is manifesting will be needed. Instructions for generating a complete memory dump are available at https://support.eset.com/kb380/.

You can also drop me a message with a link to the dump when ready so that we at ESET HQ can analyze it as soon as possible.

Share this post


Link to post
Share on other sites

I'm glad someone has reported this, I've been tearing my hair out for a couple of weeks with the exact same issues posted above on our 2016 servers. 

Checking these servers, they're all on Configuration Module v1811.6, how do I roll this back to a previous working version??

Any help would be great, thanks!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...