VERITAS Enterprise Vault (tm) 5.0 Service Pack 5 Full CD

Article:TECH42469

Created: 2006-01-02

Updated: 2006-01-02

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

Article Type
Technical Solution

Product(s)

Show all

Environment

Show all

Languages

Show all

Problem

VERITAS Enterprise Vault (tm) 5.0 Service Pack 5 Full CD

Solution

VERITAS Enterprise Vault (tm) 5.0 Service Pack 5

This document describes the changes introduced by Enterprise Vault 5.0 Service Pack 5.

The CD media comprises of

Enterprise Vault for Microsoft Exchange 5.0 SP5
Enterprise Vault for File System Archiving 5.0 SP5
Enterprise Vault for Microsoft Sharepoint 5.0 SP5
Enterprise Vault Compliance Accelerator 5.1 SP3
Enterprise Vault Discover Accelerator 5.0 SP2

For details of the changes included in the earlier updates, see the PrevUpdates.htm in the download

Contents

Installation and prerequisite software
File System Archiving changes
Offline Vault changes
Changes affecting users
Administration Console changes
Policy Manager changes
Other changes
Outstanding issues
Copyright and trademarks

Installation and prerequisite software

Server installation

When you upgrade to Enterprise Vault 5.0 SP5, it is mandatory that you upgrade all Enterprise Vault servers, including Outlook Web Access (OWA) front-end and back-end servers. In each case, load the Enterprise Vault CD-ROM in your CD-ROM drive, double-click SETUP.EXE to start the installation, and then choose the required components. For further information, see the Installing and Configuring manual.

File System Archiving changes

File System Archiving now ignores ~snapshot folders on NetApp filers [Ref: 505044]

When archiving files from a NetApp filer, File System Archiving no longer attempts to archive the files in the ~snapshot folder (which is used to store the volume snapshots).

Non-Western European characters in File System Archiving folder path [Ref: 505060]

If File System Archiving encountered non-Western European characters in a folder name, it would fail to archive files stored in that folder, and the following message would appear:

*** Error *** - Exception from HRESULT: 0x800300FC (STG_E_INVALIDNAME)

This has now been fixed.

File System Archiving now fails gracefully when trying to restore files to full disks [Ref: 505070]

If you use an application such as the Enterprise Vault Browser Search to restore an archived file, and there is insufficient disk space to store the file, File System Archiving now displays an error message instead of causing the application to stop running.

Granting local group permissions to domain users in the group [Ref: 505084]

If you create a local group to grant permissions to the folders on a file server, and you add one or more domain users or groups to this group, Enterprise Vault synchronizes the local group permissions only. It does not enumerate the users and groups within these groups and synchronize them. Domain users may therefore be unable to use Archive Explorer or Browser Search to access items in the folders associated with the local group.

You can address this issue by adding an optional value, ExpandLocalGroups, to the following registry key on the Enterprise Vault server:

HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\FSA

Giving ExpandLocalGroups a non-zero value extends the local group permissions to domain users that you have added to the local group, with the result that these users can now access the folders associated with the local group.

Fix for leaking handles problem when archiving from a NetApp filer [Ref: 505090]

When using File System Archiving to archive files from a NetApp filer, the Enterprise Vault Admin Service would sometimes create an excessive number of handles. This has now been fixed.

Fix for placeholder shortcuts error [Ref: 505092]

You can now copy and paste shortcuts to files larger than 30 MB without the following message appearing:

Cannot copy filenameX: The remote storage service was not able to recall the file

Offline Vault changes

Clicking Archive Explorer buttons no longer crashes Outlook 2003 in Cached Exchange Mode [Ref: 505024]

If you are running Outlook 2003 in Cached Exchange Mode, and you are browsing the items in an offline vault with Archive Explorer, clicking the Next Page and Previous Page buttons in Archive Explorer no longer causes Outlook to stop running.

Downloading items to offline vaults larger than 2 GB [Ref: 505045]

In Enterprise Vault 5.0 SP4, it was not possible to download new items to an offline vault that was 2 GB or larger in size. This has now been fixed.

Hyphens in folder names no longer cause offline vault synchronization to fail [Ref: 505067]

Synchronizing an offline vault no longer fails if the name of a mailbox folder contains the characters "--" or ends with the character "-".

Changes affecting users

Sent Items folder in Archive Explorer now shows To rather than From addresses [Ref: 505002]

In Archive Explorer, the Sent Items folder now shows the To addresses of messages (identifying their recipients) rather than the From addresses (identifying their senders). Note that, if you are offline, the Sent Items folder shows the From addresses as before.

Opening shortcuts from non-Microsoft MAPI stores [Ref: 505004]

You can now open shortcuts to archived messages from a non-Microsoft MAPI store. For example, if you drag and drop a shortcut to the Windows desktop, double-clicking the shortcut no longer causes the following message to appear:

Enterprise Vault cannot open this item. Copy or move it to your mailbox and then try again from there.

Note that you must install the latest shortcut form (Enterprise Vault\Languages\Forms\en\EVShortcut.fdm) for this fix to work. See the Installing and Configuring manual for guidance on how to do this.

This fix improves support for Interwoven.

Viewing messages with the Enterprise Vault Browser Search added blank entries to the list of vaults [Ref: 505007]

If you used the Enterprise Vault Browser Search to search a vault and view an archived message, and then returned to the home page of the search facility, an additional blank entry appeared in the dropdown list of vaults. Each additional message that you viewed added a further blank entry to this list. This has now been fixed.

Manual archive from a public folder in the Favorite Folders pane [Ref: 505010]

Previously, initiating an archive request from a public folder that you had added to the Favorite Folders pane in Outlook would cause the Enterprise Vault User Extensions to stop running. This is no longer the case.

Outlook 2003 running in Cached Exchange Mode no longer archives the wrong items [Ref: 505014]

If Outlook 2003 was running in Cached Exchange Mode, and you archived one or more mail items and then immediately selected another item, the wrong items would sometimes be archived. This has now been fixed.

Improved performance when running Archive Explorer [Ref: 505023]

When running Archive Explorer, you may have experienced high and protracted CPU utilization on the Vault Directory Database server. This has now been fixed, with the result that performance should improve on larger systems.

Exchange 2003 anonymous access required in a mixed Exchange 2000/2003 environment [Ref: 505030]

If you want to use OWA to open archived items on both Exchange 2000 and Exchange 2003 servers, you must configure the Enterprise Vault server for Exchange 2003 anonymous access. To do this, run the OWAUser.wsf configuration script and specify the /exch2003 option, as described in the Installing and Configuring manual.

Error code "Http1.1401" when using OWA with multiple HTTP virtual servers [Ref: 505039]

If you configured multiple HTTP virtual servers, using OWA to view an archived item would sometimes cause "Http1.1401" error messages to appear. This has now been fixed.

Controlling access to private messages for delegate users of Archive Explorer or Browser Search [Ref: 505042]

If one Outlook user has granted another user delegate access to his or her mailbox then, using Archive Explorer or the Enterprise Vault Browser Search, the delegate could previously view all the items in that user's vault archive, including those items marked as private. You can control the access that delegate users have to private messages by adding the following line to the WebApp.ini file.

Add This Line	To Do This
DelegateCanSeePrivateItems=0	Prevent delegates from viewing private items unless they have full read access to the archive. This is the default behavior
DelegateCanSeePrivateItems=1	Permit delegates to view all the items in archives to which they have access, including those items marked as private

Fixes for problems with non-Western European languages [Ref: 505035, 505049, 505062, and 505098]

This service pack addresses several problems with non-Western European language characters.

If you previously used a non-Western European language version of Archive Explorer to copy or move an item from a vault to a file system folder, a pop-up message containing incorrect characters would appear. This has now been fixed.
When using Outlook with the Enterprise Vault Self-installing User Extensions, you can now archive from and restore to mailbox folders whose names contain either non-Western-European characters or backslashes. Previously, the presence of these characters in a folder name would cause archiving to fail and an error message to appear in the log.
If you click a customized shortcut in Archive Explorer or OWA to run or save a message attachment whose name contains non-Western European characters, these characters are removed from the file name. You can correct this by adding the following line to the WebApp.ini file:

URLEncodeFilenames=1

Note that, because of Internet Explorer limits on the number of characters in a file name string, multi-byte file names may be truncated to 15 characters when URL-encoded.

If you open a message that has been archived with a code page other than the system code page, the subject line, recipient names and file names of attachments may be corrupted. You can correct this by adding the following line to the desktopsettings.txt file:

ViewOnlineUsingMessageCodepage=1

When viewing messages, this entry instructs Enterprise Vault to use the code page on the message rather than the system code page.

Hidden text in PDF message attachments is now viewable [Ref: 505053]

When it converts to HTML a PDF attachment to an archived message, the Enterprise Vault Browser Search does not normally convert any hidden text in the PDF file. You can now force Enterprise Vault to convert this text by creating a DWORD value called EnablePDF under the following key in the Windows registry:

HKEY_LOCAL_MACHINE\SOFTWARE\kvs\EnterpriseVault\PDF

If the PDF key does not already exist, you must create it. Give EnablePDF a value of 1 to enable the conversion of hidden text or 0 to stop conversion.

Error messages when clicking Enterprise Vault buttons in OWA [Ref: 505054]

If you added the Archive Explorer or Search button to the navigation bar of OWA, clicking either button while connected to an Exchange front-end server could cause the message "The Enterprise Vault service is not available" to appear. This has now been fixed.

Windows Server 2003 SP1 on SharePoint servers [Ref: 505064]

After installing Service Pack 1 for Windows Server 2003 on the SharePoint server, you may have received "Access Denied" messages when you tried to search an archive with the Enterprise Vault Web Access application. This has now been fixed.

HTML attachments whose MIME type property has been set now open correctly [Ref: 505065]

HTML attachments to archived messages now display properly when opened with a customized shortcut, regardless of whether the MIME type property attribute of the attachments has been set. Previously, only attachments for which no MIME type property had been set would display properly.

Script errors when opening archived items if WebApp.ini file contains ViewMessage_Format=ASK line [Ref: 505080]

If the WebApp.ini file contains the line ViewMessage_Format=ASK, and you use the Browser Search or Archive Explorer to open an archived item, a script error no longer appears.

New registry settings for detecting and overriding code pages on messages [Ref: 505091]

Use the following new registry values to detect the code pages on messages and specify alternative code pages to use. These values reside in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\CodepageDetection, which you must create if it does not already exist. Each value is of type DWORD.

Registry Value	Function
AttachmentSearchDepth	Specifies how far down the hierarchy of attachments to check the code page, in cases where an archived message has as its attachment a message that has an attachment of its own, which may also have an attachment, and so on. The default setting used if this registry value does not exist is 20
CodepageOverride	Specifies the code page with which messages should be archived in cases where they cannot otherwise be archived correctly, because no suitable code page exists. If you do not set this registry value, or you set its value to 0, Enterprise Vault does not archive such messages
DetectCodepage	When set to 1, instructs Enterprise Vault to detect the code page of each message before it is archived, instead of simply accepting the code page setting on the message. If necessary, Enterprise Vault then changes the code page to one that enables it to archive the message correctly. When this is not possible, Enterprise Vault does not archive the message
MaxRecipientsToDetectCodepage	For each message that is to be archived, specifies the maximum number of recipient names for which to check the code page. The default setting used if this registry value does not exist is 100, and the setting is rounded up to the nearest 100

Important: The version of mapi32.dll supplied with Outlook 2003 is not compatible with the CodepageDetection keys. If you set these keys, some Enterprise Vault services may fail to start when you choose to restart all services.

For more information on how Enterprise Vault handles multi-byte character sets, see article 277637 in the related documents below.

OWA front-end server cannot resolve back-end server using NT 4.0 user credentials [Ref: 505094]

In an environment where NT 4.0 domains and user credentials are used to access mailboxes on multiple Exchange Server 2003 servers through OWA, attempts to download archived items would fail with the message "Failed to determine back-end server". This was because the logged-in user did not have an Active Directory user account.

You can correct this by nominating one of the back-end servers as the default server. To do this, add the following parameter to the Enterprise Vault\OWA\EvFrontEnd.ini file:

<front_end_server>.defaultbeserver=<host_name>

wherehost_name identifies the default back-end server. For example:

exch-fe.1.defaultbeserver=exch2

This parameter enables the front-end server to resolve the back-end server for non-Active Directory accounts. In response to a ping request sent by the front-end server, the default back-end server sends a message containing a reference to the required back-end server for the mailbox.

Missing EVServers.txt file no longer causes Enterprise Vault extensions to OWA to malfunction [Ref: 505095]

If you did not create the optional EVServers.txt file on the Exchange back-end server, as described in the Installing and Configuring manual, the Enterprise Vault extensions to OWA did not work properly. This has now been fixed.

Access Denied errors when clicking Settings button in Archive Explorer [Ref: 505096]

On some machines, clicking the Settings button in Archive Explorer would sometimes cause an "Access is denied" message to appear. This has now been fixed.

Custom filters not archiving unmatched messages after first match [Ref: 505100]

If you used custom archiving filters to define how Enterprise Vault processes messages that meet certain criteria then, when a message matching a filter rule was first encountered, any subsequent messages that did not match the rule were incorrectly processed; they were left in the user's mailbox instead of being archived. This has now been fixed.

Administration Console changes

User interface fixes in the Vault Administration Console [Ref: 505008]

When setting an archive schedule with the Site Properties, FileServer Properties or Service Properties dialog box, you may sometimes have found that clicking and dragging with the mouse resulted in the wrong items being selected. This has now been fixed.

Permission Synchronisation changes [Ref: 505043]

If you have configured Enterprise Vault to synchronize inherited permissions between mailboxes and archives, the presence of a deleted user in the permissions list no longer causes synchronization to fail and the following message to appear in the event log:

3227: Failed to list mailbox permissions whilst synchronizing due to a missing Active Directory attribute.

Fix for errors when selecting an Archiving Service for an Exchange server [Ref: 505081]

If you used the Vault Administration Console or the Enterprise Vault configuration program to create an archiving service for an Exchange server, and the server had exactly 499 mailboxes in its mailbox store, you would receive an error message when you chose a system mailbox with which to process the server. This has now been fixed.

Policy Manager changes

OverrideArchiveLocks setting in script no longer causes Outlook 2003 crash [Ref: 505085]

If you used Enterprise Vault Policy Manager to modify the properties of folders, and your initialization file contained the setting OverrideArchiveLocks = true, then some age-based policies on subfolders would not take effect. Not only did this stop the items in a subfolder from being properly archived but it also caused Outlook 2003 to stop running when you viewed the folder's Enterprise Vault properties. This has now been fixed.

Other changes

Performance improvements in NTFS to Centera Migration tool [Ref: 505011]

There have been some improvements in the performance of the NTFS to Centera Migration tool, which moves Enterprise Vault savesets from an NTFS partition to an EMC Centera partition.

Meeting requests passed to the Compliance Accelerator Journaling Connector [Ref: 505013]

Meeting requests that are not eligible for archiving are no longer passed to the Compliance Accelerator Journaling Connector for processing. Previously, the Journaling Connector would process all meeting requests, whether or not they were going to be archived. This could have an accumulative effect on performance when the sampled mail was transferred to the review sets overnight.

Invalid characters no longer cause archiving to Centera partitions to fail [Ref: 505020]

When you archive items to an EMC Centera partition, the presence of an invalid character in an item's title, extension, or MIME type value causes the value to be replaced by a space. The presence of such characters would previously cause the archiving process to fail.

Dynamic loading of Centera FPLibrary.dll file [Ref: 505032]

The method of dynamically loading the Centera FPLibrary.dll file has been changed to resolve problems that occasionally resulted in it not loading correctly, and that in turn caused Event ID 6760 messages (Error from EMC Centera FPLibrary) to appear in the log.

Centera collections temporary area not being cleared out [Ref: 505034]

In some circumstances, when archiving an item to a Centera partition for which you have elected to use saveset collections, the Centera collections temporary area was not being cleared out. This has now been fixed.

Performance improvements in Centera collection housekeeping [Ref: 505058]

The speed with which you can perform housekeeping operations on saveset collections archived to a Centera partition has been significantly improved.

Updated Centera SDK [Ref: 505993]

Enterprise Vault 5.0 SP4 included a version of the Centera SDK that caused data loss when archiving files whose size was within a certain 10 MB window-between 100 MB and 110 MB, 200 MB and 210 MB, 300 MB and 310 MB, and so on.

Enterprise Vault 5.0 SP5 includes Centera SDK version 2.4.361, which fixes this problem.

Failover strategy for Centera node failure [Ref: 505111]

When archiving items to a partition, Centera works through the IP addresses in a list of access nodes until it finds one that is reachable. If the first node in the list is offline, there is a network timeout delay before Centera attempts to connect to the next listed node. This can lead to delays in archiving and retrieving items. You can now handle this issue by setting a new DWORD value, EMCCenteraConnectionTimeout, under the following registry key on the Enterprise Vault server:

HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Storage

Give this a value of 30 to set the timeout period to 30 seconds. When the timeout period elapses, the unreachable node is moved to the end of the list so that future connection attempts are quicker.

Outstanding issues

Error when starting Outlook 2003 [Ref: 512 and SRZ040414002287]

The first time a user starts Outlook 2003 after installing the Enterprise Vault User Extensions, the following error message may appear:

Error in registry for extension "Exchange Extensions;?".
The syntax or format of the registry entry is incorrect.
Check the registry settings and compare the registry for
this extension to other extensions in the registry.

The error does not appear the next time Outlook 2003 is started.

The registry entry to which the message refers is:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Client\Extensions

The correct value for the entry is:

"4.0;emsuix32.dll;7;011111111111110;1111011100"

The problem is caused by an Outlook 2003 bug which is fixed in Outlook 2003 SP1. For more details, see Microsoft Support article 823633 <http://support.microsoft.com/?kbid=823633>.

File System Archiving placeholder timeouts [Ref: 30880]

When a user attempts to open a placeholder shortcut and the item to be restored is large, it is possible that the user's application may assume that the file cannot be opened when in fact the file is still being restored. For example, Microsoft Word may issue the following error:

The document name or path is not valid

The file size at which this occurs depends on the speed at which files are restored. For example, on a LAN, this may occur when a file is several tens of megabytes in size.

If the user waits until the file has been restored and then tries again, the file can be opened successfully.

Copyright and trademarks

Copyright © 2005 VERITAS Software Corporation <http://www.veritas.com>. All rights reserved. VERITAS, the VERITAS Logo, and Enterprise Vault are trademarks or registered trademarks of VERITAS Software Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.