Last updated: 27-Mar-2012
This document describes the changes introduced to Enterprise Vault 9.0 by:
Note that some of the information in this document may have been superseded
by the changes described in the Enterprise Vault 9.0.4 document (Updates_en.htm) which describes the changes introduced in Enterprise Vault 9.0.4. For the most up-to-date version of
that document, see
http://www.symantec.com/docs/TECH147785
on the Symantec Enterprise Support site.
This section describes the changes introduced in Enterprise Vault 9.0.3 (service pack 3 for Enterprise Vault 9.0).
Enterprise Vault 9.0.3 provides the following new features:
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 introduces support for IPv6. Note the following restrictions:
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.
Enterprise Vault provides the following support for Domino Server 8.5.2 and Lotus Notes 8.5.2 clients:
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.
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.
This release includes Outside In® Technology version 8.3.7 content converters from Oracle® Corporation.
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.
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.
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:
Windows XP SP3 is the new minimum version that is supported for use with the following:
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.
To obtain the changes described in this section, the Enterprise Vault 9.0.3 Outlook Add-Ins must be installed.
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:
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.
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.
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's advanced Exchange desktop policy, Deploy Forms Locally, failed to delete locally deployed forms when set to Delete.
This has been fixed.
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.
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.
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.
There was a delay when deleting Outlook items when both the following were true:
This has been fixed.
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.
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.
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 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.
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.
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.
The Enterprise Vault Outlook Add-Ins caused an appreciable delay to Outlook start-up for users connected by VPN.
This has been fixed.
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.
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.
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.
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 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.
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 using Enterprise Vault browser search, even though they could be deleted using both Outlook and Enterprise Vault Archive Explorer.
This has been fixed.
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.
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 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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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.
Users did not see the 'Enterprise Vault Search Cache' menu option when Vault Cache was enabled.
This has been fixed.
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.
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.
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.
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.
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 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.
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, 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.
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:
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 performance and deadlocking have been improved when updating the metadata of archived items.
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.
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.
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.
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.
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.
Email messages that contained invalid surrogate pair characters could not be archived.
This has been fixed.
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.
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.
Under some circumstances Enterprise Vault processes could terminate unexpectedly while creating shortcuts.
This has been fixed.
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:
Special database object cannot be located
In some circumstances it was possible for shortcut bodies to be removed when you used the EVDominoExchangeMigration tool.
This has been fixed.
The Domino archiving task archived items repeatedly when the following were true:
ARCHIVENOW="true".This has been fixed.
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.
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.
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.
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 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.
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.
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.
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 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
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.
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.
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.
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.
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.
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.
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.
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.
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.
As a result of more efficient use of file locking during collections, the performance of Enterprise Vault file collection in partitions has been improved.
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.
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.
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.
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, 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.
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.
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.
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.
There have been some optimizations to database access by the StorageCrawler process.
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.
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. Items from the subfolder were placed in the root of the archive rather than in a separate archive folder.
This has been fixed.
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.
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.
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'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.
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.
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.
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.
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.
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.
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.
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.
The synchronization performance has been improved for folders and archives that have not changed.
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:
HKEY_LOCAL_MACHINE
\SOFTWARE
\KVS
\Enterprise Vault
\FSA
On a 64-bit installation of Windows:
HKEY_LOCAL_MACHINE
\SOFTWARE
\Wow6432Node
\KVS
\Enterprise Vault
\FSA
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.
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.
When SharePoint has KnowledgeLake Imaging installed, archiving failed with the following error:
Error listing folders.
This has been fixed.
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.
The Content Type/Metadata tab in the Metadata Rules page retained old values when you cleared the fields.
This has been fixed.
The Enterprise Vault StorageOnlineOpns process could become unresponsive during SharePoint Indexing with a 64-bit version of SharePoint.
This has been fixed.
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 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.
It was not possible to use Office Web Apps to open Enterprise Vault shortcuts.
This has been fixed.
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.
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. Those items were archived successfully the next day.
This has been fixed.
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.
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.
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.
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.
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.
DTrace performance has been improved when tracing Virtual Vault operations (DTrace option "StorageOnlineOpns") while many users were performing Virtual Vault operations.
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
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 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.
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 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.
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.
There have been some improvements to the Storage File Watch process.
Index locations could not be backed up because of locked 'Updates.log' files.
This has been fixed.
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.
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.
There have been improvements to the resource management and locking behavior of SQL housekeeping stored procedures.
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
Some PDF files with embedded graphics could take a long time to convert.
This has been fixed.
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.
The error checking when writing to Centera has been improved.
It was possible for the Storage service to cause SQL performance problems when the DeleteEmptyFolders registry value was used.
This has been fixed.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
This section describes the changes introduced in Enterprise Vault 9.0.2 (service pack 2 for Enterprise Vault 9.0).
Enterprise Vault 9.0.2 provides the following new features:
The following table describes the new Report and Verify facilities that are available in the latest version of EVSVR.
| Operation | Contents | Option | Action |
|---|---|---|---|
| Report | Directory | ArchiveCount | For the selected vault store, counts the number of Archive records and ArchiveFolder records. |
| Archives | For the selected vault store, lists the Archive records and ArchiveFolder records. | ||
| Directory and VaultStore | ArchiveCount | For the selected vault store, counts the following:
|
|
| Archives | For the selected vault store, lists the following information:
|
||
| VaultStore | ArchiveCount | For each vault store, counts the number of ArchivePoint (Archive) records and Vault (ArchiveFolder) records in the vault store database. | |
| Archives | Provides the following information for the ArchivePoint records and
Vault records in the vault store database:
|
||
| Verify | — | Archives | Performs an ArchivesDirectory Verify operation, followed by an ArchivesVaultStore Verify operation. |
| — | ArchivesDirectory | Verifies that the vault store database records have corresponding records
in the Directory database:
|
|
| — | ArchivesVaultStore | Verifies that the Directory database records have corresponding records
in the vault store databases:
|
The following options were redundant, and they are no longer available.
| Operation | Contents | Option |
|---|---|---|
| Report | Fingerprint | ContainerCount |
| EVContainerCount | ||
| Containers | ||
| EVContainers | ||
| EVVaultStoreObjects | ||
| VaultStore | ContainerCount | |
| EVContainerCount | ||
| Containers | ||
| EVContainers | ||
| EVVaultStoreObjects |
There is a new Outlook advanced setting named Use proxy settings in the Exchange desktop policy. Use proxy settings controls whether the Outlook Add-Ins use the Internet Explorer proxy settings on the client computer. The default is to use the proxy settings.
If users find that unarchived emails are previewed or opened slowly, you may wish to override the default so that the Outlook Add-Ins do not use the Internet Explorer proxy settings.
The new registry value InternetOpenTypeDirect performs the same function as Use proxy settings. The location of InternetOpenTypeDirect is:
HKEY_CURRENT_USER
\SOFTWARE
\KVS
\Enterprise Vault
\Client
InternetOpenTypeDirect contains a DWORD with the following possible values:
If you are using an Enterprise Vault 9.0.2 Outlook Add-In with an earlier version of the Enterprise Vault server, you need to use the registry value InternetOpenTypeDirect on each client if you want to change this policy setting.
There are new options in the EVSPShortcutManager utility:
-recall option to replace shortcuts with the corresponding documents in a site, collection, or library.-norecurse option to prevent processing a subsite.For a description of EVSPShortcutManager, see the Utilities manual.
Most of the information in the Enterprise Vault manuals is now available online as articles on the Symantec Enterprise Support site. You can access these articles by searching the Internet with any popular search engine, such as Google, or by following the procedure below.
To access the "How To" articles on the Symantec Enterprise Support site
Connections to Exchange Server may fail when you use Outlook 2007 on a busy Enterprise Vault server.
For information about this issue and a Microsoft Outlook 2007 hotfix that provides a solution, see the section Connections to Exchange Server may fail when you use Outlook 2007 on a busy Enterprise Vault server under Exchange archiving issues in the ReadMeFirst for Enterprise Vault 9.0.
We recommend that you apply the Microsoft hotfix if you encounter this issue, but the minimum required versions of Outlook are unchanged in Enterprise Vault 9.0.2. The minimum Outlook versions supported on the Enterprise Vault server are described under Points to note in the ReadMeFirst for Enterprise Vault 9.0.
If you are using Lotus Domino server 8.5.1 Fix Pack 4 or Fix Pack 5 on the Enterprise Vault Domino Gateway (EVDG), Lotus Notes users may be unable to retrieve an archived item by clicking the link to view the original item. Users can still retrieve the item by double-clicking it.
This issue does not occur with Lotus Domino server 8.5.1 Fix Packs that are earlier than Fix Pack 4.
To fix this issue, you need to obtain a hotfix from IBM and apply it on each EVDG. The hotfix applies only to Fix Pack 5, so if you are using Lotus Domino server 8.5.1 Fix Pack 4, you must upgrade to Fix Pack 5 and then apply the hotfix.
The hotfix details are:
The Enterprise Vault 9.0.2 FSA Agent requires the Microsoft Visual C++ 2005 redistributable package as an additional prerequisite. If you use the Install FSA Agent wizard to install or upgrade the FSA Agent, the wizard installs the required Visual C++ packages automatically. If you perform a manual installation or upgrade of the FSA Agent, you must install the required Visual C++ packages, as described in Setting up File System Archiving and Upgrading to Enterprise Vault 9.0.2.
The following is an important change that applies to Enterprise Vault 10.0, which is the next main release of Enterprise Vault.
In Enterprise Vault 10.0, Enterprise Vault servers require Windows Server 2008 R2 and 64-bit hardware. For information about migrating to 64-bit hardware before you upgrade to Enterprise Vault 10.0, see Migrating Enterprise Vault 9.0 to 64-bit hardware at http://www.symantec.com/docs/TECH141481.
To obtain the changes described in this section, the Enterprise Vault 9.0.2 Outlook Add-Ins must be installed.
This issue applied to Outlook 2010 and could occur in the following cases:
When the issue occurred, Outlook displayed a message that included the following text:
Your server administrator has limited the number of items you can open simultaneously. Try closing messages you have opened or removing attachments and images from unsent messages you are composing.
After the user cleared the message, Outlook required a restart.
This has been fixed.
This issue applied to Outlook 2010 when Outlook was in Cached Exchange Mode.
If the user selected a search folder and clicked Open in New Window on the View tab or on the context menu, Outlook stopped responding.
This has been fixed.
This issue applied to Outlook 2003/2007 when Outlook was in Cached Exchange Mode and the user had selected the option to work offline.
If the user tried to delete archived or unarchived items by pressing the Delete key or Ctrl + D, the attempt failed and Outlook displayed the following message:
The operation cannot be performed because the connection to the server is offline.
This has been fixed.
If end users upgraded the Outlook Add-In to Enterprise Vault 9.0.1 by running the Outlook Add-In .msi file on their own computers, Virtual Vault no longer appeared in the Outlook Navigation Pane. Users had to open the Vault Cache Properties dialog box and select the vault again on the Virtual Vault tab.
This has been fixed.
In some circumstances, users could not archive items manually after their mailboxes were moved from Exchange Server 2003 to Exchange Server 2007. The attempt failed with the following error message:
You cannot archive items from this location.
This has been fixed.
This issue occurred when:
The result of this issue was that the folders below the folder that contained the shortcut or shortcuts were deleted. The expected behavior is that no folders are deleted.
This has been fixed.
Following the upgrade to Enterprise Vault version 9.0.1, DWA users could not retrieve attachments from mail items that had not been archived.
This has been fixed.
After Enterprise Vault had archived any of the following types of messages, users could not view, reply to, or forward them:
This has been fixed. However, there are some limitations, which are determined by the version of Microsoft Exchange Server and Microsoft Outlook in your environment.
The version of Microsoft Outlook on the Enterprise Vault server imposes the following limitations in this Exchange Server environment:
The following limitations apply in these Exchange Server environments when an archived receipt message is opened:
This behavior differs from normal Entourage behavior, but it is identical to that of Outlook on Windows.
In some circumstances, the changes made by the SetEVThrottlingPolicy.ps1 script provided with Enterprise Vault 9.0 may not have prevented Exchange 2010 archiving tasks from being throttled.
This has been fixed. You must re-run this script in all Enterprise Vault environments that were previously upgraded to Enterprise Vault 9.0.0 or Enterprise Vault 9.0.1.
For more information, see the section called Configuring the Exchange 2010 throttling policy on the Vault Service account in Installing and Configuring.
In some circumstances, particularly during heavy processing, one or more of the following Enterprise Vault functions could fail:
This has been fixed.
Attempted access to Exchange calendar items could make the Storage Online process fail. The following message appeared in the event log:
Event Type: Warning Event Source: Enterprise Vault Event Category: Storage Event ID: 6654 Description: Online Process (1) - Restarting failed process The process has failed abnormally and will be restarted automatically. Exit Code: 0xc0000374
The issue occurred, for example, when moving archives to remote sites.
This has been fixed.
In some circumstances, multiple copies of non-mail items, such as calendar appointments and tasks, appeared in users' archives. This happened when users moved either folders that contained non-mail items or individual non-mail items in their Inboxes.
This has been fixed.
In Enterprise Vault 8.0 SP2, Enterprise Vault incorrectly marked Exchange mailbox root folders as having moved. This had no effect until an upgrade to Enterprise Vault 9.0.1, after which Enterprise Vault treated all the folders in these mailboxes as moved. For each folder that contained shortcuts, Enterprise Vault then generated a "process moved items" request in the Exchange Mailbox task MSMQ A6 queue. The result was a performance drain on the Exchange Mailbox task and a backlog of items on the A6 queue, with delays to the update of legitimately moved items.
The problem did not affect mailboxes that Enterprise Vault enabled in releases after Enterprise Vault 8.0 SP2.
This has been fixed.
In some circumstances, when the Enterprise Vault journal archiving task encountered an Active Directory contact in a distribution list, it wrongly treated it as another distribution list rather than an individual contact.
When this happened, Enterprise Vault wrote the following error to the event log:
Event: 3257 Source: Enterprise Vault Category: Journal Task User: N/A Computer: evsrv1.ev.local Description: Failed to open distribution list [(null)].
This has been fixed.
In some circumstances, the Enterprise Vault journal archiving task failed during the expansion of distribution lists.
This has been fixed.
If you target Exchange 2010 servers, and any of the messages that you archive contain hidden users or distribution lists, see http://www.symantec.com/docs/TECH154813 on the Symantec Support Web site for additional configuration information.
For information about an IBM hotfix that is required if you are using Lotus Domino server 8.5.1 Fix Pack 4 or Fix Pack 5 on the Enterprise Vault Domino Gateway, see Lotus Domino server 8.5.1 Fix Packs 4 and 5 on the Enterprise Vault Domino Gateway: mandatory hotfix in this document.
The Domino Provisioning task synchronizes certain ACL entries on a mail file to the associated archive. Users with access to the mail file also have access to the associated archive. Access permissions are assigned by means of a specific username ACL entry, or membership of a person, or mixed group ACL entry.
The registry setting DominoProvisioningACLSyncFilters lets you specify the names of Domino users or groups whose mail file ACL entry you do not want synchronized automatically to the associated Enterprise Vault archives.
Details of this setting are provided in the Agents section of the Registry Values manual.
In some circumstances, the Domino Archiving task continued to process mailboxes when there were no items to archive. The task continued processing until the end of the scheduled window.
This has been fixed. The Domino Archiving task stops when there is no more work to do.
When a Domino server had been added to the Enterprise Vault site as the preferred Domino server, administration operations failed when that server was not available.
The problem affected Domino-related Administration Console operations and archiving.
This has been fixed.
When a server had no Internet connection the Administration Console could take a long time to show the task list.
This has been fixed. By default, the Task Controller does not check for publisher certificate revocation.
The check is controlled by an entry in the file TaskController.exe.config in the
Enterprise Vault program folder.
If you want to force the Task Controller to check for certificate revocation, do the following:
TaskController.exe.config.TaskController.exe.config.<generatePublisherEvidence enabled="false"/>
<generatePublisherEvidence enabled="true"/>
An Enterprise Vault Storage server could become unresponsive when restoring items that were larger than 4 MB.
This has been fixed.
The New Partitions wizard now includes the Oracle Sun ZFS Storage Appliance in the list of supported devices.
A corrupt CAB file could cause EVSVR to terminate unexpectedly with the following event log entry:
Event : 1000 Source : Application Error Category : (100) Description: Faulting application evsvr.exe, version 8.0.4.1991, faulting module EVCabinet.dll, version 8.0.4.1991, fault address 0x0001e32b.
The unexpected termination also prevented restorations because StorageRestore.exe
also terminated unexpectedly with the following event log entry:
Event : 1000 Source : Application Error Category : (100) Description: Faulting application StorageRestore.exe, version 8.0.4.1991, faulting module EVCabinet.dll, version 8.0.4.1991, fault address 0x0001e32b.
This has been fixed.
A problem occurred when a user other than the original owner recalled a PowerPoint 97-2003 .PPT file from a placeholder, but did not modify the file. When Enterprise Vault reverted the file to a placeholder, subsequent attempts by any user to recall the file failed and generated the following warning in the Enterprise Vault event log:
Event Type: Warning Event Source: Enterprise Vault Event ID: 6287 Description: Unable to fetch item from <computer> Reason: Catastrophic failure [0x8000ffff] Archive name: <archive> Archive Folder Path: <path>
The problem occurred because PowerPoint changes the file size but not the modified date and time value when the user information for the file changes. Since the modified date and time value is unchanged, Enterprise Vault reverts the file to a placeholder without re-archiving the file. There was then a mismatch between the file size recorded in the new placeholder and the file size of the original archived file. The file size mismatch produced the error on any further attempt to open the file.
This has been fixed, by resolving the file size mismatch.
Previously, a File System Archiving task did not run if any of its target file servers were unreachable.
Now, the File System Archiving task logs the details of any unreachable file servers and processes the target volumes of the reachable file servers.
For an archiving run, the File System Archiving task records the details of the unreachable file servers in the summary section of the File System Archiving report, and also in the event log. For archive permissions synchronization, file version pruning, and deletion of archived files after placeholder deletion on EMC Celerra devices, the task records an error in the event log only.
Configuring File System Archiving on a clustered Windows 2008 file server where the resource group contained a GUID partition table (GPT) initialized disk could result in failover and performance issues. This issue was documented in the following technical note on the Symantec Support Web site:
http://www.symantec.com/docs/TECH135458
This has been fixed.
As a result of changes to the way the converted content of attachments is stored on Centera devices, the number of small blobs created has been reduced. As a result, retrieving items from Centera devices is now more efficient.
The SharePoint archiving report showed incorrect information for 'Total old items ready to be removed' and 'Estimated space saved after removing old items' in report mode.
This has been fixed.
If the file web.config was missing from the IIS Web site, installation of the Enterprise Vault Web Parts could fail.
This has been fixed.
A problem occurred if you attempted to create an FSA Reporting database on SQL Server 2008 R2.
Enterprise Vault created the database, but the Administration Console wizard failed and displayed the following error:
Enterprise Vault failed to create this FSA Reporting database: Database: <name> On SQL Server: <name> Reason: Unspecified error
This has been fixed.
The Deployment Scanner did not detect 64-bit versions of VERITAS Cluster Server (VCS).
This has been fixed.
Various enhancements to Enterprise Vault have improved Enterprise Vault robustness and performance, especially in relation to the following:
In some circumstances, the following stored procedures used by Enterprise Vault auditing caused high CPU utilization:
spEvAuditGetVaultIDIf you use Enterprise Vault auditing and these stored procedures show high CPU utilization, use the following procedure to upgrade the audit database schema:
EnterpriseVaultAudit database.C:\Program Files\Enterprise Vault), locate the SQL script called Audit_Schema_Upgrade.sql.db_owner credentials, run Audit_Schema_Upgrade.sql against the EnterpriseVaultAudit database.It was possible for archived items to remain in a 'pending' state because of a StorageFileWatch process failure. When this happened, the event log contained the following error:
Source: Enterprise Vault Event ID: 13360 Level: Error Description: Conversion failed when converting the nvarchar value '-1' to data type bit.
This has been fixed.
The following events have been added to the Enterprise Vault management packs for the MOM and SCOM monitoring tools:
| Code |
Type |
Identifier |
Text |
|---|---|---|---|
| 3422 | Error |
AGENTS_E_RUNNING_ACCOUNT_INVALID_ THROTTLING_POLICY_GENERIC | Exchange task associated mailbox has an invalid throttling policy applied |
| 45336 |
Error |
EV_DCC_E_DCS_NOT_AVAILABLE |
Data Classification
Client connection error |
| 45341 |
Error |
EV_DCC_E_DCS_NOT_CONFIGURED |
Data Classification
Client not configured |
| 41289 |
Warning |
EVMonJMbxNotScanned |
Domino: Journal mailbox not
scanned |
| 41290 |
Warning |
EVMonJMbxNotSubmitted |
Domino: Journal mailbox not
submitted |
| 41291 |
Warning |
EVMonExchMbxNotScanned |
Exchange mailbox not
scanned |
| 41292 |
Warning |
EVMonExchMbxNotSubmitted |
Exchange mailbox not
submitted |
See the Administrator's Guide for information on how to use MOM and SCOM with Enterprise Vault.
This section describes the changes introduced in Enterprise Vault 9.0.1 (service pack 1 for Enterprise Vault 9.0).
Enterprise Vault 9.0.1 provides the following new features:
Enterprise Vault 9.0.1 supports Outlook 2010 on end users' computers. Outlook 2010 requires the Enterprise Vault HTTP-Only Outlook Add-In. There are some differences between HTTP-Only Outlook Add-In behavior in Outlook 2010 and in Outlook 2003/2007. The differences are described in the section HTTP-Only Outlook Add-In functionality in Outlook 2010 under "Enterprise Vault Outlook Add-Ins issues" in the ReadMeFirst for Enterprise Vault 9.0.
If an end user's computer is running Outlook 2010, it is only possible to install the Enterprise Vault HTTP-Only Outlook Add-In. The Enterprise Vault installer prevents the installation of the Enterprise Vault Outlook Add-In.
If you install the Enterprise Vault 9.0.1 Outlook Add-In on Outlook 2003/2007 and later upgrade to Outlook 2010, you must then install the Enterprise Vault 9.0.1 HTTP-Only Outlook Add-In.
In Outlook 2010, the same Enterprise Vault options are available as in Outlook 2003/2007, but they have new icons and are in new locations.
The main Enterprise Vault features that a user sees in Outlook 2010 are as follows.
For information about how to control the availability and location of Enterprise Vault options, see the Enterprise Vault 9.0.1 Administration Console Help for the Exchange Desktop Policy: Options tab.
Enterprise Vault 9.0.1 supports Outlook 2010 conversation view. If an archived item exists in a Virtual Vault and also as a mailbox shortcut, Outlook controls whether the Virtual Vault item or the shortcut is shown in a conversation. The item that is shown depends on the folder in which the user views the conversation.
Enterprise Vault 9.0.1 includes a new command-line utility that enables you to manage the Enterprise Vault shortcuts that are in SharePoint. The new utility is EVSPShortcutManager.
You can use EVSPShortcutManager to replace HTML shortcuts with new shortcuts that behave exactly like SharePoint documents. The new shortcuts use the same icons as the corresponding original documents.
See the Utilities manual for details of EVSPShortcutManager.
Note that the Utilities manual does not describe the required permissions correctly.
For the correct permissions, see Permissions required for EVSPShortcutManager in the ReadMeFirst.
Four new alerts have been added to system status container in the Administration Console, as follows:
| Alert |
Threshold |
Frequency |
|---|---|---|
| Days since Exchange Journal
mailbox scanned for new items |
1 day |
Daily |
| Days since items archived from
Exchange Journal mailbox |
1 day |
Daily |
| Days since Exchange mailboxes
scanned for new items |
2 days |
Daily |
| Days since items archived from
Exchange mailboxes |
7 days |
Daily |
You may want to change the default thresholds and frequencies to match your own policies. To make changes, start the Administration Console and go to the Monitoring tab of Site Properties.
The Enterprise Vault SCOM management package is now provided as a sealed binary file. The file was sealed with the Symantec Enterprise Vault certificate.
See the Upgrade Instructions for details of how to apply the package.
In order to obtain the changes described in this section the Enterprise Vault 9.0.1 Outlook Add-ins must be installed.
In some circumstances, when you used the Outlook Calendar Overlay option to view items in the Virtual Vault calendar and items in the mailbox calendar, the Virtual Vault items were not visible.
If this issue occurred and the item was only in Virtual Vault, the appointment space was empty. If the Virtual Vault item had a corresponding mailbox item, only the mailbox item was shown.
This has been fixed.
Outlook contacts, calendar items, and tasks that had been archived and restored could not be archived again.
This has been fixed.
#%%%# within Virtual Vault caused Outlook to stop responding [Ref 9015376, E2146209]This issue occurred if a folder in Virtual Vault had a name that consisted of two hash (#) characters enclosing one or more percent (%) characters; for example, #%%%#. If you tried to copy the folder within Virtual Vault, the attempt caused Outlook to stop responding.
This has been fixed.
In rare circumstances the Enterprise Vault Add-Ins could cause Outlook to terminate unexpectedly.
This has been fixed.
The Enterprise Vault Outlook Add-In now adds a random element to the interval after which an unsuccessful scheduled Vault Cache synchronization is retried. In previous Enterprise Vault versions, the retry interval was fixed at 300 seconds (five minutes).
The random element is in the range one second to 300 seconds. So each retry is now performed after an interval that is between 301 seconds and 600 seconds.
This change means that when a number of users' scheduled Vault Cache synchronization requests occur simultaneously and are rejected, the requests are not retried simultaneously.
As in previous Enterprise Vault versions, the Vault Cache synchronization retry mechanism is invisible to users.
On Windows XP, if you upgraded the Enterprise Vault Outlook Add-Ins from Enterprise Vault 8.0 SP5 or earlier, folders could appear to be empty when viewed using offline Archive Explorer.
This issue is now very unlikely to occur. If you encounter this issue, see the section Offline Archive Explorer may not display contents of folders under "Enterprise Vault Outlook Add-Ins issues" in the ReadMeFirst for Enterprise Vault 9.0 for a solution.
In Enterprise Vault versions before 9.0.1, the search folders Could not archive and To archive were always visible in a Virtual Vault.
In Enterprise Vault 9.0.1, the folders are visible only if the Exchange Desktop policy allows the user to archive items in Virtual Vault, which depends on the Virtual Vault advanced setting Users can archive items.
If archiving is enabled and later disabled, then the Outlook Add-In hides the folders unless they contain results. If the folders contain results, the Outlook Add-In checks them at each Vault Cache synchronization and hides them when they are empty.
This section describes changes made since the October 2010 release of the Enterprise Vault Add-In for Outlook 2010. These changes are not relevant to any other previous release.
The October 2010 release of the Enterprise Vault Add-In for Outlook 2010 was supported in English only.
Enterprise Vault 9.0.1 supports the HTTP-Only Outlook Add-In in all the Enterprise Vault end user languages, with Outlook 2010 as well as Outlook 2003/2007.
This issue could occur when the Enterprise Vault Add-In for Outlook 2010 had been installed but Outlook 2010 did not have a connection to Exchange. There could be a delay, typically of 60 to 90 seconds, while Outlook added the Enterprise Vault Add-In.
This has been fixed.
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.1 Outlook Add-ins.
The Exchange desktop policy's Shortcut Deletion option controls the deletion of shortcuts in users' mailboxes, and the associated items in the archives. When this option was set to Both deleted or Ask User, and users deleted pending items from their mailboxes, Enterprise Vault's Outlook Add-Ins handled items pending deletion and restore differently from items pending archive.
On deletion of an item pending deletion or restore, Outlook Add-Ins treated the item as a shortcut and deleted both the pending item from the mailbox and any associated item from the archive.
On deletion of an item pending archive, Outlook Add-Ins allowed Outlook to delete the item from the mailbox.
Outlook Add-Ins now ignore all deletions of pending items from users' mailboxes, and the deletions are handled only by Outlook. Outlook Add-Ins do not delete any associated items from archives.
If an Outlook Add-In user used a shortcut to restore an item that was in a corrupt archive file, the restoration failed and the shortcut was deleted.
This has been fixed. If an item cannot be restored the shortcut is not deleted.
It was not possible to forward some archived items from Virtual Vault. The items had been migrated by third-party tools from Domino to Exchange Server and had then been archived from Exchange Server.
This has been fixed.
In OWA 2007, you could not view, reply to, or forward archived items that were encrypted or signed. When you attempted to open the shortcut to one of these items, the following warning was displayed:
The content cannot be displayed because the S/MIME control is not available. You may install the control by going to Email Security options page in the main window.
However, enabling the S/MIME control did not resolve the issue.
This has been fixed.
In some circumstances, users could not retrieve Domino 8.0 items from their archives. This happened in the following circumstances:
At this point, Lotus Notes displayed the following error:
The linked document cannot be found in the view
This has been fixed.
Lotus Notes users who tried to set a follow-up flag on shortcuts in their mail files saw the following error:
Object variable not set
This has been fixed.
When an iNotes user viewed an archived item that contained an embedded image, the image may not have been shown correctly, as follows:
This has been fixed.
Users could not log in to the Enterprise Vault client for Mac OS X if the Exchange server for their Entourage account had the Autodiscover service turned off. The Autodiscover service is turned on by default on Exchange 2007 and Exchange 2010 CAS servers.
This has been fixed.
If the email address that you specified in your Entourage account settings was not your primary SMTP address, you could not log in to the Enterprise Vault Client for Mac OS X.
This has been fixed.
If a user name in the Mailbox field in the Archive Explorer Settings dialog box contained an underscore (_) character, this issue occurred after the following actions:
The commands incorrectly remained disabled, even though the default setting applied.
This has been fixed.
The first time a user tried to use Archive Explorer to restore an item to a mailbox the restoration failed with the following error:
Failed to copy item Reason :- Creation of the basket by the Shopping Service failed. Ask the Enterprise Vault Administrator to check the Shopping Service configuration.
The failure affected only users who had never restored an item to a mailbox before, so an individual user never saw this problem more than once.
This has been fixed.
Changes introduced in Exchange Server 2010 prevented Enterprise Vault from accessing information about hidden Exchange 2010 mailboxes. This had the following effects:
This has been fixed, and Enterprise Vault handles hidden Exchange 2010 mailboxes the same as those in earlier versions of Exchange with one limitation. Custom filtering does not match recipients in distribution lists that are hidden from the address book.
The Exchange public folder policy's two Lock options (Archiving Actions tab) were ignored by Enterprise Vault. Even when these locks were cleared, users were unable to change the associated Delete original item after archiving and Create shortcut to archived item after archiving options in Outlook.
This has been fixed.
It was possible for some items imported from a PST to be archived but not to show the Enterprise Vault shortcut icons.
The PST import generated the following event log entry:
Event Type: Error Event Source: Enterprise Vault Event Category: Migrator Server Event ID: 6469 Description: An exception has occurred. [Internal reference CMigrator/PI/e]
This problem appeared in the following circumstances:
This has been fixed.
When the 'Name' field in the properties of a PST file was blank, importing from that PST could product a series of mail folders with names such as PST35_1.db, PST35_2.db, and so on.
This has been fixed. If the 'Name' field is blank, Enterprise Vault creates a folder name from the original PST file name.
The underlying functionality of Domino item retrieval has been changed.
Previously, when a user retrieved a Domino item from the archive, Enterprise Vault retrieved it to a temporary database on the Enterprise Vault Domino Gateway.
Enterprise Vault now retrieves Domino items to users' mail files.
Note that Enterprise Vault always retrieves items to users' mail files on the server, and not to users' local replicas. This might cause a discernible change to resource utilization patterns on the Domino servers.
Domino custom filtering rules with the action MARK_DO_NOT_ARCHIVE left matching items unencrypted in the journal mailbox.
This has been fixed.
When running the NSF migrator wizard on a 64-bit system, the wizard stopped working after you selected the NSF file that you wanted to migrate to Enterprise Vault. A Windows error was displayed.
This has been fixed.
A Notes user who tried to restore an archived calendar or task item received the error message 'Please select at least one archived message and try again'.
This has been fixed. It is now possible to restore archived calendar and task items.
When a user tried to restore an item to an over-quota mail file, Lotus Notes displayed the following error:
Notes error: Unknown OS error
This has been fixed and Lotus Notes now displays the following error:
Notes error: Unable to write to database because database would exceed its disk quota
When custom filtering was configured for Domino journaling, addresses for mail-in databases that were included in distribution lists were not recognized. If a filter rule included the <DL> tag, and the specified distribution list included the address of a mail-in database, then the rule action was not applied to messages sent to the mail-in database.
This has been fixed.
In Exchange mailbox policies configured to archive based on age and quota, it was possible to clear the Delete original item after archiving option (Archiving Actions tab).
This option is required for Exchange mailbox policies configured to archive based on age and quota, and clearing the option in the Administration Console had no effect.
This has been fixed and it is no longer possible to clear the Delete original item after archiving option on any Exchange mailbox policies configured to archive based on age and quota.
During upgrade, this option is set automatically on all Exchange mailbox policies configured to archive based on age and quota.
It was not possible to use the following syntax to set Domino organization-level wildcard permissions on archives:
*/myorg
The workaround was to use the following longer format to set wildcard permissions:
*/O=myorg
This has been fixed.
In the Administration Console it was not possible to select the 'Restoring and Retrieval issues' trace.
This has been fixed.
You can now create vault store partitions on iTernity Compliant Archive Solution devices. Enterprise Vault supports WORM volumes only, and accesses the device using CIFS protocol.
For essential information about using iTernity Compliant Archive Solution with Enterprise Vault, see the following page on the iTernity Web site: http://www.iternity.com/faq-details/items/how-do-i-configure-ifsg-when-integrating-symantec-enterprise-vault-version-80.html
For the latest information on supported devices and versions of software, see the Enterprise Vault Compatibility Charts: http://entsupport.symantec.com/docs/276547
In some circumstances, the retrieval of file items directly archived into mailbox archives created by older versions of Enterprise Vault could fail.
This has been fixed.
The New Partitions wizard now includes EMC Celerra Unified Storage Platforms in the list of supported devices.
A problem could occur if Enterprise Vault single instance storage applied fingerprints to an item which it subsequently failed to store. In some circumstances this condition resulted in orphaned fingerprints that were incorrectly left in the fingerprint database.
When this issue occurred, an error including the text in the following example was written to the event log:
Event ID: 13360 Description: An error was detected while accessing the Vault Database ... Violation of PRIMARY KEY constraint 'PK_MemberTable_nnn'. Cannot insert duplicate key in object 'dbo.MemberTable_nnn'. SQL Command: uspi_10Fingerprints
This issue did not result in any data loss.
This has been fixed.
In some rare circumstances, users could not restore certain archived emails. They could open these emails, and they could restore other emails in the mailbox.
This has been fixed.
The location for temporary collection files for an EMC Centera partition could continue to fill up during archiving. This problem was due to inefficient SQL queries to the JournalArchive table in the vault store database.
This has been fixed. Modifications to the design of the JournalArchive table have greatly improved the query performance.
On upgrade to Enterprise Vault 9.0.1, Enterprise Vault updates the JournalArchive table of each vault store database. This contributes to the upgrade time for each vault store database, depending on JournalArchive table size. For more information, see the Upgrading to Enterprise Vault 9.0.1 document.
In certain circumstances, the Storage service failed when partitions were hosted on a Centera device that was configured without a replica. This happened when the vault stores to which the partitions belonged were configured to remove safety copies immediately after archiving.
When the Storage service tried to connect to a non-existent replica, error messages with the event ID 6759 were repeatedly reported in the event log.
This has been fixed.
The format of internet shortcut file names has changed.
Enterprise Vault now appends the .url suffix to the file's original suffix, instead of replacing the
original suffix. The new format
lets you identify the original file type from the internet shortcut name.
The following table gives examples of internet shortcut names before and after the format change.
| File name | Previous shortcut name | New shortcut name |
|---|---|---|
document1.docx |
document1.url |
document1.docx.url |
graphic.gif |
graphic.url |
graphic.gif.url |
file.txt |
file.url |
file.txt.url |
If you upgrade to Enterprise Vault 9.0.1, internet shortcuts that are created after the upgrade use the new name format.
Note that if you choose the Windows Explorer option "Hide known
file types", Windows displays the original file types for the new format internet shortcuts.
For example, the internet shortcut document1.docx.url appears as document1.docx.
The FSA Agent failed to install on a Windows Server 2008 read-only domain controller (RODC) with the following error:
Unable to add the user 'USERACCOUNT' to the local 'Administrators' group
on computer 'COMPUTERNAME'. The function failed with error 50
This problem occurred with both an installation from the Administration Console, or when running the MSI file locally on the file server. The problem occurred because the read-only status of an RODC prevents the installation from making the local changes for the user account.
To install the FSA Agent on a domain controller the following conditions are required:
These privileges must be set on the primary domain controller operations master.
If you perform the FSA Agent installation from the Administration Console, Enterprise Vault is able to set these privileges for the Vault Service account, provided that the account is a local administrator. For a local installation using the MSI file, you must grant these privileges before the installation can succeed.
Enterprise Vault's FSA Agent installation error handling has now been enhanced to provide more useful dialogs and error messages if the installation is unable to make local changes:
Under certain circumstances FSA allocated the same saveset ID to two or more files. The result was that the data for some of the files was lost. On placeholder recall, all of the related placeholders recalled just one of the files.
The problem could occur when all of the following conditions applied:
_ % [ ] ^ (underscore, percent symbol, square brackets,
or circumflex accent)
For example, the problem occurred with the following pairs of files:
| file a | file b | Notes |
|---|---|---|
abc-1.txt |
abc_1.txt |
The hyphen in file a could instead be any single character, for example d, or 9. |
abcnnn1.txt
|
abc%1.txt |
nnn in file a is any number of characters. |
abcn.txt |
abc[123].txt |
n in file a is any one of the characters
that is enclosed by square brackets in file b (1, 2, or 3, in
this example). |
abcn.txt |
abc[^123].txt |
n in file a is any one character that is not enclosed by square brackets in file b
(for example, 4 or y). |
This has been fixed.
A number of changes have been made to the FSAUtility placeholder migration
(-pm) option, to prevent some conditions that can result in unsuccessful migrations.
FSAUtility does not proceed with a placeholder migration and quits with an explanatory message unless it can confirm that the following conditions are met:
The utility now records in the Enterprise Vault event log the start and the completion of a migration. The completion message indicates whether the migration was successful.
If you attempt to repeat a failed migration, the utility indicates that a migration previously failed, and asks if you want to continue. Note that If a migration fails you should not archive from the destination folder. Retry the placeholder migration to see whether it can complete successfully.
For more information, see the updated description of the FSAUtility placeholder migration option in the Utilities guide.
An FSAUtility -b operation to recall items had a handle leak if
the recall was to an EMC Celerra device. The handle leak could cause performance
problems.
This has been fixed.
File Blocking's file content checking failed to recognize and block some MP3, MOV, and WMV media files if the file type extension was renamed.
This has been fixed.
File Blocking could stop unexpectedly if either of the following applied:
This has been fixed.
If you enabled File Blocking for media files, Enterprise Vault also blocked JPEG files.
This has been fixed.
Archived Outlook .MSG files sometimes failed to recall successfully from their placeholder shortcuts.
This has been fixed.
On Chinese and Japanese Enterprise Vault systems, the FSA New Folder wizard failed with the following error if you used an unedited copy of the Default FSA Volume Policy:
Failed to update the details for this folder in Directory Services. Access is denied.
This has been fixed.
In some circumstances, it was not possible to restore an archived version from SharePoint's version history.
This has been fixed.
In certain circumstances the footer of FSA Reporting's Summary reports displayed the text #Error, even though there was no error.
This has been fixed.
The following operation reports failed to run successfully on a 64-bit version of Microsoft SQL Server Reporting Services:
The reports displayed the message "An error occurred during report processing".
This has been fixed.
In some circumstances, in Enterprise Vault environments with more than one SQL server and no mixed collations, the Deployment Scanner's SQL collation test failed with the following connectivity error:
Unable to connect to at least one of the SQL servers listed. <SQL Server>: Database: EnterpriseVaultMonitoring - no mixed collations found.
This has been fixed.
The Deployment Scanner report now provides a warning for local disks that have less than 1 GB of free space.
Index repair operations failed after the IndexCheck tool was run. Index repair operations generated entries such as the following in the event log:
Event Type: Warning Event Source: Enterprise Vault Event Category: Index Server Event ID: 7309 Description: The sequence number read from the failed items log does not correspond to the Saveset ID specified in the file. The item will not be repaired.
This has been fixed. The IndexCheck tool has been corrected. If you have seen this problem, run the IndexCheck tool on the out-of-date indexes again and then index repairs will work.
This release includes Outside In® Technology version 8.3.5 content converters from Oracle® Corporation.
Improvements to authentication performance and SQL Server resource utilization have resulted in the following:
in some circumstances, after an upgrade from Enterprise Vault 2007 to Enterprise Vault 8.0 and then to Enterprise Vault 9.0, it was possible to receive event log errors from Storage File Watch. The errors relate to items that had not been fully processed before the upgrade to Enterprise Vault 8.0.
This has been fixed. The items' processing is now completed in Enterprise Vault 9.0.1.
In certain circumstances, the number of file types associated with archived items exceeded the maximum number of entries in the file specification table in the Enterprise Vault directory database. When this happened, archiving failed and Event ID 13345 and 13360 error messages were reported in the event log during an archiving run.
This issue occurred in the following situations:
File extension management has been enhanced. Enterprise Vault now normalizes file extensions where possible, to reduce the number of additional entries created in the file specification table.
This issue occurred in the following configuration:
overridearchivelocks=true.
Behavior has now been changed. If the default options are configured on the Moved Items tab of the Exchange Mailbox policy, and the destination folder was created with the Policy Manager [Folder] option, overridearchivelocks=true, then the following action is taken:
Note that when a folder is moved into another folder, only the items with shortcuts have their retention category updated.
When a message with an HTML body part was archived and retrieved using the Enterprise Vault Content Management API, the HTML body part was sometimes missing. This issue occurred if the message was archived using the Symantec Backup Exec Archiving Option (BEAO), and Outlook 2007 SP2 with security update KB980376 or KB2288953 was installed on the Enterprise Vault server.
This has been fixed.
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