Last updated: 30-Mar-2012
|
To download the latest version of this document and the other Enterprise Vault release notes, and to obtain Japanese and Chinese versions of these documents, see: http://www.symantec.com/docs/TECH147787. For the latest news about this release, including any hotfixes, subscribe to http://www.symantec.com/docs/TECH147788. |
This document describes the changes introduced in Enterprise Vault 10.0.1 (service pack 1 for Enterprise Vault 10.0).
Before installing or upgrading to Enterprise Vault 10.0.1, you must read this document and also the ReadMeFirst for Enterprise Vault 10.0. The ReadMeFirst lists current known issues and describes new features in the original release of Enterprise Vault 10.0.
For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
Enterprise Vault 10.0.1 provides the following new features:
Note: If you run the Enterprise Vault 10.0.1 Outlook Add-In with an Enterprise Vault server that is earlier than 10.0.1, you must apply a server hotfix. For details, see Enterprise Vault server hotfixes required to support the Enterprise Vault Outlook Add-In.
Enterprise Vault 10.0.1 includes a new Outlook Add-In that replaces the Outlook Add-Ins in previous releases. The main changes (subject to policy settings where appropriate) are as follows:
You no longer need to decide between installing the Outlook Add-In or the HTTP-Only Outlook Add-In on a user’s desktop. There is now a single unified Outlook Add-In which includes all functionality from both clients. There is a single Outlook Add-In installation for each supported language.
The Enterprise Vault 10.0.1 Outlook Add-In uses HTTP-based communication with Enterprise Vault servers. It can work in full mode or light mode. Full and light functionality correspond to the Outlook Add-In and the HTTP-Only Outlook Add-In in previous releases. The Enterprise Vault Outlook advanced setting Outlook Add-In behavior controls which mode applies to an Exchange desktop policy.
On Enterprise Vault servers earlier than version 10.0.1, Outlook Add-In behavior controls the Outlook Add-In mode correctly even though its values are still named Normal and HTTP-only (default). In Enterprise Vault 10.0.1, the values are named Full and Light. For information about Outlook Add-In behavior, see the Administrator's Guide.
When you restore archived items in Outlook Add-In full mode, you can now specify a destination folder. The option to specify a destination folder is available if the Enterprise Vault server version is 10.0.1, but not if the Enterprise Vault server is an earlier version with the hotfix applied.
The Enterprise Vault 10.0.1 Outlook Add-In can work in full mode or light mode with Outlook 2010. Previously, the Add-In for Outlook 2010 only provided what is now light functionality.
Outlook 2010 users working in full mode can now do the following:
Outlook 2010 users working in light mode can change the option to suspend Enterprise Vault archiving for a mailbox.
The Outlook Add-In supports full mode for Outlook in Outlook Anywhere mode (RPC over HTTP).
Outlook 2010 users can forward original items by forwarding multiple shortcuts. Previously, only the shortcuts were forwarded. Due to a known issue with Outlook, this action only works in Outlook 2010 in Cached Exchange Mode.
Outlook 2010 users can store entire folders. On the Enterprise Vault tab on the Outlook ribbon, you click the upper part of the Store button to store the selected items. The lower part displays the options Store selected items and Store selected folder.
The option to suspend Enterprise Vault archiving for a mailbox has moved from the mailbox Enterprise Vault Properties page to the Enterprise Vault - Change Properties dialog box.
The Store in Vault dialog box in full mode no longer includes options to delete original items or create shortcuts. These options are available in the Enterprise Vault - Change Properties dialog box for a folder.
The following features are no longer available:
Federal Information Processing Standards (FIPS) 140-2 is a standard for cryptographic modules in computer systems.
Enterprise Vault 10.0.1 uses a FIPS 140-2 validated cryptographic module to provide the required cryptographic functionality.
Note that at this release the Symantec Enterprise Vault Cryptographic Module is not used for indexing.
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 10.0.1 introduces support for IPv6. Note the following restrictions:
Enterprise Vault 10.0.1 introduces three new migrators that allow you to migrate infrequently accessed data to the cloud using the following storage solutions:
These migrators are installed as part of the Enterprise Vault 10.0.1 installation.
Enterprise Vault now supports File System Archiving, including placeholder shortcuts, for Windows file servers that run Vision Solutions' Double-Take replication software.
Enterprise Vault is compatible with the following Double-Take product:
For the latest information about supported versions, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
For more details of the support for Double-Take, including configuration information, see http://www.symantec.com/docs/TECH183398.
The Enterprise Vault Client for Mac OS X that is included with this release is supported for use on client computers that run Mac OS X version 10.7 (Lion), as well as on computers that run Mac OS X version 10.5 (Leopard) or 10.6 (Snow Leopard).
At this release, Enterprise Vault installs software identification tags (SWID tags) based on the ISO/IEC 19770-2:2009 standard. The tags enable asset management tools to identify systems that have Enterprise Vault 10.0.1 components installed.
There is a single application tag for Enterprise Vault 10.0.1. A component tag is installed with each of the Enterprise Vault 10.0.1 components. Details of the component tag files, and where they are installed, are given in the technical note http://www.symantec.com/docs/HOWTO74583 on the Symantec support Web site.
The Enterprise Vault SWID tag implementation complies with the normalization requirements established by the IEEE-ISTO organization, TagVault.org (http://www.tagvault.org). Full compliance with the TagVault.org implementation model is planned for a future release.
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:
If you plan to roll out the Enterprise Vault 10.0.1 Outlook Add-In to users before you upgrade the Enterprise Vault servers, you must apply a hotfix to the Enterprise Vault servers to avoid the restrictions listed below. There is a separate hotfix for each version of Enterprise Vault.
The links to the relevant technical notes and the hotfixes that are required to support the Enterprise Vault 10.0.1 Outlook Add-In with Enterprise Vault server 9.0/9.0.n/10.0 are as follows:
| Enterprise Vault server version | Link to technical note and hotfix |
|---|---|
| Enterprise Vault 9.0 (original release) | http://www.symantec.com/docs/TECH175938 |
| Enterprise Vault 9.0.1 | http://www.symantec.com/docs/TECH175939 |
| Enterprise Vault 9.0.2 | http://www.symantec.com/docs/TECH175940 |
| Enterprise Vault 9.0.3 | http://www.symantec.com/docs/TECH175941 |
| Enterprise Vault 10.0 (original release) | http://www.symantec.com/docs/TECH175942 |
The following restrictions apply to the Enterprise Vault 10.0.1 Outlook Add-In if you have not installed the appropriate hotfix on Enterprise Vault servers that have not been upgraded:
Enterprise Vault provides the following support for Domino Server 8.5.3 and Lotus Notes 8.5.3 clients:
Data Classification Services uses various components of Symantec Enterprise Vault and Symantec Data Loss Prevention to automate the classification of Microsoft Exchange messages that are managed in Enterprise Vault. If you upgrade to Enterprise Vault 10.0.1, and you use Data Classification Services, you also need to upgrade your version of Data Loss Prevention. You can obtain the latest Data Classification Services components by going to the Enterprise Vault 10.0.1 page on Symantec FileConnect (https://fileconnect.symantec.com).
For the latest information on supported versions, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
The following changes have been made to the Enterprise Vault best practice settings:
The Enterprise Vault installation program checks whether the Enterprise Vault uses the best practice registry values. If not all the best practice registry values are set the installation program can set them automatically.
For information about the best practice settings, see the section "Best practice settings for Enterprise Vault servers" in the Installing and Configuring manual.
To obtain the changes described in this section, the Enterprise Vault 10.0.1 Outlook Add-In must be installed.
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.
The Enterprise Vault Outlook Add-Ins caused an appreciable delay to Outlook start-up for users connected by VPN.
This has been fixed.
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.
By default, the Outlook Add-In initiates 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-In does 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-In chapter in the Registry Values manual.
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.
Enterprise Vault's advanced Exchange desktop policy, Deploy Forms Locally, failed to delete locally deployed forms when set to Delete.
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.
Vault Cache synchronization could fail due to a timeout in the conversion of a large item in Virtual Vault. The item was archived, but it remained in the To Archive folder in Virtual Vault. Subsequent items were not uploaded and also remained in the To Archive folder. On the next synchronization the item was removed from the To Archive folder, though it was still not converted or indexed, and the other items were uploaded as expected.
This has been fixed. If a conversion timeout occurs, the item is archived and remains in the To Archive folder, as before. The Enterprise Vault Outlook Add-In now uploads the subsequent items. On the next synchronization the item is removed from the To Archive folder, though it is still not converted or indexed.
Note the following:
web.config file must be greater than the registry value ConversionTimeout to prevent the same item from being archived several times. For more information, see the ConversionTimeout section in the Enterprise Vault chapter of the Registry Values guide.The Enterprise Vault Outlook Add-In's Archive Explorer button should both open and close Archive Explorer. Users could successfully open Archive Explorer but, when they clicked the button again to close it, Outlook showed their folder list in the left pane, and Archive Explorer remained in the right pane.
This has been fixed. When Archive Explorer is open and users click the Archive Explorer button, Outlook returns to the previous view.
At the original release of Enterprise Vault 10.0 you could not upgrade from certain versions of Enterprise Vault 9.0.n Outlook Add-Ins to Enterprise Vault 10.0 Outlook Add-Ins.
The restriction applied to the following Outlook Add-In versions:
This restriction has been removed.
End users who install the 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 the Outlook Add-In in Setting up Exchange Server Archiving.
This issue occurred when you created a new mailbox in Exchange, added it as a provisioning target, and disabled the new mailbox.
When you ran the Disable Mailbox wizard, the following errors were written to the event log:
8390 The EnterpriseVault.DirectoryConnection object reported an error.
3196 An error has occurred whilst synchronizing the properties of mailbox mailbox_details on Exchange server server_name.
3188 An error occurred performing a request to synchronize the mailbox mailbox_details.
Also, when the Exchange mailbox archiving task ran, the following error was written to the event log four times for each disabled mailbox:
2302 Failed to locate the mailbox filter for the mailbox for mailbox_details, mailbox will not be processed.
A warning that starts as follows was often also written to the event log when the Exchange mailbox archiving task ran:
2270 A queued operation exceeded the retry count and has been discarded.
Processing a user mbx.
This has been fixed.
Enterprise Vault Add-In caused Outlook to fail when users of Firefox chose to subscribe to an RSS feed using Outlook.
This has been fixed.
In some circumstances, if a user opened an item from its shortcut in a public folder and tried to delete it using the Delete option on the message toolbar, the shortcut was not deleted and the message window did not close. If shortcut deletion in the Exchange desktop policy was set to Both deleted, the item was deleted from the archive and the shortcut was orphaned.
This has been fixed.
This issue occurred if an Outlook user who was not enabled for Enterprise Vault archiving (user A) had delegate access to the mailbox of a user who was enabled for archiving (user B). The issue caused the following problems for user A:
This has been fixed. User A now sees only the Search Vaults option, provided Search Vaults is enabled by the Exchange desktop policy for user B.
There was a delay when deleting Outlook items when both the following were true:
This has been fixed.
When you moved an Enterprise Vault shortcut to another Outlook folder, its retention category was not updated if the item was originally archived by one of the following methods:
This has been fixed.
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.
If the Outlook option In folders other than the Inbox, save replies with original message was selected, it did not work with Enterprise Vault shortcuts. (By default, this option is not selected.)
This has been fixed.
When users dragged Enterprise Vault shortcuts from their mailboxes to the Deleted Items folder in another message store, such as a PST file, the Outlook Add-In placed the items in the default Deleted Items folder in the users' mailboxes.
This happened when the Shortcut Deletion option on the Exchange Desktop Policy: Options tab was set to Shortcut Only or Ask User.
This has been fixed. Enterprise Vault now places the shortcut in the Deleted Items folder chosen by the user and, if the Shortcut Deletion option is set to Ask User, users are asked for their choice on the deletion of the archived item.
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.
In some circumstances, particularly in environments with elevated Internet Explorer security settings, the Enterprise Vault Outlook Add-Ins could cause Outlook 2007 to become unresponsive.
This has been fixed.
In some circumstances, users could not open archived items from shortcuts in a public folder if the Outlook option In folders other than the Inbox, save replies with original message was selected. (By default, this option is not selected.)
If this issue occurred, the following error was displayed:
This item cannot be displayed.
Additional information: You may need to install additional software to view items of this type or it may only be possible to display this item from the folder that contains this item.
This has been fixed.
This issue affected Outlook 2003/2007 users only.
If a user copied a calendar item by drag and drop, the Enterprise Vault Outlook Add-In caused a delay before the copy action completed.
This has been fixed. As a result of the fix, and by design, users can now always copy archived calendar items even if the Outlook advanced setting Allow shortcut copy in the Exchange desktop policy is set to its default value of Off.
In certain circumstances, duplicate entries were created in the vault cache. If this happened, the vault cache synchronization failed repeatedly. The client trace log reported that a folder contained more than one message with the same SNUM or SSID.
This has been fixed.
Deletion of archived items using the Outlook Delete button failed if Outlook was configured to use RPC over HTTP.
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.
Outlook 2010 users could not forward multiple original items by attaching Enterprise Vault shortcuts to an email. Instead, the shortcuts were forwarded.
This has been fixed, but note that due to a known issue with Outlook, forwarding the original contents of multiple shortcuts does not work in Outlook 2010 when the profile is not using Cached Exchange Mode. In this case, the shortcuts themselves are forwarded.
Occasionally, Vault Cache synchronization failed because of a missing folder property. The following error was written to the client log:
HDR:SYNC:ARC: Synchronization failed (std::exception):PSTCacheServerNewFolder being created on a folder that is missing PROP_EVSERVER_NEWFOLDER
This has been fixed.
This issue affected Outlook 2003/2007.
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.
In some circumstances, users could not open original items from Virtual Vault when the reading pane was enabled. This happened in both the following cases:
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 10.0.1 Outlook Add-In.
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.
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.
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 used the HTTP-Only Outlook Add-In to archive, restore or delete items in the results of an Outlook 2010 search, the operation could fail when the items were in different folders. This occurred if you normally logged in to Enterprise Vault but had not yet done so in that Outlook session.
This has been fixed.
In some circumstances, if you used Outlook Integrated search to search for two or more words, the search time increased if the words were adjacent to each other in the items that you searched. For example, a search for weekly meeting would find all items that contain both the word 'weekly' and the word 'meeting', but if items contained the two words adjacent to each other (for example 'weekly meeting' rather than 'weekly status meeting') then the search time might increase or the search might time out with the message Failed to perform search request.
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.
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.
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.
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 archiving and Create shortcut to archived item after archiving 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 archiving and Create shortcut to archived item after archiving in the Exchange Mailbox policy.
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.
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.
If the registry entry HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\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.
Sometimes the following warning message was displayed when a user attempted to forward a message from a mail file:
Unable to record which documents have been processed by the agent. Try making a replica of the database.
This issue could affect mail files that had the ev_mail85.ntf mail template applied.
This has been fixed.
Users did not see the 'Enterprise Vault Search Cache' menu option when Vault Cache was enabled.
This has been fixed.
When a retrieved item was opened in iNotes 8.5.2 it was not possible to change the follow-up flag or to use the delete option.
This has been fixed.
When a user's mail file was accessed by means of a database link, the user could not 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.
Enterprise Vault would create duplicate items in your Vault Cache in the following circumstances:
These issues have been fixed.
If users configured Outlook 2011 for Mac to use Kerberos authentication to connect to their Microsoft Exchange server, they could experience problems when they tried to log in to the Enterprise Vault Client for Mac OS X. The Account Information dialog box with which these users entered their login details for Enterprise Vault did not specify the correct domain and account ID information. Users who failed to correct this information could not log in to Enterprise Vault.
This has been fixed. When Outlook 2011 for Mac is configured to use Kerberos authentication, the Domain and Account ID fields in the Account Information dialog box are now empty, and users must enter the required information before they can proceed.
Note also that the format in which Enterprise Vault stores account credentials in the Mac OS X keychain has changed in version 10.0.1. The credentials are now stored in the keychain in XML format, like this:
<EnterpriseVault> <Domain>domain_name</Domain> <UserId>user_id</UserId> <Password>password</Password> </EnterpriseVault>
Users of earlier versions of the Enterprise Vault Client who stored their credentials in the keychain must resubmit them after they upgrade to Enterprise Vault 10.0.1.
Folders could appear to be empty when viewed using Archive Explorer on French and Italian systems while items were being archived.
This has been fixed.
When Archive Explorer's View archived items using option was set to Web browser, users could open an item, open a message attached to this item, then click Delete. This deleted not only the message attachment, but the parent item and any other items attached to it.
This has been fixed. The Delete button has been removed from message attachments opened in Archive Explorer.
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.
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.
Enterprise Vault automatically adds the new Task Application role to existing accounts that run Exchange Server tasks.
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.
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.
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.
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.
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.
The Exchange Provisioning task failed to process users who had a job title that was longer than 64 characters. Errors similar to the following were reported in the event log:
Type : Error
Date : 26/08/2011
Time : 06:29:52
Event : 13360
Source : Enterprise Vault
Category : Directory Service
User : N/A
Computer : EVServer1
Description:
An error was detected while accessing the Vault Database
'EnterpriseVaultDirectory' (Internal reference: .\ADODataAccess.cpp
(CADODataAccess::ExecuteSQLCommand) [lines {1392,1394,1409,1441}] built Oct 6
11:22:46 2010):
Description:
[Microsoft][ODBC SQL Server Driver][SQL Server]String or binary data would be
truncated.
SQL Command:
UPDATE ExchangeMailboxEntry SET
ExchangeMailboxEntryId=...
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.
Mailboxes whose names include the characters { or } (curly braces) were not archived. When this happened, the following error was written to the event log:
Event ID: 3361 Failed to determine the provisioning group for the mailbox /o=Example/ou=Exchange Administrative Group/cn=Recipients/cn=?G?Sales. |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 then run the provisioning task. |Error: The mailbox does not have an entry in the Enterprise Vault database. (0xc0040d1e)
In some circumstances, this issue also caused the Enterprise Vault mailbox archiving task to fail.
This has been fixed.
This issue affected the Enterprise Vault 9.0.1/9.0.2/10.0 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 cases, Exchange mailboxes can have two junk email folders with the same name but different capitalization, such as Junk E-mail and Junk e-Mail. In this case, Outlook uses only one of the folders as the special folder to which it directs mail identified as junk.
When this situation occurred, the Exchange mailbox archiving task wrote the following events to the event log:
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 10/06/2011 11:01:40
Event ID: 2243
Task Category: Archive Task
Level: Error
Keywords: Classic
User: N/A
Computer: evsrv1.example.com
Description: Could not scan user mailbox /o=SYMC/ou=Exchange Administrative Group
(SALES)/cn=Recipients/cn=jdoe, cannot list messages
Log Name: Symantec Enterprise Vault Source: Enterprise Vault Date: 10/06/2011 11:01:40 Event ID: 2270 Task Category: Archive Task Level: Warning Keywords: Classic User: N/A Computer: evsrv1.example.com Description: A queued operation exceeded the retry count and has been discarded
This has been fixed. Enterprise Vault now ignores the folder that is not Outlook's special junk email folder.
Enterprise Vault's Exchange journaling task wrote event ID 6469, "An exception has occurred", to the event log in environments where auditing was enabled.
This has been fixed.
In some environments where Enterprise Vault servers and Exchange servers were in different domains, the Exchange mailbox archiving task failed to connect to the local MSMQ queues on the Enterprise Vault server. This caused Exchange mailbox archiving to stall.
This has been fixed.
This issue occurred when all of the following conditions applied:
-BaseFolderOnly $true, which means that any subfolders should be treated as standard folders.This issue caused Enterprise Vault to treat the subfolders as managed folders, not as standard folders.
This has been fixed.
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:
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.
This has been fixed.
For a detailed description of the issue, see the document http://www.symantec.com/docs/TECH167223 on the Support Web site.
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.
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.
When neither of the following Domino archiving policy options was selected, the Domino archiving task archived large mail items repeatedly, once on each run of the task:
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.
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
Email messages that contained invalid surrogate pair characters could not be archived.
This has been fixed.
Under some circumstances Enterprise Vault processes could terminate unexpectedly while creating shortcuts.
This has been fixed.
When a non-English template that had been created by EVInstall.nsf was used, it was not possible for users to retrieve or restore archived items.
This problem was present in Enterprise Vault 9.0.1 and later.
This has been fixed.
Where the principal and delegate users are in different time zones, it was discovered that the created date of iCalendar invitation notices may be corrupt or missing. The Domino Journaling task was unable to archive such items, and reported error messages with the ID 41206 and 41058 in the event log.
This has been fixed. The Domino Journaling task now archives such items.
The issue is documented in the following technical note on the Symantec support Web site:
http://www.symantec.com/docs/TECH169575
When a user searches for archived content, the Enterprise Vault search application runs on the Enterprise Vault Domino Gateway. Previously, the search application ran on the Storage server.
The Domino Provisioning task failed to process a mail-in database file when it was added to a provisioning group as a member of a Domino directory group.
This has been fixed.
The Domino archiving task archived items repeatedly when the following were true:
ARCHIVENOW="true".This has been fixed.
The Domino Provisioning task failed to process mail-in database files that had multiple-line names. When such files were encountered, the provisioning report indicated that no mailboxes had been found.
This has been fixed.
In some circumstances, users could not retrieve some large items archived in versions of Enterprise Vault older than version 8.0. When this happened, users saw the following error message:
Network operation did not complete in a reasonable amount of time; please retry
This has been fixed.
You can now use a Domino folder link as the target for journal archiving. The link must be in the Domino data folder so that the target appears as a subfolder of the data folder.
In some circumstances it was possible for shortcut bodies to be removed when you used the EVDominoExchangeMigration tool.
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.
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, the Domino mailbox archiving task became unresponsive and wrote the following error to the event log:
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 20/12/2011 8:00:36 AM
Event ID: 41050
Task Category: Lotus Domino Mailbox Archiving Task
Level: Error
Keywords: Classic
User: N/A
Computer: EVSRV1.example.com
Description: Task: 'Domino Mailbox Archiving Task' Unable to initialize
Names and Address Book (NAB) session for Domino server:
'Failed to create Notes Session (mutex)'
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.
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.
In some circumstances it was possible for NSF migration to fail with the following error in the detailed migration report:
An exception occurred: Collection was modified; enumeration operation may not execute
This has been fixed.
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.
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
Move archive failed due to corrupt attachments. Move Archive displayed Error in the status page for the failed move operation and wrote the following error to the event log:
Exception: Object reference not set to an instance of an object
This has been fixed.
Move Archive failed for some users when their archives contained corrupt attachments. Move Archive displayed Error in the status page for the failed move operation and wrote the following to the event log:
Inner storage error code: 0x80004002
This has been fixed.
In some circumstances, a move operation could stall in backup phase when the following conditions existed:
Administrators could not complete or cancel the move when Move Archive remained in the backup phase.
This has been fixed. Move Archive now proceeds to the verification phase even if these circumstances exist.
If you use Move Archive to move a Domino archive to a different Enterprise Vault site, you need to do the following:
For more information, see the section 'Moving active archives between sites' in the Administrator's Guide.
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 issue affected only 32-bit index volumes, that is, index volumes that were created by Enterprise Vault versions earlier than Enterprise Vault 10.
This has been fixed.
There is a new 'Not Yet Created' filter in the Index Volumes Browser. This filter enables you to include or exclude index volumes that Enterprise Vault has prepared but has not yet used. The index volumes have database entries but do not yet have any data. These volumes do not yet exist on disk.
In Enterprise Vault 10.0 it was not possible to create a new partition on some CIFS/SMB devices when the 'Create Vault Store Partition with security ACLs' option was selected.
This has been fixed.
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.
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.
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.
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.
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.
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.
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.
The Storage Expiry report incorrectly treated items that were on hold, and so not eligible for deletion, as items that failed to be deleted. This behavior resulted in incorrect totals for the following:
Total number of expired items deleted Total number of items deleted
This has been fixed.
When the site setting Retain archive transaction history for x days was changed, Enterprise Vault did not apply the new setting to existing archives.
This has been fixed. When you change this setting, it applies immediately to all archives. The internal handling of transaction history has also been optimized to improve archiving performance.
You must restart the Enterprise Vault Storage service after you select or clear the Migrate files checkbox on the Migration page of vault store partition properties. You must also restart the Storage service if you change any of the other options on the Migration page.
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.
Storage Expiry always processed items that were on legal hold. When a very large number of items was on legal hold, Storage Expiry could fail to complete its work within the available time.
This has been fixed.
On the Vault Store Partition Properties: Backup tab, you can change the partition scan interval using the Scan partition every value. When you set this interval to less than the 60 minute default, the new interval was not honored by storage until after the default period of 60 minutes had elapsed.
For example, if you set a scan interval of 5 minutes, 60 minutes would elapse before the scans at 5 minute intervals began.
This has been fixed.
Enterprise Vault now writes saveset records to the Vault Store databases more efficiently.
If you use Enterprise Vault single instance storage, there is now reduced lock contention and reduced resource demand on the SQL Server, CPU, tempdb, and memory during archiving.
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.
When there were more than approximately 100,000 archives in a single vault store it was possible for Storage Delete process to terminate with the following error:
Event ID: 8390 The EnterpriseVault DirectoryConnection object reported an error. Ran out of Memory
When this problem occurs, Storage Expiry also failed with the following error:
Event: 6606 Category: Storage Delete Failed to process all expired items in Vault Store. Not enough storage is available to complete this operation.
This has been fixed.
This issue affected Domino mailbox, Domino journal, and File System archiving to Centera, when collections were used and the Remove Safety Copies setting was 'immediately after archive'. Under these conditions it was possible for Enterprise Vault to remove safety copies when the savesets were still in the staging area, before collection and transfer to the Centera.
If this situation occurred, no safety copies were available if for some reason a saveset got deleted from the staging area before collection and transfer to the Centera.
This has been fixed. Now, the safety copies are not removed before the collections are archived on the Centera. This precaution already applied to Exchange and SharePoint archiving.
Enterprise Vault 10.0.1 includes the following improvements to indexing functionality:
In some circumstances, the rebuild of an index volume that was close to its size limit could unnecessarily create two new index volumes to replace the old volume.
This has been fixed.
The deletion of large numbers of archived items can sometimes result in empty index volumes. This could occur, for example, when archived items expire.
At regular intervals, the Indexing service now checks for empty index volumes, and deletes them. You can use the following advanced indexing settings to configure the frequency of the checks, and the maximum number of volumes that can be deleted:
You can find advanced indexing settings in the Enterprise Vault Administration Console, on the Advanced tab of the properties for the Enterprise Vault server.
We recommend that you do not change these settings unless your technical support provider advises you to do so. If you do change the settings, then you must restart the Indexing service to apply the changes.
In some circumstances, the Index Volumes Browser could report an incorrect count of the indexed items in an index volume.
This has been fixed. For index volumes whose indexed items count was incorrect, Enterprise Vault corrects the count when items are added to or removed from the index, and when you rebuild or synchronize the index volume.
The Indexing service did not start if the IIS_USRS group permissions were incorrect on any of the following folders:
The Enterprise Vault now automatically corrects the IIS_USRS group permissions, if necessary.
In rare circumstances it was possible for the Indexing service to fail to start or for index rebuilds to fail.
The cause of the problem was an empty FolderName field in the IndexVolume table in the Directory database.
This has been fixed.
In some cases, the rebuild of a journal archive's index volumes could fail, even though a subsequent rebuild of the same archive could succeed. When the rebuild failed, Enterprise Vault wrote event ID 13360 to the event log. The event included the following message:
Message: Cannot find a valid upper limit sequence number for new index volume to be rebuilt.
This has been fixed.
Since Enterprise Vault 9.0.1, Enterprise Vault has not converted or indexed the content of text files in compressed attachments. This problem affected text files in .ZIP attachments, for example. The problem did not affect files such as word processed documents, spreadsheets, .PDF files, and so on.
This has been fixed. By default, Enterprise Vault 10.0.1 converts text files within compressed files to HTML and indexes them.
A side-effect of this change is that Enterprise Vault may incorrectly try to index binary files within compressed files. A new DoNotConvertBinariesInZippedFiles registry value enables you to disable the conversion and indexing of text files within compressed files, if necessary. See the description of DoNotConvertBinariesInZippedFiles in the Registry Values manual.
Do not disable conversion if there is a requirement for you to be able to search archives for compliance reasons.
The Indexing service failed to start when there was no HTTP binding for the EVIndexing web site.
This has been fixed. Enterprise Vault now automatically corrects the EVIndexing web site settings, if necessary.
The EVIndexVolumesProcessor process could terminate and then restart repeatedly when rebuilding or upgrading indexes.
The problem could happen when Enable recovery of user deleted items was selected in Site Properties in the Administration Console and thousands of items had been deleted from an archive but had not yet been permanently deleted.
This has been fixed.
In very rare circumstances, the Index Volumes Browser can report "There are items with incorrect information in the index".
To correct this problem, you must rebuild the index volume.
Email items with unusual patterns of author or recipient data, such as those without a display name, could be excluded from indexing. These items were reported as failed items by the Index Volumes Browser, and did not then appear in search results.
This has been fixed. Items that previously failed are now indexed when you synchronize index volumes.
In some circumstances, such as after index volumes are restored from backup, the range of sequence numbers in an index volume can be incorrect. During normal operation, Enterprise Vault corrects the sequence numbers in each index volume. Although an index verification task should have corrected the problem straight away, it did not.
This has been fixed.
In Enterprise Vault 10.0 there was a single setting that controlled the maximum size of an index volume. In Enterprise Vault 10.0.1 there is now a setting for the indexes of each archive type, as follows:
When you install Enterprise Vault 10.0.1, all these settings have a default of 5,000,000 items. If you have previously modified the maximum size of index volumes you must change the appropriate setting after you install Enterprise Vault 10.0.1.
See the "Computer properties advanced settings" section in the Administrator's Guide for details of the individual settings.
At the Enterprise Vault 10.0 original release, FSA could not manage Windows Server 2003 file servers that were clustered using Windows Server Failover Clustering. (Windows Server Failover Clustering was formerly known as Microsoft Cluster Server, or MSCS.)
This has been fixed.
Details of the original issue are in the following technical note on the Symantec support Web site:
http://www.symantec.com/docs/TECH71442
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.
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.
Large file retrieval times have been improved for environments where pass-through recall from Celerra devices is enabled.
If you clustered Enterprise Vault in a Windows Server failover cluster, some FSA-related operations could create resource locks that prevented the successful failover from one cluster node to another. These operations were as follows:
FileScreenFilter.sys,
of the System Volume Information folder on the cluster node.
[Ref 11035, E2565306].reg) file of the FSA-related registry
entries on the cluster node, if the .reg file could not be written
for any reason. [Ref 11820, E2569275]These issues have been fixed.
A content search failed to return any data from an archived text file, if the file had all of the following characteristics:
This has been fixed.
Previously the last modified time changed on the parent folder and volume of a folder hierarchy when FSA processed a folder in the hierarchy. Windows updated the timestamp when any of the following actions occurred:
This meant that searches for changes using the last modified time could return unexpected results.
Now, by default, FSA resets the last modified time to the previous value after it has finished processing the folder.
Two DWORD registry settings let you revert to the previous behavior if you want:
ResetFolderModifiedTimeStamp, on the Enterprise Vault server. This setting controls the behavior in all the cases except for recall of archived files from placeholders on Windows file servers. This setting must be set under the following registry location on the Enterprise Vault server:
HKEY_LOCAL_MACHINE
\SOFTWARE
\Wow6432Node
\KVS
\Enterprise Vault
\FSA
To revert to the previous behavior, give this setting a value of 0, and then restart the Enterprise Vault Admin service.
ResetFolderModifiedTimeStamp, on Windows file servers. Use this setting in addition to the setting on the Enterprise Vault server, if required. This setting controls the behavior when you recall archived files from their placeholders on the Windows file server. This setting must be set under following registry location on the Windows file server:
| On a 32-bit installation of Windows: |
On a 64-bit installation of Windows: |
HKEY_LOCAL_MACHINE
\SOFTWARE
\KVS
\Enterprise Vault
\FSA
\PlaceholderService
|
HKEY_LOCAL_MACHINE
\SOFTWARE
\Wow6432Node
\KVS
\Enterprise Vault
\FSA
\PlaceholderService
|
To revert to the previous behavior, give this setting a value of 0, and then restart the Enterprise Vault File Placeholder service on the file server.
Note: The entry in the Registry Values guide for the ResetFolderModifiedTimeStamp setting under the PlaceholderService subkey does not make it clear that this registry setting is set only on Windows file servers.
A problem could occur if the SQL Server connection was lost during an archiving run, and a "Create shortcuts later" policy was used.
Files in the folder that the File System Archiving task was processing when the SQL Server connection was broken were incorrectly added to the list of files to be archived from the next folder, when the connection was resumed. The task therefore archived these files twice, with the second copy going to the archive associated with the other folder, and with the wrong folder path reference.
This has been fixed.
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.
On an archiving run, a File System Archiving task now updates the Directory database regarding folder permissions only if the permissions have changed. This improvement means that archiving runs should take slightly less time after the initial run, especially in environments with a large number of folders.
A problem occurred with the 'Delete archived file when placeholder is deleted' feature, when deleting items that had been archived using the volume policy. If you deleted a placeholder from a 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.
Pass-through recall of items could fail with an "access denied" message. A DTrace of the EVPlaceholderService showed the following:
EV:M Cache Location not set to start cache cleanup thread. Pass-through not enabled.
The problem occurred because a thread in the recall process failed to wait for an associated thread to complete.
This has been fixed.
Previously, Enterprise Vault did not allow a connection to an EMC Celerra Data Mover HTTP server for placeholder support, if the Data Mover used SSL.
An SSL connection is now supported. For more details, see "Configuring the Data Mover server to use SSL" in the Setting up File System Archiving guide.
If the FSAUtility -pm option did not create all of the placeholders successfully at the destination location, it sometimes failed to report this issue and indicated that the migration was successful.
This has been fixed. FSAUtility now informs the user if placeholder migration failures occur. The logging of errors has also been improved.
Users with permission to delete files from folders of a file server share were unable to delete the archived files, unless they had Full Control or co-owner permissions on the file server share.
This has been fixed. The archive folder permissions are now set so that a user with permissions to delete files from the original source folder share can delete any file from the archive folder.
On upgrade, the change in archive folder permissions takes place on the next occasion that the File System Archiving task synchronizes archive permissions for a file server share.
Note that if you archive files with explicit permissions, a user with permission to delete files from the folders of a file server share can now delete an archived file even if someone else created the original file with permissions to prevent deletion. However, if the user did not have permission to delete the original file, the user cannot delete its shortcut.
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.
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 partially processed 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.
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.
When pass-through recall was enabled and a file larger than 100 MB was recalled from an EMC Centera storage device, the restored file was corrupt.
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.
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.
If you configured the Send email notification option for a File Blocking rule, 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.
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.
When the following policy settings were used, shortcut deletion paused until a new file was added to the library:
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.
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.
When an index had more than five volumes, searching the archive with a Web part or clicking Show archived versions of this document failed with the following error:
exception from HRESULT: 0xC0041C82
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.
When documents in a library were restored from the archive, the Modified column showed an incorrect date and time.
This has been fixed.
When you created a document in a document set with versioning enabled, trying to view the archived versions of the document displayed the following error:
List does not exist. It may be deleted by another user.
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.
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.
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 SharePoint has KnowledgeLake Imaging installed, archiving failed with the following error:
Error listing folders.
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.
Previously, a problem could occur if you attempted to disable all FSA Reporting data collection in the Administration Console. When you cleared the "Enable data collection for FSA Reporting" check box on the properties of the File Servers container under Targets, the change sometimes failed to propagate to the properties of all the target file servers.
The mechanism to disable all FSA Reporting data collection has now changed. The "Enable data collection for FSA Reporting" check box has been removed from the properties of the File Servers container. To disable all data collection, right-click the File Servers container and select the new option "Disable All FSA Reporting Data Collection". To re-enable data collection, enable data collection separately on the properties of each target file server.
The Enterprise Vault Deployment Scanner's Directory Database Upgrade test did not make allowance for volume mount points when it checked that sufficient disk space was available for the upgrade. Although the volume mount point that contained the Directory database had sufficient free disk space, if the drive that hosted the mount point did not have sufficient free disk space, the Deployment Scanner reported that the test had failed.
This has been fixed.
Index locations could not be backed up because of locked 'Updates.log' files.
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.
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.
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 the 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 files using the extension ldf.
Under some circumstances, scans of backed up partitions never finished. The effect was that archive pending items were never turned into shortcuts.
This has been fixed.
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
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.
If connection to the SQL Server is lost, and you need to shutdown Enterprise Vault services, stop the individual services manually, finishing with the Directory service and the Admin service. You should stop the services in this way, rather than stopping the Admin service, and relying on it to stop the other services.
Additional events now appear in the Enterprise Vault event log during the upgrade of the following databases, to indicate the progress of the upgrade:
For the Directory database, vault store databases, and fingerprint databases, an upgrade of a database generates several instances of events 13399 and 13400, as various scripts start and complete, respectively. For an upgrade of the Monitoring database, event 41396 indicates the progress of the Monitoring Configuration utility.
These events also appear during database creation.
The Enterprise Vault upgrade instructions provide more details of the events that are generated during database upgrades.
This release includes the following Outside In® Technology content converters and patches from Oracle® Corporation:
The following Storage events are no longer generated:
Request thread pool (InstanceId = [1]) started with maximum thread count = [4]
Request thread pool (InstanceId = [1]) stopped. Total threads stopped = [4]
These events were generated when vault stores were entering or leaving backup mode.
Under certain circumstances, users could search and view the index metadata of items in a folder to which they were denied access, in an archive to which they had access.
This has been fixed.
If the locale decimal separator was not a period (.), searches could fail with the following event:
Type: Error Event: 7182 Source: Enterprise Vault Description: Index Search failed: Index: Internal reference: (0xc0041c0e)
This problem affected user searches, Compliance Accelerator searches, and Discovery Accelerator searches.
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.
In rare circumstances, the NTFS to Centera migrator could cause Enterprise Vault storage to write the following error to the event log:
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 20/12/2011 12:37:28 PM
Event ID: 7109
Task Category: Storage File Watch
Level: Warning
Keywords: Classic
User: N/A
Computer: evsrv1.local
Description: An invalid saveset was encountered while doing watch file scan. This archive
operation will be attempted to be cancelled. Following further information is
available.
Partition Name = Ptn6
VaultStoreEntryId = 1726C795A7ADBFD46A551E1006292EBA71210000EVSRV1
TransactionID = C0B4556D-F1F9-B88C-BFEA-D9C328FED661
Invalid Reason = File 'V:\EVStores\Ptn6\
1DFA6N1353JSUe93GM44FLGI1QLG4169PHN83E0T92R5UTL7FFGOE' not found for
SavesetIdentity = [2772]
When this happened, users could not retrieve some items from their archives.
This has been fixed.
To ensure that the utility ResetEVClient completed all its expected actions, you had to run it twice: once as the user who had a problem with the Outlook Add-In, and once as an administrator.
This has been fixed. Now, you must start ResetEVClient as the user who had a problem with the Outlook Add-In. If necessary, ResetEVClient then prompts for the name and password of an account with administrator privileges before it performs the remaining actions. If the current user has administrator privileges, ResetEVClient does not prompt for these credentials.
In some circumstances, multi-threaded NTFS to Centera migrator jobs stalled when they were close to completion. This occurred when the migrator was processing some complex savesets.
This has been fixed.
In some circumstances Internet Explorer 8, running on Windows XP, could fail when users clicked Refresh in the Browser Search Select Folders web page dialog.
This has been fixed.
To stop the accidental deletion of an archive whose contents appear in the results of a Compliance Accelerator or Discovery Accelerator search, these two applications register their interest in the archive by creating an entry in the VaultInterest table of the Enterprise Vault Directory database. However, Enterprise Vault did not check this table when it processed a request to delete an archive. Instead, the following error message would appear in the event log when Enterprise Vault tried to delete an archive in which Compliance Accelerator or Discovery Accelerator had registered an interest:
An error was detected while accessing the Vault Database 'EnterpriseVaultDirectory'
(Internal reference: {CADODataAccess::ExecuteSQLCommand} ...
This has been fixed.
Enterprise Vault servers use DCOM for communication between software components. DCOM is based on the Remote Procedure Call (RPC) protocol, which uses the RPC end-point mapper port (port 135) for connection set up. Windows then dynamically allocates a port from the range of dynamic RPC ports.
For information on configuring Enterprise Vault for restricted DCOM access, see the technical note http://www.symantec.com/docs/TECH69642 on the Symantec support Web site.
For details of firewall settings for Enterprise Vault programs, see "Ports used by Enterprise Vault" in the Administrator's Guide.
It was possible for the Storage service to cause SQL performance problems when the DeleteEmptyFolders registry value was used.
This has been fixed.
In some circumstances, EVStgAPI.dll produced a memory handle leak. For example, this could occur when EVSVR was run against large Enterprise Vault databases.
This has been fixed.
Changes to the use of file locking have improved concurrent access of CAB files. This change can result in better performance, for example, when rebuilding indexes, where multiple threads attempt to access the same CAB file to retrieve items.
In cases where a large backlog of Enterprise Vault indexing had built up, Virtual Vault synchronizations did not take place.
This has been fixed. Even when there is a large backlog of indexing work, Virtual Vault synchronizations continue as normal.
Copyright © 2012 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, Veritas, Enterprise Vault, Compliance Accelerator, and Discovery Accelerator are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (“Third Party Programs”). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Software file accompanying this Symantec product for more information on the Third Party Programs.
The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043