Last updated: 20-Dec-2012

ReadMeFirst for Enterprise Vault™ 9.0.4
Cumulative Hotfix 2

This document describes the issues fixed by:

The Installation Instructions file, which is available with the cumulative hotfix at http://www.symantec.com/docs/TECH200520, gives details of dependencies, changed files, and how to install the hotfix.

Cumulative Hotfix 2

Enterprise Vault cumulative hotfix 2 fixes the following issues:

Enterprise Vault server

Alternate data streams for FSA archive points and folder points were truncated if the target returned an error Etrack 2711215

FSA uses alternate data streams on target folders to indicate archive points and folder points. If a target returned an error while a File System Archiving task was trying to save an alternate data stream, the alternate data stream was truncated and the following error was logged in the File System Archiving task report:

*** Warning *** - One more Root folders were not synchronized for many folders

Now, FSA writes the updates to the content of the alternate data stream in a transactional manner to prevent truncation. If the File System Archiving task fails to save the alternate data stream on the first attempt, it performs a number of retries. By default FSA performs three retries, with a gap of 100 milliseconds between each retry.

To set the registry values, do as follows:

  1. On the Enterprise Vault server create two DWORD registry values named FSASaveFolderPointRetryCount and FSASaveFolderPointRetryWaitInMilliseconds, under the following registry key.

  2. To configure the number of retry attempts to save the alternate data stream, set the value of FSASaveFolderPointRetryCount to any value between 1-10. The default value is 3.
  3. To configure the retry interval, set the value of FSASaveFolderPointRetryWaitInMilliseconds to any value between 1-2000. The default value is 100 milliseconds.
  4. Restart the Enterprise Vault File System Archiving task.

Could not archive public folders when FixOrphanedShortcut registry value used Etrack 2878481

When the FixOrphanedShortcut registry value was enabled, public folder targets were not archived. Error event 4167 was logged for each failed public folder target.

If you use FixOrphanedShortcut, remember to remove it as soon as the shortcuts have been fixed. This registry value may have an adverse effect on archiving performance.

This has been fixed.

Unable to view the contents of S/MIME-signed messages in Lotus iNotes if they had been sent from an external mail system Etrack 2937215

In Enterprise Vault 9.0.3 or 9.0.4 environments, Lotus iNotes users could not view the contents of an S/MIME-signed message if it had been sent from an external mail system. In addition, one of the following errors would appear in the mail server console:

This has been fixed.

Enterprise Vault created internet shortcuts to archived files even though the vault store setting for Remove safety copies was set to "Never" Etrack 2954909

Even though the vault store setting for Remove safety copies was Never, Enterprise Vault created internet shortcuts to archived files after the vault store was backed up, if the folder policy shortcut creation rule was Create Shortcut immediately.

This has been fixed.

EVSVR did not repair the records for collections whose RefCount value exceeded the TotalCount value [Etrack 3004436]

In rare cases, the EVSVR operations Verify DatabaseLinkages and Verify Complete would report an issue with one or more collection records, like this:

Collection file path: \\path_to\Collection123456.CAB, Identity: 123456, TotalCount: 201, RefCount: 204
Collection Reference Count greater than Total Count. Reference: 204, Total: 201

When you subsequently ran the Repair DatabaseReferences operation, and then the Repair DatabaseLinkages operation, neither corrected the issue.

This has been fixed.

SharePoint server archiving

Users were not able to open archived SharePoint items when using alternate URLs Etrack 2966283

When a SharePoint Web Application was extended to another IIS web site, users were not able to open archived items that had been replaced with a shortcut if they used the alternate URL to access SharePoint.

This has been fixed.

Discovery Accelerator

Intermittent errors in placing items on legal hold could leave them eligible for deletion Etrack 2928295

Intermittent errors in placing certain items in a case on legal hold could lead to the situation where the items were still eligible for deletion. Discovery Accelerator gave these items a LegalStatus code of 425, which means "Hold Error", and it did not make any further attempts to place the items on hold.

This has been fixed. If Discovery Accelerator initially fails to place certain items on hold, it now repeatedly tries to do so until it succeeds. In addition, Discovery Accelerator now alerts you to the situation by recording the following Error event in the log on the Discovery Accelerator server:

Discovery Accelerator has identified some cases in which it could not apply legal hold to certain items.
It will make repeated attempts to apply legal hold to these items. If you continue to receive this error
message for the next few days, contact Symantec Technical Support.
The following cases contain items to which Discovery Accelerator could not apply legal hold:
list_of_cases

By default, Discovery Accelerator records this event in the log every 12 hours. The event has the ID number 562.

Cumulative Hotfix 1

Enterprise Vault cumulative hotfix 1 fixes the following issues:

Enterprise Vault server

Event 1309 generated in error during Vault Cache synchronization Etrack 2732286

Event 1309 was sometimes generated in error during Vault Cache synchronization. The event appeared in the event log of the Enterprise Vault server.

The error did not affect the synchronization. The synchronization completed successfully.

This has been fixed.

Move Archive reported an error when it encountered an orphaned shortcut Etrack 2850441

During shortcut updates, Move Archive reported the same error when it encountered either of the following in Exchange mailboxes:

By design, Move Archive does not update orphaned shortcuts and should not have reported this as an error.

Move archive now skips orphaned shortcuts during the shortcut update stage and reports an error only for shortcuts that it does not update because the associated item was not moved to the target archive.

Note that this fix requires you to assign an additional cross-site permission in the case of moves between two sites that are controlled by different Enterprise Vault directories.

The Administrator's Guide already describes that in this case the Vault Service account or other account under which you run Move Archive in the source site must be assigned to the power administrator role in the target site.

In addition, the Vault Service account or other account under which you run the Exchange archiving task in the target site must be assigned to the task application role in the source site.

A NetApp placeholder slave process restarted periodically, causing interruptions to file archiving and recall Etrack 2914106

In a configuration with multiple target NetApp filers, a NetApp placeholder slave process named EvNetAppPhSvr.exe on the Enterprise Vault server restarted several times a day. The restarts of the process disrupted NetApp file archiving and recall.

The problem occurred during the periodic health checks of the slave process. The SQL query to fetch the list of NetApp filers did not return the list of filers in a consistent order, which implied a change in server configuration when none had occurred.

This has been fixed.

Domino archiving tasks archived multiple copies of some items Etrack 2917126

When Domino archiving tasks encountered some corrupt items that could not be archived, the tasks failed to blacklist the items. This meant that the archiving tasks tried to archive these items again on each archiving run, and created multiple savesets in the archive.

This has been fixed. The Domino archiving tasks now correctly blacklist corrupted items which they cannot archive.

Mailbox permissions for linked external accounts were not synchronized Etrack 2917129

In some circumstances, mailbox permissions for linked external accounts were not synchronized to the users' archives, with the result that users had no access to their archives.

This has been fixed.

FSAUtility -pm consumed all the available memory and terminated Etrack 2917132

If you ran FSAUtility with the -pm option to migrate placeholders, it added items to the processing queue without checking whether the queue's upper threshold had been reached. This action could result in the consumption of all the available memory, at which point FSAUtility would terminate unexpectedly.

This has been fixed.

Improved validation for database updates made by the FSAUtility –pm option Etrack 2917136

In some circumstances, the FSAUtility –pm option failed to complete certain operations successfully, which could lead to inconsistencies in the Directory database.

Now, before performing a placeholder migration, FSAUtility performs additional validation checks, to prevent the creation of the inconsistent database records.

FSAUtility restore and recreate placeholder operations did not work Etrack 2917142

FSAUtility -t and -c options to restore and recreate placeholders did not work because of an uninitialized parameter being passed to retrieve the host entry. This has been fixed.

Registering the Enterprise Vault Client for Mac OS X with the Enterprise Vault server would sometimes fail with event ID 2776, "An exception occurred in routine CArchivingAgentQueue::CanUserRegisterMailBox()" Etrack 2917144

In some circumstances, the registration request that an Enterprise Vault Client for Mac OS X submitted to the Enterprise Vault server would fail, and the following event would be recorded in the Enterprise Vault event log:

Type:       Error
...
Event:      2776
Source:     Enterprise Vault
Category:   Agent Client Broker
Description:
An exception occurred in routine CArchivingAgentQueue::CanUserRegisterMailBox()

As a result, the Enterprise Vault Client user could not restore archived items from shortcuts in the mailbox. This issue arose if the user had logged into the mailbox for the first time with a non-English version of Microsoft Outlook or Entourage.

This has been fixed.

EVSVR operation Repair DatabaseReferences could not fix SIS part records for items on a Hitachi Content Platform streamer device whose root folder path exceeded 37 characters Etrack 2946161

If the root path that you configured for a Hitachi Content Platform streamer device exceeded 37 characters, the EVSVR Repair operation DatabaseReferences could not fix certain records in the fingerprint databases and vault store databases for the items stored on the device. If you encountered this issue, the EVSVR log file would contain "Store Identifier mismatch" error messages like the following:

2012-05-17 06:36:48 Store Identifier: jnvs01/ptn17/11990A0753723546AD69AFDBBA084805/2012/May/03/c49416fe-cf15-4148-8c90-ddba700f216d/23_26_40/00621, Stored Date: 2012-05-11 14:48:37Z, Size (B): 44589
2012-05-17 06:36:48 File Type: DVSSP, File Identifier: F12E1D5706D1D13585830D987882B451~C6~05D7FC85~00~1, Archived Date: 2012-05-03 23:45:00Z
2012-05-17 06:36:48 Store Identifier mismatch, SISPart Store Identifier: EVJRNVaultStore01/EVJRNVaultStore01_Ptn017/11990A0753723546AD69AFDBBA084805/2012/May/03/c49416fe-cf15-4148-8c90-ddba700f216d/23_

The cause of the issue was a character limit on a SQL column that Enterprise Vault uses to store the URL to each saveset's storage location on the Hitachi Content Platform streamer device. A root path longer than 37 characters caused the URL to exceed the column limit and consequently be truncated. These truncated URLs prevented EVSVR from processing SIS parts effectively.

This has been fixed.

EVSVR operation Repair DatabaseReferences handled savesets with no associated index entries inefficiently Etrack 2947150

The EVSVR Repair operation DatabaseReferences would always check the index volumes when it recreated records in the fingerprint databases and vault store databases for savesets with no associated index entries, even if you unchecked the Require Index Entries box. This prolonged the operation unnecessarily.

This has been fixed. The Repair operation now only searches those index volumes where the missing item's archive date falls within the volume's archived date range.

Unable to retrieve items from a Hitachi Content Platform streamer device whose root folder path exceeded 37 characters Etrack 2947157

If the root path that you configured for a Hitachi Content Platform streamer device exceeded 37 characters, Enterprise Vault could not index, recall, and restore the items stored on it. The following errors in the Enterprise Vault event log were the most obvious signs of this issue:

Event Type: Error
Event Source: Enterprise Vault
Event Category: Storage Crawler
Event ID: 28944
Computer: EVSERVER
Description:
The 3rd party storage system application 'Hitachi Content Platform (HCP) Streamer' has logged the following message:
CStreamerObject::Read method failed
Reason = 0x80070002
ConnectionManager::Set_Curl_Operation method http://HCPStorage.mydomain.com/rest/VeryLongRootPathNameForHitachiTestDevice
/94618370CEA1E545AFDF5186F1604A8E/2012/May/03/7fd197f7-f12c-44ab-8653-0752c49f8b01/23_28
Reason = 404 : Not Found - opr_GETConnectionManager::Set_Curl_Operation method http://HCPStorage.mydomain.com/rest/VeryLongRootPathNameForHitachiTestDevice
/94618370CEA1E545AFDF5186F1604A8E/2012/May/03/7fd197f7-f12c-44ab-8653-0752c49f8b01/23_28
Reason = 404 : Not Found - opr_GET
Event Type: Error
Event Source: Enterprise Vault
Event Category: Storage Crawler
Event ID: 7083
Computer: EVSERVER
Description:
Retrieval of saveset failed.
Archive Id: 17309ED17DCB9B746931C1521D361D5061110000EVMBX01
Transaction Id: F0ECD449CD75B30B7FDCD645018E5691
Extended information: The system cannot find the file specified. (0x80070002)
Internal Ref: Vault/RI

The cause of the issue was a character limit on a SQL column that Enterprise Vault uses to store the URL to each saveset's storage location on the Hitachi Content Platform streamer device. A root path longer than 37 characters caused the URL to exceed the column limit and consequently be truncated.

This has been fixed. If you have previously encountered this issue, we recommend that you do the following:

  1. Use the HCP Data Migrator to move the data on your Hitachi Content Platform streamer device to a shorter root path.
  2. Use the EVSVR Repair operation DeleteSurplusReferences, and then use the Repair operation DatabaseReferences.

EVSVR DeleteSurplusReferences does not always handle SIS parts on streamer devices Etrack 2962395

When you ran the EVSVR Repair operation DeleteSurplusReferences against a partition on a streamer storage device, the operation would sometimes fail to delete orphaned SIS part records. If this issue arose, the message "The parameter is incorrect" would appear in the EVSVR log file.

This has been fixed. The DeleteSurplusReferences operation now takes streamer-specific attributes into account when it verifies SIS parts.

File Server Archiving

File server became unresponsive after placeholder recall Etrack 2926284

After a placeholder recall, a file server could become unresponsive and require a reset. The problem occurred when the FSA filter driver evmf.sys became deadlocked with the Windows Cache Manager, when a file was recalled as part of the cache read-ahead mechanism.

This has been fixed.

SharePoint server archiving

EVSPShortcutManager may fail to recall items with a custom date and time property Etrack 2912499

If you added a custom date and time property to a Microsoft Office document or an item in SharePoint, EVSPShortcutManager failed to recall the document from the archive.

This has been fixed.

Enterprise Vault Outlook Add-In

Discrepancy in the number of items in Vault Cache Etrack 2754539

In certain circumstances, the Vault Cache contained fewer items than expected. In addition, the content of some items was missing in Virtual Vault.

This could occur in the following situation:

The issue resulted from a problem with the client retry mechanism, which has been fixed. If a Vault Cache database file fails to download to the client, the client now retries the download. The retry mechanism can now handle multiple database files for a quarter.

If the number of download attempts exceeds the maximum threshold, then the client writes to the log file, FailedDBDownloads.log, and moves on to download the next database file. The log file is located in the Vault Cache folder. The log file entry provides information about the dates and SNUM values of the items that the client failed to download.

The location of the Vault Cache folder is defined by one of the following client registry settings:

Invalid EntryIds in Virtual Vault caused Outlook to stop Etrack 2788714

Outlook stopped unexpectedly if an invalid or missing EntryId was encountered in Virtual Vault.

This has been fixed.

Outlook sometimes stopped during Vault Cache synchronization Etrack 2836737

Under certain conditions, Outlook stopped unexpectedly during a synchronization of the Vault Cache.

This has been fixed.

Virtual Vault could not be configured when a Microsoft Office language pack was in use Etrack 2903540

Attempts to configure Virtual Vault failed if the following actions had been taken before installing the Enterprise Vault Outlook Add-In:

This has been fixed.

Note that if you install a new language after installing the Outlook Add-In, you must take one of the following actions:

Compliance Accelerator

Occasional SQL deadlock errors when clicking the Employees tab in the Compliance Accelerator client while large numbers of employees were being synchronized with Active Directory Etrack 2754799

If you clicked the Employees tab in the Compliance Accelerator client at the same time that the application was synchronizing the details of 70,000 or more employees with Active Directory, you could sometimes receive error messages like the following:

System.Data.SqlClient.SqlException: Transaction (Process ID nnn) was
deadlocked on lock | communication buffer resources with another process
and has been chosen as the deadlock victim. Rerun the transaction.

This has been fixed.

Cannot reject Compliance Accelerator or Discovery Accelerator search results or review the search criteria when the criteria include two or more adjacent question marks in a From or To field Etrack 2909866

When you define the criteria for a Compliance Accelerator or Discovery Accelerator search, you can include question marks (?) as wildcard characters in the email addresses that you specify in the From and To fields. If you include multiple adjacent question marks in an email address, as in john.sm???@example.com, then the following issues can arise:

This has been fixed.

Discovery Accelerator

Discovery Accelerator client would sometimes continue to report that it was applying legal holds after the operation had been completed Etrack 2919945

If the number of items that were on legal hold was already very large (more than 2147 million) then, when you used the Discovery Accelerator client to place more items on hold, it would continue to report that it was "Adding hold" after the operation had completed.

This has been fixed.

Cannot reject Compliance Accelerator or Discovery Accelerator search results or review the search criteria when the criteria include two or more adjacent question marks in a From or To field Etrack 2909866

When you define the criteria for a Compliance Accelerator or Discovery Accelerator search, you can include question marks (?) as wildcard characters in the email addresses that you specify in the From and To fields. If you include multiple adjacent question marks in an email address, as in john.sm???@example.com, then the following issues can arise:

This has been fixed.

Legal notice

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

http://www.symantec.com