Last updated: 13-Mar-2012

Symantec Compliance Accelerator™ 10.0.1

This document describes the changes that Compliance Accelerator 10.0.1 introduces.

Before installing or upgrading to Compliance Accelerator 10.0.1, you must read both this document and the Read Me First file for Compliance Accelerator 10.0.

For the latest information on supported devices and versions of software, see the Enterprise Vault Compatibility Charts (http://www.symantec.com/docs/TECH38537).

For the latest information on supported upgrade paths, see the technical note called Supported upgrade paths for Enterprise Vault, Compliance Accelerator, and Discovery Accelerator (http://www.symantec.com/docs/TECH53174).

Contents

• New features in Compliance Accelerator 10.0.1
• Fixes to known issues
• Legal notice

New features in Compliance Accelerator 10.0.1

This release of Compliance Accelerator provides the following new features.

FIPS 140-2 compliance

Compliance Accelerator 10.0.1 complies with the U.S. government's Federal Information Processing Standard (FIPS) 140-2. FIPS defines the security and interoperability requirements for the computer systems that the U.S. government uses. The FIPS 140-2 standard defines approved cryptographic algorithms and sets forth the requirements for key generation and key management.

For more information on Compliance Accelerator's FIPS certification, and about using Compliance Accelerator in an environment that is enabled for FIPS-compliant cryptography, see the following article on the Symantec Enterprise Support site:

http://www.symantec.com/docs/DOC4820

IPv6 support

Besides working in IPv4-enabled environments, Compliance Accelerator 10.0.1 works in IPv6-enabled environments and mixed environments where both protocols are enabled.

You can now enter IPv6 addresses in contexts where previously you were limited to entering host names or IPv4 addresses. For example, in the Accelerator Manager Web site, you can now enter the IPv6 addresses of the following:

• The SQL Server computers on which the configuration and customer databases are to reside.
• The Enterprise Vault Directory Service computer.
• The SQL reporting server.
• The IIS Server that is to host the Compliance Accelerator Web sites. In this instance, you cannot type an IPv6 address that includes colons (:) or is enclosed in square brackets ([]).

Compliance Accelerator clients can now connect to the Compliance Accelerator server in an IPv6 environment.

Facility to nominate multiple classification policies in the criteria of a search

When you set the criteria for a Compliance Accelerator search, you can now nominate multiple classification policies for which you want to search. Previously, you were limited to searching for one policy only, or all policies of the selected type (inclusions, exclusions, or categories).

Fixes to known issues

50-character limit on export folder paths [Ref 11349, 11350, 11351, R9038938, E2343032]

When you entered the export or production details for a department or research folder, you could not specify an output folder path that contained more than 50 characters.

This has been fixed. Export folder paths can now contain up to 100 characters.

"Object reference not set to an instance of an object" error when displaying the printable version of a review item on non-English computers [Ref 10248, R90310230, E2278871]

The following error message would sometimes appear in the Review pane of the Compliance Accelerator client when you clicked the Printable tab to display the printable version of an item:

Error: Object reference not set to an instance of an object

The issue affected users who were running a non-English version of Windows only.

This has been fixed.

Some Search configuration options were ineffective [Ref 10293, R90310250, E2418794]

The following configuration options, which you can access by clicking Configuration > Settings in the Compliance Accelerator client and then expanding the Search section of the pane, were ineffective:

• Require 'Recipient' to be specified
• Require 'Author' to be specified
• Require 'Subject' to be specified
• Require 'Content' to be specified

If you selected any of these options and then created a search, Compliance Accelerator did not require you to enter the selected criteria.

This has been fixed.

Email address exclusion did not work when conducting searches [Ref 11121, R9038495, E2093817]

In the Search criteria pane of the Compliance Accelerator client, the facility to exclude certain email addresses by prefixing them with a minus sign (-) in the Freeform emails / domains field did not work. When you subsequently ran the search, items whose From, To, CC, or BCC field contained an excluded address would still appear in the search results.

This has been fixed.

The Compliance Accelerator client would display an error message when you tried to view the criteria of certain old searches [Ref 11140, R9037871, E1998493, E2280062]

The following error message would appear in the Compliance Accelerator client after you tried to view the criteria of certain old searches:

The value for column 'DeptID' in table 'source' is DBNull.

This issue arose when both of the following conditions applied:

• You had created the searches with Compliance Accelerator 2007 or earlier.
• In the Authors and Recipients section of the search criteria, you had selected individual employees rather than one or more departments.

This has been fixed.

Random-sampled review sets could contain items spanning a two-day time period [Ref 11142, R9038222, E2009534, E2320703]

In some circumstances, the randomly-sampled items in a department review set could span a two-day time period, even though the random sampling feature is designed to sample yesterday's items only. This issue arose because the Compliance Accelerator database stores the date and time at which an item was sent or received as the UTC date and time, rather than the local date and time on the Compliance Accelerator server.

For example, suppose that the Compliance Accelerator server is located on the west coast of the United States in the PST time zone (eight hours behind UTC). When presented with an email that was sent at 20:30 PST on March 30, Compliance Accelerator would store the item's date/time stamp as 04:30 UTC on March 31. Then the random sampling feature would process the item on April 1, instead of March 31 as expected. For more information on this issue, see the following article on the Symantec Enterprise Support site:

http://www.symantec.com/docs/TECH128253

This has been fixed.

When reviewing items, you could not display previews of items addressed to very large numbers of recipients [Ref 11143, R9038141, E1995530, E2301651]

If an item contained many thousands of addresses in its To, Cc, and Bcc fields, you may have been unable to display a preview of it in the Review pane of the Compliance Accelerator client.

This has been fixed.

No archives listed in the Archives To Search pane of the Compliance Accelerator client after importing configuration data from an XML file [Ref 11322, R90310119, E2425267, E2425309]

After you imported configuration data into a customer database from an XML file, the Application > Archives pane of the Compliance Accelerator client did not list any archives until you clicked the Synchronize button.

This has been fixed.

Clicking the hyperlinks in certain Compliance Accelerator reports would cause errors in SQL Server 2008 R2 environments [Ref 11341, R9039028, E2270840]

The following Compliance Accelerator reports contain hyperlinks that, when clicked, display more information on the selected item:

• Message Stats Summary
• Message Summary
• Reviewer Activity by Department
• Unreviewed Departments

In SQL Server 2008 R2 environments, clicking these hyperlinks would cause an error message like the following to appear:

Item '/Compliance Accelerator Reports/CACustomer/EVDomain vaultadmin/Reviewer Activity by Department 2nd Drilldown' cannot be found.

This has been fixed.

The Domino Journaling task process did not terminate on computers where you installed the Journaling Connector [Ref 7722, E2274616]

On computers where you installed the Compliance Accelerator Journaling Connector, the Enterprise Vault Domino Journaling task would continue to run and be available in Task Manager after you shut down the Enterprise Vault services. This could lead to the situation where multiple instances of the task ran simultaneously, after you restarted the Enterprise Vault services.

This has been fixed.

Unable to create searches if running the Compliance Accelerator client on a Windows 7 computer whose language pack differed from that on the Compliance Accelerator server [Ref 11853, E2619816]

The Searches tab of the Compliance Accelerator client was not accessible if you ran the client on a Windows 7 computer that had a different language pack than that on the Compliance Accelerator server. For example, you could experience this problem if the language pack on the client computer was German, and the language pack on the server computer was English.

The following error message would appear in the Compliance Accelerator client when you encountered the problem:

An exception of type Accelerator.Client.Common.HandledException occurred and was caught.
Message : Object reference not set to an instance of an object.

This has been fixed.

The search criteria pane of the Compliance Accelerator client would sometimes misidentify the template on which you based a search [Ref 12304, E2639575]

When you viewed the criteria of a search that you had based on a search template, the Compliance Accelerator client would sometimes misidentify the template or not identify it at all. This issue typically arose when you ran a series of template-based searches in multiple departments and then viewed the criteria for the first search in the series. It did not prevent the search from running successfully.

This has been fixed.

Growth in size of customer databases if old search results were not removed in a timely fashion [Ref 11656, E2608060]

In very large Compliance Accelerator environments where communications between the SQL Server and Compliance Accelerator server were slow, timeouts could sometimes occur when inserting search results in the customer database and then expanding them into complete messages. The consequence of these timeouts was that the customer database could sometimes contain duplicated or orphaned records, which would increase the size of the database over time.

This has been fixed.

After you disabled the archive registration task, Compliance Accelerator did not discard the archive registrations that it had previously made [Ref 10980, E2530944]

Compliance Accelerator 8.0 SP3 introduced an archive registration feature, which prevents the accidental deletion of Enterprise Vault archives in which Compliance Accelerator has an interest. However, if you turned off this feature by disabling the archive registration task, Compliance Accelerator did not discard any existing registrations that it had made. This stopped you from deleting the registered archives, even when Compliance Accelerator had no further interest in them.

This has been fixed. Two system configuration options now give you greater control over the archive registration feature. To access these options, click the Configuration > Settings tab in the Compliance Accelerator client, and then expand the list of Vault Directory Synchronization configuration options.

"The department has no email addresses defined" message when running some scheduled searches [Ref 12449, E2649247]

A scheduled, department-level search would fail with the message "The department has no email addresses defined" when all the following conditions applied:

• You set up at least one employee group and added it to the Monitored Employees list for the department.
• In the Authors and Recipients section of the search criteria pane, you set the message route to BETWEEN <department> and 'Internal and/or External to Organization'.
• In the same section of the search criteria pane, you chose to search for communications to or from individual employees who were members of the employee group that you added to the Monitored Employees list.

This has been fixed.

In exceptionally large Compliance Accelerator environments, error messages would sometimes appear in the client when you performed administrative tasks

In very large Compliance Accelerator environments where the customer databases contained many millions of records, you could receive one or other of the following messages when you performed an administrative task in the Compliance Accelerator client, such as assigning a role or creating a research folder:

• System.Data.SqlClient.SqlException: Error converting data type timestamp to numeric.

  If you received this message, it was necessary to restart the Enterprise Vault Accelerator Manager service to resume work in the client. [Ref 11719, E2590165]

• Incorrect syntax near '*' [Ref 12960, E2678242]

These issues have been fixed.

Legal notice