Jump to content

Archived

This topic is now archived and is closed to further replies.

karsayor

SQL Server Native Client 11.0 errors after update to EFSW 7.0.12014.0

Recommended Posts

Does anyone encounters issue with SQL Server Native Client 11.0 after update to 7.0 of File Security ? I get the attached error every 30 minutes, and it was not present with 6.5. After I uninstalled EFSW 7.0 I can confirm the issue is gone.

Any idea ?

Capture.PNG

Share this post


Link to post
Share on other sites

Does any of the following make a difference?
- disabling real-time protection and rebooting the machine
- disabling HIPS and rebooting the machine
- disabling protocol filtering

Share this post


Link to post
Share on other sites

Disabling HIPS seems to do the trick, no more messages after the reboot. How can we fix this ?

Share this post


Link to post
Share on other sites

We found we stopped having the logs after running a repair of the SQL Server Native Client 11.0

John

 

Share this post


Link to post
Share on other sites

I tried this as well but the issue happens again after a reboot I think.

Only way is disabling HIPS or uninstalling native client

also, it only happens on server 2016, not isolated issue it happens on all of them with native client. 2012R2 doesn’t seems to be affected.

Share this post


Link to post
Share on other sites

Does it make a difference if you keep HIPS enabled and temporarily disable only Self-defense (followed by a reboot)?

Also please provide a debug HIPS log that you create as follows:
- have HIPS and Self-defense enabled (after re-enabling either, the machine has to be restarted)
- enable logging of blocked operations in the advanced HIPS setup
- reproduce the problem
- disable logging

Gather logs with ELC and post the generated archive here.

Share this post


Link to post
Share on other sites
On 10/23/2018 at 1:23 PM, Marcos said:

Does it make a difference if you keep HIPS enabled and temporarily disable only Self-defense (followed by a reboot)?

Also please provide a debug HIPS log that you create as follows:
- have HIPS and Self-defense enabled (after re-enabling either, the machine has to be restarted)
- enable logging of blocked operations in the advanced HIPS setup
- reproduce the problem
- disable logging

Gather logs with ESET Log Collector and post the generated archive here.

Yes, disabling only self-defense is enough to fix the issue.

Unfortunately, there are no logs in the HIPS event log at the same time of the event, still I collected the logs as requested. I send them via PM.

Share this post


Link to post
Share on other sites

hi Marcos,

Do you know if the issue can be fixed ?

Thanks

Share this post


Link to post
Share on other sites

Hi. We worked with support on this and had this excellent response to the issue:

Update for Case #207376 - "SQL Error with EFS"

 

 

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...