Last updated: 26-Mar-2012

Enterprise Vault™ 9.0.3

To download the latest version of this document and the other Enterprise Vault release notes, and to obtain Japanese and Chinese versions of these documents, see: http://www.symantec.com/docs/TECH147782.

For the latest news about this release, including any hotfixes, subscribe to http://www.symantec.com/docs/TECH147783.

This document describes the changes introduced in Enterprise Vault 9.0.3 (service pack 3 for Enterprise Vault 9.0).

Before installing or upgrading to Enterprise Vault 9.0.3, you must read this document and also the ReadMeFirst for Enterprise Vault 9.0. The ReadMeFirst lists current known issues and describes new features in the original release of Enterprise Vault 9.0.

Note: If you upgrade from Enterprise Vault 9.0.3 to the Enterprise Vault 10.0 original release, some issues that have been fixed in 9.0.3 may still be present in 10.0, which was released earlier. These issues will be fixed in Enterprise Vault 10.0.1. Features and fixes in 9.0.3 that were also included in Enterprise Vault 10.0 are marked as [10] in this document, for example: Improved synchronization performance [Ref 9039823, E2250441] [10].

For changes introduced to Enterprise Vault 9.0 by earlier service packs, see the Previous Updates document.

For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.

Contents

New features

Enterprise Vault 9.0.3 provides the following new features:

FIPS 140-2 compliance

Federal Information Processing Standards (FIPS) 140-2 is a standard for cryptographic modules in computer systems.

Enterprise Vault 9.0 archiving, Compliance Accelerator, and Discovery Accelerator are FIPS 140-2-compliant from Enterprise Vault 9.0.3 onwards.

Note that the term "FIPS 140-2-compliant" is not a defined FIPS term. Where the Enterprise Vault documentation states that a version of Enterprise Vault is FIPS 140-2-compliant, it means that:

For more information about Enterprise Vault and compliance with the FIPS 140-2 standard, and about using Enterprise Vault in a FIPS 140-2-compliant environment, see the following article on the Symantec Support Web site:

http://www.symantec.com/docs/DOC4820.

Enterprise Vault 9.0.3 supports IPv6

Enterprise Vault 9.0.3 introduces support for IPv6. Note the following restrictions:

Backtrace provides improved tracing

The new Backtrace utility enables you to obtain log files of tracing information from Enterprise Vault processes in which the logging starts before a problem occurs. Unlike a DTrace utility log file, a Backtrace log contains tracing information from a single process.

You can control which events trigger Backtrace to create log files. You specify the events that trigger Backtrace or the events that never trigger Backtrace.

See the 'Backtrace' section in the Utilities manual.

Domino 8.5.2 now supported [Ref 9039320, 9039287] [10]

Enterprise Vault provides the following support for Domino Server 8.5.2 and Lotus Notes 8.5.2 clients:

Changes to account permissions for Exchange Server tasks [Ref 9039490, E2389896]

When you change an Exchange Server task so that it does not use the Vault Service account to log on to Exchange Server, Enterprise Vault now automatically grants the new accounts the permissions that it requires to run the task.

If you modify the Exchange Server tasks so that a particular account is no longer used to run Exchange Server tasks, Enterprise Vault automatically removes the permissions that were required to run the Exchange Server tasks.

Enterprise Vault changes account permissions automatically when you change the logon account for the following tasks:

When you change the logon account for a task to an account other than the Vault Service account, Enterprise Vault does the following:

If you use Enterprise Vault roles-based administration there is also a new 'Task Application' role that Enterprise Vault applies to accounts that run Exchange Server archiving tasks. The Task Application role provides the permissions that are required to run Enterprise Vault Exchange Server tasks.

When you upgrade to Enterprise Vault 9.0.3, Enterprise Vault automatically adds the new Task Application role to existing accounts that run Exchange Server tasks.

Setup.exe may be required for manual installation of an Outlook Add-In [Ref 90310123, 90310672]

In Enterprise Vault 9.0.3 and later, end users who install an Outlook Add-In manually may require a setup.exe file as well as an MSI file.

In some cases, users can launch the Enterprise Vault Outlook Add-In MSI package directly. But for Windows Vista/7 users who have Windows User Account Control (UAC) turned on, you also need to provide a setup.exe file. The users must run setup.exe to launch the MSI. The setup.exe files that you may need are included on the Enterprise Vault media, in the same folders as the MSI files.

For more information, see the section on setting up manual installation of an Outlook Add-In in Setting up Exchange Server Archiving.

Updated content converters [Ref 90310156, E2496115]

This release includes Outside In® Technology version 8.3.7 content converters from Oracle® Corporation.

New DTrace scripts [Ref 9038667, E2282855]

There are new DTrace scripts that enable you to trace issues with the following:

The new DTrace scripts are available from within the Administration Console.

NetApp filer ~snapshot folders are now excluded from FSA Reporting scans by default [Ref 9037804, E2252677] [10]

By default FSA Reporting now excludes any folder named ~snapshot from its scans of NetApp filer volumes. It is usually undesirable to include the data from these folders in the reports because the data does not reflect the state of the live system.

You can include NetApp filer ~snapshot folders in the FSA Reporting scans if required, by setting a registry value. See "Including NetApp filer snapshot folders in FSA Reporting scans" in the Reporting guide.

Windows Search indexing of Vault Cache is supported for 64-bit Windows/32-bit Microsoft Office [Ref 9038976]

In Enterprise Vault 9.0.1/9.0.2, where 64-bit Windows was combined with 32-bit Microsoft Office, Enterprise Vault did not enable Windows Search to index the full content of items in Vault Cache. Windows Search only indexed the header information.

In Enterprise Vault 9.0.3, Windows Search indexing of the full content of items in Vault Cache is supported for the following:

Changes to requirements and supported versions

Service Pack 3 is the new minimum version of Windows XP [Ref 90310584]

Windows XP SP3 is the new minimum version that is supported for use with the following:

New minimum supported versions for Outlook on the Enterprise Vault server [Ref 9039494]

For Exchange Server archiving, you must install one of the following on the Enterprise Vault server:

Note: To archive from Exchange Server 2010, you must install Outlook 2007 SP2 with hotfix KB2475891.

For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.

Changes affecting Outlook users and requiring new Outlook Add-Ins

To obtain the changes described in this section, the Enterprise Vault 9.0.3 Outlook Add-Ins must be installed.

Virtual Vault now supports items that are encrypted using Entrust® [Ref 9039807, 90310725, E2421548, E2557282, E2557288]

In earlier releases, archived items that were encrypted using Entrust® Entelligence Security Provider 9.x could not be displayed when retrieved from Virtual Vault.

To remove this limitation, install the following software on Enterprise Vault users' computers:

Outlook Add-Ins with 64-bit Outlook 2010 did not deploy forms locally [Ref 9039559, E2217123] [10]

Enterprise Vault Outlook Add-Ins with the 64-bit edition of Outlook 2010 did not deploy Enterprise Vault forms to the Outlook personal forms library.

This has been fixed.

Custom MAPI properties in archived items could cause Virtual Vault to fail [Ref 9038596, E2321458]

Archived items that had custom MAPI properties with unexpected value types could cause Virtual Vault to fail when opened from Virtual Vault.

This has been fixed.

Outlook process could persist after user closed Outlook [Ref 9039117, E2386893]

In some circumstances, the Outlook.exe process could persist for up to 30 seconds after the user closed Outlook. For example, this happened when the Enterprise Vault Outlook Add-Ins could not contact the Enterprise Vault server.

This has been fixed.

Enterprise Vault failed to delete locally deployed forms [Ref 9039613, E2226792]

Enterprise Vault's advanced Exchange desktop policy, Deploy Forms Locally, failed to delete locally deployed forms when set to Delete.

This has been fixed.

Outlook.exe process persisted for some users who closed Outlook during Vault Cache synchronization [Ref 9039291, E2401600]

Users with many folders in their archives found that the Outlook.exe process persisted for a long time if they closed Outlook during Vault Cache synchronization.

This has been fixed.

Outlook did not show message content after Cumulative Client Hotfix installed [Ref 90310904, E2560912]

This issue was introduced by Enterprise Vault 9.0.2 Cumulative Client Hotfix Build 1185.

Outlook did not show the content of Virtual Vault items when both the following were true:

When this happened, Outlook did not show the content even when the user opened an item.

This has been fixed.

New registry setting allows Outlook Add-Ins to ignore missed Vault Cache synchronizations [Ref 9039059, E2350514]

By default, the Outlook Add-Ins initiate a Vault Cache synchronization soon after the user starts Outlook, if a scheduled Vault Cache synchronization has been missed. If you enable the new registry setting, OVAllowMissedMDCSyncOnStartup, then the Add-Ins do not initiate a synchronization until the next scheduled synchronization time after the user starts Outlook.

You can use this setting to alleviate synchronization slot and SQL Server contention issues. These can occur if a large number of users, who have missed a scheduled synchronization, all start Outlook within a short timeframe.

For details of the registry setting, see the Outlook Add-Ins chapter in the Registry Values manual.

Delays when Outlook Add-In was on a computer with unenabled mailbox [Ref 90310112, E2422002]

There was a delay when deleting Outlook items when both the following were true:

This has been fixed.

Switching between Integrated Search and Archive Explorer caused the failure of Enterprise Vault functionality in Outlook [Ref 90310583, E2525736] [10]

Users of Outlook 2007 and 2010 found that Enterprise Vault functionality failed in Outlook when they switched between Integrated Search and Archive Explorer. For example, Enterprise Vault buttons disappeared from the toolbar and items in Virtual Vault became inaccessible.

This has been fixed.

Outlook 2010 user could delete public folder content inadvertently [Ref 90311261, E2575712]

When an Outlook 2010 user deleted a favorites link to a public folder, the link was deleted and also the Enterprise Vault shortcuts in that public folder and the corresponding archived items were deleted.

This has been fixed.

Duplicate Windows Search results for Virtual Vault items [Ref 9039215, E2278791] [10]

After a rebuild of the Windows Search index, Windows Search results that included a Virtual Vault item could incorrectly include a duplicate of the item. This issue did not affect items in the user's mailbox, or items in Vault Cache.

This has been fixed.

Users lost the ability to search Virtual Vault from Outlook Instant Search [Ref 9039332, E2401372] [10]

Users who had Virtual Vault enabled could sometimes lose the ability to search Virtual Vault from Outlook Instant Search. At first, Outlook Instant Search found archived items, but some time later it could not find them, even when the user entered the same search terms. Typically, the issue occurred after the user opened an archived item from a shortcut or from Virtual Vault.

This has been fixed.

Enterprise Vault properties tab was still visible when Hide tab was set [Ref 9039368, E2367543]

This issue affected the Outlook Add-Ins in Enterprise Vault 9.0.1/9.0.2.

The Outlook Add-Ins did not apply the following Exchange desktop policy advanced settings correctly if you set their value to Hide tab:

The result was that the Enterprise Vault properties tab was still visible.

This has been fixed.

Outlook Add-In failed to load if PR_SERVICE_UID was missing [Ref 9038741, E2291986]

The Enterprise Vault Outlook Add-In failed to load if the PR_SERVICE_UID value was missing from the client's default Outlook profile registry key.

This has been fixed.

Outlook Add-Ins delayed Outlook start-up for VPN users [Ref 90310219, E2477261]

The Enterprise Vault Outlook Add-Ins caused an appreciable delay to Outlook start-up for users connected by VPN.

This has been fixed.

The Virtual Vault advanced setting Show content in Reading Pane has changed [Ref 9038605, E2336818] [10]

In the Administration Console, the default value for the Exchange Virtual Vault advanced setting Show content in Reading Pane is now When in Vault Cache.

Show content in Reading Pane can only have the value Always show content if the following conditions apply:

Always show content is no longer available in the Modify Setting dialog. So if Always show content is the current value and you change it, you cannot go back to it.

Always show content is no longer available because it can result in excessive downloading of the content of items. It is still possible to set the registry value VVReadingPaneContent to the value 2 (that is, the reading pane always shows the header and content of the item that is selected in Virtual Vault). We recommend that you do not set VVReadingPaneContent to the value 2.

Deletion with Delete key failed in Outlook 2003/2007 if there was no network connection [Ref 9039374, E2361371]

This issue affected Outlook 2003/2007 with the Enterprise Vault 9.0.1/9.0.2 Outlook Add-Ins.

If a user's computer was disconnected from the network and Outlook was open in Disconnected mode, the user could not delete any item in the mailbox using the Delete key. The issue affected both archived and unarchived items. Methods of deletion other than the Delete key worked correctly.

The following message was displayed:

This operation failed because of a registry or installation problem. Restart Outlook and try again. If the problem persists, reinstall Outlook.

This has been fixed.

Policy settings were not applied to Store in Vault options [Ref 9039395, E2209650]

This issue affected only the Outlook Add-In, not the HTTP-Only Outlook Add-In. It occurred when both of the following conditions applied:

If the user selected multiple items in an enabled folder for archiving, the correct Exchange mailbox policy settings were not applied to the options Delete original items after storing and Create shortcuts to stored items in the Store in Vault dialog box.

This has been fixed.

Users could not retrieve archived items even when PSTDisableGrowAllowAuthenticodeOverrides was enabled [Ref 9038418, E2236549]

This issue affected the Enterprise Vault 9.0.1/9.0.2 Outlook Add-Ins in Outlook 2007 and 2010.

If the Microsoft registry value PSTDisableGrow was enabled on a user's computer in the following location:

HKEY_CURRENT_USER\Software\Microsoft\Office\Office_version\Outlook\PST

then Enterprise Vault could not retrieve archived items, even if the registry value PSTDisableGrowAllowAuthenticodeOverrides was also enabled.

The issue also prevented retrieval of archived items in Outlook Integrated search, and in Archive Explorer when it was opened in Outlook.

Users saw the following error in Outlook:

The item could not be downloaded [OIOM] 80070005.

An error of the following type appeared in the client log:

08/01/2011 13:21:32.714[7896]: CShortcutItem::Display...Return Last Failed error: 0x80070005
08/01/2011 13:21:32.714[7896]: ~CShortcutItem::Display: 0x80070005

(Note that PSTDisableGrowAllowAuthenticodeOverrides can be set only in the following location:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\Office_version\Outlook\PST

The issue did not occur if PSTDisableGrow and PSTDisableGrowAllowAuthenticodeOverrides were both enabled in this location; that is, the location that includes the subkey \Policies.)

This has been fixed. If PSTDisableGrowAllowAuthenticodeOverrides is enabled, Enterprise Vault can retrieve archived items even if PSTDisableGrow is enabled only in HKEY_CURRENT_USER\Software\Microsoft\Office\Office_version\Outlook\PST. Also, if PSTDisableGrow is enabled and PSTDisableGrowAllowAuthenticodeOverrides is not enabled, the Enterprise Vault Outlook Add-In displays a warning when it starts.

For more information on the use of PSTDisableGrowAllowAuthenticodeOverrides, see the Setting up Exchange Server Archiving manual.

In some circumstances, the upgrade to Office 2010 SP1 caused Windows Desktop Search to fail [Ref 90310259, E2481056]

In some circumstances, the upgrade to Microsoft Office 2010 SP1 caused Windows Desktop Search to fail on client computers with the Enterprise Vault Outlook Add-Ins installed.

This has been fixed.

Changes affecting Outlook users and not requiring new Outlook Add-ins

The changes described in this section are obtained as a result of upgrading Enterprise Vault server software and so do not require the updated Enterprise Vault 9.0.3 Outlook Add-ins.

Users could not delete archived items in browser search [Ref 9039621, E2421835]

Users could not delete archived items using Enterprise Vault browser search, even though they could be deleted using both Outlook and Enterprise Vault Archive Explorer.

This has been fixed.

Outlook users could not retrieve items protected by Windows Rights Management Services [Ref 9030742, E2535918]

In Outlook, items that were protected by Windows Rights Management Services did not have any content when retrieved after archive. The items could be restored successfully.

This has been fixed.

Missing addresses when using EML in multisite environments [Ref 90310918, E2566360]

If you had a multisite environment and a client downloaded a message in EML format, it was possible that the SMTP addresses were omitted from the message header.

This problem affected Mac clients, for example.

This has been fixed.

Users with access to very large numbers of archives experienced delays while the list of archives was populated [Ref 9039921, E2433311] [10]

Users such as system administrators, who have access to very large numbers of archives, experienced significant delays while the list of archives was populated in Integrated Search, Archive Explorer, and Browser Search.

The performance of this functionality has been greatly improved.

Changes to OWA support

Archived items were deleted after the shortcuts were accessed using OWA [Ref 9038370, E2291228]

If the registry entry HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Agents\RestoreAndDelete was set to "1", archived items were deleted after you accessed the shortcuts from an OWA client.

This has been fixed.

In Exchange Server 2003 OWA clients, search results were displayed incorrectly [Ref 9038619, E2343986]

If you used Search Archives in an OWA client, then opened a search result, the item was rendered by Enterprise Vault instead of OWA. This meant that the reply and forward functions were not available for the item. This occurred in Exchange Server 2003 OWA clients, with the default Exchange Desktop policy settings.

This issue has been fixed.

User could not archive or restore items when accessing another user's mailbox in OWA [Ref 90310805, E2551841]

This issue affected Exchange Server 2010 OWA clients. If user A had full access permissions to the mailbox of user B, user A was unable to perform Enterprise Vault functions when accessing user B's mailbox in OWA.

This has been fixed.

EVAnon folder path was created incorrectly [Ref 90310857, E2563418, E2567370]

Sometimes when the owauser.wsf script was run, the folder path for the EVAnon virtual directory was created incorrectly; an extra backslash was added to the path. As a result, Enterprise Vault functions did not work in OWA clients.

This has been fixed.

Certificate based authentication is now supported in OWA clients [Ref 9038807, E2319507]

Enterprise Vault functionality was not available in OWA clients when certificate based authentication was used.

This has been fixed. Enterprise Vault OWA 2007 and 2010 Extensions now support certificate based authentication.

Event errors were reported when explicit URLs were used to access Exchange Server 2010 OWA clients [Ref 9039348, E2367110]

Explicit URLs have the user name or address of the mailbox appended to the OWA URL, for example,
https:\\Exchange.Example.com\owa\room1@example.com

When accessing an Exchange Server 2010 OWA client using an explicit URL and basic or Integrated Windows authentication, multiple errors were sometimes reported in the event log on the CAS computer. The errors were reported by the Enterprise Vault OWA extensions, and had an Event ID of 0. The following text was included in the error description:
System.Exception: EVOWA - Request not Authenticated (Could not establish the UserContext)

This has been fixed.

In OWA clients, shortcuts were always created and the original item deleted if the OWA archive function policy setting was "Basic" [Ref 9039366, E2361460]

This issue affected Exchange Server 2003, 2007, and 2010 OWA Premium and Light clients, if archive function was set to Basic in the Exchange Desktop policy. The archive function settings are in the advanced OWA settings list, in the Exchange Desktop policy. The setting for OWA Premium clients is Premium archive function. The setting for OWA Light clients is Basic archive function.

In Exchange Server 2010 OWA clients, archive function is set to Basic automatically when Conversation View is turned on. Conversation View is on by default.

If archive function was set to Basic, shortcuts were always created and the original item deleted, irrespective of the values set for Delete original item after storing and Create shortcut to stored item in the Exchange Mailbox policy.

This has been fixed. When archive function for OWA clients is set to Basic, Enterprise Vault honors the values set for Delete original item after storing and Create shortcut to stored item in the Exchange Mailbox policy.

OWA users could not open items from the Archive Explorer tab after closing the primary OWA tab [Ref 90310198, E2427686]

OWA users who displayed a list of items in Archive Explorer, then closed the primary OWA tab in Internet Explorer, could not open, reply to or forward any of the items in Archive Explorer.

This has been fixed. Items opened from Archive Explorer now open in a new Internet Explorer window if the primary OWA tab has been closed.

Changes affecting Notes and DWA users

Unable to restore encrypted items that had multiple attachments in Lotus iNotes or Domino Web Access [Ref 9038350, E2246686]

When an encrypted item had multiple attachments, you could not restore it from an Enterprise Vault shortcut in Lotus iNotes and Domino Web Access.

This has been fixed.

Issues when opening and restoring archived items if your mail database was close to or over quota

If you were close to or had exceeded the maximum quota for your mail database, you could experience the following issues when you tried to open or restore archived items from Enterprise Vault shortcuts:

Both issues have been fixed. If you try to open an item in these circumstances, Enterprise Vault now displays a version of the item with limited functionality. An accompanying message explains why Enterprise Vault cannot open or restore the full item.

No 'Enterprise Vault Search Cache' option when Vault Cache enabled [Ref 9039631, E2426458]

Users did not see the 'Enterprise Vault Search Cache' menu option when Vault Cache was enabled.

This has been fixed.

Shortcuts could not be opened when user had database link to mail file [Ref 90310159, E2413313]

When a user's mail file was accessed by means of a database link, the user could not use shortcuts to retrieve archived items. When the user tried to open a shortcut the following error was shown:

Notes Error: Remote pathnames must be relative to the Data Directory

This has been fixed.

Changes to Archive Explorer

Offline Archive Explorer could display a blank page in Outlook 2003 [Ref 90310753, E2552443]

In Outlook 2003, when the user had no network connection, offline Archive Explorer could in some circumstances display a blank page.

This has been fixed.

Archive Explorer could not retrieve Outlook notes from Vault Cache while offline [Ref 90311447, E2584651]

While users were disconnected from the network, Archive Explorer failed to open Outlook notes that were present in Vault Cache, and reported that a connection to the Enterprise Vault server could not be established.

This has been fixed.

Changes to Exchange Server archiving

In some circumstances, newly enabled Exchange mailboxes generated errors during archiving [Ref 9038459, E2332523] [10]

In some circumstances, when the archiving task ran against a newly enabled Exchange mailbox, it wrote the following errors to the event log:

Event Type:     Error
Event Source:   Enterprise Vault
Event Category: Archive Task
Event ID:       2776
Date:           3/16/2011
Time:           3:25:50 PM
User:           N/A
Computer:       EVSRV1
Description:    An exception occurred in routine
CArchivingAgent::AddOrphanedShortcutsToDeleteList
EXCEPTION_ACCESS_VIOLATION @ 0x 619098A
Event Type:     Error
Event Source:   Enterprise Vault
Event Category: Archive Task
Event ID:       2243
Date:           3/16/2011
Time:           3:25:50 PM
User:           N/A
Computer:       EVSRV1
Description:    Could not scan user mailbox /o=First
Organization/ou=First Administrative Group/cn=Recipients/cn=johndoe,
cannot list messages

This happened when the user had archived mail items before the Archiving task had run against the mailbox for the first time.

This has been fixed.

Enterprise Vault removed a retention property from items in users' managed folders [Ref 9038557, E2127321] [10]

During archiving, Enterprise Vault removed a managed folder retention property from items in users’ managed folder. This prevented the removal of the affected items from the folder by MRM policies.

This has been fixed.

Illegal errors in RSS messages prevented them from being archived [Ref 9038803, E2186352]

Illegal characters in RSS message prevented the items from being archived. Additionally, when these illegal characters were encountered, Enterprise Vault wrote the following error to the event log:

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault
Date:          10/25/2010 3:05:31 PM
Event ID:      6592
Task Category: Storage Archive
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EVSRV1.example.com
Description:   Abnormal error occurred
VaultId:       1B38DFA14F69B734E834AE63D4253B5F31110000vs1.example.com

This has been fixed. Illegal characters are now replaced with a legal character.

Default value has changed for RestartOnMAPIMutexError [Ref 9039478, 9039588, 9039699]

The default for registry value RestartOnMAPIMutexError has changed from 0 to 1.

In previous versions of Enterprise Vault, the default value for RestartOnMAPIMutexError was 0. With this value, Enterprise Vault did not restart MAPI services when it encountered a MAPI mutex error. With the new default value of 1, Enterprise Vault automatically restarts MAPI services when it encounters a MAPI mutex error.

Note that the default for registry value RestartAllMAPITaskIntervalMins is 0, as in previous versions of Enterprise Vault.

On a 32-bit installation of Windows, both these registry values are under the following registry key:

HKEY_LOCAL_MACHINE
\SOFTWARE
 \KVS
  \Enterprise Vault
   \Agents

On a 64-bit installation of Windows, both these registry values are under the following registry key:

HKEY_LOCAL_MACHINE
\SOFTWARE
 \Wow6432Node
  \KVS
   \Enterprise Vault
    \Agents

For more information, see the Registry Values guide.

In some circumstances, Enterprise Vault disabled over-quota Exchange mailboxes [Ref 9039589, E1746208]

In some circumstances, over-quota Exchange mailboxes became disabled during mailbox synchronization.

This has been fixed. Enterprise Vault now writes an error to the event log to indicate that a mailbox could not be synchronized, and the mailbox remains archiving enabled.

Change to PST Migration wizard [Ref 90310183, E2291639]

The PST Migration wizard no longer creates shortcuts for appointments or tasks. This new behavior matches the existing behavior of the Exchange Mailbox task.

The message classes for which the PST Migration wizard no longer creates shortcuts are as follows:

Exchange journaling task reported that the provisioning task must run against the journal mailbox [Ref 90311044, E2525010] [10]

The Exchange journaling task failed to archive the journal mailbox and wrote the following error to the event log:

Event Type:     Warning
Event Source:   Enterprise Vault
Event Category: Journal Task
Event ID:       3357
Date:           10/10/2011
Time:           17:09:47
User:           N/A
Computer:       EVSRV1
Description:    This mailbox cannot be processed until the Exchange provisioning task has
                processed the corresponding user's details. Ensure that a provisioning group
                includes this user and run the provisioning task.

This has been fixed.

SQL improvements when updating item metadata [Ref 9038707, E2347729]

SQL performance and deadlocking have been improved when updating the metadata of archived items.

Enterprise Vault could display incorrect 'Archive limit status' [Ref 9038500, E2240106]

In the Administration Console, under certain circumstances, in the properties of the archive, Archive limit status was incorrectly displayed as Unknown.

This has been fixed.

Exchange managed folder retention policies were not applied correctly [Ref 90310337, E2493183]

In some circumstances, retention policies set on Exchange managed folders were not applied correctly to archived items that had the message type Email.

This has been fixed.

Notification message for each item when archive over quota [Ref 9039582, E2420296] [10]

Whenever an item was stored in an archive that was over quota, the user received a notification mail message. There was one message for each item.

This has been fixed. There is now one notification per day.

Changes to PST Migration

PST locator task did not report the presence of PST files in very long file paths [Ref 9037913, E2127575]

The PST locator task cannot process files in file paths longer than approximately 260 characters. Previously, the PST locator did not report the presence of these PST files and they were therefore ignored by the task.

The PST locator task now reports the presence of PST files that are too deep in a long file path for it to process. The task writes a summary warning in the event log, and lists the affected files in the PST locator task report file.

PST Locator task failed to process some PST files stored on NetApp Filers [Ref 9038396, 9039549, E2206973, E2417815]

When the PST Locator task scanned a NetApp filer for PST files, some volumes and shares were added to the search list while others were not.

When PST Locator task added the default CIFS share, C$, the associated mount point /vol/vol0 was added to the search list. If there were additional volumes with a mount point prefixed by the string "/vol/vol0", for example /vol/vol020/research, these volumes were ignored, and not added to the search list.

The same applied to CIFS shares which were prefixed by "HOME" and based on a mapping to /vol/vol0. If the share, HOME$, with the mount point path /vol/vol0/home, was added to the search list, any further share with a mount point path that started with the string "/vol/vol0/home" was not added to the list. For example, the share HOME1$ with the mount point path /vol/vol0/home1 would not be added.

For a detailed description of the issue, see the document http://www.symantec.com/docs/TECH167223 on the Support Web site.

This has been fixed.

Changes to Domino server archiving

Messages with invalid surrogate pair characters could not be archived [Ref 9038095, E2301875]

Email messages that contained invalid surrogate pair characters could not be archived.

This has been fixed.

EVLotusDominoJournalTask.exe processes sometimes failed to shut down [Ref 9038406, E2078103]

If the Compliance Accelerator Domino Journaling Connector was present, EVLotusDominoJournalTask.exe processes did not always stop when the Domino Journaling task was stopped or when Enterprise Vault services were shut down.

This has been fixed.

Archiving failed when mail file had hidden folders [Ref 9038749, E2351604]

The Domino Mailbox Archiving task could not process mail files that contained hidden folders. There was no indication that archiving had failed.

This has been fixed. The task now processes mail files that contain hidden folders but does not archive the contents of hidden folders.

Possible process termination when creating shortcuts [Ref 9038752, E2355061]

Under some circumstances Enterprise Vault processes could terminate unexpectedly while creating shortcuts.

This has been fixed.

Archiving task is more tolerant of minor errors [Ref 9038757, E2351607, E2344471, E2344251, E2344255]

The Archiving task is now more tolerant of minor errors in a mail file. The following no longer cause the Archiving task to fail to archive from a mail file:

Shortcut bodies removed when EVDominoExchangeMigration tool used [Ref 9039906, E2423010]

In some circumstances it was possible for shortcut bodies to be removed when you used the EVDominoExchangeMigration tool.

This has been fixed.

Items archived repeatedly when using Domino Retention Plan [Ref 9030218, E2481520]

The Domino archiving task archived items repeatedly when the following were true:

This has been fixed.

Large Domino items could be archived repeatedly [Ref 9039437, E2389517]

When neither of the following Domino archiving policy options was selected the Domino archiving task could sometimes archive large mail items repeatedly, once on each run of the task:

This has been fixed.

Members of Domino Directory "ACL only" groups could not access archives [Ref 9039841, E2438267]

Access permissions for members of Domino Directory groups that were defined as "ACL only" were not applied to the corresponding archive. As a result, users who were members of these groups could not access the archive.

This has been fixed.

Best practice when moving Domino archives [Ref 9039646, E2359036]

If you use Move Archive to move a Domino mailbox to a different Enterprise Vault site, run the Provisioning task on the new site before you enable the moved mailbox.

Changes to NSF Migration

NSF migration failed when Domino cluster server had failed over [Ref 9038580, E2327279]

The NSF migration wizard failed to import NSF files when a Domino cluster server had failed over. The wizard produced an error message saying that NSF files were unavailable.

This has been fixed.

NSF migration can now migrate items with no 'Form' field [Ref 9039877, E2322605]

NSF migration could not migrate items that did not have a 'Form' field.

This has been fixed. You can now use the DominoArchiveMissingFormMails registry value to force NSF migration to migrate items that do not have a 'Form' field.

See the Registry Values manual for details of DominoArchiveMissingFormMails.

Changes to Move Archive

During cross site moves, Move Archive prevents the source site's Mailbox archiving task from taking back ownership of the mailbox [Ref 90310300, E1956414]

When a mailbox is provisioned in two Enterprise Vault sites that target one Exchange organization, both sites' Mailbox archiving tasks take ownership of the mailbox each time they run. To avoid this situation, you should not provision any mailbox in two Enterprise Vault sites that target one Exchange organization.

When you used Move Archive to move an archive between two Enterprise Vault sites that target one Exchange organization, Move Archive created a situation in which this could occur but did not prevent it. For the duration of the move, each time one of the site's Mailbox archiving tasks ran, it took ownership of the mailbox.

This has been fixed and Move Archive does not allow the source site's Mailbox archiving task to take back ownership of the mailbox.

Embedded mail items with absent properties caused Move Archive to fail [Ref 9039675, E2428422]

During the retrieval of items from a source archive, Move Archive failed when it encountered an item that was embedded in another item, and was missing certain properties.

This has been fixed.

Move Archive now always waits for backup [Ref 9039760, E2400184] [10]

Previously, Move Archive entered a waiting state until the destination archive was backed up, except when the source vault store was configured to remove safety copies immediately after archiving.

This behavior has changed, and Move Archive now always waits for backup before it moves to the verification step.

When Move Archive encountered items with more than 2048 recipients, it treated them as corrupt [Ref 9038782, 9039148, E2248239]

When Move Archive encountered items with more than 2048 recipients in the To, CC, or BCC fields, it treated them as corrupt.

To solve this issue, the Enterprise Vault installer now sets the RecipientMax registry DWORD value to 0xFFFFFFFF. RecipientMax is under the following registry key:

HKEY_CURRENT_USER
\Software
 \Microsoft
  \Office
   \nn.0
    \Outlook
     \Options
      \Mail

Changes to Administration Console

Administration Console prevented the addition of two Exchange domains whose domain controllers had the same host name [Ref 9038390, E2167388]

The Enterprise Vault Administration Console prevented the addition of a domain as an Exchange archiving target, if its domain controller had the same host name as a domain controller in an existing Exchange archiving target domain.

This has been fixed.

Index locations did not always go into backup mode [Ref 90310067, E2304006]

When an index location was placed in backup mode it was possible for the operation to fail for some index volumes, leaving the location only partially in backup mode.

This has been fixed.

IPv6 and Administration Console on Windows XP and Windows Server 2003 [Ref E2304470]

In Windows XP and Windows Server 2003, Windows Explorer cannot browse shares on systems that are pure IPv6. This restriction means that it is not possible to use a remote Administration Console on Windows XP and Windows Server 2003 to create a vault store group if the SQL server is pure IPv6.

Changes to storage

Enterprise Vault retention policy prevented the deletion of invalid savesets [Ref 9039435, E2108309]

During the removal of safety copies, Enterprise Vault ensures that archived items have been backed up before it removes the associated original items. If the Storage service encounters an invalid saveset in an archive, it retains the original item and removes the invalid saveset from the archive. However, if the applicable Enterprise Vault retention policy was set to prevent the deletion of items from the archive, the Storage service was unable to delete the invalid saveset.

This has been fixed, and the Storage service now overrides the retention policy to remove invalid savesets.

Corrupted SIS parts caused some items to remain in a pending state [Ref 9039472, E2143836]

With sharing enabled in a vault store group, a corrupted SIS part caused some mail items to remain in a pending state. When the Storage service first detected an item with a corrupted SIS part, it rolled back the item in the user's mailbox. However, other items that shared the SIS part permanently remained in a pending state.

This has been fixed.

Unreplicated Centera clip could block further post processing [Ref 9039594, E1992210]

The Storage service marks the savesets contained in Centera clip files as secure when the clip file has been replicated. If the Storage service encounters 10 consecutive unreplicated clips, it stops processing assuming that the remaining clip files on the partition are also unreplicated.

In some circumstances, just one unreplicated clip on a partition could cause the Storage service to stop processing the partition. For as long as this clip file remained unreplicated, no more savesets in the remaining clip files were marked as secure.

This has been fixed.

Redundant JournalUpdate table entries could persist in vault store databases [Ref 9039612, E2065445]

In some circumstances, redundant JournalUpdate table entries could persist in vault store databases. This could happen when items were subject to a change of retention category or shortcuts were moved to a different folder in the mailbox. If users then deleted affected shortcuts before shortcut processing ran, redundant JournalUpdate table entries occurred.

This has been fixed.

Use of DeleteEmptyFolders registry value caused SQL deadlocks [Ref 9039795, E2245691]

When DeleteEmptyFolders is set to a value other than 0, the Storage service removes empty folders from the archives it owns. In some circumstances, this produced SQL deadlocks and the removal of folders could be very slow or fail completely.

This has been fixed.

Improved post-processing performance for storage devices using a Storage Streamer API implementation [Ref 9038685, E2332399] [10]

An issue with the StorageFileWatch process could cause poor post-processing performance for users of the following storage devices using an Enterprise Vault Storage Streamer API implementation:

Post-processing checks backup or replication status on the vault store partition and processes backed-up or replicated items.

This has been fixed.

Improved file collection rate [Ref 90310129, E2429500]

As a result of more efficient use of file locking during collections, the performance of Enterprise Vault file collection in partitions has been improved.

Enterprise Vault wizards did not display shared disks in a clustered environment [Ref 9038421, E1888484]

This issue applies to the following Enterprise Vault configuration:

When creating a new vault store partition, or PST Migration task, the wizard failed to display shared disks in the Windows Server 2008 cluster nodes. This happened if the wizard was launched from a remote Vault Administration Console session.

This has been fixed.

Error reported when archiving to a streamer storage device [Ref 9039365, E2354237]

When archiving certain items, error 13360 was reported repeatedly in the event log. This occurred when the vault store partition was located on a streamer storage device, and sharing was enabled.

The error reported was similar to the following:

Event Type: Error
Event Source: Enterprise Vault
Event Category: Storage Archive
Event ID: 13360
Date:  4/18/2011
Time:  1:32:06 PM
User:  N/A
Computer: B13-EV5
Description:
An error was detected while accessing the Vault Database
'VaultStoreName' (Internal reference: CADODataAccess::ExecuteSQLCommand
.\ADODataAccess.cpp [lines {1407,1409,1424,1442}], built Apr 11 21:04:29 2011):
Description:
Violation of PRIMARY KEY constraint 'PK_WatchSISPartFile'. Cannot insert
duplicate key in object 'dbo.WatchSISPartFile'.

This has been fixed.

Enterprise Vault now supports HP X9000 Systems (IBRIX) devices [Ref 9039992, E2414690]

You can now create vault store partitions on HP X9000 Systems (IBRIX) devices in both WORM and non-WORM configurations.

For the latest information on supported versions of devices and software, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.

Items could remain in Pending state [Ref 9039475, E2411945]

In some circumstances, post-processing notifications were not sent after archived items were secured. The result was that archived items remained in the Pending state until the StorageFileWatch process was restarted.

This has been fixed.

In some circumstances, some index properties could be omitted from signed and encrypted MAPI messages [Ref 90310406, E2518573]

In some circumstances, Message Security (SECU) index properties could be omitted from signed and encrypted MAPI messages that were archived by agents other than Enterprise Vault's own archiving agents. For example, this problem occurred for items archived by the Content Management API and by File System Archiving.

As a result, some items could be excluded from searches that include criteria based on these properties.

This has been fixed.

Changes to EVSVR

Failure of EVSVR [Ref 90310199, E2433738]

In rare circumstances an EVSVR verify archives operation could fail and incorrectly log the error Failed to connect to Vault Store Database (0xc0041a5f). When this happened, EVSVR had not made any attempt to connect to the Vault Store Database.

This has been fixed.

Changes to indexing

HTML tags could result in incorrect indexes [Ref 9039610, E2355445]

Since Enterprise Vault 8.0 SP1, indexing has incorrectly treated the following HTML tags as white space:

 span, big, font, i, s, strike, strong, sub, sup, u

This meant, for example, that the following HTML was indexed as "In correct" instead of "Incorrect":

    <u>In</u>correct

This problem could affect the results of Compliance Accelerator and Discovery Accelerator searches.

The only way to correct existing indexes is to rebuild them.

Event 7264 could be logged when accessing index volumes [Ref 90310072, E2486737]

An error event could be logged when any of the following actions was performed on a 32-bit index volume that contained items that had had metadata updates:

The event was as follows:

    Event 7264
    Abnormal error occurred
    Error:  Exception occurred.

This has been fixed.

SQL improvements for indexing [Ref 9038434, E2237002] [10]

There have been some optimizations to database access by the StorageCrawler process.

Changes to File System Archiving

FSA using Celerra pass-through recall could produce event ID 6992 [Ref 9038775, E2351159]

In rare circumstances, FSA using Celerra pass-through recall produced event ID 6992 on the Enterprise Vault server. When this happened, users could not recall further files using Enterprise Vault placeholders, and in some cases the Celerra device became unresponsive.

This has been fixed.

Performance improvement for the pass-through recall of large files from Celerra devices [Ref 9039221, E2235866]

Large file retrieval times have been improved for environments where pass-through recall from Celerra devices is enabled.

FSA failed to distinguish between an archive point's root folder and a subfolder with the same name [Ref 9039561, E2417997]

FSA failed to distinguish between an archive point's root folder and a subfolder with the same name. Items from the subfolder were placed in the root of the archive rather than in a separate archive folder.

This has been fixed.

The 'Delete archived file when placeholder is deleted' feature failed to delete the archived item in retention folders [Ref 90310754, E2558340]

A problem occurred with the 'Delete archived file when placeholder is deleted' feature, when used with retention folders. If you deleted a placeholder from a retention folder, Enterprise Vault deleted the placeholder but it failed to delete the archived item and the index entry.

The following event appeared in the Enterprise Vault event log:

Event ID: 20545 Failed to determine whether to delete an archived file
following the deletion of its placeholder. The archived item will not be
deleted.

This has been fixed.

File System Archiving task generated false warning events for volumes it had already processed [Ref 9038453, E2257966] [10]

If a File System Archiving task was stopped before completion then when it continued it generated false warning events in the Enterprise Vault event log for volumes that it had finished processing on the previous run. The warning events had the following format:

Event ID: 40976
The file system volume \\?\UNC\server\volume has no Archive
points associated.
No items will be archived for this volume.
See the Administrator Help for information on configuring file
system volume archive points.

This has been fixed.

File Blocking failed to quarantine all media files within tar.gz files on NetApp filers [Ref 9038781, E2244251]

A problem could occur with the File Blocking of media files within tar.gz files on NetApp filers. Enterprise Vault blocked the media files, but it did not always quarantine them.

This has been fixed.

FSAUtility placeholder operations failed on Celerra DART 5.5 if the Celerra backup mode was set to passthrough [Ref 9039165, E2362694]

FSAUtility's placeholder-related operations failed to have any effect on Celerra DART 5.5 volumes if the Celerra's backup mode was set to passthrough. FSAUtility failed to identify the placeholders in this configuration.

FSAUtility now provides two methods for placeholder identification. The alternative method recognizes the placeholders regardless of the Celerra backup mode, but is more demanding of resources. You can choose which method to use, depending on your Celerra configuration.

For more information, see "About using FSAUtility with EMC Celerra placeholders" in the Utilities guide.

Recall from placeholder failed for files greater than 50 MB [Ref 9039501, E2355827]

The recall from a placeholder of a file that was larger than 50 MB could fail, due to an error in the mechanism for comparing checksums.

This has been fixed.

Memory leak when recalling placeholder shortcuts on NetApp filers [Ref 9039240, E2391461]

Recalling placeholder shortcuts on NetApp filers caused a memory leak. The problem occurred when the NetApp filer was configured for pass-through recall, and the placeholder shortcuts were located in the snapshot folder.

This has been fixed.

File Blocking email notification failed with 'Error initializing MAPI' [Ref 90310665, E2197426]

If you configured the Send email notification option for a File Blocking rule in Enterprise Vault 9.0.1 or 9.0.2, the File Blocking service failed to send the email. The following error appeared in the Enterprise Vault event log on the file server:

Event Type: Error
Event Source: Enterprise Vault
Event ID:  28687
Description:
Failed to send email with following details:
To:User@Domain.local
From:Account@Domain.local
Subject:Test Mail
Reason:Error initializing MAPI

This has been fixed.

FSAUtility command to restore files to a different file server failed if the source file server was unreachable [Ref 9039139,E2170316]

An FSAUtility –t command to restore archived files to a different file server failed if the source file server was unreachable.

This has been fixed.

Large number of file extensions caused archiving to fail [Ref 9039448, E2347288]

If FSA attempted to store more than 32,767 different file extensions, archiving began to fail with the following event in the Enterprise Vault event log:

Type:  Error
Event:  13345
Source:  Enterprise Vault
Category: File System Archiving Task
Description:
An error was detected while accessing the Vault Database
'Provider=SQLOLEDB;Server=VaultServer;Database=Databasename_1_1;Integrated
Security=SSPI' (Internal reference: CADODataAccess::AddInputParameter @Type_0
.\ADODataAccess.cpp [lines {2148,2165}], built Nov 24 00:04:01 2010), error code
<0x800a0cc1>.

This has been fixed.

FSAUtility did not recreate placeholders forcibly if the folder path exceeded 1177 characters [Ref 9039484,E2193394]

On Windows file servers and NetApp filers, if you used FSAUtility with the -c -f options to recreate placeholders forcibly, FSAUtility failed to recreate the placeholders if the path exceeded 1177 characters.

This has been fixed. Note that for EMC Celerra there is an EMC restriction that prevents archiving when the path to the files exceeds 1024 characters.

The file server sometimes stopped responding when a user accessed a placeholder shortcut [Ref 9039598, E2407858]

Sometimes when a user accessed a placeholder shortcut, the file server stopped responding, or shut down unexpectedly. This problem could occur if the file server was running Windows Server 2008 or later, and the Enterprise Vault Placeholder service was installed.

This has been fixed.

Improved synchronization performance [Ref 9039823, E2250441] [10]

The synchronization performance has been improved for folders and archives that have not changed.

Checkpointing issue with NetApp filers if folders are not listed alphabetically [Ref 90310124, E2438721]

The FSA checkpoint mechanism is designed to process the subfolders of a partially processed target volume in alphabetical order to determine whether the previous checkpoint has been reached. On some NetApp systems the system does not present the list of folders in alphabetical order. A non-alphabetical list can cause FSA to reprocess some folders repeatedly during multiple archiving runs.

To fix this issue, you can now set a registry value to make the checkpoint mechanism sort the list of NetApp folders into alphabetical order before inspection.

To set the registry value, do as follows:

  1. On the Enterprise Vault server create a DWORD registry value named CheckpointSort, under the following registry key.
    On a 32-bit installation of Windows:
    HKEY_LOCAL_MACHINE
     \SOFTWARE
      \KVS
       \Enterprise Vault
        \FSA 
    On a 64-bit installation of Windows:
    HKEY_LOCAL_MACHINE
     \SOFTWARE
      \Wow6432Node
       \KVS
        \Enterprise Vault
         \FSA 
  2. To perform alphabetical sorting, set the value of CheckpointSort to 1.
    If you want to disable alphabetical sorting, set the value to 0.

Wizard-based installation of FSA Agent failed from Windows Server 2008 R2 [Ref 9038730, E2346997] [10]

If you used the "Install FSA Agent" wizard to install the FSA Agent from an Enterprise Vault server that ran Windows Server 2008 R2, the installation failed. The following message appeared in the log file for the file server, in the evpush\logs folder under the Enterprise Vault installation folder:

Inside ThreadToConnect. Failed to check credentials. Error code 8000401A.
FAILED
Inside exception handle. Error code: 0x8000401A

This has been fixed.

Changes to SharePoint support

Running Backup Exec on a target SharePoint Server caused the Enterprise Vault Admin Service to stop unexpectedly [Ref 9038051, E2073751]

If Backup Exec was installed on the same computer as the Enterprise Vault Microsoft SharePoint Components, then the Enterprise Vault Admin Service on the computer stopped unexpectedly. This occurred when Backup Exec attempted to refresh backup locations.

This has been fixed. The Admin Service no longer stops if it receives a refresh backup locations command. However, we recommend that you do not install Backup Exec on the same computer as the Enterprise Vault Microsoft SharePoint Components.

Archiving error when SharePoint had KnowledgeLake Imaging installed [Ref 90310160, E2206326]

When SharePoint has KnowledgeLake Imaging installed, archiving failed with the following error:

Error listing folders.

This has been fixed.

Enterprise Vault ignored dates in archiving policy rules [Ref 90310328, E2350375]

Enterprise Vault ignored the metadata date criteria in policy rules for the SharePoint library while archiving. This resulted in Enterprise Vault archiving fewer items than expected.

This has been fixed.

Metadata Rules ignored empty fields [Ref 9038271, E2294637] [10]

The Content Type/Metadata tab in the Metadata Rules page retained old values when you cleared the fields.

This has been fixed.

Enterprise Vault StorageOnlineOpns process could become unresponsive [Ref 9038303, E2323539] [10]

The Enterprise Vault StorageOnlineOpns process could become unresponsive during SharePoint Indexing with a 64-bit version of SharePoint.

This has been fixed.

EVSPshortcutManager could be unable to recall shortcuts [Ref 9038305, E2247264]

In some circumstances, the EVSPshortcutManager utility could fail to recall a shortcut in a library when the utility was run at the site or server level.

This has been fixed.

Enterprise Vault could fail to create shortcuts or to read old versions of files [Ref 9038780, E2210026, E2242792]

Enterprise Vault could fail to create shortcuts to items that had been previously recalled and then re-archived, or fail to read old versions of a file.

The shortcut creation failed with the following error:

Object reference not set to an instance of an object.

The SharePoint archiving task failed with the following error:

Error listing versions of the file.

These have been fixed.

Archived SharePoint files with shortcuts do not open with Office Web Apps [Ref 9038896, E2280786]

It was not possible to use Office Web Apps to open Enterprise Vault shortcuts.

This has been fixed.

SharePoint archiving task can now authenticate using a client certificate [Ref 9038962, E2351313]

For more information, see the section 'About SharePoint archiving with Enterprise Vault' in the Setting up SharePoint Server Archiving guide on the Enterprise Vault media.

Shortcut deletion was suspended when the policy specified zero days [Ref 9038990, E2282582]

When the following policy settings were used, shortcut deletion was suspended until a new file was added to the library:

This has been fixed.

When an archiving rule had a Date set to Today, some items were not archived immediately [Ref 9039277, E2218239]

When an archiving rule had a Date set to Today, some items were not archived immediately. Those items were archived successfully the next day.

This has been fixed.

Content type of archived files appeared changed [Ref 9039660, E2399148]

Archived files could appear as a different content type after Enterprise Vault created shortcuts. This problem existed for most types of Office 2007 files on SharePoint 2007.

This has been fixed.

SharePoint could not display archived versions of documents in archives that had multiple index volumes [Ref 90310257, E2302242]

SharePoint could not display archived versions of documents in archives that had multiple index volumes.

If this issue occurred, you saw the following error when you clicked the Show archived versions for this document link on the versions history page:

No versions of this document were found in the archive.

This has been fixed.

Changes to Enterprise Vault Reporting and FSA Reporting

Enterprise Vault Reporting's Vault Store Usage reports failed to generate [Ref 9039470, E2330046]

Enterprise Vault Reporting's 'Vault Store Usage by Archive' report and 'Vault Store Usage by Billing Account' could fail to generate, with the following error:

An error occurred during client rendering.
  An error has occurred during report processing.
    Query execution failed for dataset 'VaultStoreDetailsByArchiveName' or
    'VaultStoreDetailsByBillingAccount'
       For more information about this error navigate to the report server on the
       local server machine, or enable remote errors

The problem occurred if a mailbox owner or the billing account of an archive was deleted from Active Directory.

This has been fixed.

FSAReporting IIS virtual directory was not created on reinstallation of an Enterprise Vault server [Ref 9039507, E2416437]

A problem could occur if you removed and reinstalled an Enterprise Vault server and specified the same SQL Server. If you had not removed the old database entries from the SQL Server, then when Enterprise Vault attempted to update them for the new configuration it failed to create the IIS virtual directory FSAReporting.

This has been fixed.

Changes to Windows Desktop Search support

Windows Desktop Search control panel did not list 'Symantec Vault Cache'

Windows Desktop Search control panel did not list 'Symantec Vault Cache' [Ref 9039698, E2425447]

In the Windows Desktop Search (WDS), the Indexing Options Control Panel did not list the Symantec Vault Cache even after enabling the WDS plug-in for Exchange Server archiving.

This has been fixed.

For information on how to enable the WDS plug-in, see the section 'Enabling Windows Desktop Search plug-in for Exchange Server archiving' in the Setting up Exchange Server Archiving guide on the Enterprise Vault media.

Changes to DTrace

Performance improvement to DTrace [Ref 9038514, E2318240]

DTrace performance has been improved when tracing Virtual Vault operations (DTrace option "StorageOnlineOpns") while many users were performing Virtual Vault operations.

Other changes

Fully qualified name of Exchange Server 2010 computer required in the EVPM command line [Ref 90310435, E2419793]

When running Enterprise Vault Policy Manager against Exchange Server 2010, you must specify the fully qualified domain name of the Exchange Server. The Exchange Server computer is specified using the -e parameter in the EVPM command line. For example,

EVPM -e ExchSvr1.evexample.local -m EVSvceMbx -f c:\ExchSvr1.ini

Policy Manager PST migration did not import unexpired calendar items [Ref 9039833, E2174084]

A new setting, ArchiveUnExpiredCalItems, allows Policy Manager to import unexpired calendar items from PST files. The setting can be added to the [PSTdefaults] or [PST] section in the Policy Manager initialization file. The default value of the setting is "false"; that is, unexpired calendar items are not imported. To import unexpired calendar items, add the setting to the initialization file and give it the value "true". For example,

[PSTdefaults]
ArchiveUnExpiredCalItems = true

If you choose to migrate unexpired calendar items, users must restore the items before they can modify them.

Enterprise Vault failed to archive messages with corrupt PR_SENDER_ENTRYID [Ref 9039908, E2437334]

Enterprise Vault failed to archive messages that had a corrupt PR_SENDER_ENTRYID. This corruption can occur when an external tool is used to migrate messages from Domino to Exchange Server.

This has been fixed.

Repeated event log errors 6727, 6796, 7264 [Ref 90310276, E2488831] [10]

In some circumstances it was possible for the following events to be logged every few minutes during archiving:

6727 (StorageCrawler) Abnormal error occurred
6796 (StorageCrawler) A COM exception has been raised
7264 (IndexServer) Abnormal error occurred

This has been fixed.

In some circumstances, the creation of new Enterprise Vault databases failed [Ref 9038526, 9038845, E2195720, E2342551]

In environments where the size of the model SQL database exceeded the default size of a new Enterprise Vault database, Enterprise Vault failed to create the new database.

This has been fixed. On the creation of a new database, Enterprise Vault compares the default size of the database with size of the model database, and creates the new database at the larger of the two sizes.

Additionally, Enterprise Vault used to create database log files with the extension mdf. Enterprise Vault now creates these file using the extension ldf.

Backup mode problem after failover in a building blocks configuration [Ref 9039274, E1596605]

When Update Service Locations had been used in a building blocks configuration it was sometimes not possible to set or clear the backup mode on a vault store.

Attempting to change the backup mode produced the error message "Could not set backup mode for vault store" and an event log entry that said "The parameter is incorrect".

This has been fixed.

Improvements to Storage File Watch [Ref 9030269, 90310412, E2523803, E2069020]

There have been some improvements to the Storage File Watch process.

Locked 'Updates.log' files prevented backup [Ref 90310030, E2371986]

Index locations could not be backed up because of locked 'Updates.log' files.

This has been fixed.

EVDominoExchangeMigration failed when the Exchange 2010 CAS role and Mailbox role were hosted on separate servers [Ref 9039337, E2364037]

The EVDominoExchangeMigration tool failed when it connected to an Exchange 2010 Mailbox server that did not also host the Exchange 2010 CAS role. In this case, EVDominoExchangeMigration displayed the following error:

Could not setup MAPI session [CTrawlerBase::CTrawlerBase] 0x80040201

This has been fixed.

Enterprise Vault installation restarted all Enterprise Vault services [Ref 9038696, E2331413] [10]

When you installed Enterprise Vault, Setup restarted all Enterprise Vault services, including those that had been stopped before running Setup.

This has been fixed. Setup restarts only those services that it has stopped.

Improvements to SQL housekeeping [Ref 90310677, E2189070]

There have been improvements to the resource management and locking behavior of SQL housekeeping stored procedures.

Event 6760 logging has been reduced [Ref 9039681, E2168430]

Occurrences of the following Storage Crawler event have been much reduced:

Event: 6760
Task Category: Storage Crawler
Error from EMC Centera FPLibrary
Function call: FPXMLTag.GetAttributeValue(AttachmentId)
Reason: Attribute with that name not found

Slow conversion for some PDF files with embedded graphics [Ref 90310213, E2330135]

Some PDF files with embedded graphics could take a long time to convert.

This has been fixed.

Mailbox archiving task produced errors when it encountered shortcuts from inaccessible Enterprise Vault sites [Ref 90310229, E2355306]

When the Mailbox archiving task encountered shortcuts from an inaccessible Enterprise Vault site, such as a withdrawn site, it stopped processing the mailbox and wrote the following error to the event log:

The EnterpriseVault.DirectoryConnection object reported an error.
0x800706ba
Internal references:
Error 0x800706ba
CDirectoryConnectionObject::GetArchiveFolder .\DirectoryConnectionObject.cpp
[lines {3567,3574}], built Mar 14 10:55:02 2011
For more information, see Help and Support Center at
http://evevent.symantec.com/rosetta/showevent.asp

This has been fixed. These events are no longer written to the event log, and the task continues to process the remaining items in the mailbox.

Improved error checking when writing to Centera [Ref 90311203, E2578306]

The error checking when writing to Centera has been improved.

DeleteEmptyFolders registry value could affect SQL performance [Ref 90310331, E2425326]

It was possible for the Storage service to cause SQL performance problems when the DeleteEmptyFolders registry value was used.

This has been fixed.

Getting Started Wizard maximum domain length was 32 characters [Ref 90310776, E2534795]

It was not possible to use the Getting Started Wizard to add an archiving target when the domain name was longer than 32 characters.

This has been fixed.

Possible memory leaks in StorageOnlineOpns or Retrieval task [Ref 90310979, E2567760, E2004232]

In some circumstances it was possible for there to be memory leaks in the StorageOnlineOpns process or the Retrieval task process.

These have been fixed.

Exchange Browser Search appeared to empty a basket that was not open [Ref 90311088, E2565836]

In Exchange Browser Search, if you tried to empty a basket that was not in the Open state, a page appeared saying incorrectly that the basket had been emptied.

This has been fixed. A message now says that the operation only works on an open basket.

Database backup status warnings ignored differential backups [Ref 9039907, E2428292]

Enterprise Vault failed to take into account differential backups when calculating the time since the last backup of a database. Warning and critical status messages could therefore be generated for the time since the last backup, despite the existence of a differential backup within the threshold period. This problem affected Enterprise Vault Operations Manager as well as the Enterprise Vault performance monitoring messages that appear in the event logs and in the Status pane of the Administration Console.

This has been fixed. Enterprise Vault now monitors the time since the last full backup or differential backup.

Storage crawler errors reported after starting Indexing service [Ref 9038603, E2342535] [10]

After starting the Indexing service on a very busy Enterprise Vault server, many repeated error messages were sometimes reported in the event log. The error messages were similar to the following:

STORAGE CRAWLER - Error
Could not create an EnterpriseVault.DirectoryConnection object.
436C617373466163746F72792063616E6E6F7420737570706C792072657...
STORAGE CRAWLER - Error
Abnormal error occurred
Object:    CVaultCache
Reference: RE(1)/fe
...
STORAGE CRAWLER - Error
Abnormal error occurred
Error:     Catastrophic failure  (0x8000ffff)
Reference: CArchiveCrawler::SetContext
Info:      Requestor - Indexing Service
           11478D37F55DD9244BCBF295C76C269D51110000vault
           example\VSA
...

This has been fixed.

Users could not delete shortcuts to archived items which had no Subject field [Ref 90310173, E2327551]

Although it was possible to archive mail items which had no Subject field in their headers, users who tried to delete them found that only the archived item was deleted, the shortcut remained in the mailboxes.

This has been fixed.

Some Enterprise Vault backup mode PowerShell cmdlets processed the wrong site [Ref 9039650, E2226963, E2253862] [10]

In some circumstances, Enterprise Vault's backup mode PowerShell cmdlets completed the requested actions on the wrong Enterprise Vault site in multi-site environments, and failed to report that a site didn't exist if an invalid site was specified.

This has been fixed.

Setting or clearing backup mode did not work in a Building Blocks environment [Ref 9039815, E2409426]

After running Update Service Locations (USL) in a Building Blocks configuration, attempting to set or clear backup mode on vault stores sometimes failed. This could occur if there were multiple concurrent Administration Console sessions. If you ran USL in one session, cached location data in the other session was not updated until the Vault Store Group was refreshed (F5), or the Administration Console was restarted.

This has been fixed.

Manual repair of incorrect archive ID [Ref 90310117, E2083525]

The Enterprise Vault provisioning task can repair an out-of-date or corrupt archive ID in the mail file or database. These repairs used to take place automatically but you now have manual control of when the provisioning task performs the repairs.

See the descriptions of DominoSynchMigratedMailFiles and DominoRepairMissingDefArchiveID in the Registry Values manual.

Server installation no longer includes Outlook Add-In [Ref 9039871]

The Outlook Add-In is no longer installed automatically when you install the Enterprise Vault server kit.

If you require the Outlook Add-In on an Enterprise Vault server, install the Outlook Add-In from the Enterprise Vault media.

Legal notice

Copyright © 2011 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