Jump to content

Evado

Members
  • Posts

    4
  • Joined

  • Last visited

About Evado

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Croatia
  1. Now it stopped generating errors ?? Without restart... hmmm... OK... after disabling all automatic exclusions ... maybe this was the problem all the time ? My programmer is telling me that it is necessary to have that 2012 Client and that's why I put him in Excluded folders... Is dangerous to work with disabled all automatic exclusions ?
  2. Is restart required after all changes ? Didn't restarted server because I need wait maintenance time. On other server the same. I have SQL 2016 on that server.
  3. The same here. ESET File Security 7.0.12014.0. Windows server 2012R2 and SQL Server 2012 Native Client. I tried: - Exclude path : C:\Windows\System32\sqlnclir11.rll C:\Windows\System32\1033\sqlnclir11.rll C:\Windows\SysWOW64\1033\sqlnclir11.rll C:\Windows\WinSxS\amd64_microsoft-windows-wid_31bf3856ad364e35_6.3.9600.16384_none_986967552fdc62b2\sqlnclir11.rll C:\Windows\WinSxS\amd64_microsoft-windows-wid-x86_31bf3856ad364e35_6.3.9600.16384_none_a99acdd86e54f943\sqlnclir11.rll Even tried - HIPS - Rules - Allow File with paths above. Nothing helps. Can you please just tell us how to exclude this file and everything will work without errors ?
×
×
  • Create New...