mfichera 2 Posted April 2, 2015 Share Posted April 2, 2015 A little background first. My organization currently has a small test environment for EES 6 for Mac and PC. All computers were upgraded from EES 5 (PC) and Nod 32 v4 (Mac). We just began experimenting with v6 policies. First We noticed one of the PCs shows a "Smart Scan" in the computer scan tab with a scan date of 12/31/1969 4:00 PM, which is strange because we did not enable the "First Scan" policy. The scan itself has not made any progress and has been running for two days. The scan still appears in the computer scan tab after several restarts. Second In the computer scan logs, each of the scheduled scans (in-depth scan with strict cleaning, every morning at 1:00 AM) were marked "Scan in Progress." The same thing happens when we perform an on demand smart scan. The Log Files screen also seems to flicker when viewing the computer scan logs. Any ideas/thoughts? Link to comment Share on other sites More sharing options...
Administrators Marcos 4,694 Posted April 3, 2015 Administrators Share Posted April 3, 2015 1, First scan is run automatically unless the task is disabled (e.g. via a policy). 2, Enabling logging of all scanned objects should give you a clue as to which folder contains a problematic file that causes the scanner to freeze. After narrowing it down to the particular file, please contact Customer care and send it to them for analysis. Link to comment Share on other sites More sharing options...
mfichera 2 Posted April 13, 2015 Author Share Posted April 13, 2015 I spoke with ESET Support and they also recommended to enable the scan logging to find any problematic files. They also recommend performing a clean reinstall of the product, because we did not uninstall EES v5 when we upgraded the client to v6 Link to comment Share on other sites More sharing options...
Administrators Marcos 4,694 Posted April 13, 2015 Administrators Share Posted April 13, 2015 Also a Process monitor log would shed more light into what files are being accessed by ekrn and possibly scanned. Link to comment Share on other sites More sharing options...
mfichera 2 Posted April 15, 2015 Author Share Posted April 15, 2015 A clean install of EES 6 fixed this issue, but now the client gets "General Compiler Error" when trying to update virus DB. Clearing the update cache did not resolve the issue like it usually does with typical update errors. Link to comment Share on other sites More sharing options...
Recommended Posts