Symantec Enterprise Vault (tm) 5.0 - Service Pack 7 (build 6299)

Article:TECH50802  |  Created: 2007-01-12  |  Updated: 2008-01-08  |  Article URL
Article Type
Technical Solution



Symantec Enterprise Vault (tm) 5.0 - Service Pack 7 (build 6299)


This document is intended to give an overview of the changes introduced by Symantec Enterprise Vault 5.0 Service Pack 7 (SP7).
The installation media for Symantec Enterprise Vault 5.0 SP7 can be downloaded from the link at the end of this article.

Before installing or upgrading to Enterprise Vault 5.0 SP7, you must read this document which can be found in full as the file Updates.htm in the installation media, and also the ReadMeFirst (ReadMeFirst.htm) for Enterprise Vault 5.0.

For instructions on installing or upgrading to Enterprise Vault 5.0 SP7, see the Installing and Configuring manual, which is in the Documentation folder in the installation media.

For the latest information on supported versions of software, see the Enterprise Vault Compatibility Charts at

High priority fixes

Changes to North America Daylight Saving Time

The 2005 Energy Policy Act passed by the U.S. Congress changed the dates of both the start and end of Daylight Saving Time (DST) for the U.S. and Canada. The DST changes will be applied in 2007. These changes may cause items to be indexed with an incorrect time stamp during the extended period of DST. This could result in the items being incorrectly excluded or included in searches using date-based criteria. In addition, the date and time properties of items with time stamps prior to 2007 may be presented as an hour later than the actual values.

For detailed information on this issue, see the following Enterprise Vault TechNote:

Note that the Enterprise Vault updates for this issue rely wholly on the deployment of the relevant Microsoft DST patches for Windows, Exchange Server, SharePoint, Outlook and any other applicable application. See the above TechNote for more information.

Symantec Corporation strongly recommends that you deploy the relevant Microsoft DST patches and Symantec Enterprise Vault Service Packs before March 11th 2007.

Searches could return duplicate results, and fail to show some results [Ref 507025-2, CAP355, 603159, 602549]

Under certain circumstances a search could return duplicate results, and fail to show some results. This could, for example, affect Discovery Accelerator and Compliance Accelerator searches, if the number of results exceeded the search result chunk size (default value 50,000).

This has been fixed. For more information


No client upgrades required

The changes made in Enterprise Vault 5.0 SP7 do not require you to upgrade Enterprise Vault clients.

Client installations

Do not install the Enterprise Vault 5.0 SP7 Self-Installing User Extensions (the HTTP 'Lite' client).
There is no problem with installing the User Extensions (the DCOM 'Full' client).

If you have made the Self-Installing User Extensions available to users on your network you need to copy your existing Self-Installing User Extensions files before upgrading to Enterprise Vault 5.0 SP7 and then replace the new files with your saved copy.
For further information see the Updates.htm file in the installation media for Symantec Enterprise Vault 5.0 SP7.

New features and fixes

Making the Journaling Service reprocess failed messages [Ref 507022 THR34396 E595614]

Archive Explorer problem after installing Microsoft security update KB924191 [Ref 507025-1, 603205-1, 604053, CAP961, E832762]

Changes to File System Archiving

File server fails to shutdown cleanly [Ref 507019-1]

When shutting down an archiving target file server, that was running Symantec AntiVirus™ 10 with the Streaming File Objects (SFO) option enabled, the Windows server intermittently failed with a blue screen.

Placeholder shortcuts cannot be created for files with extended attributes [Ref 507019-2]

If configured in the archiving policy, Enterprise Vault attempted to create Placeholder shortcuts for files with extended attributes. These are typically files that originally resided on some older operating systems, such as IBM OS/2. The shortcuts were 0 KB in size and could not be used to retrieve the files.

This limitation is because Enterprise Vault implements Placeholder shortcuts as reparse points and NTFS support for extended attributes and reparse points is mutually exclusive.

If a file does have extended attributes, Enterprise Vault archives the file but does not create a Placeholder shortcut. An error is logged to the archiving report. Alternatively, you can remove the extended attributes from such files before archiving.

Changes to OWA support

Could not use OWA to access archived items in a cross-domain environment [Ref 507004]

Changes to the Administration Console

Cannot list archives when security descriptors are corrupt [507006, E515833]

It was not possible to list archives that had corrupt security descriptors.

Other changes

Enhancements to the way the Journaling Service handles messages with failed distribution lists in the address fields [Ref 507005 THR34425]

Corrupted shortcuts on Exchange Server 5.5 [Ref 507021 E595614]

Shortcuts could be corrupted when archiving HTML messages that had attachments from Exchange Server 5.5 with the Enterprise Vault shortcut settings set to 'Use Message Body'. Shortcuts to such messages were shown correctly in the Outlook preview panel but showed an error when the user attempted to open them. The corrupt shortcuts could be restored correctly.

Improved use of SQL resources [Ref 507013 THR34837]

The use of SQL resources could gradually increase over a long period of time.

Renamed PST import folders correctly archived [Ref 507008, E518559]

PST migration fails if messages present in PST root folder [Ref 507026-1, CAP303, 603142]

PST migration fails if migrating to an unstructured mailbox archive [Ref 507026-2, CAP303, 603142]

Importing a PST file to an unstructured mailbox archive failed if you selected the following settings in the PST Migration wizard:

  • Create shortcuts in the mailbox.
  • A folder under the root folder in the mailbox to correspond the root folder of the PST.

Custom filter prevents manual archive [Ref 507001 THR34425]

When a custom filter was defined, it was sometimes not possible to archive an item manually when using the Self-Installing User Extensions.

Messages fetched using Simple API displayed incorrectly [Ref 507012 THR34569]

The Simple API fetch method did not set the storage class of messages as CLSID_MailMessage. This meant that fetched messages had the message class IPM.Document.msgfile instead of IPM.Note, and were therefore not displayed correctly in Outlook.

Searches fail if double quote (") in Archive name [Ref 507017]

Browser searches failed with the message service is not available if there was a double quote (") in the Archive name.

Attachments (78.5 MBytes)

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices