Veritas eDiscovery Platform Release Notes
- Overview
- Operational notes
- New in Release 9.1.1
- Known issues
- Fixed issues
Fixed issues in Release 9.1.1
The following issues are fixed in Release 9.1.1:
Table: Fixed issues in Identification and collection
Issue number | Description |
---|---|
CFT-1472 | Forbidden error when a user creates an Enterprise Vault collection task. A Forbidden error was displayed when a user with a custom role creates an Enterprise Vault collection task. This issue is now fixed and users can create an Enterprise Vault collection task. |
CFT-1569 | Date filter in Enterprise Vault.Cloud collections allow incorrectly formatted dates to be entered manually. Invalid date formats are not recognized while creating Enterprise Vault.Cloud collection task causing incorrect results to be collected This issue is now fixed. |
CFT-1653 |
Enterprise Vault Hold tasks showing mismatched search hit counts for items held counts. Retries of Enterprise Vault Hold Task wrongly increased Item Held counts on eDiscovery Platform UI (CFT-1604) : This fix resolves a problem of inaccurate statistics of Item Held count for Enterprise Vault Hold task during task retry situations. |
CFT-1667 |
Incomplete ADSync disables valid Exchange mailbox display flag. Exchange Mailboxes are marked as disabled after an incomplete ADSync run. This fix resolves the way eDiscovery Platform deals with environment situations during the AD Sync process. The fix is multifold and solves different environmental problems observed in the field.
|
CFT-1679 |
No record of who deleted a (non EV-hold) collection task. For Enterprise Vault Collection task and Search tasks, logs do not mention the user who deleted them. This fix resolves the problem and enhances logging with by storing details of user who deleted Enterprise Vault Collection and Search tasks. |
CFT-1739 |
Enterprise Vault collection ends in a false SUCCESS when an Index Server fails. Enterprise Vault collection task falsely end with Success state when one or more Enterprise Vault Index Server fails to respond in the stipulated time (CFT-1585). This fix resolves the problem and ensures that the Enterprise Vault collection task shows the correct job status at the end of the run. |
CFT-1786 | Enterprise Vault collections threads causes Enterprise Vault to go down. Multiple collection requests to the Enterprise Vault Server causes services to go down. The fix introduces a control mechanism to ensure that Enterprise Vault collection tasks raised by eDiscovery Platform are not overloading Enterprise Vault services and allow them to function smoothly. |
CFT-1795 | Collections from Enterprise Vault.Cloud fail with error EVcloud export failed for exportURL due to null after Enterprise Vault.Cloud update. Enterprise Vault.Cloud collections tasks fail while collecting data from Enterprise Vault.Cloud environment. This fix resolves the integration related issue between eDiscovery Platform and EV.Cloud. With the fix eDiscovery Platform should be able to collect to Enterprise Vault.Cloud mailboxes and download messages which match the ilter criteria of the collection task. |
Table: Fixed issues in Infrastructure
Issue number | Description |
---|---|
CFT-1706 | Node backup is failing with due to Perl version difference. eDiscovery Platform appliance backup fails to initialize on the specific schedule. This fix resolves a problem while appliance backup was not initialized on the scheduled time. |
Table: Fixed issues in Processing
Issue number | Description |
---|---|
CFT-1518 | The field has multiple sender email addresses. The source is NSF file.NSF file that has multiple mail addresses in the Sender field is not correctly processed. The fix has resolved the issue where the processing engine incorrectly strips our email addresses stamped on each message coming from the NSF file of Lotus Domino. |
CFT-1535 | EMLs with embedded images never index EML messages with embedded images cause the Indexer to crash. This fix resolved an issue where the indexer was crashing because of EML messages with embedded images. As a workaround, you can truncate the message body to process EML messages successfully by changing the value of the esa.crawler.eml.droplargebodyeml property to false. As a result, EML messages will not be dropped even if the body size is greater than the defined value. You can define the body size for the truncated messages by reducing the value of PROPERTY_ESA_EML_MSG_BODY_SIZE property. The default value is 1024000 bytes. |
CFT-1599 | All entries in BCC fields are not index due to too many listed. Emails with multiple Bcc fields in message header are not getting indexed correctly (CFT-1486).This fix resolves dataset specific issue where items with multiple Bcc fields in message header were not getting indexed in its entirety. This change ensures that all the recipient values are indexed and searchable in eDiscovery Platform. |
Table: Fixed issues in Search
Issue number | Description |
---|---|
CFT-1699 | Custom field Advanced Search fails until the first eDiscovery Platform restart (or first case of backup and restore). Advanced Search using the Custom Fields section fails to find responsive documents until the eDiscovery Platform services are restarted or until the case is backed-up and then restored. This fix resolves a problem where advanced search using the Custom Fields section fails to find responsive documents. |
Table: Fixed issues in Export
Issue number | Description |
---|---|
CFT-1264 | When generating the Production Export Slipsheet, the |
Table: Fixed issues in System Administration
Issue number | Description |
---|---|
CFT-1497 |
This issue is now fixed. |
Table: Fixed issues in Review
Issue number | Description |
---|---|
CFT-1635 | Retrieval of EML files failing with error: [#41047] Unable to retrieve email content: Retrieval timed out. Reviewing specific EML files results in an error "[#41047] Unable to retrieve email content: Retrieval timed out" (CFT-1383). This issue is now fixed. |