Veritas eDiscovery Platform Release Notes
- Overview
- Operational notes
- New in Release 9.5.1
- Known issues
- Fixed issues
Fixed issues in Release 9.5.1
The following issues are fixed in Release 9.5.1:
Table: Fixed issues in Release 9.5.1
Issue number | Description |
---|---|
Infrastructure | |
This fix resolved an issue where the eDiscovery Platform services failed to start in case the memory configuration of the appliance was changed. | |
System Administration | |
CFT-2936 | This fix resolved an issue where the scheduled node backups failed after an upgrade in certain situations. |
Identification and Collection | |
ESA-53685 | Release 9.5.1 supports federated search for SharePoint 2016 collections. |
CFT-2522 | This fix resolved an issue where the eDiscovery Platform user interface freezes intermittently in certain situations, and the users were not able to view the System > Jobs window and the status log. With this fix, the following new properties have been added that users can modify based on their requirements. Property: esa.common.mail.smtp.connectionTimeout The default value: 300000 Property: esa.common.mail.smtp.socketIOTimeout The default value: 300000 |
CFT-2385 | This fix ensures that the Enterprise Vault collection task Traits filter option "Include items that have not been indexed by Enterprise Vault" collects relevant emails even though the Keyword filter is not used. |
CFT-2460 | This fix resolved an issue where the Enterprise Vault collection task appeared to be unresponsive when it failed to acquire the lease on the Enterprise Vault server in certain situations. Users can set the following properties: esa.icp.collection.ev.waitAfterLeaseRelease to 2000 esa.icp.ev.contentretriever.leaseWaitTimeMills to 1 second |
Legal Hold | |
CFT-2887 | This fix resolved an issue where the footer information in the legal hold notices was not retained after upgrade in certain situations. |
Processing and Post Processing | |
CFT-2668 | This fix resolved an issue where the EML files were incorrectly categorized and processed as plain text documents in certain situations. |
Search and Review | |
CFT-2994 | This fix resolved an issue where the participant picker in the advanced search failed to save the selected participants in certain situations. With this fix, advanced search includes the selected participants using the participants picker. |
CFT-2487 | This fix resolved an issue where certain hidden content, such as "bubble information" was not displayed properly in the Review screen. |
Production and Export | |
CFT-3066 | This fix resolved an issue where the Native only export failed when the and export options were selected. With this fix, the Native Only export work as expected. |
CFT-2496 | This fix resolved an issue where the exports were not copied to the location specified in the property esa.export.joboutput.external. With this fix, a new configurable property, esa.export.joboutput.external.nozip has been added. By default, the value if set as false, that exports the data as a ZIP file at the location specified in the esa.export.joboutput.external property. If the value is set as true, the data will not be exported as a ZIP file. |
CFT-2408 | For environments where customers are using remote location to store items from Export/Production run, this is an optional workflow which helps in making the Export/Production feature more reliable in situation when network fluctuations are being observed in the environment. When enabled using the below-mentioned property settings, this solution uses the Scratch folder as the temporary location to store the collection of all items that are required to be exported/produced. At the end of export/production, these items will be moved together to the user-specified remote location. esa.export.xml.enable.tempstorage = true (the default value is false) esa.export.xml.disk.required.mb = 10000 (specify the value of your choice as per your requirement) esa.export.xml.disk.required.waitbetweenretries.minutes = 1 esa.export.xml.disk.retry.count = 3 |
Load File Import | |
CFT-2602 | This fix resolved an issue where the users could not view data from a specific load file in text mode when the case was restored to another server. |