Last updated: 10-Sep-2012

Symantec Discovery Accelerator™ 10.0.2

This document describes the changes that Discovery Accelerator 10.0.2 introduces.

Before installing or upgrading to Discovery Accelerator 10.0.2, 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

• Fixes to known issues
• Legal notice

Fixes to known issues

Certain locale settings on your Discovery Accelerator server could stop you from implementing analytics in cases [Ref 14721, E2704121]

If you configured the locale settings on your Discovery Accelerator server so that the character used as the decimal symbol was a comma rather than a period, you could not enable analytics in any cases. For example, this would typically be the case if you set the locale of the server to French or German, where it is customary to write the number 123.45 as 123,45.

This has been fixed.

The contents of bulleted lists in some messages were not visible when displaying previews of the messages in the Review pane of the Discovery Accelerator client [Ref 14753, E2745187, R14104, E2674357]

When you displayed a preview of a message in the Review pane of the Discovery Accelerator client, the contents of any bulleted lists in the message were not visible if all the following conditions applied:

• The message was an HTML-formatted message.
• In the criteria of the search with which you found the message, you chose to look for a search term in the subject line or contents of the message.
• In the Review Preferences dialog box of the Discovery Accelerator client, you selected the option Highlight search terms in the reading pane.

This has been fixed.

"XML file is invalid" error messages when importing configuration data into a customer database from an XML file [Ref 14877, E2647196]

You may have received the following error message when you tried to import configuration data into your customer database from an XML file:

Error: System.ArgumentException: The value does not conform to the validation regex string
'^([a-zA-Z]\:)(\\?|((\\{1})([^/\\\]\[:;|><"+=,?*]+))+)$|^(\ \\\[^/\\\]\[:;|><"+=,?*]+\\
[^/\\\]\[:;|><"+=,?*]+)((?:\\[^\\/:*?><"|]+)*\\?)$' .
at System.Configuration.RegexStringValidator.Validate(Object value) at
KVS.Accelerator.ImportExport.AcceleratorImportExport.Validate(String

Finished with errors: The XML file is invalid. Correct the validation errors and try again

This issue could affect XML files that you generated with the ImportExport command-line utility as well as XML files that you manually generated. The issue would arise if the XML file contained an ExportOutputDirectory attribute value with a backslash character at the end. For example:

<Department ... ExportOutputDirectory="D:\Discovery_Export\" ... >

However, the issue did not arise if you specified a UNC folder path with a trailing backslash; only direct folder paths like the one above would cause the issue.

This has been fixed.

Unable to synchronize manually-created custodians and groups in Custodian Manager if you had not previously added the appropriate Directory Synchronization details [Ref 14947, E2784351]

The following Custodian Manager procedure would fail if you had yet to add the details of the relevant Active Directory domain to the Directory Synchronization page of the application:

1. You manually added the details of a custodian or custodian group.
2. You clicked Synchronize Now to synchronize the new details with the relevant Active Directory domain.

This has been fixed.

Applying legal holds could fail with Event ID 13360, "Arithmetic overflow occurred" [Ref 15225, E2752551, R14443, E2752550]

When you tried to apply legal holds to the items in a vault store database, the following message may have appeared in the Enterprise Vault event log on the Discovery Accelerator server:

Event ID: 13360
Event Type: Error
Description: An error was detected while accessing the Vault Database 'vault_store'
...
[Microsoft][SQL Server Native Client 10.0][SQL Server]Arithmetic overflow occurred. 

This issue arose because of a limit that SQL Server imposed on the maximum size of one of the values in the vault store database: the HoldIdentity value in the HoldSaveset table. When this value approached its maximum limit, you could no longer apply legal holds to the contents of the vault store.

This has been fixed.

Discovery Accelerator allowed you to specify an invalid search term when you defined the criteria for a search [Ref 15667, E2685005]

When you defined the criteria for a search, you could specify a search term that consisted only of an excluded word or phrase (that is, a word or phrase preceded by a minus sign to indicate that it must not appear in the search results). This should not have been permitted, as you can only specify such words or phrases in conjunction with a positive word or phrase that must appear in the search results.

This has been fixed. Discovery Accelerator now displays an error message if you try to specify a search term that consists only of an excluded word or phrase.

Unable to modify search schedules after you configured their SQL Server Agent jobs to send notification emails [Ref 15696, E2178633]

If you set up a Discovery Accelerator search schedule and then configured its SQL Server Agent job to send a notification email whenever the job completed, you could not subsequently modify the schedule. The following error event was recorded in the event log when you tried to save any changes that you made to the schedule:

Event Type:   Error
Event Source: Accelerator Service Processor
Event ID:     147
Description:
APP AS - Customer ID: 2 - An error occurred updating a schedule.
System.Data.SqlClient.SqlException: The specified '@notify_level_email' is
invalid (valid values are: 1, 2, 3).

This has been fixed.

Analytics data collection appeared to complete successfully, but some analytics facilities produced inaccurate results [Ref 15847, E2647511]

Some analytics facilities such as advanced search and automatic categorization would occasionally fail to produce the expected results, even though Discovery Accelerator had seemingly completed the process of collecting the required analytics data. This issue arose because the SQL Server full-text indexing of the tables in the Discovery Accelerator customer database had failed or was still in progress. The following article on the Symantec Enterprise Support site outlines the circumstances in which this issue could arise:

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

This has been fixed. When you enable a case for analytics, Discovery Accelerator now verifies that the full-text indexing of the collected items has taken place and notifies you if there is a problem.

Underscores in email addresses were omitted when you reviewed the criteria of a search [Ref 16290, E2837738]

When you reviewed the criteria of a previously-run search in the Discovery Accelerator client, any underscore characters in email addresses were not displayed. For example, the email address john_doe@company.com would appear as johndoe@company.com. This issue did not prevent the search from running correctly.

This has been fixed.

Legal notice