Last updated: 31-May-2012
This document describes the changes introduced to Discovery Accelerator 9.0 by the following:
This release of Discovery Accelerator provides the following new features.
In earlier versions of Discovery Accelerator, when you defined the criteria for a search or analytics rule, you nominated the custodians for whom you wanted to search by specifying their Display Names. If you prefer to search for custodians by an attribute other than Display Name, Custodian Manager now lets you set that attribute as the primary.
The Display Name and Employee ID attributes are the only standard custodian attributes that you can set as the primary attribute. However, you can set any custom attribute as the primary attribute.
After you set an attribute as the primary attribute, you must restart the Enterprise Vault Accelerator Manager service on all Discovery Accelerator servers and restart all Discovery Accelerator clients. You can then nominate custodians by their primary attribute values when you set up searches and analytics rules with the Discovery Accelerator client.
Discovery Accelerator 9.0.1 supports the use of Microsoft Outlook 2010 on Discovery Accelerator client computers. However, this support is not yet available on Discovery Accelerator server computers.
In some circumstances, placing the items in a case on legal hold could lead to increased memory usage and degraded performance on the Enterprise Vault server and SQL Server. This was particularly noticeable when the searchable archives that you selected for one case overlapped with those that you selected for another case. Having applied the legal holds in one case, you could experience performance issues when you applied the legal holds in the second case.
This has been fixed.
Custodian Manager could not synchronize a custodian or custodian group with Active Directory if the LDAP container path that you specified for the custodian or group contained a forward slash or backward slash in its distinguished name. For example, this was the case if you specified an LDAP container path like the following:
LDAP://OU=Forward / Slash / Organization, DC=MyCompany, DC=com
This has been fixed.
When you created or edited a custodian group and chose to add the members to the group, Custodian Manager would sometimes stop responding if it had to fetch the details of many thousands of users from Active Directory.
This has been fixed. When you choose to add members to a custodian group, the dialog box in which you select them no longer tries to list all the available users. Instead, you must conduct a search for the required users. Custodian Manager then returns a list of the first 1000 users to match the search term that you entered.
If you exported more than 400,000 items at once, Discovery 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 Discovery 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 Discovery 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 Discovery Accelerator server, issues could arise when Discovery Accelerator synchronized with the Enterprise Vault archives. During the synchronization process, Discovery Accelerator did not check for any deleted archives and register that they were no longer present. Consequently, when you later ran a Discovery Accelerator search, it would try to search the deleted archives instead of ignoring them.
This has been fixed.
The following error message would sometimes appear when you conducted an advanced search in the review set of an analytics-enabled case:
The requested items could not be loaded.
This issue typically arose when the attribute that you selected for one or more search conditions was Tag, and its value was No Group.
This has been fixed.
The Application > Roles tab of the Discovery Accelerator client let you assign the "View Reports" permission to folder-level roles, such as Folder Full Control and Folder Capture Messages. However, this permission is applicable to case-level roles only. Users who possessed the "View Reports" permission at the folder level but not at the case level would see a Reports tab in the Discovery Accelerator client, but they could not generate any reports.
This has been fixed.
When viewing certain Discovery Accelerator reports, you may have received the following error message when you tried to display the details of a search that was listed in the report:
An error has occurred during report processing. (rsProcessingAborted) Cannot read the next data row for the data set DateRange. (rsErrorReadingNextDataRow) Conversion failed when converting datetime from character string.
This has been fixed.
Discovery 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 Discovery Accelerator is currently using. An archive is in use if its items are in a Discovery 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.
The message "Syntax error: Missing operand" would appear in the Discovery Accelerator client in the following circumstances:
This has been fixed.
In the Rule Builder tab of the Discovery Accelerator client, if you clicked Edit Query to edit a rule and then clicked any tab to switch away from the Rule Builder, you would sometimes receive the following error message when you switched back to it:
Object reference not set to an instance of an object.
This has been fixed.
Several fields in the search creation page of the Discovery 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.
In some circumstances, after you installed the cumulative hotfix for Discovery Accelerator 8.0 SP4, the process of collecting analytics data for a case would fail to complete.
This has been fixed.
In environments where you ran Enterprise Vault 8.0 SPn with Discovery Accelerator 9.0 or 9.0 SP1, the following error message would appear in the Discovery Accelerator client when you tried to apply or remove legal holds in a case:
Could Not Load Type KVS.EnterpriseVault.Interop.iHold3 from assembly KVS.EnterpriseVault.Interop.EVContentManagementAPI.DLL
This has been fixed.
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.
The Choose custodians and / or custodian groups dialog box, which lets you select custodians and custodian groups to include in the criteria of a search or analytics rule, would sometimes display the wrong result count. For example, suppose that you set the fields in the dialog box to find custodians to which a specified custom attribute had been assigned. The dialog box would sometimes indicate that fewer custodians matched your chosen settings than actually did, or it would indicate that no custodians matched the settings.
This issue only arose when all the following circumstances applied:
This release of Discovery Accelerator provides the following new features.
Discovery 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.
All the following types of Discovery Accelerator cases are FIPS-compliant:
You can ensure FIPS compliance for pre-9.0.3 cases and research folders by disabling analytics and then re-enabling it with Discovery Accelerator 9.0.3.
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
Besides working in IPv4-enabled environments, Discovery 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:
Discovery Accelerator clients can now connect to the Discovery Accelerator server in an IPv6 environment.
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.
The following legal hold issues have been fixed in this release:
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 9039670, 90310210, E2181627, E2410261, E2426524]
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.
If the system locale that you set on the Discovery Accelerator server was not recognized on the computer on which you ran the Discovery 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.
A Discovery Accelerator Searches report contains 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:
The item '/Discovery Accelerator Reports/DACustomer/EVDomain vaultadmin/Search Criteria Drilldown' cannot be found.
This has been fixed.
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:
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.
In the Review pane of the Discovery Accelerator client, if you conducted a quick search whose criteria included a NEAR operator then Discovery Accelerator would return unexpected results. For example, suppose that you set the criteria of the search to "stock NEAR price". Instead of returning only those items where the words "stock" and "price" were within 50 words of each other, the search would simply return items that contained both words, regardless of how far apart they were.
This has been fixed.
When Discovery Accelerator collected and indexed analytics data, it categorized the items that Enterprise Vault archived from Microsoft SharePoint servers as File System items or SMTP items rather than as SharePoint items. The consequences of this included the following:
This has been fixed. You can now choose SharePoint as the required type when you filter the items in the case review set or perform an export or production run. In addition, when you enter the criteria for an analytics rule or advanced search, you can now define conditions in which Message type is the required attribute and SharePoint is the required value.
When you exported or produced items to a Personal Folders (.pst)
file, the Discovery 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 Discovery Accelerator. Instead of exporting the items in their original file format, Discovery Accelerator exported them as MSG files.
This has been fixed.
The Custodian Manager Web site was inaccessible after you upgraded to Discovery Accelerator 9.0.n, if you had previously applied certain hotfixes to the older version.
This has been fixed.
If you used the facilities in Custodian Manager to edit the properties of a custodian then, after you saved the changes that you made, Custodian Manager might temporarily delete any custom attribute values assigned to the custodian. This issue typically arose only with custom attribute values that you synchronized with an external source such as Active Directory. Custodian Manager would restore the values when it next synchronized the custodian details with the external source.
This has been fixed.
You would sometimes experience out-of-memory errors when you exported or produced 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 Discovery Accelerator client.
| Configuration option | Description |
|---|---|
| Number of production threads per production run | Specifies the number of threads in the SQL connection pool that Discovery Accelerator assigns to each export or production 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 Discovery Accelerator assigns when it conducts export or production 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, Discovery 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.
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.
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.
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.
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.
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.
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.
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:
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.
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