Veritas Enterprise Vault (tm) 6.0 Service Pack 2 revision 6.0.0.7791

Article:TECH46489

Created: 2006-01-27

Updated: 2006-01-15

Article URL http://www.symantec.com/docs/TECH46489

Article Type
Technical Solution

Product(s)

Show all

Environment

Show all

Languages

Show all

Problem

Veritas Enterprise Vault (tm) 6.0 Service Pack 2 revision 6.0.0.7791

Solution

Veritas Enterprise Vault (tm) 6.0 Service Pack 2

This document describes outstanding issues and the changes introduced by Enterprise Vault 6.0 Service Pack 2 (SP2).

The download is comprised of the following:

Enterprise Vault for Microsoft Exchange 6.0 SP2

Enterprise Vault for File System Archiving 6.0 SP2

Enterprise Vault for Microsoft Sharepoint 6.0 SP2

Enterprise Vault for Lotus Domino 6.0 SP2

Enterprise Vault for SMTP Archiving 6.0 SP2

Symantec recommends all customers sign up for our Email Notification Service by clicking "Subscribe" in the top right corner of the Support site http://support.veritas.com and selecting the products you are running. To receive monthly updates on new r republished TechNotes, select "Digest" updates. To receive notifications of critical technical issues , select "Software Alerts"

See the Enterprise Vault Certification Tables: http://support.veritas.com/docs/276547 for the latest information on supported software versions

Contents

1. Issues and Restrictions

2. New features

3. Changes affecting users

4. Administration Console

5. File System Archiving

6. PST migration

7. Enterprise Vault for Domino Journaling

8. Other changes

1. Issues and Restrictions

Restoring from Domino Journal archives

A new feature in Enterprise Vault 6.0 SP2 is the ability to restore from Domino Journal archives. At the time of release to manufacturing, outstanding issues prevented Symantec from including this feature in this update.

Working together with IBM® Lotus® Software, Symantec has now resolved this issue. To enable this feature, refer to TechNote http://support.veritas.com/docs/283407

Multilingual Unicode data

There are outstanding issues related to the use of multilingual Unicode data. For details, see TechNote 282030, http://support.veritas.com/docs/282030 , Enterprise Vault 6.0 Service Pack 2 (SP2) Issues Relating to Multilingual Unicode Data

Exchange Server and Enterprise Vault cannot coexist on a Veritas Cluster Server node

Enterprise Vault cannot be installed on the same Veritas Cluster Server node as Exchange Server.

For more information, see TechNote 282080: http://support.veritas.com/docs/282080

2. New Features

Veritas Cluster Server

Enterprise Vault 6.0 SP2 integrates with Veritas Cluster Server (VCS) to provide a highly available solution for Enterprise Vault in a VCS cluster. VCS must be version 4.3 MP1 or later: http://support.veritas.com/docs/281154

The VCS GenericService agent detects an application failure if a configured service is not running. When this occurs, the Enterprise Vault service group is failed over to the next available system in the service group's SystemList and the services are started on the new system, thus ensuring continuous availability for the data that Enterprise Vault is managing and archiving.

See Installing and Configuring in the Documentation folder in the kit, or TechNote: http://support.veritas.com/docs/282074 , for more information about configuring Enterprise Vault in a cluster configuration.

Enterprise Vault Deployment Scanner

The Enterprise Vault Deployment Scanner is a wizard that checks that all the prerequisites for Enterprise Vault have been correctly installed.

The tool creates a Reports folder in the folder in which it is run and places a report file in the Reports folder.

For more information, see the documentation in the in the Deployment Scanner folder in the kit:Enterprise Vault 6.0 SP2\Deployment Scanner

The Deployment Scanner is available for download separately: http://library.veritas.com/docs/282034

Linking mailboxes to archives

When using the Enable Mailbox wizard, it is now possible to select an existing archive to be used for a mailbox that is being enabled. This is useful when a mailbox has been migrated to a different Exchange Server in the same Enterprise Vault site and needs to be enabled for archiving to the same archive as before.

Migration of remote PST files

Client driven migration now supports migration of PST files that are on remote network drives, provided that the PST files are listed in the users' Outlook profiles.

Note that Microsoft does not support the use of PST files over a LAN or WAN link. See Microsoft Support article 297019: http://support.microsoft.com/default.aspx?scid=kb;en-us;297019 for more information

Age based archiving from Microsoft SharePoint [Ref 602137]

When archiving from Microsoft SharePoint, it is now possible, in both SPS 2003 document libraries and Windows SharePoint services document libraries, to configure age based archiving with documents being replaced by shortcuts:

a. Users can use the shortcuts to access the original documents.

b. Users have access to the old versions of the original document because of the integration with the SharePoint version history display.

c. Users can restore documents from the SharePoint version history display.

To set up age based archiving, define a SharePoint policy in the Administration Console. On the Shortcuts tab, specify the age at which documents must be archived and, optionally, select Replace items with shortcuts to create shortcuts

Changes to index searches

There are changes to the search user interface when searching rolled over archives. In previous releases, users had to select a date range when searching rolled over archives. This is no longer required: there is now a maximum number of search results that can be displayed. You can use the following WebApp.ini settings to control the behavior of searches of rolled-over archives:

a. UseFederatedSearch - Whether or not to enable searches across multiple index volumes. Default is 1 (enable automatic searches across rolled-over archives)

b. FederatedSearchMaxVolSets - The maximum number of index volume sets to search simultaneously when performing a search of rolled-over archives. Default is 5

c. FederatedSearchMaxItems - The maximum number of items to return in a result set and therefore the maximum number of items to be located in each index volume set. Default is 1000

d. FederatedSearchTimeout - The maximum amount of time to allow for a search across rolled-over archives. Default is 60 (seconds)

The search help has been modified to describe the new behavior.

Disabling Indexing for FSA

When using File System Archiving (FSA), it is now possible to specify, per archive point, whether to perform indexing. This provides greater archiving performance but, because archived files are not indexed, it is not possible to search for items that have been archived.

To control whether indexing is performed, use the new <indexDisabled> setting in the XML file that you supply as a parameter to the ArchivePoints tool. The default setting of "False" for <indexDisabled> means that indexing is enabled. To disable indexing, specify a "True" for <indexDisabled>

For example, to disable indexing:

<archivePoint mlns="urn:kvsplc-com:FileSystemFolderArchivePoint">

<indexDisabled>True</indexDisabled>

</archivePoint>

To enable indexing:

<archivePoint mlns="urn:kvsplc-com:FileSystemFolderArchivePoint">

<indexDisabled>False</indexDisabled>

</archivePoint>

You can enable indexing after it has been disabled. Once enabled, indexing will start after the next file has been archived, or when you use the Index Volume Replay tool to update the index. Note: If there is a large backlog, the indexing could take a long time.

See the Utilities manual for a description of Index Volume Replay: http://support.veritas.com/docs/282077

Collection file verification

When you use collection files on NTFS volumes or network share partitions, Enterprise Vault now automatically verifies the contents of each collection file when it has been created. This ensures that there is no corruption of the file.

Because of the performance impact of this change, the following additional changes have been made:

a. There is new DWORD registry value that enables you to turn off collection file verification. The value is VerifyCollectedFiles, under the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Storage

Set VerifyCollectedFiles to 0 to turn off collection file validation

b. The default maximum collection size has been reduced from 200 MB to 10 MB. Increasing this value when collection files verification is on has a significant performance impact.

c. The permissible range for the maximum CAB file size is now 1-99 MB; previously this was 1-999 MB. Existing partitions where this setting exceeds the permissible range will be reset to 10 MB, which affects new collections.

Custom filtering enhancements

In previous releases, you could specify additional MAPI properties to be indexed by Enterprise Vault when archiving Exchange Server messages. A new <NAMEDPROP> element has been added to custom filtering ruleset files to enable you to select messages to archive, based on the value of Named MAPI properties that you have defined in the custom properties.xml file.

Named properties can be custom MAPI properties or standard MAPI properties, such as Outlook Categories, and can be multi-valued. For example, if company policy requires certain Outlook Categories to be added to messages containing particular information, you can configure custom filtering to select and archive messages that have the Outlook Categories set. Because Enterprise Vault indexes the Named properties, you can later search archives for messages that have the required Outlook Categories.

In the custom properties.xml file, you can now define Lotus Domino properties to be indexed by Enterprise Vault when archiving Lotus Domino messages.

See Installing and Configuring for more information on custom filtering: http://support.veritas.com/docs/282074

Content Management API

The existing Enterprise Vault Simple API provides an interface for an application to perform a simple set of operations within Enterprise Vault. The API was not designed to be used beyond the store, retrieve, and delete operations provided. Content Management API provides a new, object oriented API for use by Enterprise Content Management (ECM) applications that manage documents and records stored in Enterprise Vault.

The Content Management API will provide the following functionality to third party application developers:

a. Create a new archive

b. Store items in an archive

c. Fetch items from an archive

d. Delete items from an archive

e. Get archive properties

f. Get Item properties

g. Extend the compliance period on an item in an archive

h. Copy an item between archives (or within the same archive)

i. Move items between archives

j. Put item on hold, store metadata associated with the hold and release items from hold (see Legal Hold)

k. Handle large items

Note: The existing Simple API will continue to be supported but will not be extended.

The following features are included in the Content Management API:

Legal Hold

Legal Hold is an extension to the Content Management API, which enables third party applications to put a hold on archived items to safeguard them from expiry and user deletion. The API also enables the applications to remove the hold placed on items. For example, using this API, third-party records management companies can provide legal hold in their applications when working with documents stored in Enterprise Vault. Support for this API feature will be added to Discovery Accelerator in a future release.

Custom properties API

API documentation will include information on how third party applications can access the Enterprise Vault custom properties, including Named MAPI properties and Lotus Domino message properties.

API retrieval of items from shortcuts

API documentation will include information on shortcuts that enable third party applications to open the shortcut and use the information to retrieve the original item from the archive using the SimpleAPI or new Content Management API.

Hebrew Translation

The Enterprise Vault User Extensions are now also supplied in Hebrew. Additionally, Archive Explorer and the search applications are also supplied in Hebrew.

Documentation changes

Additions to Installing and Configuring: http://support.veritas.com/docs/282074

The TechNotes on custom filtering and on SMTP archiving have now been incorporated into Installing and Configuring.

Installing and Configuring also contains extensive information on configuring Enterprise Vault in a VERITAS Cluster Server environment.

Enterprise Vault Utilities manual: http://support.veritas.com/docs/282077

There is a new Utilities manual in the Enterprise Vault documentation set, which currently describes the following:

a. Archive Conversion Manager

b. ArchivePoints

c. Audit Viewer

d. CenteraPing

e. CenteraVerify

f. Dtrace

g. DVS Checker

h. Evrights

i. Evservice

j. IndexServer

k. Index Volume Replay

l. NTFS to Centera Migration

m. Policy Manager

n. Vault Store Usage Reporter

o. Vault Store Verification

Note:

Enterprise Vault Policy Manager (EVPM) is now described in this Utilities manual. The Utilities manual describes the DVSChecker and VSVerify utilities which are available from Symantec Support and are not supplied with the Enterprise Vault software. The Utilities manual is supplied as Utilities.chm and as Utilities.pdf.

Changes to the Administrator's Guide: http://support.veritas.com/docs/282075

Various topics have been moved from the Administration Console help to the Administrator's Guide, including: "How to configure File System Archiving" (see the "File System Archiving" chapter)

How to modify Exchange Server journal mailbox settings: see the "Customizations and best practise" chapter

3. Changes affecting users

Controlling the Archive Explorer button [Ref 602065]

The mailbox policy Advanced tab enables you to control which buttons are shown in the User Extensions. The Menu only option for Archive Explorer button visible had no effect, so it was not possible to show the Archive Explorer menu option without showing the button.

This has been fixed.

Archive Explorer did not restore items to mailboxes with extended (8-bit) characters in their names [Ref 602304]

Archive Explorer did not permit you to copy or move an archived item back to a mailbox whose name contained extended characters such as accented characters.

This has been fixed.

Archive Explorer incorrectly restored archived files whose names had extended characters [Ref 602342]

If you used File System Archiving to archive files whose names contained ASCII extended or non Latin characters, restoring those files with Archive Explorer would create files whose names did not contain these extended characters. The original placeholder shortcuts would remain unchanged.

This has been fixed.

Improvements to Archive Explorer [Ref 602201, 602229]

a. When searching offline in Archive Explorer, the search pane remained displayed when you selected a different folder in the tree. This has been fixed. Search pane behavior is now the same for online and offline Archive Explorer.

b. When using Outlook 2000, the Archive Explorer update process sometimes appeared to stop responding. This has been fixed.

c. When you started Archive Explorer in Outlook, the initial page had no close button. This has been fixed.

'Forward' option now on context menu [Ref 602268]

When right clicking an Enterprise Vault shortcut, there is now a 'Forward' option. Previously, 'Forward' was available only on the Outlook toolbar.

To implement this change, you must install the Exchange Server forms that are supplied with Enterprise Vault 6.0 SP2.

Messages display "sent on behalf of" information [Ref 602292]

In search results, messages that have been sent by delegates are now displayed as having been sent on behalf of the primary author.

Nested message size reported correctly [Ref 602385]

The size of nested messages was reported incorrectly in archive search results. This has been fixed.

Long Outlook 2003 start-up time [Ref 602287]

Outlook 2003 could take up to 30 seconds to start when used disconnected from the network and in Exchange Cached Mode.

This has been fixed.

Truncated text in Japanese Offline Vault wizard [Ref 602317]

The heading text on the third page of the Offline Vault wizard was slightly truncated in the User Extensions (Japanese).

This has been fixed.

Client-driven migration [Ref 602339]

Client-driven migration could fail when the path to a PST contained multi byte characters.

This has been fixed.

Email message is archived as a document [Ref 602409]

It was possible for a MAPI message to be archived as a document with the result that the content was not indexed and links to attachments did not work. This occurred in the following circumstances:

a. A user restored an item that had been archived and then forwarded the restored item.

b. The recipient dragged the message to a PST file or to a disk folder.

c. The message was archived, either by PST migration or File System Archiving.

This has been fixed.

Deleting a group of items also deletes the folder [Ref 602376]

Selecting items as a group (for example, 'Date: Yesterday') and then clicking Delete resulted in the folder and all its items being deleted in the following circumstances:

a. The user was using Outlook 2003 or Outlook 2002 (from Office XP)

b. The Exchange Mailbox Policy Desktop setting Shortcut deletion behavior was set to Both deleted or Ask user

This been fixed, with the following changes when Shortcut deletion behavior is set to Both deleted or Ask user:

a. Clicking Delete has no effect when a group is selected.

b. Attempting to delete a folder fails if the previous item that was selected was a group (such as 'Date: Last Week')

Custom filter prevents manual archive [Ref 602155]

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

This has been fixed.

Corrupt Shopping Basket [Ref 602077]

On rare occasions, it was possible for the first Shopping Basket created in a browser session to be corrupt, resulting in many "Failed to update the restoration status of a restoring item" Event log entries (Event Id 5122).

This has been fixed.

Error when opening archived task [Ref 602048]

When using Outlook Cached Exchange Mode, opening a shortcut to an archived task correctly retrieved the task and also showed a second copy of the form with error 80040106 (MAPI_E_UNKNOWN_FLAGS). If the task was edited there was no warning that it could not be saved.

This has been fixed.

Performance improvement to OWA restores [Ref 602126]

When using OWA to restore items, the restoration speed had been significantly improved.

Manually restoring Public Folder items generated random conflicts [Ref 602294]

Manually restoring a large number of archived items to Public Folders would sometimes generate multiple conflict messages.

This has been fixed.

OWA files removed from Deleted Items when item closed [Ref 602260]

When viewing an item using OWA 2003 clients, the item is temporarily restored (as a hidden item) to the Deleted Items folder. Although such items have a timeout of 2 hours, they were only deleted during an archive run. In situations where low mailbox quota limits were enforced, these temporary, hidden messages could cause the mailbox limit to be reached.

For OWA 2003 Premium client, a change has been made to the way these files are handled. The temporary file is now removed from Deleted Items when the item being viewed is closed.

Note that the behavior for OWA 2003 Basic client and OWA 2000 clients is the same as before; temporary items that are older than 2 hours are only deleted during the next archive run.

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

OWA users could not access archived items in an environment where primary domain controller emulation was disabled and a proprietary DNS system was used.

This has been fixed.

Truncated prompt on German systems when user chooses to delete a shortcut [Ref 602112]

In the Vault Administration Console, the Advanced tab of the Exchange Policy Properties dialog box enables you to specify the Shortcut deletion behavior. If you set this to Ask user, so that the user is prompted to delete either the original item and the shortcut or just the shortcut, then the resulting prompt was truncated on German systems.

This has been fixed.

Printing a calendar page with vault items on it results in inaction [Ref 602064]

In Outlook, if you opened the Calendar in Week or Month view and then tried to print a view that contained one or more archived items, nothing would be printed.

This has been fixed.

Outlook stopped responding when searching using related items [Ref 602031]

If you used the Outlook integrated search to locate an archived message, and then searched for related messages by clicking Tools > Find All > Related Messages, Outlook would sometimes stop responding if you dragged one of these related messages into another folder.

This has been fixed.

4. Administration Console

Vault Store ID now shown in Administration Console [Ref 602095]

The General tab of a vault store's properties now shows the Vault Store ID.

Corrupt default file name from Vault Store Usage Reporter [Ref 602181]

When clicking a link in the Save Report By column of a Vault Store Usage Reporter report, the default file name is the same as the name of the Vault store. If the Vault store name contained double-byte characters, the default file name was corrupt.

This has been fixed.

Synchronization of Exchange Server Journal Tasks [Ref 602182]

When synchronizing an Exchange Server Journal Task and choosing to update details of Selected journal mailboxes, it was possible for the list of mailboxes to be empty. When this happened, it was still possible to click OK which resulted in a message box that did not contain any text.

This has been fixed.

Mailbox names containing "(", ")" or "," cannot be synchronized [Ref 602225, 602358]

If a username in Active Directory terminated with a comma, or included the characters "(" or ")", Enterprise Vault could not synchronize the associated mailbox.

This has been fixed.

Cannot list archives when security descriptors are corrupt [Ref 602179]

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

This has been fixed. An event log entry now identifies the archive with the corrupt security descriptor.

Failure to enable mailboxes for archiving [Ref 602199]

Mailboxes that did not have storage limits set in Active Directory could not be enabled for archiving or, if already enabled, could not be synchronized. This issue could occur, for example, after an upgrade from Exchange Server 5.5 to a later version of Exchange Server.

This has been fixed.

Archive's properties show 'Service not set' [Ref 602235]

When viewing the properties of an archive, the Status showed 'Service not set' and generated the following Event log errors:

Event Type: Error
Event Source: Enterprise Vault
Event Category: Admin Console
Event ID: 8392
Date: 07/01/2006
Time: 5:14:28 PM
User: N/A
Computer: BETELGEUSE
Description:
The EnterpriseVault.DirectoryVault object reported an error.

This has been fixed.

File server's properties show 'Unknown' status [Ref 602326]

When viewing the properties of a file server it was possible for the Status to show as 'Unknown'. When this happened, the 'Status' column in right pane of the Administration Console also showed the status as 'Unknown'.

This has been fixed.

Multiple Web Application URLs in desktop settings [Ref 602305, 602336]

The Web Application URL entry in Desktop settings on the Advanced page of Exchange Mailbox policy enables you to enter the address of another Vault site's Web access application. This enables users in one Vault site to open shortcuts in another. You need to enter multiple Web application URL addresses if a public folder hierarchy is processed by Exchange Public Folder tasks from more than one Vault site.

URL addresses added to this entry were added incorrectly. This has been fixed.

You can add multiple addresses to this entry using the following format:

[site1.dns.alias]=http://site1.server.com/EnterpriseVault;[site2...

where siten_dns_alias is the Vault site alias and siten_webappserver is the name of the Enterprise Vault Web application server for the site.

If you specify multiple addresses, separate them with semicolons (;). The overall length of the string cannot exceed 255 characters.

If you have specified a value for Web Application URL, you may wish to review its setting.

Quote in mailbox name prevents journal archiving [Ref 602023]

It was not possible to add a journal mailbox as an archiving target if the journal mailbox had a single quote in its name.

This has been fixed.

Efficiency improvements when deleting archives [602070]

There have been efficiency improvements when deleting an archive and any orphaned records associated with it.

Changed PST task logon details now persist [Ref 602429]

If you changed the logon details for any of the following tasks, the new account details persisted for the current run and then reset to the Vault Service account:

a. PST Locator task

b. PST Migrator task

c. PST Collector task

This has been fixed.

New safety copy setting for Exchange Server journaling [Ref 602197]

There is a new Vault store safety copy setting for Exchange Server journaling, After backup (immediate for Journaling). This enables you to use the same Vault store for mailbox archives and journaling, thus benefiting from single instance storage, but to delete the safety copy from the journaling mailbox immediately and retain safety copies in users' mailboxes until after backup.

Note that this setting is not available for Domino Journaling.

5. File System Archiving

Out-of-memory errors when synchronizing [Ref 602037]

It was possible to get out-of-memory errors when synchronizing with millions of folders on the same volume.

This has been fixed.

No archiving when folder and volume rule on drive root [Ref 602047]

If a folder and volume rule were both set at the root of a drive, File System Archiving did not archive anything from the root folder or its subfolders.

This has been fixed

Performance improvement to placeholders [Ref 602058]

Placeholders used by File System Archiving are now created as sparse files. This provides for a significant performance improvement when listing the contents of folders that contain placeholders.

The performance improvement is seen for new placeholders, including those created when an item is recalled and then re-archived.

You must install the Enterprise Vault 6.0 SP2 File Placeholder service to obtain this performance improvement.

Multiple file system volumes archived correctly [Ref 602348]

If the number of target volumes for file system archiving exceeded the number of process threads configured to process items, volumes in excess of the number of configured threads were not archived.

This has been fixed.

6. PST migration

PST Locator Task searches [Ref 602099]

The PST Locator Task now gives you the choice of searching for domains and computers using Active Directory or NetBIOS.

Migration of ANSI PSTs fails if messages do not have code page property [Ref 602074]

Migration of an ANSI PST file stopped at the point when the migration encountered a message that did not have the code page property set. Other migrations were not affected by this failure.

This has been fixed.

Renamed PST import folders correctly archived [Ref 602215]

If you import items from a PST and create shortcuts for the items in the mailbox, the PST folder structure is created in the mailbox for the shortcuts.

If any of these folders were renamed and new items added, both the old folder and the renamed folder are displayed in Archive Explorer after an archive run. This has been fixed.

7. Enterprise Vault for Domino Journaling

Improved handling of Domino Journaling addresses [Ref 602096/1, 602272]

Various issues with the archiving of message addresses have been fixed. These included issues with duplicate addresses, short form addresses, addresses with Unicode characters, and group expansion across domains.

HTML preview is incorrect when items attached multiple times [Ref 602368]

If the same item is attached to a message multiple times then, after archiving, the HTML preview is correct for the first attachment, but corrupt for the copies of the attachment.

This has been fixed.

Domino Journaling task fails to shut down [Ref 602096/2]

Occasionally it was not possible to shut down a Domino Journaling task while it was archiving. The shutdown attempt caused the task to stop responding.

This has been fixed.

Domino Journaling memory leak [Ref 602097/1]

A memory leak when archiving has been fixed.

Domino Journaling Task fails to start [Ref 602097/2]

Occasionally there were startup issues if you attempted to start multiple Domino Journaling tasks simultaneously. The following error was logged in the Enterprise Vault log:

Event Type: Error
Event Source: Enterprise Vault
Event Category: Lotus Domino Journaling Task
Event ID: 41047
Date: 11/9/2005
Time: 5:16:37 PM
User: N/A
Computer: VLTEU1
Description:
Task: 'Domino Journaling Task EXEU4'

Unable to initialize Lotus session.

Ensure you have the Lotus Client installed with valid registry entries.

This has been fixed.

Prepending backslash to Domino journaling location caused issues [Ref 602222]

When specifying the Domino journaling location in the Vault Administration Console, if you prepended a backslash (\) character to the folder from which you wanted to archive items, then Enterprise Vault failed to find the databases in that folder.

This has been fixed.

Sender's name malformed in Lotus messages sent between domains [Ref 602261]

In a Lotus Domino environment where Directory Assistance is employed, messages between users in different domains would be journaled and archived with the sender's name malformed (the sending domain name would be prepended to the sender's address).

This has been fixed.

Domino Journal Archiving task could not archive message attachments with reserved characters in their names [Ref 602285]

The Domino Journal Archiving task could not archive Lotus Notes messages whose attachments contained an exclamation mark or @ symbol in their file names.

This has been fixed.

8. Other changes

Change to Public Folder Enablers [Ref 602011]

It is now possible to set up archiving from a Public Folder Auto-Enabler's root folder and to specify which archive is to be used.

Corrupt shortcut when 'Delivery Status Notification (Failure)' message is archived [Ref 602017]

A message sent to an invalid recipient resulted in a 'Delivery Status Notification (Failure)' message being delivered to the sender. If this message contained Unicode data (because the original subject line contained Unicode characters), then the shortcut content looked similar to the following:

<<
\'a5\'e9\'a5\'a4\'a5\'c0\'a9\'60\'c4\'ee\'ee\'8a\'a4\'ce\'b8\'df\'cb\'d9\'b5\'c0\'3b\'20\'d2\'f2 \'ce\'aa\'c4\'c7\'d1\'f9\'bb\'e1\'cd\'fe\'d0\'b2\'b5\'bd\'b9\'fa\'bc\'d2\'ba\'cd\'c9\'e7\'bb\'e1\'b5\'c4\'b0\'b2\'b6\'a8 (1.6KB)

(1.6KB)
>>

Double clicking the item to open it showed the content correctly and the item could be restored successfully without corruption.

This shortcut corruption has been fixed.

Errors when processing root public folder [Ref 602018]

If an Auto-Enabler was configured to archive from the root of the public folder hierarchy, some spurious errors were generated at the start of each archiving run. For example:

Event Type: Error
Event Source: Enterprise Vault
Event Category: Public Folder Task
Event ID: 2956
Date: 21/10/2005
Time: 16:28:49
User: N/A
Computer: VERCETTI
Description:
An error has occurred whilst processing the Public Folder \.

Check the Event Log for any previous errors, as they may help determine the cause.

Error: 0xC004088A

Event Type: Warning
Event Source: Enterprise Vault
Event Category: Public Folder Task
Event ID: 2270
Date: 21/10/2005
Time: 16:28:54
User: N/A
Computer: VERCETTI
Description:
A queued operation exceeded the retry count and has been discarded

This has been fixed.

Improvement to Vault Store Usage Reporter statistics [Ref 602019]

The accuracy of the sizes reported by Vault Store Usage Reporter has been improved. The sizes refer to the compressed size of savesets before sharing.

Unexpected font sizes in archived items [Ref 602100]

In Enterprise Vault 6.0 SP1 there was an issue with Domino Journaling that could result in email messages being journal archived with unexpected font sizes.

This has been fixed.

No Tasks after upgrade to Enterprise Vault 6.0 SP1 [Ref 602195]

When upgrading from Enterprise Vault 5.0 to Enterprise Vault 6.0 SP1, it was possible for the upgrade to complete without error but for there to be no tasks created. When this happened, the log file of the upgrade contained text similar to the following:

*** Starting Upgrade of Enterprise Vault Services To Tasks at 14:17:21 2005/12/12 ***

Installing SQL Scripts

---------------------------------------------------------

Scripts...Installation Failed

*** Finished Upgrade of Enterprise Vault Services To Tasks at 14:17:22 2005/12/12 ***

This has been fixed for upgrades to Enterprise Vault 6.0 SP2.

Older User Extensions cannot open archived item [Ref 602219]

Attempting to open an archived item failed in the following circumstances:

a. The user had a version of Outlook earlier than Outlook 2003

b. The Enterprise Vault User Extensions was a version earlier than Enterprise Vault 6.0 SP1

c. DefaultFormatType was not set in WebApp.ini

Clicking the error banner after attempting to open the message showed error 0x80040103.

This has been fixed.

From Enterprise Vault 6.0 SP1, Unicode items are stored in Unicode savesets and ANSI items are stored in ANSI savesets, thus avoiding possible corruption. See the Previous Updates in the download(Enterprise Vault 6.0 SP2\PrevUpdates.htm) for more information

Single instance storage ignores changes in codepage [Ref 602245]

If an item was archived twice, using different codepages, then it was stored as a shared item. When the item was viewed, the codepage used was always that of the first version to be archived.

This has been fixed.

Failing searches when using double-byte character set spaces [Ref 602255]

When searching for archived items, including a space character from a double byte character could cause the search to fail.

This has been fixed.

Updates to Policy Manager [Ref 602262]

a. Prompt offering default system mailbox now displays correct mailbox alias: EnterpriseVault(servername).

b. If no Vault store and retention category information was supplied in a script, Policy Manager retrieved Vault store and retention category information from the OU archiving target. This has been extended to include the indexing service.

c. If no indexing service is specified in the script and no OU target exists, Policy Manager will now attempt to find an indexing service that is local to the Vault store. If no local Indexing service exists, Policy Manager will use the site default Indexing service.

Failure to store to Centera partition [Ref 602250]

There have been some failures when storing to a Centera partition, either as part of archiving or migrating. All such failures involved items that had attachments.

The errors resulting from this type of failure are not consistent.

This has been fixed.

EVStgOfflineOpns.exe process fails to start [Ref 602327]

When the Windows process performance counters (perfproc.dll) were disabled, the Enterprise Vault EVStgOfflineOpns.exe process would not start.

This has been fixed.

Incorrect character formatting in HTML preview [Ref 602337]

When a message was sent to a user's SMTP address or Notes username, the HTML preview of the archived version did not include all the character formatting, such as underline, strikethrough, and superscript.

This has been fixed.

Deletion from collection Clip on Basic Centera [Ref 602370]

On basic model Centera devices, it was not possible to delete a saveset from a Collection clip.

Enterprise Vault was enforcing the retention period on basic model Centera devices, but EMC recently changed basic model Centera devices so that the retention period is no longer enforced.

This has been fixed.

PEA file not specified when connecting to replica Centera [Ref 602371]

When a primary Centera had replication enabled and a profile specified, the pool entry authorization (PEA) file was not being specified when connecting to the replica Centera, resulting in connection failures.

This has been fixed. The same PEA file works for both the primary and replica Centera devices.

If you employ the workaround of setting the Windows environment variable CENTERA_PEA_LOCATION to be the path to a PEA file, you can delete this environment variable.

Incorrect codepages used for documents with double-byte characters [Ref 602372]

An incorrect codepage is sometimes used when archiving documents that contain text with double-byte character sets. When this happens the HTML preview is unreadable and the documents are not indexed correctly, so it is not possible to search for them.

There has been some work on improving the codepage recognition, requiring manual configuration, which can reduce the occurrence of this issue. For further information, see Support article 282055: http://support.veritas.com/docs/282055

Shortcuts deletion not working [Ref 602416]

In Enterprise Vault 6.0 SP1, the settings for automatic Shortcut Deletion were not being applied, with the result that Shortcut Deletion did not take place.

This has been fixed.

Shortcut shows recipient's alias instead of display name [Ref 602142/SRX060109600553]

In some cases, when the system locale of the Enterprise Vault archiving task server is different from the locale of the user's computer, the recipient's display name in a shortcut is the recipient's alias instead of the display name as seen in the Global Address List.

For example, the shortcut would show the recipient's alias when all the following are true:

a. The message originated from a user with Windows XP (Japanese)

b. The recipients had Japanese display names

c. The archiving task server has a system locale of English

To work around this issue, set the locale of the Enterprise Vault archiving task server to match that of your users. See the Microsoft Global Development and Computing Portal: http://www.microsoft.com/globaldev/DrIntl/faqs/Locales.mspx for information system locales.

Improvements to SMTP archiving [Ref 602043, 602347]

a. Recipient information in SMTP messages was not indexed. This has been fixed.

b. SMTP archiving terminated if it encountered a recipient address containing an invalid character. Buffer overrun errors were reported by InetInfo.exe, the process under which SMTP archiving runs. This has been fixed.

c. When configuring SMTP archiving, an error is now reported if IIS is not installed.

Updated Centera SDK [Ref 602183]

Enterprise Vault 6.0 SP2 includes Centera SDK version 3.0 SP1 (3.0.414.0) released by EMC on 23 November, 2005.

Deletion when in read-only mode [Ref 602082]

When Enterprise Vault Services were put in read-only mode, in preparation for taking a backup, users of Browser Search or Outlook Integrated Search could still delete archived items.

This has been fixed.

Verification of saveset files in a collection (CAB) file [Ref 602395]

Enterprise Vault can now check for corrupted saveset (.DVS) files before or after it collects them into a .CAB file on an NTFS volume or network share partition. To enable or disable this feature, set the following registry keys as required.

Registry key	Permitted values	Function
HKEY_LOCAL_MACHINE\KVS\Enterprise Vault\Storage\VerifyFilesPreCollection	0 (do not verify) 1 (verify)	Specifies whether to verify the saveset files before collecting them into a CAB file. The default is 0.
HKEY_LOCAL_MACHINE\KVS\Enterprise Vault\Storage\VerifyFilesInNewCollection	0 (do not verify) 1 (verify)	Specifies whether to extract and verify the saveset files after they have been collected into a CAB file. The default is 0.
HKEY_LOCAL_MACHINE\KVS\Enterprise Vault\Storage\LogVerifyOfCollectionFiles	0 (do not log) 1 (log)	Specifies whether to generate DTrace and event log messages when the VerifyFilesPreCollection or VerifyFilesInNewCollection key is set. The default is 0.

Optimized vault indexing [Ref 602435]

The indexing of vaults has been optimized to improve the performance of collection management operations, such as compaction, deletion, and expiry.

Less memory used when processing large messages [Ref 602032]

Your system may have run out of virtual memory when the Storage service was processing many very large messages on an EMC Centera device. This has been fixed.

Service synchronization in a multi-server site [Ref 602275]

Previous issues with service synchronization when using multiple Enterprise Vault servers in the same site have now been fixed.

Messages fetched using Simple API display correctly [Ref 602364]

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.

This has been fixed.