Veritas Enterprise Vault™ 12.0.2
|
Last updated: 21-Jun-2016 |
This document describes the issues fixed by:
Enterprise Vault 12.0.2 includes fixes included in earlier release updates.
Enterprise Vault 12.0.2 is a release update for Enterprise Vault 12. From Enterprise Vault 12, release updates replace cumulative hotfixes, which were used to deliver fixes for earlier releases of Enterprise Vault.
The Installation Instructions document, which is available with the release and also at http://www.veritas.com/docs/000108117, describes how to install Enterprise Vault 12.0.2.
Enterprise Vault 12.0.2 contains the following updates and fixes:
Enterprise Vault 12.0.2 includes an updated version of the Veritas Quick Assist tool. Deployment Scanner launches Veritas Quick Assist when you choose to gather support information using the Gather information through Veritas Quick Assist option.
The most up-to-date version of Veritas Quick Assist is available at http://www.veritas.com/docs/000076764.
When Enterprise Vault archives items, it converts them to HTML or plain-text
format to index and create previews of the items. In some circumstances, this conversion
process would stop when it encountered certain Microsoft Access (.accdb)
files. The issue would generate a large number of Event ID 1000 errors in the event
log.
This has been fixed.
If there were a large number of items in your Enterprise Vault environment that had been sampled for submission to Compliance Accelerator, archiving from the Storage Queue could take longer than normal. This could lead to a build-up of items in the Storage Queue and, in some circumstances, could cause archiving to stop.
This has been fixed.
If you selected the Use message body option in the PST Migration policy settings or Exchange Mailbox policy settings, shortcuts that the PST Migrator task created would fail to display special characters correctly in the message body.
This has been fixed.
After Enterprise Vault was unable to store an item on a streamer device, Enterprise Vault attempted to clean up files that did not exist on the device. This caused the streamer device to report errors in the Enterprise Vault event log.
This has been fixed.
The following message appeared when you tried to generate an Items Archival Rate operation report with Enterprise Vault Reporting, if the total size of the archived items over the selected period exceeded 2 terabytes:
There is no data available to display
This has been fixed. Note that after you have installed this release update, you must run the Enterprise Vault Reports Configuration utility and choose the option to Configure Reporting and deploy or upgrade reports. See the Reporting guide for instructions.
You could experience significant delays and excessive memory usage if you configured the Enterprise Vault classification feature to evaluate the content of items against a classification rule that had the following characteristics:
This has been fixed.
If you tried to access Enterprise Vault Operations Manager from a web browser with a Japanese (ja) or Simplified Chinese (zh-cn) locale, you would receive a message indicating that a server error had occurred in the application.
This has been fixed.
The EVSVR operation Repair DatabaseReferences would stop processing if it encountered
an Enterprise Vault saveset (.dvs) file that did not contain an
"ArchivePointID" property value.
This has been fixed.
After you upgraded to Enterprise Vault 12.0.1, you could no longer auto-enable new mailboxes for archiving. The following Error event in the Veritas Enterprise Vault event log would report this issue:
Log Name: Veritas Enterprise Vault Source: Enterprise Vault Event ID: 2776 Task Category: Archive Task Level: Error Keywords: Classic Description: An exception occurred in routine CArchivingAgentQueue::EnableMailbox(1)
This has been fixed.
The following issues would arise when you clicked an Enterprise Vault shortcut in the item list in IBM Notes and then clicked More > Copy Into New to create a new message or calendar entry from the shortcut:
These issues have been fixed.
The Enterprise Vault housekeeping process did not remove temporary mail file replica files (EVR_*.nsf) on 64-bit Enterprise Vault Domino Gateway servers.
This has been fixed.
If you migrated items from Domino to Exchange and then ran the EVDominoExchangeMigration
tool to modify their shortcuts in Exchange, the tool would convert any embedded
images in the bodies of the items to attachments with malformed file names, such
as image.gifgif or image.jpgjpg.
This has been fixed.
The EVDominoExchangeMigration tool would stop running when it tried to process an item from which the sender's Display Name was missing.
This has been fixed.
When the FileSystemArchivingAPI service sent an archiving request to the File System Archiving task, the task would crash if it was not able to find the specified directory.
This has been fixed. If the task does not find the directory path, it now returns the following error:
Could not open the directory: path
In certain circumstances, target file servers could become unresponsive during placeholder recalls.
This has been fixed.
If the File System Archiving task stopped before it had completely processed an auto-enabling folder, it failed to resume correctly.
This has been fixed.
The SharePoint task stopped archiving when a site administrator user was deleted from the Active Directory. When this occurred, the SharePoint task wrote the following error to DTrace:
Server was unable to process request, Some or all identity references could
not be translated, error fetching permissions
This has been fixed.
When the SharePoint task auto-enabled site collections, it stopped if a site collection was not accessible. This prevented it from auto-enabling other site collections.
This has been fixed. If a site collection is not accessible, the SharePoint task now logs an error and continues to auto-enable other site collections.
If you opened an archived SharePoint item from a shortcut and then closed it without making any changes, the item did not revert to a shortcut. This happened when both of the following conditions applied:
This has been fixed.
When the Outlook add-in was installed, and Vault Cache was enabled, a failure to delete an item from the content cache could cause synchronization to fail.
This has been fixed.
In the Compliance Accelerator client, if you removed permissions from the Compliance Supervisor role and then viewed the permissions history of a user to whom you had assigned this role, the permissions history would correctly report the removal of the permissions from departments in which the user was a Compliance Supervisor. However, if these departments contained one or more exception employees, the permissions history did not report the removal of the permissions from the exception employee subdepartments. This was a visual issue only, as the correct permissions were still enforced in these subdepartments.
This has been fixed.
Enterprise Vault 12.0.1 contains the following updates and fixes:
Enterprise Vault 12.0.1 includes an updated version of the Veritas Quick Assist tool. Deployment Scanner launches Veritas Quick Assist when you choose to gather support information using the Gather information through Veritas Quick Assist option.
The most up-to-date version of Veritas Quick Assist is available at http://www.veritas.com/docs/000076764.
In some circumstances, using the option in the Administration Console to recover user-deleted items would sometimes cause the following event messages to be recorded in the Enterprise Vault event log:
Event ID: 6651 Storage Deletion Server has failed Reason: <0x80040e2f>
Event ID: 13405 A constraint violation error was detected while accessing the Vault Database 'EnterpriseVaultDirectory'
In these circumstances, certain folders in the users' archives would no longer be visible in facilities such as Virtual Vault.
This has been fixed.
Users’ permissions on shared folders were sometimes removed when an Exchange server was unreachable during an archiving run.
This has been fixed.
The EVSVR operation Repair DatabaseReferences would fail when it tried to repair
a saveset (.dvs) file that Enterprise Vault 2007 or earlier had created.
The following error message would appear in the EVSVR output log file:
EVSVR ERROR: COperationCIFS::SavesetFileNext, Error: Not implemented (0x80004001) Failed to get the next Saveset, Error: Not implemented (0x80004001)
The issue arose because EVSVR would try to read a property value that exists only in the saveset files that Enterprise Vault 8.0 or later has created.
This has been fixed.
In an environment where the number of available domains exceeded 100, if you ran the PST Locator task to look for computers, the task would return the following error:
"Error converting data type int to nvarchar" executing the "SQL Command: GetDomainIdentity"
This has been fixed. The PST Locator task now supports thousands of domains.
An issue with Oracle Outside InŽ Technology content converters meant that Enterprise Vault sometimes became unresponsive when attempting to convert Microsoft Excel binary format (.xlsb) files. Error 28993 "Unable to convert item content" was reported in the Enterprise Vault Converters event log. The item was archived, but the content was not indexed and no preview of the content was created.
This has been fixed.
If Enterprise Vault cannot archive items for any reason, it moves them to a
Failed Items folder in the Storage Queue. When this happens, error
events 29058 and 29061 appear in the Enterprise Vault event log.
This release update adds a new Repair option to EVSVR so that you can re-queue the failed items for archiving. Follow the steps below.
Create an EVSVR operation file to perform a Repair operation, with the option RequeueStorageQueueFailedItems, on the vault store group or vault store whose items were not archived.
You can use the information from event 29061 to identify the vault store group or vault store that you want to process.
The log file that EVSVR saves in the folder Reports\EVSVR gives
more information on the operation.
In an environment where you previously used Enterprise Vault 9.0 or earlier and then upgraded to version 10.0 or later, Enterprise Vault would sometimes create 64-bit index volume folders for certain 32-bit index volumes. (These index volumes were created by Enterprise Vault 9.0 or earlier, as later versions use 64-bit index volumes. However, the 32-bit volumes are still needed in order to search legacy data.) The 64-bit index volume folders were unused and could consume significant amounts of storage space.
This has been fixed.
In some circumstances, if the PST Migrator task started when vault cache synchronization was in progress, both PST migration and vault cache synchronization could fail to complete.
This has been fixed.
You could experience performance issues after you enabled collection from an existing, large vault store partition that was held on an EMC Centera device.
This has been fixed.
In Domino Server Archiving environments, shortcut creation failed for some items and error 41163 was recorded in the event log. The items remained in archive pending state. The items affected were new messages with embedded images that were added using the Insert image option in iNotes.
This has been fixed.
In a clustered Domino environment where a network load balancer was in use, iNotes users were sometimes unable to open archived items. The following message in the iNotes console log would report this issue:
A problem has occurred which may have caused the current operation to fail. Access denied.
This has been fixed.
Users who did not have Delete Documents permissions in their mail databases would receive the following error message when they tried to reply to or forward Enterprise Vault shortcuts:
Notes error: You are not authorized to perform that operation
This has been fixed.
When you highlighted an Enterprise Vault shortcut in Notes and then selected the option Reply to All with Internet-Style History, the CC field was not populated.
This has been fixed.
The error message "The domain name is empty" would appear in the Vault Administration Console when you tried to modify the properties of a Client Access Provisioning task, if this task was associated with the search provisioning group for a Domino domain.
This has been fixed.
The File Blocking service would terminate unexpectedly if content-based checking was enabled.
This has been fixed.
Enterprise Vault failed to recall files archived from a NetApp C-Mode file server with the following error:
Event ID: 45074 The slave process for the NetApp placeholder server named:
EvNetAppCModePhSvr.exe has failed and will be restarted.
This has been fixed.
FileScreenService.exe failed repeatedly and wrote the event 7034 to the event viewer.
This has been fixed.
When File System Archiving was performing post-processing of archived items, I/O deadlocks sometimes caused target file servers to become unresponsive.
This has been fixed.
After you granted access permissions in a SharePoint 2013 document library to the Everyone group, the members of the group were sometimes unable to open the archived items in the library.
This has been fixed.
If tilde (~) was the leading character in the mailbox name, message subject field, or other message attribute fields, Enterprise Vault Search truncated the first two characters of the field value in the results list. For example, if the mailbox display name was ~John Smith, Enterprise Vault Search truncated the value to ohn Smith.
This has been fixed.
The following message would appear in the Search pane of the Discovery Accelerator client when you tried to run or save a search, if you specified certain values in the Custom attributes section of the search criteria:
Error Invalid custodian(s)
The issue arose when you added the display name of a custodian as a custom attribute value, and that name included one or more commas (,). For example, display names of the form "Lastname, Firstname" would cause the issue to arise.
This has been partially fixed. The custom search attributes do not yet support custodian names that include commas, but it is now possible to run and save searches that contain such values.
In the Settings page of Custodian Manager, the following Profile Synchronization settings for automatically deactivating custodians were ignored for Active Directory synchronizations:
However, these settings did work when synchronizing with deleted Domino directory accounts.
This behavior is by design. In older versions of Discovery Accelerator, the settings worked for both Active Directory synchronizations and Domino directory synchronizations. However, Discovery Accelerator 10.0.4 introduced new methods for deactivating custodians that are synchronized with deleted Active Directory accounts. From this version onwards, the settings have not played any role in detecting and deactivating such custodians.
To make it clear that the settings apply to Domino profiles only, their names have now changed to the following:
Copyright © 2016 Veritas Technologies LLC. All rights reserved.
Veritas, the Veritas Logo, Enterprise Vault, Compliance Accelerator, and Discovery Accelerator are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This product may contain third party software for which Veritas 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. Refer to the third party legal notices document accompanying this Veritas product or available at:
https://www.veritas.com/about/legal/license-agreements
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 Veritas Technologies LLC 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. VERITAS TECHNOLOGIES LLC 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, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Veritas as on-premises or hosted services. 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.
Veritas Technologies LLC
500 E Middlefield Road
Mountain View, CA 94043