Last updated: 13-Mar-2012

Symantec Discovery Accelerator™ 10.0.1

This document describes the changes that Discovery Accelerator 10.0.1 introduces.

Before installing or upgrading to Discovery Accelerator 10.0.1, you must read both this document and the Read Me First file for Discovery 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 Discovery Accelerator 10.0.1
• Fixes to known issues
• Legal notice

New features in Discovery Accelerator 10.0.1

This release of Discovery Accelerator provides the following new features.

FIPS 140-2 compliance

Discovery 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.

All the following types of Discovery Accelerator cases are FIPS-compliant:

• Cases that you create with Discovery Accelerator 10.0.1.
• Pre-10.0.1 cases in which analytics is disabled.
• Cases that you create by promoting research folders that you have added with Discovery Accelerator 10.0.1.
• Cases that you create by promoting pre-10.0.1 research folders in which analytics is disabled.

You can ensure FIPS compliance for pre-10.0.1 cases and research folders by disabling analytics and then re-enabling it with Discovery Accelerator 10.0.1.

For more information on Discovery Accelerator's FIPS certification, and about using Discovery 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, Discovery 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 Discovery Accelerator Web sites. In this instance, you cannot type an IPv6 address that includes colons (:) or is enclosed in square brackets ([]).

Discovery Accelerator clients can now connect to the Discovery 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 Discovery 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/production folder paths [Ref 11349, 11350, 11351, R9038938, E2343032]

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

This has been fixed. The 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 Discovery 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 Discovery 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, Discovery Accelerator did not require you to enter the selected criteria.

This has been fixed.

Fixes to various legal hold issues

The following legal hold issues have been fixed in this release:

• In the Discovery Accelerator client, in the properties pane for a case, the Number of items field in the Legal Holds area did not provide any information. [Ref 11122, R9038523, E2314575]

• If you released the legal hold in a case at a time when the associated vault stores were in backup mode, the vault store databases could contain orphaned legal hold records. These records could stop Enterprise Vault from deleting archived items at the end of their retention period. In addition, this issue could lead to multiple entries like the following in the event log:

  Log Name:      Symantec Enterprise Vault
  Source:        Enterprise Vault 
  Event ID:      6621
  Task Category: Storage Online
  Level:         Error
  Description:   An exception has occurred. 
  Type:          CStoreAccessor::ReleaseHoldsByGroup 
  Reason:        The Vault Store is currently in Backup Mode.

  [Ref 10379, R9039670, R90310210, E2181627, E2410261, E2426524]

• If you changed the list of searchable vault stores for a case after you placed the items in the case on legal hold, Discovery Accelerator would repeatedly check that the legal hold was still in force. On occasions, the case properties pane in the Discovery Accelerator client would show that the wrong number of items was on hold, or that none of them was. [Ref 11345, R9039133, E2380880, E2380859]

Analytics data collection could not process certain email messages [Ref 10330, 10598, R90310171, R90310295, E2408154, E2438002, E2497137]

The following types of email messages would fail the analytics collection process:

• Messages that Discovery Accelerator considered to be malformed. The messages that Enterprise Vault archives and indexes typically contain XML markup tags to denote the beginning and end of sections. For example, one such section is the message body, which has a start-tag of <Body> and an end-tag of </Body>. If an end-tag was omitted from a message for any reason, the analytics collection process would consider the message to be malformed and mark it as failed.

  If this issue arose, you would see the following message in the Error Management window (accessed by clicking the Error details hyperlink in the Cases > Analytics pane of the Discovery Accelerator client):

  System.ArgumentOutOfRangeException: Length cannot be less than zero.
  Parameter name: length

• Messages that had certain non-standard characters in the index metadata that Enterprise Vault assigned to them. When this issue arose, the following message would appear in the Error Management window:

  System.Runtime.InteropServices.COMException (0x80040306): An internal failure occurred.
  Internal Error: 'The parameter is incorrect. [0x80070057]'.

Both issues have been fixed.

Timeouts and out-of-memory issues in large Custodian Manager implementations containing thousands of custodians, custodian groups, or custom attributes

In very large Custodian Manager implementations where you submitted the details of many thousands of custodians, custodian groups, or custom attribute values, you could experience timeouts and out-of-memory issues in various parts of the application. For example, you could experience these issues in the following circumstances:

• When you opened the Custodian Groups Management page, if it had to list many thousands of custodian groups. [Ref 10875, 11123, 11127, 11128, R9038625, E2241692, E2343942]
• When you opened the Create/Edit Custodian page, if it had to list many thousands of custom attribute values. You could also experience timeouts in this page when you clicked a Browse button to search for an account with which to associate the custodian. [Ref 11019, 11130, 11318, R9038836, R9039727, E2318752, E2362115, E2395109]
• When you browsed for the Active Directory account details of a custodian whom you were setting up in the Create/Edit Custodian page. [Ref 11149, E2395030, E2395110]
• When you opened the Custodian Groups page, if it had to list many thousands of custodians in the Membership History box. [Ref 11047, 11352, R9039310, E2351141]

These issues have been fixed. Custodian Manager now limits the number of items that each page can list to 1000 and, in some cases, it prompts you to search for the items that you want to list.

Error message would sometimes appear in Custodian Manager after you imported configuration data from an XML file [Ref 10909, R9039920, E2425885, E2425896]

In some circumstances, the following error message would appear in the Custodian Management page of Custodian Manager after you imported configuration data into the Custodian Manager database from an XML file:

Exception of type 'System.Web.HttpUnhandledException' was thrown. -
System.InvalidCastException: Unable to cast object of
type 'System.DBNull' to type 'System.String'. at
KVS.Accelerator.AddressManager.Target.GetPrimaryAttribute...

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 Discovery Accelerator client.

This has been fixed.

No archives listed in the Archives To Search pane of the Discovery 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 Discovery Accelerator client did not list any archives until you clicked the Synchronize button.

This has been fixed.

Issues in Custodian Manager when synchronizing very large numbers of objects with Active Directory or another external source [Ref 11369, 10831, R90310121, R90310636, E2395167, E2395168]

When Custodian Manager had to synchronize the details of millions of objects with an external source such as Active Directory, the process could sometimes consume large amounts of memory and even fail to complete. If this issue arose, multiple entries like the following would appear in the event log:

Event Type:     Error
Event Source:   Accelerator AD Synchronizer
Event ID:       34
Description:
APP AT - Customer ID: 5 - An error occurred in ProfileSynchroniser::SynchroniseEmployeeProfile while retrieving properties.

This has been fixed.

Issues when setting up custodians with Custodian Manager in a multi-domain forest environment [Ref 11569, R90310068, E2477395]

You could experience problems in Custodian Manager if you installed Discovery Accelerator in a multi-domain, Active Directory forest environment. When setting up a custodian in Custodian Manager, you may have been unable to browse for the custodian's Active Directory account in any domain other than the domain in which you installed Discovery Accelerator. This was the case even if the domains in the forest had a two-way trust relationship.

This has been fixed.

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

The Searches tab of the Discovery 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 Discovery 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 Discovery 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.

Some custom attribute values appeared truncated in the criteria of a running search [Ref 11393, E2586550]

When you chose to view the criteria of a running search, certain custom attribute values that you specified in the search criteria could appear truncated. This issue typically arose when the attribute value comprised a letter followed by eight numbers, such as v12345678, which would appear on-screen without the final number (v1234567). The issue did not prevent the search from running correctly.

This has been fixed.

The search criteria pane of the Discovery 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 Discovery 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 cases 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 Discovery Accelerator environments where communications between the SQL Server and Discovery 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, Discovery Accelerator did not discard the archive registrations that it had previously made [Ref 10980, E2530944]

Discovery Accelerator 8.0 SP3 introduced an archive registration feature, which prevents the accidental deletion of Enterprise Vault archives in which Discovery Accelerator has an interest. However, if you turned off this feature by disabling the archive registration task, Discovery Accelerator did not discard any existing registrations that it had made. This stopped you from deleting the registered archives, even when Discovery 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 Discovery Accelerator client, and then expand the list of Vault Directory Synchronization configuration options.

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

In very large Discovery 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 Discovery 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