Last updated: 6-Jul-2009
This document describes the changes introduced by Enterprise Vault 8.0 Service Pack 2 (SP2).
Before installing or upgrading to Enterprise Vault 8.0 SP2 you must read this document and also the ReadMeFirst for Enterprise Vault 8.0 which lists current known issues as well as the new features in the original release of Enterprise Vault 8.0. For the most up-to-date versions of these documents, see http://entsupport.symantec.com/docs/308966 on the Symantec Enterprise Support site.
For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at http://entsupport.symantec.com/docs/276547.
The upgrade instructions are no longer provided in HTML format. They are now provided in both .CHM and .PDF formats, included as Upgrade_Instructions.pdf and Upgrade_Instructions.chm on the Enterprise Vault media.
Enterprise Vault 8.0 SP2 provides the following new features:
This service pack provides an Enterprise Vault Client for Mac OS X. Once installed, the client enables Microsoft Entourage users to archive, restore, and delete items, and conduct searches of the items in their archives. The administrator can control which functionality is available to users by using configuration settings in the Exchange Desktop Policy in the Enterprise Vault Administration Console.
The installer kit for the Enterprise Vault Client for Mac OS X is available
as a disk image (.dmg) file on the Enterprise Vault distribution
media. You can install the Enterprise Vault Client for Mac OS X on any computer
that meets the following requirements:
Note the following limitations and known issues in this release of the Enterprise Vault Client for Mac OS X:
.rge) files into Enterprise Vault archives.If an Entourage mailbox folder contains a shortcut to a non-mail item, such as a Word document or Excel spreadsheet, the following error message appears when you try to perform any Enterprise Vault operation on the shortcut:
Error in download... Operation could not be completed
This issue typically arises when an Entourage mailbox contains shortcuts to items that Enterprise Vault originally archived from Outlook. Unlike Entourage, Outlook permits users to drag and drop non-mail items into a mailbox folder. [Ref 1723146]
When the body or subject line of an Enterprise Vault shortcut contains certain Japanese characters, an Entourage user who chooses to view or reply to the original item may receive an error message. You may be able to resolve this issue by doing one or both of the following on the Enterprise Vault server:
In Exchange Server 2003 environments, nothing happens when Entourage users try manually to archive mail items that have Japanese characters in their subject lines. However, these items can be archived without problem in Exchange Server 2007 environments or whenever background archiving occurs.
This issue may also affect mail items that use certain multi-byte character sets other than Japanese.
Users who encounter this issue can work around it by emptying their mailbox folder caches before they undertake manually archiving. For instructions on how to do this, see the Entourage documentation. After users have synchronized the items in their mailbox folders with the Exchange server, they can manually archive any items that this issue affects. [Ref 1702806]
Symantec Enterprise Vault Mobile Search is a Web-based application that lets you use a browser on a mobile device to search for and view archived Microsoft Exchange Server emails and their attachments. You cannot use Mobile Search to reply to or forward an archived email, or to save an attachment.
Mobile Search accepts connection requests from most common mobile devices without the need for any device-specific configuration. The available mobile device models and ranges change continually, so we do not specify a list of supported devices.
You install Mobile Search separately from the main Enterprise Vault installation. Among other prerequisites, it requires the Enterprise Vault Runtime API to be installed on the Mobile Search server. No client installation is required on the mobile device. For information about installing and configuring Mobile Search, see the Setting up Exchange Server Archiving manual.
For end users, there is a Mobile Search Getting Started guide, which is on the Enterprise Vault release media.
The new Domino Retention Folder feature enables you to create a single folder or a hierarchy of folders automatically in users' mail files. Enterprise Vault archives these folders according to policies that you assign. If a user deletes any folders in the retention folder hierarchy, Enterprise Vault automatically recreates them.
You use Enterprise Vault provisioning groups to apply retention plans to mail files. Thus, different users can have different retention folders with the appropriate retention categories.
See the 'Domino mailbox archiving' chapter in Introduction and Planning for information about Domino retention folders.
The new retention folder functionality may affect the permissions that the archiving task requires.
The Domino archiving user account needs permissions to all the mail files to be archived. We recommend that you provide Manager access to the mail files. The minimum permissions that are required depend on which version of Notes is installed on the Enterprise Vault server on which the archiving task runs.
The minimum permissions required to mail files are as follows:
The simplest way to provide the required permissions is to install Notes 8 on each Enterprise Vault server that runs a Domino archiving task. If you do not want to install Notes 8, you may need to change the permissions on all mail files.
We expect that future versions of Enterprise Vault will require Notes 8 on Enterprise Vault servers.
See the section 'Granting the Domino archiving user access to mail files' in Installing and Configuring.
This service pack includes a new version of the EVSVR command-line utility. The main enhancements in this version are as follows:
As well as performing Report and Verify operations with EVSVR, you can now perform the following Repair operations:
You can no longer choose to process a single archive if the operation that you want to perform does not support this level of granularity. The operations that this change affects are as follows:
For more information on these enhancements, see the Utilities manual. The following technical note on the Symantec Enterprise Support site provides additional guidance on when to use EVSVR to identify and resolve various issues:
http://entsupport.symantec.com/docs/326694
The mechanism for the deletion of archived files on FSA placeholder deletion has been improved at SP2. Previously, for NTFS and NetApp file servers, Enterprise Vault always used the archiving policy setting that applied when the placeholder was created. Now the mechanism takes into account changes to the archiving policy setting after a placeholder is created, or as a result of moving the placeholder.
For information on how the new mechanism works, see the topic "Deleting archived files on placeholder deletion" in the Setting up File System Archiving manual.
Note: The new mechanism does not currently support the deletion of archived files from mounted disk volumes. [Ref E1673096]
The following improvements have been made to the way that Enterprise Vault archives calendar items, meeting cancellation and response items, task and task request items:
1509 16:54:28.236 [2508] (ArchiveTask) <4124>
EV:M GetCalculatedModifiedDate - calculated date -
31/3/2009 14:32.42 (CalendarEndDate)
You can now use CMT Universal™ 2.7 or later from Binary Tree to migrate Enterprise Vault shortcuts from Domino mail files to Exchange Server.
CMT Universal automatically includes Enterprise Vault properties when it migrates shortcuts.
For more information, see the following technical note:
http://entsupport.symantec.com/docs/294878
Enterprise Vault can now archive from Domino 8.5 mail servers.
Currently there is a limitation in that the mail template that Enterprise Vault uses for Domino 8.5 servers is based on the Domino 8.0 mail template.
You can use Microsoft SQL Server 2008 to manage Enterprise Vault databases from Enterprise Vault 8.0 SP2 onwards.
For the latest information on the supported versions of Microsoft SQL Server 2008, see the Enterprise Vault Compatibility Charts at http://entsupport.symantec.com/docs/276547.
Note: To upgrade Microsoft SQL Server Reporting Services on a computer on which you have configured Enterprise Vault Reporting, you must perform the steps described in the following Enterprise Vault technical note: http://entsupport.symantec.com/docs/326830.
Previously, the documentation for Enterprise Vault Reporting was split among several books:
Now, all of the documentation for Enterprise Vault Reporting is located in a new book, the Reporting guide. The guide provides comprehensive and updated information on how to deploy and use Enterprise Vault Reporting, with or without FSA Reporting. The introductory chapter includes a new overview of how Enterprise Vault Reporting and FSA Reporting work.
As part of a detailed review of Enterprise Vault OWA documentation by Symantec Enterprise Support engineers, information on installing Enterprise Vault OWA Extensions in Setting up Exchange Server Archiving has been expanded and reorganized. In addition to these improvements, OWA troubleshooting information has been consolidated and published in a new OWA Troubleshooting document, which is available at the following address on the Symantec Enterprise Support site:
http://entsupport.symantec.com/docs/321591
This new document includes information on the following topics:
In order to obtain the changes described in this section the Enterprise Vault 8.0 SP2 Outlook Add-ins must be installed.
In environments where administrators have not completed the configuration that enables Enterprise Vault extensions for users of RPC over HTTP, a new dialog box warns end users that Enterprise Vault user extensions are not available to them.
For more information about configuration for RPC over HTTP, see the section Desktop policy advanced settings in the Administrator's Guide.
Under certain circumstances, Vault Cache users experienced an Outlook memory leak.
This has been fixed.
If a public folder that was listed under Favorites in Outlook contained archived items, the folder entry under Favorites could not be deleted.
This has been fixed.
When Enterprise Vault was configured to expire items based on their modified dates, the client expiry report could show a negative number of days until expiry for some unsent items. This happened even though the actual expiry of items was working correctly.
This has been fixed.
Under some circumstances, Outlook Add-Ins did not detect that the Enterprise Vault server was not available, and some functionality failed unexpectedly.
This has been fixed.
In an environment with CAS proxying configured, OWA 2007 users could not open items in archive search or Archive Explorer if the advanced Exchange Desktop policy setting, View mode, was set to OWA.
This has been fixed.
Enterprise Vault 8.0 SP2 supports Microsoft hotfix KB963664 for Exchange Server 2003, and OWA control file version 6.5.7655.4.
The title of Microsoft article KB963664 is: Error message when you click the flag icon of a message in the message list view in Outlook Web Access 2003 when you are using Internet Explorer 8: "'firstchild.firstchild' is null or not an object".
The Enterprise Vault extensions for Lotus Notes have been updated so that the Enterprise Vault Delete command is available to users who are working in an offline replica. The Enterprise Vault Domino Gateway must be available for the deletion to succeed.
If you initiated a search of the online Help for the Enterprise Vault extensions to Domino Web Access, a prompt to type your password would appear repeatedly. Despite submitting the password, you were unable to search the online Help.
This has been fixed.
The following error message may have appeared when you tried to restore certain items to a Domino mailbox:
Notes error: %s element must contain a value
This has been fixed.
If the name of an archived file included the % (percent) character, you could not restore the file from Archive Explorer. The restore operation failed with an error message including the following reason:
An error has occurred. Cannot complete the operation.
This has been fixed.
You could not open Archive Explorer from Outlook Web Access if, when logging on, you submitted a password that contained one or more accented characters, such as ä or ó.
This has been fixed.
After you ran the ResetEVClient utility to reset the Enterprise Vault Outlook Add-In, the Close button in Archive Explorer stopped working.
This has been fixed.
In previous releases, the following default policies were created automatically by Enterprise Vault for Exchange Server archiving:
You could edit the settings in these policies, but you could not assign another policy as default, or delete the default policy.
In Enterprise Vault 8.0 SP2 you can set a different policy as the default, and then, if required, delete the policy created by Enterprise Vault. This new functionality is currently only available for Exchange policies.
To set a new default policy:
Remember to stop and restart each task that uses the default policy for the changes to take effect. If you change the default Exchange Mailbox or Exchange Desktop policy, the new settings will be applied to user mailboxes on the next synchronization run of the Exchange Mailbox task. If you want to apply the changes before the next synchronization, run Synchronize, which is on the Synchronization tab of the Exchange Mailbox task's properties.
A new setting on the Advanced tab of the Exchange Policy Properties dialog box allows you to archive users' draft items. This applies to all draft items, not just those in users' Drafts folders.
When you enable this feature, all draft items that qualify under the archiving policy are archived but are not converted to shortcuts. Archived draft items are treated as shortcuts for purposes of shortcut deletion.
Under some circumstances, Exchange journaling repeatedly wrote the following errors to the event log:
Event ID: 2776 An exception occurred in routine CExchangeArchivableItem::GetSenderRecipientInfoV2 Event ID: 2776 An exception occurred in routine CExchangeArchivableItem::BuildAuthorInformation()
This has been fixed.
When an Exchange user is enabled for archiving, the retention category defined in the relevant provisioning group is applied to the user’s mailbox. If the retention category in the provisioning group is changed subsequently, the new provisioning group is synchronized to the user's mailbox. However, if the administrator also cleared the Overall lock option on the Archiving Actions tab of the mailbox archiving policy properties, the user's mail was archived under the original retention category, rather than the one subsequently set.
This has been fixed. Now, when the Overall lock option is cleared, the retention category defined in the provisioning group is used, except when the user has changed the retention category from the default.
During Exchange Server archiving, if the archiving task failed to find a user in the Active Directory, at the location recorded in the Enterprise Vault directory, a series of one error and two warnings was written to the event log. The warnings stated:
An error occurred whilst reading the message store quotas for the mailbox /O=Enterprise/OU=Sales/cn=Recipients/cn=John_Doe
This has been fixed. Under these circumstances, Enterprise Vault now writes just one event like the following example:
Cannot process a mailbox until the mailbox has been re-provisioned. The following user object was not found in Active Directory, it may be that the user object has been moved or deleted. AD Object: CN=John Doe, OU=Users, DC=Symantec,DC=COM Legacy DN: /O=First Organization/ou=Exchange Administrative Group/cn=Recipients/cn=John_Doe
Vault cache synchronization did not complete when connecting to Enterprise Vault hosted on servers with United States regional settings.
This has been fixed.
There was a memory leak in Exchange shortcut processing which became apparent at very high volumes.
This has been fixed.
If the Exchange mailbox policy was set to archive based on Age and Quota, but the Exchange mailbox had no quota set, Enterprise Vault archived everything in the mailbox other than those items younger than the Never archive items younger than value.
This has been fixed.
When printing Outlook calendars, users who had large numbers of calendar items and who were not running Outlook in Cached Exchange Mode found there was a long delay, sometimes a matter of minutes, before the print dialog box appeared.
This has been fixed.
Quota based archiving logged spurious events, warning that there were insufficient archivable messages to bring mailboxes within quota when this was not actually the case. For example:
Type: Warning Date: 20/03/2009 Time: 16:02:40 Event: 3379 Source: Enterprise Vault Category: Archive Task User: N/A Computer: E03EA01-UKDY Description: There were too few archivable items available to take mailbox '/o=EXCHANGE/ou=Exch01/cn=Recipients/cn=JohnDoe' below the quota-free level of 50. Quota limit: 150000KB Quota used: 104246KB (69 of quota limit) Previously archived (pending): 0KB Required to archive: 29245KB (adjusted 29245KB) Amount archived (this run): 12KB You may need to review your mailbox archiving policies to allow more items to be archived if you regularly see this warning for mailboxes. For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp
This has been fixed. These events are now logged only when it is true.
The desktop policy can be configured such that, when users delete items from public folders, they are given the choice to delete just the shortcuts, or to delete both the shortcuts and the archived items.
When users chose to delete just the shortcuts, the shortcuts were not deleted and remained in the folder.
This has been fixed.
With the desktop policy Shortcut Deletion option set to Ask User, under some circumstances, users who deleted a very large number of items, and who chose to delete the archived items and the shortcuts, found that some of the selected items were not deleted, and remained in the folder.
This has been fixed.
When a user moves an archived item from one folder to another, certain item attributes such as location and retention category can be updated. If an error occurs during this update, or if the update is not allowed, event ID 3378 is written to the event log. For example, if an item is moved from a folder whose retention category prevents the deletion of items, the retention category from the target folder cannot be applied to this item unless it also prevents deletion.
In some cases, event ID 3378 is logged in very large quantities. You can use the new HideMovedItemUpdateFailure DWORD registry value to suppress the logging of these events. Set HideMovedItemUpdateFailure to 1 to suppress logging of event ID 3378. If HideMovedItemUpdateFailure is not present, or is set to its default value of 0, these events are logged.
HideMovedItemUpdateFailure is in:
HKEY_LOCAL_MACHINE \SOFTWARE \KVS \Enterprise Vault \Agents
Under some circumstances, users whose SMTP address contains an apostrophe could not retrieve archived items via Outlook Web Access (OWA). The server returned HTTP status code 500 (internal server error).
This has been fixed.
Enterprise Vault should prevent users from using the Delete from Vault button to delete items in a pending state (items due to be archived). However, in some cases, users were able to delete pending items.
This has been fixed, Enterprise Vault now prevents the deletion of pending items.
When a mailbox had an Entire Mailbox managed folder policy in Exchange, the following issues occurred:
These issues have been fixed.
This issue occurred when all the following conditions applied:
Contrary to the archiving policy, shortcuts were created for items that were archived from managed folders.
This has been fixed.
This issue occurred when both the following conditions applied:
In this case, some items were archived even though they were not eligible for archiving based on their age.
This has been fixed.
This issue occurred after you used Enterprise Vault Policy Manager (EVPM) to set a retention category for a mailbox folder. Enterprise Vault did not apply that retention category to items that were archived by a scheduled archiving run, or by an archiving run started with Run Now.
The issue did not affect manual archiving, which applied the correct retention category.
This has been fixed.
Preemptive caching is the process where the Enterprise Vault Outlook Add-In copies items from the user's Outlook .OST file to the vault cache before the items are due to be archived. In time zones that are in advance of Greenwich Mean Time (GMT) (that is, to the east of GMT), preemptive caching ran too frequently at some times of day. In time zones that are behind GMT (that is, to the west of GMT), preemptive caching ran too infrequently at some times of day.
This has been fixed.
Under some circumstances, Enterprise Vault set the PR_CONTAINER_CLASS property on the Inbox and Sent Items folders. This prevented these folders from being processed by some versions of the Exchange Mailbox Manager.
This has been fixed. Enterprise Vault no longer sets this property.
PST Migrations can be configured to place shortcuts to migrated content in a folder in each user's inbox. For users who have more than one PST file administrators can choose to create a separate sub-folder for each PST file, rather than to merge all the shortcuts. For example, the migration might be configured to place shortcuts in sub-folders of a folder called PST Migrations. A user with three PST files whose display names are January, February and March, would find three sub-folders with these names beneath PST Migrations.
The following issue applied to wizard-driven PST migrations and those scripted with Enterprise Vault Policy Manager (EVPM). If an interruption occurred under this configuration, on restart users found that PST contents had been split between two sub-folders of PST Migrations. For example, if the migration of PST file January was interrupted and restarted, folders called January and January 2 would have been created.
This has been fixed.
A memory leak occurred during PST location. After the location of very large numbers, the automatic matching of PSTs to archives began to fail.
This has been fixed.
Double-byte characters in the name of a PST file caused client-side PST migration to fail. The following example shows an error written to the Enterprise Vault server's event log:
Event Type: Error Event Source: Enterprise Vault Event Category: Directory Service Event ID: 8567 Date: 09/04/2009 Time: 18:09:41 User: N/A Computer: EV1 Description: Error occurred with client-driven migration of PST '\\CLIENT\C$\Documents and Settings\n2\Desktop\é-é+é¦.pst'. PST record not found. Reference: 'HasPstChunkMigrated'. For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp
This has been fixed.
The PST locator task has been enhanced, and now validates PST files to ensure they are Microsoft personal store files before they are added to the list of files to be migrated.
Note: The PST locator task cannot validate files that are exclusively locked by another program, and these files are still added to the list of files to be migrated.
If multiple Domino Servers were listed for your configuration in the Getting Started Wizard, the wizard aborted if one of the listed Domino Servers was not running.
This has been fixed.
Domino vault cache did not automatically download items when it was reconfigured for automatic download, after initially being configured for manual download.
This has been fixed.
The Domino Mailbox Archiving task could not archive a message if the email addresses of its sender or recipients contained one or more non-standard characters, such as the vertical bar character ( | ). When this problem arose, the following error message would appear in the event log:
Event Type: Error Event Source: Enterprise Vault Event Category: Lotus Domino Journaling Task Event ID: 41206 ... Description: There was an error processing an item in a database. The task will process the item again on the next archiving run.
This has been fixed.
If the Domino mailbox archiving policy was configured to create a customized shortcut body, the shortcuts created could contain more than the number of characters set in Message characters to include. The shortcut actually contained the configured number of characters from every body field in messages with multiple body fields, not just from the first body field.
This has been fixed.
This issue occurred when the following conditions applied:
When you tried to open the Enterprise Vault mail templates, or a user tried to retrieve an archived item, the following error was returned:
Error loading USE or USELSX module: CSUIViewClass
This has been fixed.
The Domino Mailbox Archiving task was unable to archive an item to which the Domino mail server had assigned an invalid creation date. When this issue arose, the following error would be reported in the event log:
Type: Error Event: 41164 Source: Enterprise Vault Category: Lotus Domino Mailbox Archiving Task Description: There was an error processing an item in a mailbox. The task has previously failed to process this item on several occasions. This item will not be processed again. Task: Domino Mailbox Archiving Task ... Error: Not a legal OleAut date.
This has been fixed.
If the Domino group was an 'ACL only' group, the permissions set on the mail database were not inherited by the archive when the Domino Provisioning Task was run.
This has been fixed.
Enterprise Vault Policy Manager (EVPM) now supports the following four new keynames in the initialization file, all of which relate to scripted NSF migrations:
IgnoreInsufficientMailFileAccess |
By default, EVPM does not process an NSF file if the Domino archiving user does not have sufficient access set the ACL of the corresponding mail file. Set this keyname to True to override this default behavior. |
IgnoreNoManagerAccess |
By default, EVPM does not process an NSF file if the Domino archiving user does not have manager access set in the ACL of the corresponding mail file. Set this keyname to True to override this default behavior. |
IgnoreNonExistentMailFile |
By default, EVPM does not migrate the contents of NSF files whose associated mail file is not available. Set this keyname to True to override this default behavior. |
IgnoreNonStandardTemplate |
By default, EVPM does not process an NSF file that is based on a non-standard template. The list of standard templates is determined by a registry string value which is called HKEY_LOCAL_MACHINE \SOFTWARE \KVS \Enterprise Vault \Agents Set this keyname to |
All these keynames are available for use in the [NSFDefaults] and [NSF] sections of the EVPM initialization file, all are optional, and all can be set to False (default) or True.
NSF migrations scripted using Enterprise Vault Policy Manager (EVPM) failed
if the Storage service was not running on the directory server specified in the Directory section of the initialization file.
This has been fixed. You can use the new StorageSvcComputerName keyname in the Directory section of the initialization file to specify the server that runs the
Storage service. However, this keyname is optional. If you do not set a value for this keyname, EVPM connects to any Enterprise Vault server that runs a
Storage service and has the Lotus Notes client installed.
When run in process mode, EVPM ignored DoNotProcess when it was set to True.
This has been fixed.
Under certain circumstances, Enterprise Vault Policy Manager (EVPM) reported that an invalid MailFileCN value was specified in the initialization file, even though the canonical name (CN) was valid.
This has been fixed, and the EVPM MailFileCN keyname has been changed to UserCN.
During scripted NSF migration using Enterprise Vault Policy Manager (EVPM), the migration run proceeded even if the initialization file contained invalid keynames or attributes.
This behavior has been changed. When EVPM finds an invalid line in the initialization file, it still writes an error to the command prompt, but now terminates the migration run.
Some storage devices that were certified for use with Enterprise Vault 2007 have not yet been certified for Enterprise Vault 8.0.
Before you create a partition on a new device, check the Compatibility Charts for details of the supported devices:
http://entsupport.symantec.com/docs/276547
If your storage device is not certified, contact Symantec support.
Default shortcuts in Exchange Server and Domino Server mailboxes now include the first 1,000 characters of the message body.
You can configure how much of the message body to include in shortcuts using the settings Content of shortcut body and Message characters to include on the Shortcut Content tab in Exchange Mailbox or Domino Mailbox policies. Previously, the default value for Content of shortcut body was None. This has been changed to Customize and the default value of Message characters to include is now 1000.
When the Enterprise Vault administration console runs on a computer with no Internet connection, it repeatedly pauses while trying to check digital certificates.
To fix this problem, install Microsoft .NET Framework 2.0 SP1, or apply Microsoft hotfix KB936707 to .NET Framework 2.0. See the following Microsoft article for more information: http://support.microsoft.com/kb/936707.
If you do not want to upgrade or patch .NET Framework, you can turn off the Internet Explorer setting Check for publisher's certificate revocation for every account that runs an Enterprise Vault service. For more information, see the section called Issues when an Enterprise Vault server has no Internet connection in the Installing and Configuring guide.
In the previous release, certificate revocation checking caused significant delays in the Administration Console if the Enterprise Vault server did not have an Internet connection; Enterprise Vault processes were slow to start because of the timeout while waiting for an Internet connection. You could work around this issue by turning off certificate revocation checking for each account that ran an Enterprise Vault service.
This has now been fixed. You no longer need to turn off certificate revocation checking.
Under some circumstances, PST files created using the Administration Console's Export archives to PST files feature produced unexpected results. When the file's contents were imported into a user's Inbox, there were duplicate items, items were missing, and the folder structure did not match that in the archive.
This has been fixed.
In the Administration Console on Chinese and Japanese systems it was not possible to open the data analysis reports or operation reports from Common Tasks.
This has been fixed.
During start-up, if the Storage service failed to verify a partition network share, a series of events was written to the event log, and the Storage service failed to start. Although the initial error indicated that the verification of a partition network share had failed, the following warning gave no indication of the share that failed verification. For example:
Event Type: Warning Event Source: Enterprise Vault Event Category: Storage Server Event ID: 2 Date: 23/06/2009 Time: 11:37:35 User: N/A Computer: XXXSRV1 Description: The description for Event ID ( 2 ) in Source ( Enterprise Vault ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: .
This has been fixed. Now, an initial error provides details of the partition that failed verification. For example:
Event Type: Error Event Source: Enterprise Vault Event Category: Storage Management Event ID: 7169 Date: 23/06/2009 Time: 11:43:06 User: N/A Computer: XXXSRV1 Description: There was an error verifying a Partition Network Share. Error: The system cannot find the file specified. [0x80070002] Details of the last partition that was processed: VaultStore: VS0001 Partition: VS0001 Ptn1 Partition Root Path: H:\Enterprise Vault Stores\VS0001 Ptn1 Secondary Storage Location: none For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp
This issue occurred when you restored an archived item and then archived it again from the same folder with a different retention category. A new shortcut was created, but the re-archived item still had the original retention category.
This has been fixed.
CPU usage by SQL Server was unusually high, and SQL deadlock error messages similar to the following were reported in the event log:
Type: Error
Date: 12/04/2009
Time: 03:32:08
Event: 6796
Source: Enterprise Vault
Category: Storage Online
User: N/A
Computer: server1
Description:
A COM exception has been raised.
The SQL database server detected a deadlock while accessing the
Vault Database ''
Description: Additional Microsoft supplied information:
Source: Number: SQL State: Native Error: HRESULT
SQL Command: [0xc0043433]
Internal reference
.\VaultStoreDB.cpp (CVaultStoreDB::UpdateItemsMetadata) [lines
{12041,12048,12050,12052,12054,12056,12058}] built Mar 15 20:10:09 2009
An exception is raised when a process encounters an unexpected fault.
This has been fixed.
Messages similar to the following were reported in the event log when archiving attachment types for the first time:
Type: Error
Date: 13/04/2009
Time: 00:50:03
Event: 13360
Source: Enterprise Vault
Category: Directory Service
User: N/A
Computer: server1
Description:
An error was detected while accessing the Vault Database
'EnterpriseVaultDirectory' (Internal reference: .\ADODataAccess.cpp
(CADODataAccess::ExecuteSQLCommand) [lines {1379,1381,1396,1414}] built Mar 15 19:19:01 2009):
Description:
Cannot insert duplicate key row in object 'dbo.FileSpecification' with unique
index 'IX_FileSpecification'.
SQL Command:
[dbo].[uspsi_FileSpecification]
This has been fixed.
If no default email client was specified in Internet Explorer on the Enterprise Vault server, then the Storage service failed to start after an upgrade.
This has been fixed.
If multiple CIFS partitions were sharing data within a single vault store, Enterprise Vault could incorrectly log instances of warning event 7110 (An invalid SIS part was encountered while doing watch file scan) when data was backed up. An issue specific to locating shared large file SIS parts whose parent savesets had been collected caused Enterprise Vault to look for the files in the wrong place when it checked to verify their existence.
This has been fixed.
Enterprise Vault now supports the Data Domain Network Attached Storage device in WORM mode.
The IndexCheck command-line utility now provides additional facilities with which you can rebuild multiple invalid indexes simultaneously. In outline, the procedure for doing this is as follows:
Run this command to generate a comma-separated value (.csv)
file that lists the invalid indexes:
IndexCheck -f index_folder -c exist -csv filename
Run this command to rebuild the invalid indexes:
IndexCheck -rebuild filename
When attempting to uninstall the FSA Agent from an Enterprise Vault server computer, the following message was displayed:
In order to uninstall Enterprise Vault FSA Agents you must uninstall Enterprise Vault. You may prefer to disable the Enterprise Vault File Placeholder Service instead.
This has been fixed. You can now uninstall the FSA Agent from Enterprise Vault server computers without having to uninstall Enterprise Vault.
In some rare circumstances, attempting to restore files from placeholder shortcuts could cause a file server or cluster nodes to stop responding.
This has been fixed.
Data loss can occur if you use the EMC Celerra pass-through recall facility in combination with Enterprise Vault's archiving policy setting "Delete archived file when placeholder is deleted". A new warning dialog in the Administration Console reminds the administrator to avoid this combination.
Enterprise Vault displays the warning dialog when you configure a Celerra target volume or target folder, if the applied or inherited archiving policy specifies "Delete archived file when placeholder is deleted".
Enterprise VaultTemp folder [Ref 802081, E1543518]On file servers where the FSA Agent was installed, the folder Enterprise VaultTemp was erroneously created in the FSA Agent installation folder when the File Blocking Service started.
This has been fixed.
When using Placeholder shortcuts, any alternate data stream (ADS) associated with a file was lost if you took either of the following actions:
This has been fixed.
Over time the amount of virtual memory consumed by the FSA Archiving task gradually increased. As the virtual memory exceeded the system limit for a process, intermittent Out of system memory messages were reported in the event log during archiving.
Several sources of memory leaks in the FSA Archiving task code have now been fixed.
FSA did not delete files in the TEMP folder that were created during archiving.
This has been fixed.
It was not possible to add a volume from a NetApp Filer as an archiving target if the root volume's security type was set to UNIX. The administration console reported the following error:
Could not detect the Data ONTAP version of the file server
This has been fixed.
If the File System Archiving task was unable to complete the processing of a target file system during a scheduled archiving run, it stopped without attempting to process any other targets that were scheduled for archiving.
This has been fixed. If the File System Archiving task now encounters a problem when archiving a particular target, it will continue to process any other scheduled targets.
The following improvements have been made to FSA Reporting bulkload operations:
A program fault has raised an exception. Exception: Error opening the data file. Diagnostic: HRESULT: 80046000 Type: System.Runtime.InteropServices.COMException Reference: FSAReportingWebService - BulkLoad operation failed Command Line: d:\windows\system32\inetsrv\w3wp.exe -a \\.\pipe\iisipma84d0087- 074e-4a31-a97c-d8b9f87b6864 -t 20 -ap "EnterpriseVaultFSAReporting" Application Domain: /LM/W3SVC/1/Root/FSAReporting-1-128825344870051121 Process Id: 4292 Thread Id: 7892 Stack Trace: at SQLXMLBULKLOADLib.SQLXMLBulkLoadClass.Execute(String bstrSchemaFile, Object vDataFile) at KVS.EnterpriseVault.FSAReportingServerWebService.ThreadContainer.LoadData ()This has been fixed.
A program fault has raised an exception. Exception: Equal expected. or Quote expected. Diagnostic: HRESULT: c00cee25 Type: System.Runtime.InteropServices.COMException Reference: FSAReportingWebService - BulkLoad operation failed Command Line: d:\windows\system32\inetsrv\w3wp.exe -a \\.\pipe\iisipm7e2db005-6e89-4818-a046-0a556a7ef4fc -t 20 -ap "EnterpriseVaultFSAReporting" Application Domain: /LM/W3SVC/1/Root/FSAReporting-1-128832548792749796 Process Id: 4264 Thread Id: 2820 Stack Trace: at SQLXMLBULKLOADLib.SQLXMLBulkLoadClass.Execute(String bstrSchemaFile, Object vDataFile) at KVS.EnterpriseVault.FSAReportingServerWebService.ThreadContainer.LoadData()Improvements have now been made to the way Enterprise Vault handles these data transfers.
FSA Reporting creates temporary data files on a file server during a scan of the file server. If these files became very large, the drive that contains the files was at risk of becoming full.
Enterprise Vault now regularly monitors the free space on the appropriate drive. If the free space falls below a value of 100 MB by default, Enterprise Vault stops the FSAReportingService process and generates the following message in the event log:
The FSAReportingService process will be shut down because there is
insufficient disk space on drive <drive>.
Delete any unwanted files from the drive and then restart the process as
follows. On file servers on which the FSA Agent is installed, restart the
Enterprise Vault File Collector service. Otherwise, restart the Enterprise Vault
Admin Service on the Enterprise Vault server.
Note that by default FSA Reporting stores the temporary files on the file
server in the FSAReports subfolder of the Enterprise Vault installation folder.
This location is typically on a drive that has limited space. If there is likely to
be insufficient space for the temporary files on the installation drive, we recommend that
you relocate the storage location to an existing path on a drive
that has sufficient free space.
To relocate the storage location for the temporary files, edit the TempFilePath registry value under the following registry key:
HKEY_LOCAL_MACHINE
\SOFTWARE
\KVS
\Enterprise Vault
\FSA
\Reporting
For NTFS file servers, the registry value is located on the file server. For NetApp and EMC Celerra file servers, the registry value is located on the Enterprise Vault server.
Enterprise Vault creates a subfolder named FSAReports on the file server under the path that TempFilePath defines, in which to hold the temporary
files.
After FSA Reporting has scanned a target volume it sends the data file from the file server to a temporary folder on the Enterprise Vault server. The FSA Reporting Web service then uploads the data file from the Enterprise Vault server to the FSA Reporting database. If the database upload fails, FSA Reporting resends the data file to the Enterprise Vault server, and the FSA Reporting Web service attempts to upload the resent file. If the database upload continues to fail, FSA Reporting repeats the resend and upload process up to ten times.
Previously, FSA Reporting deleted the data file from the Enterprise Vault server only if the upload to the FSA Reporting database succeeded. If an upload failed, multiple data files could accumulate on the Enterprise Vault server, which increased the size of the temporary folder significantly.
Enterprise Vault now deletes a data file after the upload to the FSA Reporting database, irrespective of whether the upload succeeds.
On a Windows Server 2008 64-bit file server, if you added an FSA target volume or target folder with FSA Reporting configured, the FSA Reporting scan could fail to start. In this case an error that began "Faulting application FSAReportingService.exe" appeared in the event log.
This has been fixed.
Debug messages were written to the FSA cluster log file, FSA-MSCSType.log, when the default log level (0) was configured. As a result, the file size increased quickly. This log file is located in the FSA Agent installation folder on the cluster nodes.
This has been fixed. Now the debug and diagnostic messages are only written to the log file when you configure logging level 5 using the registry setting,
HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault\FSA\LogLevel
If the current locale setting was configured to use a character other than period for the decimal point, the following problems occurred:
Failed to save or update details for File Server '<unknown>' in the Directory Service. The EnterpriseVault.DirectoryConnection object reported and error.
This has been fixed.
If you used FSAUtility to move shortcuts, only the latest version of the associated file was moved to the destination archive folder. Any earlier versions of the file remained in the source archive folder.
This has been fixed. Now all versions of the file are moved to the destination archive folder. If you have configured Enterprise Vault to retain items that users have deleted (on the Archive Settings tab of Site Properties), and some deleted versions of the file still exist, these will also be moved, but will appear as undeleted in the destination archive folder.
Error reporting has been enhanced to assist in resolving connection issues between Enterprise Vault servers and target file servers.
If you chose not to use placeholder shortcuts when adding an EMC Celerra device as an archiving target, then the following dialog was displayed when you added a volume:
Failed to check logging state on EMC Celerra Volume.
If you then tried to add a folder to the volume, the following dialog was displayed:
Failure to save or update details for folder ... in the Directory service. Could not mark the folder with File System Archiving information. Access is denied.
This has been fixed.
With SynchroniseFSASharePermissions set to 0, under some circumstances users could not access items in their archives.
This has been fixed.
When a user deleted an item from the archive and then re-archived the original file, the newly archived item was not visible in the archive. This happened if Enterprise Vault was configured to retain deleted items (using the Archive Settings tab of Site Properties), and shortcuts were not created for archived items.
This has been fixed.
When an FSA task archived files from a Celerra device, messages similar to the following were written repeatedly to the Data Mover server_log file:
FMP: 3: cannot find share= FMP: 3: last message repeated 100 times
This has been fixed.
The folder location for checkpoint data is specified on the General tab of the FSA task properties. The default location is .\FSATaskCheckPoint.
When the default location was specified, the FSA task sometimes failed to locate the folder and save the data. This caused multiple FSATaskCheckpoint warning messages to be written to the event log every 60 seconds.
This has been fixed.
Previously, the removal of the FSA Agent from an Enterprise Vault was not supported.
This action is now supported.
When Centera collection ran, performance degraded as the Saveset table in the vault store database grew. You may have noticed some or all of the following symptoms:
In previous releases, this issue could be resolved by manually creating the new index, IX_Collection_Saveset_Partition, for the Saveset table. To check if the index exists:
In this release, Enterprise Vault attempts to create the index automatically, if it does not exist. The space required for this index on the SQL Server hosting the relevant vault store database is approximately 27 bytes per row in the Saveset table. The index is created when the Storage service starts, provided the following conditions are satisfied:
An informational message in the event log will report that the new index has been created.
If there are more than 1,000,000 records in the Saveset table, then the index is not created automatically and the following warning message is reported in the event log:
Type: Warning ... Event: 7162 Source: Enterprise Vault Category: Storage File Watch ... Description: You are recommended to create a new SQL index for this vault store database to improve the performance of processing items in the Centera collection area. Table Name: Saveset Database: vault store database name SQLServer: SQL Server name VaultStoreEntryId: VaultStoreEntryId ...
You can create the index manually, as described in the document, http://entsupport.symantec.com/docs/288036, on the Symantec Enterprise Support site.
You should only create this index for Centera vault store partitions that are enabled for collection. If the open partition is not a Centera partition enabled for collection, creating this index may impact archiving performance on the partition.
Before creating the index ensure that there is available space on the SQL Server.
If the SharePoint archiving task was set to run using an account other than the Vault Service account, the task may not have had access to the storage server or the SQL server. In this case, Enterprise Vault failed to archive items.
This has been fixed. If you select an account other than the Vault Service account for the SharePoint archiving task to run under, the task's archiving process continues to run as the Vault Service account. The other account details are used only when the task communicates with SharePoint.
The normal way to handle authentication for the SharePoint archiving task is as follows:
If you do not want to allow the Vault Service account to be a site collection administrator, you can create a new account that is a site collection administrator and then do either of the following:
When upgrading Enterprise Vault, the following error was reported in the event log if the Operations Manager monitoring agent stopped before it had completed its start-up routine:
Event Type: Error Event Source: Enterprise Vault Event Category: Monitoring Event ID: 40966 Date: ... Time: ... User: N/A Computer: ... Description: A program fault has raised an exception. Exception: Collection was modified; enumeration operation may not execute. Diagnostic: Type: System.InvalidOperationException Reference: Monitor Command Line: "C:\Program Files\Enterprise Vault\EVMonitoring.exe"
This has been fixed.
In Enterprise Vault SP1, it was possible for a user account that did not belong to the Windows Administrators group to be denied access to all the reports on a SQL Server. The problem only occurred with Microsoft SQL Server 2000 Reporting Services. The problem occurred even though the user account was assigned to an appropriate Enterprise Vault administrator role.
This has been fixed.
Enterprise Vault Operations Manager's tables specified the wrong units in the label for "Number of saveset files awaiting backup or replication". The label specified KB instead of number of files.
This has been fixed.
This issue could have occurred, for example, if the archiving schedule was due to start at 9 PM on 18 June Eastern Daylight Time (EDT), which translates to 1 AM on 19 June Coordinated Universal Time (UTC). In this example, the Items Archived per Hour report would not have included items archived after 9 PM on 18 June Eastern Daylight Time (EDT).
This has been fixed. The following document on the Symantec Enterprise Support site, http://entsupport.symantec.com/docs/323103, describes how to work around this issue. This is no longer required.
The following Enterprise Vault Reporting reports now include an additional column, "Total Compressed Size":
The new column shows the total size in gigabytes of the archived items.
If you upgraded from Enterprise Vault 2007, the Single Instance Storage Reduction Summary report generated an execution error when both the following conditions applied:
This has been fixed. When these conditions apply, the report now correctly indicates that there is no data to display.
The Archive Points Space Usage Summary report's "Total Size" column and "Archived Files" column could show the wrong values if the "Archived Files" value for an archive point exceeded 4 GB.
This has been fixed.
When Windows Search indexed the items in a vault cache on a Windows Vista computer, it did not index many of the properties of Calendar, Contact, Note, and Task items. For example, Windows Search did not index the Start date, End date, and Is recurring properties of archived Calendar items.
This has been fixed. The table below lists the properties that Windows Search now indexes.
| Calendar properties | Contact properties | Note properties | Task properties |
|---|---|---|---|
| End date Free/busy status Is recurring Location Name Optional attendee addresses Optional attendees Required attendee addresses Required attendees Start date Type |
Assistant's name Assistant's phone Cell phone Company Company main phone Department E-mail address E-mail display name File as Home phone IM addresses Name Office location Profession Title Type |
Color Name Type |
Due date Is completed Is recurring Name Start date Task owner Type |
This issue affected both Exchange Server archiving and Domino Server archiving. If tens of thousands of users were already enabled for archiving, there was a delay when you ran the Enable Mailbox wizard. The delay occurred after you clicked Next on the wizard page where you select the server on which the mailboxes are located.
This has been fixed.
This update applies to both Exchange Browser Search and Domino Browser Search.
You can use new settings in the Web Access application initialization file WebApp.ini to prevent users from restoring or deleting archived items from Browser Search results. By default, the restore and delete actions are available to users.
The new settings are as follows:
| Setting | Description | Values |
|---|---|---|
| BSRestoreButton | Controls whether Browser Search displays options that are related to restoring archived items. |
0. The options that are related to restoring archived items are not displayed. 1 (default). The options that are related to restoring archived items are displayed. |
| BSDeleteButton | Controls whether Browser Search displays options that are related to deleting archived items. |
0. The options that are related to deleting archived items are not displayed. 1 (default). The options that are related to deleting archived items are displayed. |
Sometimes operations that access archives using the Enterprise Vault Web application failed to complete after the Exchange Mailbox task had processed shortcuts. Operations could include integrated, browser or Archive Explorer searches and Vault Cache synchronization.
This has been fixed.
Mail items with a date stamp of midnight on December 30, 1899 were not archived by the archiving or journaling tasks. This date stamp is represented internally by a value of 0 which Enterprise Vault treated as invalid.
The following error was written to the event log:
Event ID 6881: Unable to complete archive request. The parameter is incorrect.
Exchange and Domino permit this date stamp, and Enterprise Vault now archives these items.
Note: The prevailing retention category may immediately expire such items. If you do not want these items to expire, ensure your retention categories are configured such that they are not expired. You must also ensure your backup regime protects you from unexpected loss of these items.
An error would occur when you used the Enterprise Vault Content Management API to extract an archived Lotus Domino item that did not have a subject line.
This has been fixed.
The drop-down menu on the Storage Device page of the New Partition wizard now includes the storage type Sun Storage 7000 Unified Open Storage System.
For the latest information on supported storage devices, see the Enterprise Vault Compatibility Charts (http://entsupport.symantec.com/docs/276547).
When users of the Enterprise Vault Deployment Scanner selected the Gather information about your environment ... option, it did not collect the reports from the Reports sub-directory beneath the Enterprise Vault program folder (normally C:\Program Files\Enterprise Vault).
This has been fixed.
If the Microsoft Management Console (MMC) was running while upgrading Enterprise Vault, the Event Viewer was not upgraded until it was restarted.
This has been fixed.
On extremely slow systems, an EvAzUtil error could occur during upgrades to Enterprise Vault 8.0 from Enterprise Vault 2007, including all service packs.
The following error was written to the event log:
Event ID: 8591 Category: Directory Service Description: Error launching EvAzUtil utility in order to upgrade the roles- based administrator database. Error code: 'Success [0]'
This has been fixed.
Enterprise Vault Integrated Search from Outlook 2007 did not set the initial focus to the Look for box.
This has been fixed.
In environments where network connectivity was unreliable, Enterprise Vault could log too many instances of the following events:
This has been fixed. Enterprise Vault logs an instance of each event once after every ten minutes of continuous unreliable network connectivity.
In earlier versions of Enterprise Vault, before you upgraded the Outlook Add-In to a different type, you had to uninstall the existing Outlook Add-In. For example, you had to uninstall the existing Outlook Add-In before you upgraded from the HTTP-only Outlook Add-In to the Outlook Add-In.
With Service Pack 2, you can upgrade to a different type of Outlook Add-In without uninstalling the existing one.
Enterprise Vault did not remove messages from the Restore Spool Admin queue. The result was that for each message on the queue, a large number of warnings with event ID 6419 (MSMQ negative acknowledgment message(s) have been handled) were added to the event log.
This has been fixed. Enterprise Vault generates one warning for each message on the queue, and deletes the message from the queue.
On SQL Server 2005 systems where the vault service account was not granted the VIEW SERVER STATE permission, frequent errors with ID 13360 were written to the event log.
The Enterprise Vault Deployment Scanner now checks that the vault service account has this permission. On existing installations, you must ensure the vault service account is granted the VIEW SERVER STATE permission. Previously only the dbcreator permission was required.
The new features section includes information about new and improved documentation provided with Enterprise Vault 8.0 SP2.
The upgrade instructions are no longer provided in HTML format. They are now provided in both .CHM and .PDF formats, as follows:
Symantec Enterprise Vault 8.0 SP2\Upgrade_Instructions.pdf
Symantec Enterprise Vault 8.0 SP2\Upgrade_Instructions.chm
C:\Program Files\Enterprise Vault\Upgrade_Instructions.pdf
C:\Program Files\Enterprise Vault\Upgrade_Instructions.chm
Copyright © 2009 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, VERITAS, and Enterprise Vault 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 contains 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 Enterprise Vault 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 Enterprise Vault
350 Ellis Street
Mountain View, CA 94043