Last updated: 5-Jul-2013
|
The latest version of this document and the other Enterprise Vault release notes are available from the Symantec Enterprise Support site in the following languages: For the latest news about this release, including any hotfixes, subscribe to http://www.symantec.com/docs/TECH200691. |
This document describes the changes introduced in Enterprise Vault 10.0.4 (service pack 4 for Enterprise Vault 10.0).
Enterprise Vault 10.0.4 contains a number of security enhancements and improvements. These were identified and addressed as part of a comprehensive internal code review of the core components. Symantec strongly recommends that customers upgrade to Enterprise Vault 10.0.4.
Before installing or upgrading to Enterprise Vault 10.0.4, 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 changes introduced to Enterprise Vault 10.0 by earlier service packs, see the Previous Updates document.
For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
Enterprise Vault 10.0.4 provides the following new features:
The Enterprise Vault Extensions feature allows Symantec Technology Enabled Program (STEP) partners to develop integrated archiving solutions for content that is not supported by the standard Enterprise Vault release. The third party extension application is displayed in the Administration Console. Administrators configure and manage the extension application in a similar way to archiving tasks.
Information about available extensions can be found at the following address:
http://go.symantec.com/archive-anything
Enterprise Vault 10.0.4 includes various enhancements to PST file migration that enable you to do the following:
Add-EVPstComputer
and Add-EVPstFile.For more information on the new PST file migration features, see the Administrator's Guide and the Outlook Add-In documentation.
In the archive settings for an Enterprise Vault site, there is now a setting to update the retention category for moved items only when the retention period is increased or unchanged. By default, the retention category is always updated for moved items.
In the properties of a retention category, the setting Prevent deletion of archived items in this category is replaced by the following two settings:
By default, both settings are turned off for new retention categories. On an upgrade, both settings are turned on for an existing retention category if Prevent deletion of archived items in this category was turned on.
Enterprise Vault 10.0.4 introduces an indexing exclusion feature. You can use this feature to specify email content that you do not want Enterprise Vault to index, such as email disclaimers and corporate email signatures.
The content that you exclude is not added to Enterprise Vault indexes, and the quality of searches is improved by avoiding unwanted search hits that would otherwise arise from the excluded text.
For more information about indexing exclusions, see the Help topic in the Site Properties: Indexing tab.
The Enterprise Vault Office Mail App is now supported for use on tablets and phones that are running iOS 6.1.n.
Note: Cumulative Update 1 for Exchange Server 2013 is a requirement for use of the Office Mail App on tablets and phones. For information about Cumulative Update 1, see http://support.microsoft.com/kb/2816900.
After deployment of the Office Mail App in Enterprise Vault 10.0.4, it is enabled by default on tablets and phones as well as computers. If required, you can add entries to the Enterprise Vault web.config file to disable the Office Mail App on computers, tablets, or phones. For details, see the Setting up Exchange Server Archiving guide.
If you deployed the Office Mail App in Enterprise Vault 10.0.3, it was disabled by default on tablets and phones. In this case, note that when you upgrade to Enterprise Vault 10.0.4 the default changes and the Office Mail App is enabled on tablets and phones.
The Office Mail App options Restore and Delete are not available on tablets and phones. This restriction is outside the control of Enterprise Vault. It is caused by a known issue with Exchange Server 2013.
For the latest information on supported versions of operating systems, see the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
Enterprise Vault now supports mailbox archiving and journal archiving from IBM Domino 9.0. In addition, client users can now access Enterprise Vault functionality in version 9.0 of IBM Notes and IBM iNotes.
For the latest information on the supported versions of Domino and Notes, see the Enterprise Vault Compatibility Charts at: http://www.symantec.com/docs/TECH38537.
As well as specifying retention categories for SharePoint targets, you can now apply retention categories in SharePoint rules. This allows you to specify different retention categories for different contents in a SharePoint target. You can apply retention categories according to content type, metadata, file type, or size for archiving rules.
The retention categories applied through the rule override those that are applied to the target.
Support is planned for Enterprise Vault servers on Windows Server 2012. For the latest information about Windows Server 2012 support, see http://www.symantec.com/docs/TECH207259 and the Enterprise Vault Compatibility Charts at http://www.symantec.com/docs/TECH38537.
You can now enable checkpointing for most EVSVR operations. This facility causes EVSVR to create snapshots of the current state of an operation as it progresses. Then, if the operation is stopped or fails for any reason, you can continue it from the latest checkpoint instead of having to restart it from the beginning.
For more information, see the "EVSVR" chapter of the Utilities guide.
This version of Enterprise Vault provides the following new facilities with which you can view and change the legal hold status of selected archives:
In the Enterprise Vault Management Shell, you can now run the following PowerShell cmdlets to view and change the legal hold status of selected archives:
| Cmdlet | Description |
|---|---|
| Get-EVArchive | Returns a list of the Enterprise Vault archives in which a specified user has various permissions, either directly or through membership of an Active Directory group. You can filter the list by a number of archive properties. For example, you can choose to list only those archives in which the user has permission to delete the archived items, or only those archives that are on legal hold. |
| Set-EVArchive | Sets a number of properties of the nominated archive, including whether users can manually delete the items in the archive and whether Enterprise Vault can automatically delete the archived items when their retention period has expired. You can also specify a description and administrative note for the archive for display in the Administration Console. |
For more information on these cmdlets, see the "Day-to-day administration" chapter of the Administrator’s Guide.
In Policy Manager (EVPM) initialization files, you can now use the following
keynames in the [Archive] section to allow or deny the deletion
of archived items:
| Keyname | Description |
|---|---|
| DeleteExpiredItems (existing) | For the nominated archive, specifies whether to allow Enterprise Vault to delete the items automatically when their retention period has expired. |
| DeleteProtected (new) | For the nominated archive, specifies whether to allow users to delete items manually from the archive. If you choose to prevent this then, in addition, the archive cannot be moved or deleted. |
For more information on these keynames, see the "Policy Manager (EVPM)" chapter of the Utilities guide.
When you view the properties of an archive in the Vault Administration Console, the following options are now available on the Advanced tab of the Archive Properties dialog box:
| Option | Description |
|---|---|
| Allow deletion of archived items and of this archive (new) | When checked, allows users to delete items manually from the archive and also allows the archive to be moved or deleted. |
| Delete expired items from this archive automatically (existing) | When checked, lets Enterprise Vault delete items from the archive when their retention periods expire. |
Kerberos authentication between the Enterprise Vault Client for Mac OS X and the Exchange and Enterprise Vault servers is now supported. Note that Kerberos authentication is currently supported for use with Outlook 2011 for Mac only.
For information on how to set up Kerberos authentication for the Enterprise Vault Client for Mac OS X, see the Setting up Exchange Server Archiving guide.
The Enterprise Vault Client for Mac OS X that is included in this release is supported for use on client computers that run Outlook 2011 SP3 (14.3.0).
To obtain the changes described in this section, the Enterprise Vault 10.0.4 Outlook Add-In must be installed.
In some rare circumstances Outlook users received the following error message when they tried to open an archived item from its shortcut:
The custom form cannot be opened. Outlook will use an Outlook form instead.
The form required to view this message cannot be displayed. Contact your administrator.
This has been fixed. The Outlook Add-In installer now sets the Microsoft registry value ForceFormReload to the value 1, so that Outlook forces the forms to be reloaded if it finds a problem with a form.
Note that the Enterprise Vault advanced Outlook setting Force form reload on error in the Exchange desktop policy sets ForceFormReload by default but can also be set to remove it, in which case Outlook will not reload forms.
When Outlook 2010 was configured to open in a minimized state and the Enterprise Vault Outlook Add-In was enabled, Outlook stopped responding during initialization.
This has been fixed.
This issue occurred when the Vault Cache advanced setting Synchronize archive types in the Exchange desktop policy was set to All mailbox archives or All mailbox and shared archives. The issue affected users with access to a large number of archives. Vault Cache synchronization failed and users experienced out of memory errors, even when the primary mailbox archive was the only archive selected for synchronization with Vault Cache.
This has been fixed. A user with access to a large number of archives can now successfully enable a few of them for Vault Cache synchronization. Errors may still occur if the user enables too many archives for Vault Cache synchronization.
When an attempt to delete an item failed because the vault store that contained the item was in backup mode, the shortcut was still deleted without prompting for confirmation.
This has been fixed. A prompt tells you that there was an internal error on the web server and asks whether you want to delete the shortcut. Clicking Yes deletes the shortcut only, and clicking No cancels the operation.
This issue affected Outlook users whose computers were running 64-bit Windows 7 and 32-bit Microsoft Office 2010.
If the logging level was set to 0 (errors only) or 1 (information), the Outlook Add-In tab was not displayed on the Outlook ribbon. In the client log, an unknown exception was reported.
The issue did not occur if the logging level was set to 2 (minimum tracing) or higher.
The logging level is set by the registry value LoggingLevel. For information about LoggingLevel, see the Registry Values guide.
This has been fixed.
If the Exchange Vault Cache setting Download item age limit was set to a value other than zero, a "Last synchronization was interrupted" message was sometimes incorrectly displayed after an initial Vault Cache synchronization, even though the synchronization had completed successfully. This occurred if the oldest calendar quarter within the age limit did not contain any items to download to the Vault Cache.
This has been fixed.
In some circumstances, Enterprise Vault did not download all items to the Vault Cache during an incremental synchronization. Enterprise Vault incorrectly used the age limit for the initial synchronization, which is set by the Exchange Vault Cache setting Download item age limit. If the age limit was after the last incremental synchronization, items that were archived between the age limit and the last synchronization would not be downloaded.
This has been fixed. Incremental synchronizations now download all items that have been archived since the last synchronization.
This issue occurred when the Shortcut Deletion setting in the Exchange desktop policy was set to Both deleted. If an Outlook user pressed the Delete key to delete a shortcut from a delegated mailbox, the item was correctly deleted from the archive but the shortcut was not deleted.
This has been fixed.
A user who did not have write permission to a folder received an incorrect message when attempting any action that required write access. The user received the message "Enterprise Vault is not available. Try again later".
The problem was most likely to be noticed when restoring to a public folder or a mailbox that had delegate access.
This has been fixed. A user without write permission who attempts an action that requires write permission now receives the message "You do not have permission to perform this Enterprise Vault operation".
If the name and alias of an Enterprise Vault server were changed, the changes could cause Vault Cache synchronization to fail.
This has been fixed.
When delegate permissions had been given on specific folders in Outlook, it was possible for an access warning to be logged each time the user synchronized the Vault Cache. The warning was logged only if the AuditAccessFailureEvent registry value had been set to 1.
When the user synchronized the Vault Cache, Event 6940 "Client request refused due to insufficient privileges, user userName attempted to access the Archive archiveName" was logged.
An access failure was also always logged in the Enterprise Vault audit database.
The warning and access failure should not have been logged. The Vault Cache synchronization succeeded.
This has been fixed.
Opening an archived item from the list of messages displayed in Archive Explorer caused Internet Explorer 10.0 to stop responding.
Note that this issue affected only Touch-friendly Internet Explorer, and not Internet Explorer for the desktop.
This has been fixed.
Enterprise Vault did not apply the Exchange Vault Cache setting Download item age limit correctly during the Vault Cache initial synchronization. It downloaded all items that had been archived in the calendar quarter in which the age limit fell.
This has been fixed. Enterprise Vault does not now download items older than the age limit.
An issue could occur with Outlook 2010 if a user was granted delegate access to another user’s mailbox, and they added the mailbox to their Outlook profile. When the delegate moved an item to a folder in the other user’s mailbox, Outlook closed unexpectedly.
This has been fixed.
When Outlook was not running and you opened an item from Windows Desktop Search (WDS) results, the item did not open correctly. When you closed the item, either Windows or Outlook could stop responding.
The issues have been fixed for Outlook 2010. They did not affect Outlook 2013.
For Outlook 2003 and 2007, the issues are less likely but could still occur in some circumstances. As before, there is no issue if Outlook is already running when you open the item.
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.4 Outlook Add-In.
When Enterprise Vault starts to restore an item to a mailbox at a site where Blackberry Enterprise Server (BES) is in use, BES detects that a new item is in the mailbox and tries to notify the Blackberry device. In doing so BES modifies the item, which can cause the restore operation to fail. In this case the original shortcut remains in the mailbox. Before Enterprise Vault 10.0.4, a number of partly restored items from retry attempts also remained in the mailbox.
In Enterprise Vault 10.0.4 and later, if the restore operation fails for this reason, no partly restored items remain in the mailbox. A warning of the following type is written to the event log:
User username failed to restore an item into mailbox mailbox_name because this item was modified by another process.
For example it could have been modified by a third party application.
SavesetID: saveset_id.
On Exchange Server 2010 and 2013 it was not possible to restore an item to a mailbox if that item had several hundred specific recipients.
The attempted restore produced an event log entry similar to the following:
Event ID: 2227 User '<unavailable>' failed to restore an item into mailbox 'testmailbox'. |SavesetID: 201212105154286~201211301540543500~Z~B0ABB155F7722E8D2F7F0D22FC195D41 |
There was no problem with items that had large distribution lists.
This has been fixed.
Users would experience the following issues if one or more of their Outlook mailbox folders had ASCII control characters in their names:
This has been fixed.
This issue affected both Outlook users and OWA users.
A minor corruption in a shortcut could result in a primary key error such as the following:
Event ID: 13360 An error was detected while accessing the Vault Database 'MyEVDatabase' Description: Violation of PRIMARY KEY constraint 'PK#33A944155123A6B24587C82'. Cannot insert duplicate key in object 'dbo.@SavesetIDsAndTranIDs'. SQL Command: usps_SavesetsProps
The functionality of the corrupted shortcut was not affected but Enterprise Vault could not update metadata. The result could be that when the user moved the shortcut the change of location was not reflected in the archive.
This has been fixed.
Users would experience problems when opening Archive Explorer if they changed the Internet Explorer security option "Websites in less privileged web content zone can navigate into this zone" from its default setting of Enable. If set to Disable, the user could not open Archive Explorer. If set to Prompt, the following security warning would appear when the user opened Archive Explorer:
The current web page is trying to open a site in your Trusted sites list. Do you want to allow this?
This has been fixed.
In some cases, an incorrect character set was used when generating the preview of HTML items. The problem was noticed with some Korean and Chinese mail messages.
The result was that the preview was unreadable and it was not possible to search for the content of those items.
This has been fixed for new items. The fix does not apply to items that have already been archived.
When an archived email had a Microsoft Word document attached, the text in the header and footer of the document was not searchable.
This has been fixed.
This issue could occur only in Enterprise Vault 10.0.3 with Cumulative Hotfix 2.
When a user restored an item from Archive Explorer to a mailbox hosted on Exchange Server 2013, the restored item in the mailbox could be rendered incorrectly when the user opened it.
This has been fixed.
Enterprise Vault 10.0.4 supports Microsoft hotfix KB2628229 for Exchange Server 2003 SP2, and OWA control file version 6.5.7656.5.
The title of Microsoft article KB2628229 is: October 2011 cumulative DST update for Exchange Server 2003 SP2.
This issue affected both Outlook users and OWA users.
A minor corruption in a shortcut could result in a primary key error such as the following:
Event ID: 13360 An error was detected while accessing the Vault Database 'MyEVDatabase' Description: Violation of PRIMARY KEY constraint 'PK#33A944155123A6B24587C82'. Cannot insert duplicate key in object 'dbo.@SavesetIDsAndTranIDs'. SQL Command: usps_SavesetsProps
The functionality of the corrupted shortcut was not affected but Enterprise Vault could not update metadata. The result could be that when the user moved the shortcut the change of location was not reflected in the archive.
This has been fixed.
The following four related issues could affect Office Mail App users when Internet Explorer 10 was installed on their computers. The issues occurred only when users ran the Office Mail App from OWA 2013 in Internet Explorer 10. They did not occur when users ran the Office Mail App in Outlook 2013.
The issues have been fixed in Enterprise Vault 10.0.4, although some restrictions apply. The restrictions are outside the control of Enterprise Vault. They are caused by the operation of Internet Explorer 10 security features when Internet Explorer 10 is used in conjunction with the Office Mail App.
This issue occurred when all of the following conditions applied:
The effect was that when you launched Search (Integrated or Browser), Archive Explorer, or Help from the Office Mail App, the browser window failed to open but there was no error message.
This has been fixed. The Office Mail App now displays an error message if a browser window fails to open, for example:
Failed to launch Search
A tooltip for the error message provides more detail, for example:
Browser security settings may have prevented the search window from opening.
On Office Mail App users' computers running Internet Explorer 10, it is a requirement that if the Exchange server and the Enterprise Vault web server are in different zones, each zone must have the same Enable Protected Mode setting. Otherwise, the issue of the browser window not opening may still occur.
Archive Explorer was not displayed correctly when it was launched from the Office Mail App in Internet Explorer 10.
This has been fixed. Archive Explorer is now available when it is launched from the Office Mail App in Internet Explorer 10. The following restrictions apply:
To avoid these restrictions, launch Archive Explorer directly (that is, not from the Office Mail App). Launching Archive Explorer directly in a new tab in your existing Internet Explorer session, or in a new session, enables full Archive Explorer functionality. For information about launching Archive Explorer directly, see the section "Archive search and Archive Explorer in standalone browser" in the Installing and Configuring guide.
Messages could not be downloaded or displayed from Integrated and Browser searches when the searches were launched from the Office Mail App in Internet Explorer 10.
This has been partly fixed. Messages are displayed in HTML from a search that is launched from the Office Mail App in Internet Explorer 10, rather than downloading the original items.
To download the original items, launch the search directly (that is, not from the Office Mail App) in a new Internet Explorer session. Launching the search directly in a new tab in your existing session does not enable downloading of the original items. For information about launching a search directly, see the section "Archive search and Archive Explorer in standalone browser" in the Installing and Configuring guide.
The Browse button that enables you to select folders to search did not work in Integrated and Browser searches when the searches were launched from the Office Mail App in Internet Explorer 10. Clicking the Browse button next to In folder (Integrated search) or Folders (Browser search) returned an error message.
In Enterprise Vault 10.0.4, the option to specify folders to search has been made unavailable when the search is launched from the Office Mail App in Internet Explorer 10.
To avoid this restriction, launch the search directly (that is, not from the Office Mail App) in a new Internet Explorer session. Launching the search directly in a new tab in your existing session does not enable the option to specify folders to search. For information about launching a search directly, see the section "Archive search and Archive Explorer in standalone browser" in the Installing and Configuring guide.
In some circumstances, when you ran EVInstall.nsf against templates which had customizations on certain shared actions, the EVInstall log contained the following error:
WARNING: Error compiling shared actions
This could occur if you had customized any of the following shared actions:
This has been fixed.
A Notes or iNotes user with reader or author access on another user's mail file was unable to retrieve items from the Domino archive associated with the owner's mail file. Attempts to do so produced the following error:
Notes error: Unknown OS error
This happened because the delegate user did not have sufficient permissions to retrieve items to the owner's mail file.
This has been fixed. Enterprise Vault now temporarily retrieves these items to the delegate user's mail file.
Note that this fix has been implemented for mail templates and iNotes Forms files for Domino 8.5.3 and later.
Enterprise Vault did not honor the Domino desktop policy's Shortcut Deletion setting. Irrespective of the chosen setting, users were always asked if they wanted to delete both the shortcuts and the associated archived items.
This has been fixed, and the Shortcut Deletion settings behave as follows:
In Domino 8.5.2 and earlier environments, iNotes users could not display previews of the items in their Trash folders, whether Enterprise Vault had archived them or not. When users tried to preview these items, the message "Loading document..." persisted in the Preview pane, and the message "Bad HTTP status: 404 (Not Found)" appeared in the status bar.
This has been fixed.
The following error message would appear in iNotes when you tried to retrieve certain archived messages by double-clicking them:
Error encountered retrieving data: Unterminated string constant
This has been fixed.
Notes users who searched for and tried to retrieve items in another user's archive would receive the error message "Notes Error: File does not exist", if that user had been deleted from the Domino Directory and disabled from Enterprise Vault archiving.
This has been fixed.
After Enterprise Vault archived a Domino calendar item in which you had embedded an attachment, the archived item would sometimes contain two hyperlinks to the attachment. Clicking one of the hyperlinks worked, but clicking the other would fail with the message "Note item not found". This issue arose if you had first added the attachment to the calendar item and then dragged and dropped the attachment to reposition it within the Description field.
This has been fixed. When Enterprise Vault archives a calendar item that has an attachment, it now creates one link to the attachment only.
If you created a new message in iNotes by selecting an archived message and then choosing the Reply with Attachments or Forward with Attachments command, certain attachments to the original message could be omitted from the new one. This issue arose when both of the following conditions applied:
This has been fixed.
In the Vault Administration Console, the Domino desktop policy option Shortcut Deletion was ineffective for iNotes users. In consequence, when an iNotes user chose to delete a shortcut, Enterprise Vault would always ask the user to choose between deleting the shortcut alone and deleting both the shortcut and the original item—even if you had chosen a setting other than Ask User for the Shortcut Deletion option. This issue did not affect Notes users.
This has been fixed.
The following error message would sometimes appear in iNotes when you tried to open encrypted messages, including messages that Enterprise Vault had yet to archive:
A problem has occurred which may have caused the current operation to fail.
This issue affected only those users whose Internet passwords differed from their iNotes-imported Domino ID passwords.
This has been fixed.
In iNotes, the error message below would appear when you tried to open certain archived messages that had been PEC-certified. (PEC, or Posta Elettronica Certificata, is a certified email system that is in use in Italy.)
http web server - couldn't find design note -0
This has been fixed.
In iNotes, when two or more archived messages had attachments with the same file name (but different content), selecting the messages and then forwarding them as a new message would cause Enterprise Vault to add an extra copy of one of the attachments to the new message.
This has been fixed.
In Enterprise Vault 9.0.3 or 9.0.4 environments, iNotes users could not view the contents of an S/MIME-signed message if it had been sent from an external mail system. In addition, one of the following errors would appear in the mail server console:
HTTP Web Server: Couldn't find design note
Invalid URL Exception
This has been fixed.
If you used the Browser Search feature to find an archived item and then view it in its original form, rather than in an HTML representation of the item, then the BCC recipient information was missing. The HTML representation of the item did provide the complete recipient information.
This has been fixed.
This issue affected Enterprise Vault 10.0.2/10.0.3 Browser Search in Safari 6.0.
When you copied a basket, the items in the new basket had no titles. If you clicked an item in the new basket, the following message appeared:
The item no longer exists.
This has been fixed.
If the commands on the Enterprise Vault Client application menu were dimmed when Enterprise Vault began an archiving operation, performing either of the following activities while the operation was in progress would enable the commands:
This has been fixed.
The Enterprise Vault toolbar and menu commands would always appear when you opened Outlook 2011 for Mac, even if you had yet to add an email account to Outlook. The issue did not affect Entourage users.
This has been fixed. The Enterprise Vault toolbar and menu commands no longer appear if you have yet to set up Microsoft Outlook for Mac 2011 to access your email account.
If you installed the Enterprise Vault Client for Mac OS X using the Terminal command-line interface rather than the graphical installation interface, the Enterprise Vault Client application menu did not appear until after you restarted your computer. This issue affected installations of the Enterprise Vault Client on Mac OS X 10.7 (Lion) and later only.
This has been fixed.
You could not log in to the Enterprise Vault Client for Mac OS X if, in Internet Information Services (IIS) Manager on the Microsoft Exchange server, you configured the EWS virtual directory under the default website to use basic authentication only.
This has been fixed.
When Archive Explorer was used to restore items to the root of an Exchange mailbox, the archive's folder hierarchy disappeared.
The problem affected Archive Explorer only when it was used in a web browser. Archive Explorer in Outlook did not show this problem.
This has been fixed in that Archive Explorer does not have this problem. The fix does not correct archives that have already lost their hierarchy.
This issue occurred if you copied a document directly into an Outlook folder in a mailbox that was hosted on Exchange Server 2013, and then archived the document. You could not open the document from its shortcut.
This has been fixed. The fix does not apply to items that have already been archived from Exchange Server 2013.
Users whose mailboxes were migrated to Exchange 2013 were unable to restore items to their mailboxes if the items were archived from an earlier version of Exchange.
This has been fixed.
The Journaling task sometimes incorrectly logged an error event when a Data Classification Services response rule was set as follows:
Do not archive message -> Move message to Deleted Items folder
The event that was logged was as follows:
Event ID: 3438 Task Category: Journal Task Description: Failed to process a message. This message will not be archived and could not be changed back from the Archive Pending state. This problem can occur when a message has large numbers of recipients or attachments.
The messages were correctly processed. The event should not have been logged.
This has been fixed.
By default, Enterprise Vault uses Active Directory expansion of distribution lists for Exchange Server 2010 and later. For these versions of Exchange, when the journal archiving task encountered a distribution list that contained another distribution list that was not mail enabled, the task failed while trying to complete Active Directory expansion of the list.
This has been fixed.
If the Windows Management Instrumentation (Winmgmt) service was not available on the Enterprise Vault server, the Exchange archiving tasks would not start.
The failure produced the following error:
Event ID: 3418 Task Category: Journal Task Level: Error Description: An unsupported Microsoft Outlook version has been detected.
This has been fixed. Enterprise Vault now correctly reports that Windows Management Instrumentation is unavailable and continues to try to start.
It was possible for the archiving task to terminate unexpectedly when processing an RTF message that contained multiple embedded attachments.
This has been fixed. The archiving task no longer terminates in this manner. However, if shortcuts are configured to retain message bodies, some shortcut bodies for RTF messages may not show all the placeholders for embedded attachments.
The Exchange public folder task tried to update shortcuts that were moved in public folders, which it is not designed to do. As a result, the task intermittently wrote the follow error to the event log:
Type: Error
Date: 12/4/2012
Time: 3:00:03 PM
Event: 2956
Source: Enterprise Vault
Category: Public Folder Task
User: N/A
Computer: EVServer01.testlab.local
Description: An error has occurred whilst processing the Public Folder \FolderA\SubfolderB.
Check the Event Log for any previous errors, as they may help determine the cause.
Error: 0xC00E0003
This issue was described in the following technical note:
http://www.symantec.com/docs/TECH206080
This has been fixed.
If an Enterprise Vault task or tool opened a MAPI message store while another task or tool was creating a MAPI profile, it was possible for the task or tool that opened the message store to fail.
This problem could affect all Enterprise Vault tasks and tools that accessed Exchange mailboxes or public folders.
This has been fixed.
The 'From' field was blank in email items with attachments that were restored to Exchange Server 2010 after Enterprise Vault 10.0.3 cumulative hotfix 1 or 2 had been installed.
The workaround was to uninstall the hotfix.
This has been fixed.
When the FixOrphanedShortcut registry value was enabled, public folder targets were not archived. Error event 4167 was logged for each failed public folder target.
This has been fixed.
If you use FixOrphanedShortcut, remember to remove it as soon as the shortcuts have been fixed. This registry value may have an adverse effect on archiving performance.
The Exchange Journaling task could terminate unexpectedly when the Data Classification Services filter processed messages that did not have the PR_SENSITIVITY MAPI property. This was the case with messages that had been delivered to Exchange Server 2013 by SMTP.
The problem occurred only on Exchange Server 2013.
This has been fixed.
Outlook calendar items that had been archived and re-archived a number of times could fail to be archived into a mailbox archive when Virtual Vault was enabled. Event ID 6592 "Abnormal error occurred Reference: GOPV/dt" was logged for each item that failed.
This has been fixed.
Depending on the Windows system locale that was set on the server, Mobile Search could show the following error when the Sent filter was set to "Anytime":
An Internal Error has occurred
This has been fixed.
The formatting of messages that were larger than the PageContentSize value was poor. This was because messages that are larger than the PageContentSize limit are split into pages and the formatting is removed.
This has been fixed as follows:
Mobile Search failed to perform a search and returned one of the following errors:
An internal failure occurred. Internal Error: No such interface supported (0x80004002)
Unspecified error 0x80004005
This issue did not occur if Mobile Search was installed on an Enterprise Vault server. (Symantec recommends that Mobile Search is not installed on an Enterprise Vault server except for pilot or demonstration purposes.)
This has been fixed.
During client-driven PST migration, when Enterprise Vault encountered a backslash character in a folder name in a PST file, it treated the backslash as a delimiter in a folder structure. For example, if a PST file contained a folder called July\August, rather than create a folder of the same name in the associated archive, Enterprise Vault created the following folder hierarchy:
July \August
This has been fixed. In this example, Enterprise Vault now correctly creates an archive folder called July\August.
When the 'TO' 'CC' and 'BCC' fields of a calendar item were all blank, Enterprise Vault did not index any recipient information. These fields are blank in the sender's copy of meetings and appointments.
If all the fields are blank, Enterprise Vault now checks for values in the REQUIREDATTENDEES, OPTIONALATTENDEES, and FYIATTENDEES. If any of these are present, Enterprise Vault uses them to obtain recipient information as follows:
In the Site Properties: Storage Expiry tab, storage expiry can be configured to run to a schedule, and to run in report mode. In this case, the Domino mailbox archiving task did not honor the Run in report mode option and deleted any shortcuts that matched the retention criteria.
This has been fixed.
In some circumstances the Domino Archiving task could repeatedly fail to archive some items, producing one of the following errors:
This has been fixed. Items that previously failed are now blacklisted and an event is logged. The event ID depends on which version of Enterprise Vault you are using, as follows:
If items have previously failed in this manner it is possible that Enterprise Vault archived many duplicates of those items. For details on how to manage blacklisted items, see http://www.symantec.com/docs/TECH201608.
In some circumstances, Domino journal custom filtering rules that matched any combination of sender, recipient, and message direction, could apply the associated action to all subsequent messages, even those not matched by the rule.
This issue was described in technical note TECH204198. See http://www.symantec.com/docs/TECH204198.
This has been fixed.
Before version 10.0.3, Enterprise Vault did not adjust the maximum size of the Vault Cache file EVOffline.nsf to reflect correctly the percentage set by the Domino desktop policy setting Maximum use of initial free space. This behavior was fixed in Enterprise Vault 10.0.3, so that Enterprise Vault now adjusts the maximum size of a Vault Cache as the amount of free space changes.
In Enterprise Vault 10.0.4, the policy setting is renamed to Maximum use of current free space.
When the Domino mailbox archiving task found a mailbox for which the corresponding mailbox had been deleted, event 41170 was logged correctly, as follows:
The archive for an enabled mailbox could not be found. The archive may have been deleted. This mailbox has been disabled. Enable the mailbox again to resume archiving.
Event 41170 was then logged on each subsequent run of the mailbox archiving task.
Event 41170 is now logged on the first run of the mailbox archiving task after the archive has been deleted but not on subsequent runs of the archiving task.
The banner link in Internet shortcuts failed if the user's home mail server was a Domino cluster node that was unavailable.
This has been fixed.
For Domino 8.5.3 and later, banner links in Internet shortcuts no longer require changes to Forms files on the users' target mail servers.
Even though the vault store setting for Remove safety copies was Never, Enterprise Vault created shortcuts to archived email messages after the vault store was backed up, if the Domino Mailbox policy shortcut creation rule was Create shortcut to archived item after archiving.
This has been fixed.
A File System Archiving task now checks whether any archives are already associated with a folder path before it creates an archive for the folder path. If an archive is already associated with the folder path, that archive is assigned to the archive point. If more than one archive is associated with the folder path, the oldest associated archive is assigned to the archive point.
For more information, see "About adding target volumes, target folders, and archive points for FSA" in the Setting up File System Archiving guide.
File System Archiving’s volume and folder policies now include an option on the Permissions tab which lets you choose whether to archive or ignore files that are under Dynamic Access Control. The default policy setting is not to archive these files.
For more information, see "About archiving from Windows Server 2012 file servers" in the Setting up File System Archiving guide.
File blocking did not send a notification email if the user's login and email address formats were different. For example, the email would fail if the user's login was 'APerson' and the email address was 'A_Person@example.com'.
There is a new notification message variable that you can use if the user's logon and email names might be different.
The new variable is [USER MAIL ID] and it contains the email ID of the user who caused the action. This ID is taken from Active Directory.
An FSARunNow Archive command failed to run if you specified a file server with the FileServerEntryID parameter.
The utility reported that no volumes were found for the file server.
This has been fixed.
A problem could occur when using File System Archiving with placeholder shortcuts from an EMC Celerra or VNX server running the DART operating system. When the File System Archiving task archived the files, it failed to create the associated placeholders. The File System Archiving task report showed the following error for each affected file:
OFFLINE_MTIME_BAD_FORMAT
The problem occurred only on the first archiving run, when the files were archived. In subsequent runs the placeholders were created successfully for the previously archived files. The problem was caused by a parameter value that was passed incorrectly between Enterprise Vault and the EMC Celerra/VNX target when the file was archived.
This has been fixed.
The recall of archived items from placeholders on EMC Celerra/VNX servers was occasionally very slow. When Enterprise Vault handled multiple download requests for the same saveset from the Celerra/VNX server, an error could result in a 60-second delay before a timeout triggered the processing of the next request.
This has been fixed.
Retrieval of large items could be very slow for Celerra placeholders, with some versions of IIS. After the retrieval of each chunk of an item, the instruction to keep the HTTP connection alive was not honored.
This has been fixed.
Even though the vault store setting for Remove safety copies was Never, Enterprise Vault created internet shortcuts to archived files after the vault store was backed up, if the folder policy shortcut creation rule was Create Shortcut immediately.
This has been fixed.
FSA uses alternate data streams on target folders to indicate archive points and folder points. If a target returned an error while a File System Archiving task was trying to save an alternate data stream, the alternate data stream was truncated and the following error was logged in the File System Archiving task report:
*** Warning *** - One more Root folders were not synchronized for many folders
Now, FSA writes the updates to the content of the alternate data stream in a transactional manner to prevent truncation. If the File System Archiving task fails to save the alternate data stream on the first attempt, it performs a number of retries.
If you ran the FSAUtility -pm command to migrate placeholders to a NetApp file server, the command could fail with the following error:
Index was out of range. Must be non-negative and less than the size of the collection.
The problem occurred when FSAUtility did not find a matching entry in the ComputerEntry table of the Directory database for the name of the Enterprise Vault server on which you ran the command. FSAUtility uses this table entry to check whether the Enterprise Vault server is registered with the destination NetApp file server's FPolicy. In a clustered environment the ComputerEntry table stores the virtual server name, which did not match with the NetBIOS computer name of the Enterprise Vault server.
This has been fixed. If the Enterprise Vault server is in cluster mode, FSAUtility now reads the virtual server name from the registry, to enable a successful match in the ComputerEntry table.
When users clicked Show archived versions for this item for an archived item, the operation sometimes failed and the following message appeared:
Your search encountered an error. If the problem persists, contact the site administrator.
Error details:
Input string was not in a correct format
This occurred when the regional settings for the site, or the user's personal regional settings, were set to a locale that uses a comma as a decimal mark.
This has been fixed.
If you search for SharePoint social content by specifying the number of attachments, the search returns items with a different number of attachments.
To get the correct search results, specify one more attachment than you require. For example, if you are searching for list items with three attachments, specify four attachments.
Enterprise Vault archives content from only those web applications in SharePoint 2013 that have integrated Windows authentication.
Archiving is not supported for SharePoint web applications that have form-based or trusted identity provider authentication.
When a SharePoint Web Application had been extended to another IIS website, users could not open shortcuts if they used the extended website URL to access SharePoint.
This has been fixed.
In the Administration Console the New Partition wizard showed only the first partition of each cluster shared disk. The result was that only the first partition could be added to a vault store.
This has been fixed.
Processing attached messages that had thousands of recipients caused high CPU usage.
This has been fixed. Storage Crawler now uses considerably less CPU resource when processing these attached messages.
In some circumstances, Enterprise Vault failed to index attachment properties for items archived in Enterprise Vault 8.0 and later. This occurred only in the following circumstances:
This has been fixed. For more information, see technical alert TECH203789 at http://www.symantec.com/docs/TECH203789
In some circumstances, the Storage Expiry Report event logged by the Storage service showed that storage expiry performance was low.
The performance of storage expiry has been improved.
In some circumstances, requests to set vault store backup mode took a very long time.
This has been fixed.
This issue only affected write once read many (WORM) storage devices that allow retention period extension.
When Enterprise Vault tried to extend a saveset retention period, it always used the expiry basis (modification date or archived date) that was set in the site properties. However, the expiry basis can also be set in the retention category properties. If the saveset expiry basis and the site expiry basis were different, the new retention period was calculated incorrectly.
This has been fixed.
The Administration Console restricted the maximum archive size that you could enter on the Archive Usage Limit tab in the Site Properties or the Archive Properties to 16 GB. However, you could set a higher value manually in the Directory database.
This has been fixed. The maximum archive size is now 200 GB.
The date field of messages archived as attachments to other messages was not indexed correctly. The result was that you could not successfully search by date for a message archived as an attachment to another message.
This has been fixed.
The Enterprise Vault Indexing service failed to start when an IP address was used in the IIS Default Web Site Bindings.
When the failure occurred, Event 41293 "An unexpected error has occurred" was logged.
This has been fixed.
It was possible for a build-up of non-committed records to occur in the vault store database if the records related to updates or deletions of items that were missing from the index.
This has been fixed.
This issue only affected Centera devices in compliance mode.
When the expiry of archived items was based on the modified date, savesets were stored as if expiry was based on the archived date. The result was that an attempt to delete an expired item could cause an error that prevented deletion.
For example, a saveset might have had a modified date of January 1, 2009 and a retention period of ten years. If it was archived on January 1, 2013 then the expected clip retention period was six years, but the actual clip retention period was 10 years.
This has been fixed. Enterprise Vault prevents existing savesets from being deleted for a period equal to the difference between the modified date and the archived date. For newly archived items, when expiry is based on the modified date, savesets can be deleted at the correct time.
A problem could occur when archiving to Centera without the "Enable device level sharing" option. If lots of large items were archived and the collection sets reached the maximum saveset data blob size (10 MB) before reaching the maximum collection size (100 savesets), then saveset collection would become very slow. The resulting backlog of savesets could cause the Centera staging area to fill up.
This has been fixed.
FSA Reporting's Storage Trends report failed to display if the SQL Server used a language other than US English.
When you ran the report the following SQL Server error appeared:
The conversion of a char data type to a datetime data type of
datetime values is out of range. The Statement has been Terminated.
This has been fixed.
An FSA Reporting scan could fail on a clustered file server, with DTrace reporting the following error for the FSAReportingService:
Version not found from registry. Returning default version. Error Code: 2.
The error occurred because the FSA Agent version was not recorded correctly in the registry on the clustered nodes.
This has been fixed.
When a Move Archive operation encountered a mailbox folder that had been created by Enterprise Vault Policy Manager (EVPM), and from which no items had yet been archived, the folder structure in the associated archive became corrupted. This occurred during Move Archive's "Updating shortcuts" stage. The corruption also caused archiving to stop for the mailbox that contained the EVPM-created folder.
This has been fixed.
Even after configuring Move Archive to skip duplicate items, using SkipDuplicateItems in the configuration file, it raised the following exception when it encountered duplicates:
Exception: System.Runtime.InteropServices.COMException (0x8004030D): Item Id is not unique within the target Vault Store.
This has been fixed.
Note that this issue was also present in Enterprise Vault 10.0.3, and was fixed by Enterprise Vault 10.0.3 Cumulative Hotfix 2 (see http://www.symantec.com/docs/TECH205731). If you use Move Archive on Enterprise Vault 10.0.4 to move an archive to a 10.0.3 destination server which does not have Cumulative Hotfix 2, this issue can still occur.
When you performed the following operations on a partition on a streamer storage device, the resulting log files would report the wrong information on any mismatches in Converted Content Stream sizes:
This has been fixed.
When it processed one or more large file items in a partition, the operation Verify ArchiveObjects > FingerprintValid would fail to complete if it could not locate one or more .DVFSP files in the partition. When this problem occurred, the following error message would appear in the log file:
**** EVSVR ERROR: Failed to process Partition 'partition_name': Error: The system cannot find the file specified. (0x80070002)
This has been fixed.
The following issues could sometimes arise when you ran the EVSVR operation Verify ArchivesDirectory or Repair ArchivesDirectory on a File System archive:
These issues have been fixed. Note that the log files for these two operations have been reorganized and now include the following sections:
The "Summary" section of the log file now provides the following information on inconsistencies between the ArchivePoint records in the vault store database and the Archive records in the Directory database:
Records in Vault Store Database:
ArchivePoint records: nnn (Number of ArchivePoint records in the vault store database)
Records in Directory Database:
Root records found: nnn (Root records in the Directory database)
Root records missing: nnn (Root records missing from the Directory database)
Archive records found: nnn (Archive records in the Directory database)
Archive records missing: nnn (Archive records missing from the Directory database)
Missing Root records: nnn (Both the Root record and Archive record are missing)
Missing Archive records: nnn (The Root record exists, but no Archive record was found)
Incorrect Archive records:
Root without Archive: nnn (The Root record exists, but no Archive record was found)
Type is Folder: nnn (The Root record type is "Folder" and not "Archive" as expected)
Type is unknown: nnn (The Root record type is unknown)
Similarly, the log file now provides the following information on inconsistencies between the Vault records in the vault store database and the ArchiveFolder records in the Directory database:
Records in Vault Store Database: Vault records: nnn (Number of Vault records that are not associated with archive points in the vault store database) Vault records processed: nnn (Number of Vault records processed) Records in Directory Database: Root records found: nnn (Root records in the Directory database) Root records missing: nnn (Root records missing from the Directory database) ArchiveFolder records found: nnn (ArchiveFolder records in the Directory database for the vault store being processed) ArchiveFolder records missing: nnn (ArchiveFolder records missing from the Directory database for the vault store being processed) Root, ArchiveFolder and Archive records missing: nnn (Detailed breakdown of the missing records) Root and ArchiveFolder records missing: nnn (Detailed breakdown of the missing records) ArchiveFolder records missing: nnn (Detailed breakdown of the missing records) Summary of missing records by item count: With Items: nnn (Missing ArchiveFolder records with archived items) Without Items: nnn (Missing ArchiveFolder records without archived items) Incorrect ArchiveFolder records: Root without ArchiveFolder: nnn (The Root record exists, but no ArchiveFolder record was found) Type is Archive: nnn (The Root record type is "Archive" and not "Folder" as expected) Type is unknown: nnn (The Root record type is unknown) NULL ContainerRootIdentity: nnn (The Root record's ContainerRootIdentity column is NULL)
These changes to the log file are also evident when you run the operations on Exchange Mailbox archives.
Selecting a value in one field of the EVSVR Operations dialog box would sometimes reset the value that you selected in another field. For example:
This has been fixed.
In rare circumstances, the EVSVR operation Repair DatabaseReferences did
not properly validate and repair the database records of certain savesets
that Enterprise Vault had collected into more than one .cab file.
As a result, these records would be left with Collection ID values that pointed
to the wrong collection records. Users who tried to retrieve the affected
savesets would consequently receive the message "Item is no longer in the
vault".
This has been fixed. EVSVR now performs an additional validation of the Collection ID values for the saveset records before it updates the vault store database.
In Enterprise Vault 10.0 through 10.0.3, when you ran the Index Verify
wizard in the Administration Console to check the health of a 32-bit index
volume, it would sometimes leave an IndexMissing.log file on
that volume, even after you had resolved any issues with it. If you subsequently
conducted a search of the index volume with Compliance Accelerator or Discovery
Accelerator, the presence of the IndexMissing.log file would
cause the following message to appear in the search results pane:
Some items could not be searched. Items or content missing.
These messages were informational messages rather than error messages; it was safe to ignore them after you had determined that there were no items in the index volume that Enterprise Vault had failed to index.
This has been fixed.
Searching for items that were archived by File System Archiving or SharePoint archiving could produce unexpected results if you included the retention category in the search criteria. The issue occurred if the retention category based the expiry on the modified date.
This has been fixed.
In Advanced Browser search, the drop-down list next to All Fields no longer includes the option is exactly phrase.
Enterprise Vault is supported for use with version 6.0 of Veritas Cluster Server (VCS). However, with earlier versions of Enterprise Vault, you needed to install a hotfix (TECH178773) before you could configure it in a VCS 6.0 cluster.
This is no longer the case. Enterprise Vault 10.0.4 comes with components that are compatible with VCS 6.0.
Saveset files that contained corrupt header information caused retrieval processes to fail. For example, EVSVR operations could fail when they encountered corruption.
This has been fixed. During retrieval operations, Enterprise Vault uses default header values when it encounters corruption in saveset headers.
This release includes the following Outside In® Technology content converters and patches from Oracle® Corporation:
The following additional file types are now excluded from conversion: MP3, MP4, MKV.
Files of these types cannot be converted.
These additional file types are automatically added to the ExcludedFileTypesFromConversion registry value when you upgrade to Enterprise Vault 10.0.4.
Enterprise Vault failed to archive items when their archive dates were set to be earlier than 1/1/1900.
This has been fixed.
In Enterprise Vault 10.0.3 some SCOM alerts were duplicated unnecessarily.
The duplication has been reduced.
Event 13343 could sometimes be logged in error, with the following text:
An exception was detected in 'DeleteConnection' while accessing
the Vault Database EnterpriseVaultAudit
This has been fixed.
Some items or attachments can result in very large files of converted content. The conversion and indexing of these files could affect archiving performance. Files of several gigabytes could cause archiving errors.
This has been fixed. By default, when converted content is larger than 30MB, that converted content is neither indexed nor stored. The original item or attachment is archived as normal.
You can use the MemLimitForTextConversionFallback registry value to control the maximum size of converted content that can be indexed and stored. See the Registry Values manual.
The table below shows the new rules that have been added to the SCOM pack.
| Event | Target | ID | Rule Name |
|---|---|---|---|
| 4257 | Admin Service | Symantec.EnterpriseVault.AdminService.Event_filter_activated_or_config_changed | Event Filter activated or configuration updated |
| 4259 | Admin Service | Symantec.EnterpriseVault.AdminService.Event_Filter_deactivated_events_suppressed | Event Filter deactivated. Some events were suppressed |
| 4258 | Admin Service | Symantec.EnterpriseVault.AdminService.Event_Filter_deactivated_no_events_suppressed | Event Filter deactivated, no events were suppressed |
| 4254 | Admin Service | Symantec.EnterpriseVault.AdminService.Events_suppressed_error | Events suppressed |
| 4255 | Admin Service | Symantec.EnterpriseVault.AdminService.Events_suppressed_warning | Events suppressed |
| 3460 | Exchange Journaling Task | Symantec.EnterpriseVault.ExchangeJournalingTask.Task_logon_failure | Task logon failure |
| 3467 | Exchange Mailbox Archiving Task | Symantec.EnterpriseVault.ExchangeMailboxArchivingTask.Error_processing_archiving_request | Error processing archiving request |
| 3460 | Exchange Mailbox Archiving Task | Symantec.EnterpriseVault.ExchangeMailboxArchivingTask.Task_logon_failure | Task logon failure |
| 3465 | Exchange Mailbox Archiving Task | Symantec.EnterpriseVault.ExchangeMailboxArchivingTask.Unsupported_Outlook_version_2 | Unsupported Outlook version |
| 3471 | Exchange Mailbox Archiving Task | Symantec.EnterpriseVault.ExchangeMailboxArchivingTask.WMI_Service_not_running | Windows Management Instrumentation Service not running |
| 3466 | Exchange Public Folder Task | Symantec.EnterpriseVault.ExchangePublicFolderTask.No_legacy_Public_Folder_mailboxes | No legacy public folder mailboxes |
| 3460 | Exchange Public Folder Task | Symantec.EnterpriseVault.ExchangePublicFolderTask.Task_logon_failure | Task logon failure |
| 41470 | File System Archiving Task | Symantec.EnterpriseVault.FileSystemArchivingTask.Archive_associated_with_other_volume | Archive associated with other volume |
| 41468 | IndexingService | Symantec.EnterpriseVault.IndexingService.Index_locations_in_backup_mode_schema_upgrade_require | Index locations in backup mode require schema upgrade |
| 41488 | IndexingService | Symantec.EnterpriseVault.IndexingService.Indexing_metadata_corrupt | Indexing not starting because of corrupt repository.xml |
| 41447 | Server | Symantec.EnterpriseVault.Server.Exchange_mailbox_sync_not_occurring | Exchange mailbox synchronization is not occurring |
| 41446 | Server | Symantec.EnterpriseVault.Server.Exchange_provisioning_task_run_incomplete | Exchange Provisioning task run was incomplete |
| 41444 | Server | Symantec.EnterpriseVault.Server.Multiple_failed_tasks__All | Multiple Enterprise Vault tasks have failed (All) |
| 41445 | Server | Symantec.EnterpriseVault.Server.Multiple_failed_tasks__Partial_list | Multiple Enterprise Vault tasks have failed (Partial list) |
| 41443 | Server | Symantec.EnterpriseVault.Server.One_failed_task | One Enterprise Vault task has failed |
| 41448 | Server | Symantec.EnterpriseVault.Server.Storage_expiry_not_processing_vault_stores__All | Storage expiry not processing one or more vault stores (All) |
| 41449 | Server | Symantec.EnterpriseVault.Server.Storage_expiry_not_processing_vault_stores__Partial_list | Storage expiry not processing one or more vault stores (Partial list) |
| 4266 | Server | Symantec.EnterpriseVault.Server.Thread_running_unexpectedly_after_wait | Thread running unexpectedly after wait |
| 29017 | StorageService | Symantec.EnterpriseVault.StorageService.Last_generated_collection_id_could_not_reset | Last generated collection ID higher than highest collection ID in vault store database |
You can now choose the geographical region where Amazon Simple Storage Service stores the buckets that you create using the Administration Console. The Advanced tab of the vault store partition properties includes the Amazon bucket region parameter, which provides various region options.
For more information, see http://www.symantec.com/docs/DOC5387.
Copyright © 2013 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, the Checkmark Logo, 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