Last updated: 31-May-2012
This document describes the changes introduced to Compliance Accelerator 9.0 by the following:
Compliance Accelerator 9.0.1 supports the use of Microsoft Outlook 2010 on Compliance Accelerator client computers. However, this support is not yet available on Compliance Accelerator server computers.
If you exported more than 400,000 items at once, Compliance Accelerator would sometimes fail to generate a report that listed the exported items.
This has been fixed.
When you displayed a preview of an item in the Review pane of the Compliance Accelerator client, the Bcc field would show the message's author and all its recipients, regardless of whether they were Bcc recipients or not. This issue arose because Compliance Accelerator added the details of a message's journal recipients to the Bcc field.
This has been fixed. In message previews, the Bcc field now lists Bcc recipients only. A new Journal Recipients field below the Bcc field now lists the journal recipients.
If you chose to install the Enterprise Vault API Runtime rather than a full copy of Enterprise Vault on your Compliance Accelerator server, issues could arise when Compliance Accelerator synchronized with the Enterprise Vault archives. During the synchronization process, Compliance Accelerator did not check for any deleted archives and register that they were no longer present. Consequently, when you later ran a Compliance Accelerator search, it would try to search the deleted archives instead of ignoring them.
This has been fixed.
The Application > Roles tab of the Compliance Accelerator client let you assign the "View Reports" permission to folder-level roles, such as Full Control and Capture Messages. However, this permission is applicable to department-level roles only. Users who possessed the "View Reports" permission at the folder level but not at the department level would see a Reports tab in the Compliance Accelerator client, but they could not generate any reports.
This has been fixed.
In some circumstances, when Compliance Accelerator synchronized the details of an employee group with the corresponding Active Directory or Domino directory details, it did not take any changes in group membership into account. For example, if you added new members to an Active Directory container, they did not appear in the corresponding employee group after synchronization.
This issue was only apparent after you upgraded to Compliance Accelerator 8.0 SP5 or 9.0 original release.
This has been fixed.
Compliance Accelerator's archive registration task did not work correctly in environments where you ran Enterprise Vault 9.0 original release. The purpose of this task is to register with Enterprise Vault all the archives that Compliance Accelerator is currently using. An archive is in use if its items are in a Compliance Accelerator review set or appear in the results of a search. Registering the archives stops Enterprise Vault from deleting them during an operation to move the archives from one server to another.
The archive registration task worked correctly in environments where you ran Enterprise Vault 8.0 SP4 or 8.0 SP5, but it did not work correctly in Enterprise Vault 9.0 environments.
This has been fixed.
Several fields in the search creation page of the Compliance Accelerator client unnecessarily restricted the number of characters that you could type in them. These fields were as follows:
This has been fixed. You can now type up to nine characters in each field.
By default, the Search configuration option "Use sequence numbers for searches" was disabled. This option is designed to optimize the processing of searches that return more than 50,000 results.
This has been fixed. The option is now enabled by default.
If you nominated a user other than the Vault Service account as the owner of a department, that user could not customize the list of the searchable archives for the department.
This has been fixed.
This release of Compliance Accelerator provides the following new features.
Compliance Accelerator 9.0.3 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
Besides working in IPv4-enabled environments, Compliance Accelerator 9.0.3 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:
Compliance Accelerator clients can now connect to the Compliance Accelerator server in an IPv6 environment.
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:
This has been fixed.
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.
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.
In SQL Server 2008 R2 environments, you would receive the following Internet Explorer script error after you tried to load a Department Roles Summary report in the Compliance Accelerator client:
An error has occurred in the script on this page. Line: 2980 Char: 13 Error: Object required
This has been fixed.
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 subsequent 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.
When you entered the export 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.
If the system locale that you set on the Compliance Accelerator server was not recognized on the computer on which you ran the Compliance Accelerator client, the client could not connect to the server. For example, suppose that you installed the client software on a Windows XP computer and the server software on a Windows Server 2008 computer. Windows Server 2008 supports a number of locales that Windows XP does not recognize, such as English (India) and English (Singapore). If you set the server computer to one of these locales, you would receive the following error message when you tried to establish a connection from the client computer:
A problem occurred while connecting to instance instance_name on server server_name. The Accelerator service is either not running or the server could not be contacted.
This has been fixed.
The following Compliance Accelerator reports contain hyperlinks that, when clicked, display more information on the selected item:
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.
When you exported items to a Personal Folders (.pst) file,
the Compliance Accelerator client would always report that the operation was
successful, even if it was not.
This has been fixed.
If you used the Discovery Collector add-on application to collect items from a SharePoint site and store them in an Enterprise Vault archive, you may have experienced problems when you subsequently exported them from Compliance Accelerator. Instead of exporting the items in their original file format, Compliance Accelerator exported them as MSG files.
This has been fixed.
When duplicate items existed in the tblintTarget table of a customer database, you could not upgrade it to Compliance Accelerator 9.0.1 or 9.0.2. If this issue arose, the following entries would appear in the event log:
Event Type: Error Event Source: Accelerator Manager Event ID: 59 Description: APP ATM - Failed to update database. System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK_tblIntTarget'. Cannot insert duplicate key in object 'dbo.tblIntTarget'.
Event Type: Error Event Source: Accelerator Manager Event ID: 64 Description: APP ATM - Error installing a Customer. Install Thread - worker thread (1) Customer ID: 4 Number of tries: 1 Cause: Violation of PRIMARY KEY constraint 'PK_tblIntTarget'. Cannot insert duplicate key in object 'dbo.tblIntTarget'. The statement has been terminated.
This has been fixed.
You would sometimes experience out-of-memory errors when you exported items as PST files, especially when you performed multiple runs at once.
This has been fixed. By default, you can now perform up to four runs simultaneously. However, you can adjust this number by setting the following system configuration options in the Compliance Accelerator client.
| Configuration option | Description |
|---|---|
| Number of production threads per production run | Specifies the number of threads in the SQL connection pool that Compliance Accelerator assigns to each export run. Enter a value in the range 1 to 25, where the default is 25. |
| Total number of production threads per customer | Specifies the maximum number of threads per customer database that Compliance Accelerator assigns when it conducts export runs. Enter a value between 50 and 1000, where the default is 100. |
To access these configuration options
To determine the maximum number of runs that you can perform simultaneously, divide the "Total number of production threads per customer" value by the "Number of production threads per production run" value. For example, if you specify 100 for the first setting and 25 for the second setting, you can perform up to four runs simultaneously. When you try to perform additional runs, Compliance Accelerator holds them in a queue until it has completed some of the active runs. Then it undertakes the additional runs in the order in which you initiated them.
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.
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.
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:
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.
Copyright © 2012 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, Veritas, Enterprise Vault, Compliance Accelerator, and Discovery Accelerator are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (“Third Party Programs”). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Software file accompanying this Symantec product for more information on the Third Party Programs.
The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043