Configuring Symantec AntiVirus, Corporate Edition

The following sections outline a few performance issues that often occur when implementing NAVCE.
After completing a run of LiveUpdate, NAVCE might encounter either (or both) of the following problems:
In subsequent scans, all files are omitted from scanning.
RTVScan uses 100 percent of CPU.
Windows generates the following error: Microsoft Visual C++ runtime library, with the text of Runtime Error! Program: ...\rtvscan.exe. R6025 -pure virtual function call.
This problem is generally caused by an old dec2cab.dll file. To solve this problem, you have two choices. First, try simply restarting NAVCE and conducting another scan. Sometimes, NAVCE will mistakenly think that its dec2cab.dll file is too old, when it really isn t. If this solution does not help, take the following steps:
Check the date and time of other Dec2 files. Conduct a search for all De2-based files by entering the following into Windows Search: De2*. All of the files you find should have the same date and version.
Remove the old dec2Cab.dll file and obtain a new dec2Cab.dll file from your NAVCE installation disk.
Stop and restart NAVCE to make sure your changes take effect.
When troubleshooting performance, it is important to remember the maximum number of clients recommended by Symantec. According to Symantec, NAVCE servers should have fewer than 1000 clients connected at a time. If your server has anywhere near this number of clients attached to it, you likely will need to...