Maintenance Release 9 (MR9)
This section describes the fixes in Maintenance Release 9 of Symantec AntiVirus 10.1 and Symantec Client Security 3.1.
Components | Component | Version | | Symantec AntiVirus | 10.1.9.9000-71 | | Symantec Client Firewall | 8.7.4.205 | | QServer | 3.5.4.101 | | Symantec AntiVirus Reporting | 1.0.258 | | AMS | 6.12.0.152 | | AntiSpam | 2005.3.0.115 | | Auto-Protect | 9.7.7 | | Behavior Blocking | 2.4.1 | | Common Client | 104.0.19.5 | | Decomposer (Windows) | 3.16.5.5 | | Decomposer (NetWare) | 3.2.14.33 | | DefUtils | 3.1.13.0 | | ECOM | 51.3.0.11 | | IPS | 6.2.2.2 | | LiveUpdate | 3.3.0.85 | | NAVAPI | 4.2.0.8 | | NIS Shared Components | 2005.3.0.90 | | SymEvent | 12.5.4.2 | | SymNetDrv | 6.0.11.3 | | SymSentry | 2.1.0.101 |
Symantec AntiVirus Fixes
IAO.exe terminates unexpectedly
Fix ID: 1433485
Symptom: IAO crashes unexpectedly.
Solution: Updated AMS.
A primary server stops distributing virus definitions to secondary servers.
Fix ID: 1518955
Symptom: Virus definitions are not distributed to secondary servers.
Solution: Resolved a deadlock issue in VDTM (Virus Definition Transport Method).
Network scanning option "Trust" does not reduce file transfer times
Fix ID: 1409059
Symptom: When files are copied to a Symantec AntiVirus computer from a trusted computer, transfer times are not reduced compared to copying data from a non-trusted computer.
Solution: Auto-Protect update.
Symantec Antivirus service cannot be stopped and generates an application error
Fix ID: 1416075
Symptom: Unable to stop the Symantec Antivirus service.
Solution: Rtvscan.exe is now properly notified when SCScomms.dll is unloaded, thereby preventing it from calling an unloaded DLL upon service shutdown.
Computer stops responding during migration from MR5 PP1 to MR5 MP1
Fix ID: 1459124
Symptom: During migration from MR5 PP1 to MR5 MP1, the system may hang.
Solution: Rtvscan.exe no longer tries to access the scanner interface after it has already been shutdown.
Symantec AntiVirus/Symantec Client Security logon script does not recognize an already up-to-date client installation
Fix ID: 936979
Symptom: Client installation files are not updated, causing clients to re-run the client upgrade during every startup.
Solution: Rtvscan.exe was updated to stop updating the VP_LOGIN.INI file, which will prevent clients from re-running the client installation when no new update is available.
Sorting Computer Status logs by "Status" does not sort in a logical or meaningful manner
Fix ID: 1366952
Symptom: When sorting computer status logs by "status," the logs are not properly sorted.
Solution: The status option was removed from the user interface for Computer status logs, since the inventory status is never displayed.
Scheduled scan fails because the wrong user account is used for the scan
Fix ID: 1508155
Symptom: After initiating a scan, the following error can be found in the logs: "Could not start scan, scan engine returned error 0X20000058".
Solution: A startup scan is skipped for interactive users that do not have a user registry. The startup scan will initiate when an actual user logs into the computer.
Computer stops responding when a process is terminated
Fix ID: 1278390
Symptom: Symantec AntiVirus crashes the computer in some cases when a process is terminated. A memory dump references SAVRT.SYS, stop-code 7F or 8E.
Solution: Auto-Protect update.
Symantec Antivirus service crashes when moving server from group to group using the Symantec System Center console
Fix ID: 1517743
Symptom: The Symantec Antivirus service crashes upon moving it from group to group using the Symantec System Center console.
Solution: Rtvscan.exe was updated to prevent it from accessing invalid memory.
Scheduled scans occur at unscheduled times
Fix ID: 1586711
Symptom: Scheduled scan changes do not propagate appropriately to computers that are off-line.
Solution: When a scan is updated, the LastStart value is set to the next immediate run time after the Created time. This will ensure that the scan will not run on the unintended schedule and that missed events are caught from the next scheduled cycle onwards.
Unexpected crash in Rtvscan.exe
Fix ID: 1368594
Symptom: RTVSCAN.exe halts suddenly referencing a c0000005 error.
Solution: Decomposer update.
LiveUpdate cannot update virus definitions from current/monthly delta
Fix ID: 1459345
Symptom: Symantec AntiVirus client is unable to update to the latest virus definitions correctly which leads to full content updates.
Solution: Rtvscan.exe update to avoid installing files in the BinHub folder.
Process termination crash in SAVRT.SYS
Fix ID: 1545197
Symptom: A blue screen error occurs referencing a process termination crash, stop-code 50.
Solution: Auto-Protect update.
Group roaming settings do not move during the promotion of a new primary server
Fix ID: 1411550
Symptom: After moving the primary server role from server to server, "Client Roaming Options" are disabled.
Solution: Changes were made to the registry so that changes are propagated correctly and group roaming settings are retained after moving the primary server role.
Setting change propagates to clients even though Auto-Protect is not "locked" in the Symantec System Center settings
Fix ID: 1385205
Symptom: Setting changes to "Client Auto-Protect Options" are propagated even though these settings are not locked down which may lead to custom user "Exclude selected files and folders" settings to be overwritten.
Solution: "Auto-Protect Options" will only be propagated when these are locked in the settings, thereby restoring the intended design of locking these options.
Server crash with stop-code 7F referencing SAVRT.SYS
Fix ID: 1511249
Symptom: A blue screen error occurs with stop-code 7F on Windows 2000.
Solution: Auto-Protect update.
High CPU usage of Rtvscan.exe on Citrix Presentation Server
Fix ID: 1523553
Symptom: Rtvscan.exe CPU usage fluctuates between 0 and 40%, and possibly high memory usage.
Solution: Rtvscan.exe update which corrects sudden spikes in CPU usage when there was no Rtvscan.exe activity.
Netware Server abends due to RTVSCAN.NLM
Fix ID: 1532338
Symptom: Netware Server abends when RTVSCAN.NLM processes GRC.DAT.
Solution: RTVSCAN.NLM was updated to restore stability while processing "Extension Exclusions" in a GRC.DAT.
Reporter displays incomplete information in risk and status reports
Fix ID: 1235081
Symptom: When the date format is configured to use anything other than the default MM/DD/YYYY, information is missing from risk and status reports.
Solution: Reporting server update to correct date formatting issue.
Conflict between SymTDI and network management software causes blue screen error
Fix ID: 1669963
Symptom: Upon installing Symantec AntiVirus and custom network management software, the computer stops responding with a blue screen.
Solution: Auto-Protect update.
Symantec AntiVirus Server generates excessive connections to Symantec AntiVirus client during client installation
Fix ID: 1669780
Symptom: Symantec AntiVirus server may attempt to reach a client on a port that is no longer in use.
Solution: Increase of the default MaxFileMemoryFootPrint to accommodate increase of the size of virus definitions over time.
"Quarantine" is triggered when "Cleaned" action is selected if threat is detected on a Windows File Share
Fix ID: 1556883
Symptom: Virus log shows that a threat was quarantined rather than cleaned by deletion.
Solution: Auto-Protect update.
Symantec Client Firewall fixes
Computer crashes when Symantec Protection Agent and Symantec Client Security are installed on the same computer
Fix ID: 1445417
Symptom: When Symantec Protection Agent is installed on a computer with Symantec Client Security installed, the computer crashes with stop-code 7F.
Solution: SND update.
After uninstalling/upgrading Symantec Client Security, port 80 is blocked until the computer restarts
Fix ID: 1476693
Symptom: Traffic to port 80 is blocked on Symantec Client Security until a restart after uninstalling or upgrading the product.
Solution: Change in uninstaller so that the firewall is disabled during uninstallation. Future migrations from MR9 will benefit from this change as well.
Symantec AntiVirus Reporting
Virus Outbreak email alert contains non-functional report link
Fix ID: 1318048
Symptom: After clicking on the link in the email alert, a Reporting server login screen appears.
Solution: Reporting server update.
10 minute CGI timeout on Reporting server Home page
Fix ID: 1401005
Symptom: When logging into the Reporting server homepage, the request times out after 10 minutes with the error "CGI Error - The specified CGI application misbehaved by not returning a complete set of HTTP headers."
Solution: Virus queries on the Reporting Server Dashboard were changed to reduce the likelihood that the issue occurs.
"Risk Reports > Auto-Protect not running" fails to apply filters over a specific time period
Fix ID: 1544755
Symptom: "Risk Reports > Auto-Protect not running" events are displayed even though they fall outside of the specified time range.
Solution: Reporting queries were updated to select the correct records.
The "Computers Not Scanned" report for the past 24 hours lists computers that were scanned in the last 24 hours
Fix ID: 1526615
Symptom: The "Computers Not Scanned" report for the past 24 hours lists computers that were scanned in the last 24 hours.
Solution: Reporting server update to address this problem, along with improvements to report computers that have not scanned at all.
Virus definition out-of-date email alert link does not link to expected clients list
Fix ID: 1373213
Symptom: Upon clicking the link, Reporting server will display the Computer Status logs for all computers instead of those that are out of date.
Solution: Reporting server email alert was updated to include the correct query.
Question mark cannot be used as wildcard in Reporting Server's Advanced options
Fix ID: 1474412
Symptom: When using "?" as a wildcard, reports return unexpected data.
Solution: Reporting server was updated to return correct data when using "?" as a wildcard.
The "Computers Not Scanned" report displays the wrong date when the Last Scan Time in the database is NULL
Fix ID: 1317985
Symptom: The "Computers Not Scanned" report returns data for all computers and not those computers that were not scanned during the specified period.
Solution: The "Last Scan Time" now displays "N/A" when a computer has not been scanned.
The "Auto-Protect not running" report does not display all computers where Auto-Protect is not running
Fix ID: 1319587
Symptom: The "Auto-Protect not running" report does not display all computers where Auto-Protect is not running.
Solution: The report name was changed to "No Auto-Protect due to errors," since its true purpose is to single out problematic clients rather than all clients that have Auto-Protect disabled.
README Items
Running LiveUpdate after installation requires additional space
Fix ID: 1234789
Symptom: After running LiveUpdate, additional free space is required to accommodate virus definitions.
Solution: For full details, see the readme.txt section entitled "Running LiveUpdate after installation requires additional space." Symantec AntiVirus 10.1.9客户端（英语）： Symantec AntiVirus 10.1.9客户端64位（英语）： Symantec Client Security 3.1.9客户端（英语）： PS：可能用SAV和SCS的人不多了吧，但我决定坚持用到End of Support Life那一天
[ 本帖最后由 zmda 于 2009-9-13 18:43 编辑 ] |
发表于 2009-9-13 15:56:01
楼主
发表于 2009-9-13 19:14:50
