Veritas Enterprise Vault (tm) 6.0 Service Pack 3 (SP3) revision 6.0.3.8000

Article:TECH48594  |  Created: 2006-01-09  |  Updated: 2014-03-26  |  Article URL http://www.symantec.com/docs/TECH48594
Article Type
Technical Solution


Environment

Issue



Veritas Enterprise Vault (tm) 6.0 Service Pack 3 (SP3) revision 6.0.3.8000


Solution



Veritas Enterprise Vault (tm) 6.0 Service Pack 3

This document describes outstanding issues and the changes introduced by Enterprise Vault 6.0 Service Pack 3 (SP3).
The download is comprised of the following:

 
Enterprise Vault for Microsoft Exchange 6.0 SP3
 
Enterprise Vault for File System Archiving 6.0 SP3
 
Enterprise Vault for Microsoft Sharepoint 6.0 SP3
 
Enterprise Vault for Lotus Domino 6.0 SP3
 
Enterprise Vault for SMTP Archiving 6.0 SP3
 

Symantec recommends all customers sign up for our Email Notification Service by clicking on the following link:    http://maillist.support.veritas.com/subscribe.asp and selecting the products you are running. To receive monthly updates on new or 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.   New features
2.   High priority fixes
3.   Changes affecting users and requiring new User Extensions
4.   Changes affecting users and not requiring new User Extensions
5.   Changes to OWA support
6.   Changes to File System Archiving
7.   Changes to Exchange Server Journaling
8.   Changes to PST migration
9.   Changes to SharePoint archiving
10.  Changes to custom filtering
11.  Changes to Domino archiving
12.  Other changes


1. New features

Personal Information Store (PST) migration support for Active Directory Home folders [Ref CAP094, 603034, E535976]
It is now possible to use client-driven PST migration to migrate PST files in folders that are defined, in users' Active Directory Users and Computers profiles, as Home folders that are connected using a single drive letter, such as "H:". Previously, PST files were not found if they were referenced using a home folder letter or a mapped drive that was not configured to reconnect at logon.

Note the following restrictions when Home folders are connected using a single drive letter:

 
  • If you are using Locate and Migrate (that is, using the PST Locator task) and searching for PST files by using a registry search, there must be only one Outlook mail profile on the user's computer.
  • If you are using client-driven migration, the account running the Enterprise Vault Directory service must be at least a Power User on the computer that hosts the PST file.
  • If you are using client-driven migration, then PST files must be in a user's Outlook mail profile in order to be migrated. Client-driven migration does not search Home folders for PST files that are not in mail profiles.

PST migration support for NetApp Filer devices [Ref CAP126, 603061]
Previously it was possible to migrate PST files that were located on Microsoft Windows Servers. It is now also possible to migrate PST files that are located on NetApp Filer devices. Before Enterprise Vault 6.0 SP3, neither the PST Locator Task nor client-driven migration could locate PST files held on NetApp Filer devices, so such files could not be migrated.  Note: NetApp Filer snapshot folders (~snapshot) are ignored. PST files in these folders are not migrated.
Although the PST Locator task automatically recognizes NetApp Filer devices, the automatic recognition does not work in the following circumstances:

 
  • The NetApp Filer device was found by a PST Locator task from a release of Enterprise Vault that was before SP3.
  • The NetApp Filer is switched off.

This means that, when a NetApp Filer device has been found by the PST Locator task, it will be necessary to edit the device's properties in the Administration Console to specify that this is a NetApp Filer device.

 
To edit the properties of a NetApp Filer device:
 

 
In the left pane of the Administration Console, expand the vault site and then expand Personal Store Management.
 
Click Computers.
 
In the right pane, double-click the name of the NetApp Filer device to show its properties.
 
Click the Settings tab.
 
Select This computer is a NetApp Filer and click OK.
 

 
Note the following restrictions:

 
  • The PST Holding folder cannot be on a NetApp Filer device.
  • PST files cannot be migrated from a WORM share.

Support for multiple Global Catalogs in a domain forest [Ref CAP095, 603020, 602516, E538206]
In previous releases, archiving mailboxes across multiple domains and Global Catalogs within an Exchange server domain forest was not easily configured in Enterprise Vault.   In Enterprise Vault 6.0 SP3 and later, Enterprise Vault supports automatically multiple domains and multiple Global Catalogs within an Exchange server domain forest. There is a hotfix to enable this for Enterprise Vault 6.0 SP2.  To enable Enterprise Vault to find the Global Catalog automatically, we recommend that you remove any specific Global Catalog entries in your Enterprise Vault server configuration, as described in the following TechNote:    http://support.veritas.com/docs/284037


Support for Outlook 2003 RPC over HTTP connections
Microsoft Exchange Server 2003 and Microsoft Office Outlook 2003 support the use of Remote Procedure Call (RPC) over HTTP to access Exchange Server computers. Using RPC over HTTP, remote office users can connect to their Exchange Server mailbox using Outlook 2003 MAPI client, without the requirement for a virtual private network (VPN) connection.  This release includes Exchange Server RPC Extensions, which enable Outlook 2003 users, with either Enterprise Vault User Extensions or Self-Installing User Extensions installed, to access Enterprise Vault when using an RPC over HTTP profile.
Users will have access to all the main Enterprise Vault features over RPC over HTTP connections:

 
  • Open items in Enterprise Vault archives
  • Archive items manually
  • Restore archived items manually
  • Delete archived items
  • Find archived items using Enterprise Vault Integrated Search and Archive Explorer
  • Use Offline Vault
  • Client-side PST migration

 
When using RPC over HTTP connections, users will not be able to view the Enterprise Vault properties of folders or select a different archive or retention category for items being archived.  Instructions for installing and configuring Enterprise Vault RPC Extensions are given in the Installing and Configuring guide, found below, in the Related Documents section.

New Journaling Policy option to retry archiving of messages in 'Failed' folders [Ref CAP216, 505147, E595614]
If the Enterprise Vault Journaling Task encounters an issue while processing an item, it moves the item out of the Inbox to a folder such as 'Failed to Copy' or 'Failed to Store'. Over time a build-up of items may occur in the 'Failed' folders. The Enterprise Vault administrator will need to return these items to the Inbox in order for Enterprise Vault to attempt to archive them again. A second attempt at archiving a message is often successful if, for example, the first attempt failed because Enterprise Vault was temporarily unable to expand the message's distribution list.

A new setting Return failed items to Inbox is now available under the Advanced tab of the Exchange Journaling Policy properties. When set to On, this causes the Exchange Journaling Task, each time it starts, to return the contents of the journal mailbox 'Failed' folders back to the Inbox for reprocessing. This return of items will happen on a regular basis since, by default, the Exchange Journaling Task restarts automatically after processing a set number of operations. Selecting this option removes the need for the Enterprise Vault administrator to return the items manually. However, note that any genuinely corrupt items will repeatedly fail to archive, resulting in repeated errors appearing in the Enterprise Vault Event log for each attempt at archiving.

New message size limit avoids compression errors when archiving very large items [Ref CAP318, 603143, E597851]
At this release there is a maximum size, default value 250 MB, above which Enterprise Vault does not archive an item from a mailbox, journal mailbox, or public folder. This size limit has been introduced to prevent compression errors that can occur when Enterprise Vault attempts to archive very large items.
A new DWORD registry value MaxMessagesSizeToArchiveMB allows you to change the maximum size of items to archive. If you see error events relating to failed archiving of items that are known to be large, consider specifying a lower maximum size using this value. Place MaxMessagesSizeToArchiveMB under the following registry key:

HKEY_LOCAL_MACHINE
\Software
 \KVS
  \Enterprise Vault
   \Agents

If MaxMessagesSizeToArchiveMB is not present, the maximum message size defaults to 250 MB.  If you set this registry value to 0, Enterprise Vault attempts to archive messages irrespective of their size. This is not recommended in a production environment.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

Note: During manual archiving, if a custom filter reduces the size of an item (for example, if it removes the attachments from a message), Enterprise Vault evaluates the size of the item after the custom filter has taken effect. However, during automatic archiving Enterprise Vault performs the size evaluation before any custom filtering.


2. High priority fixes

Wrong shortcuts deleted when deleting multiple items in Outlook Cached Exchange Mode [Ref CAP059, 603013, 602511, 507015, 506087, E565330]
Users who were running Outlook in Cached Exchange Mode could delete the wrong items from their mailboxes if they selected multiple items and then, before clicking the Delete from Vault toolbar button, deselected one or more of those items. The same problem could occur if the users clicked the Delete from Vault button and then, before the deletion process had completed, selected further items.  This has been fixed.

Delegate mailbox access: PST files archived incorrectly [Ref CAP108, 603042, E578360]

It was possible for PST files to be archived incorrectly if the owner had not been enabled for archiving, but did have delegate access to another mailbox that was enabled, as in the following example.

If a secretary, whose mailbox had not been enabled for archiving, was given delegate access to a manager's mailbox and archive, then enabling client-driven PST migrations for the manager could result in the secretary's PST files being migrated into the manager's archive.
This has been fixed.

Could not view attachments to nested messages on Centera [Ref CAP117, CAP090, 603044, E575007]
When archiving to a Centera device, attachments to a nested MAPI message could not be viewed correctly. When you tried to view the attachments, they were displayed as blank documents. This problem affected messages archived using Enterprise Vault 6.0 SP2 only.
This has been fixed. The fix is retrospective, so attachments to nested messages archived using Enterprise Vault 6.0 SP2 are now shown correctly.

Improvements to Centera collections [Ref 506085, 507014, 603003, CAP005, E540249]
 
A number of issues, that caused file read errors during Centera collections, have been resolved. Changes and fixes include the following:
 
  • Centera collections are now performed using a stored procedure.
  • A looping behavior, caused by files being deallocated from the collection and not found during subsequent collection, has been fixed.
  • A housekeeping process now cleans up temporary saveset files that remain in the Centera collection folder after indexes have been rebuilt. Previously, rebuilding indexes resulted in an accumulation of temporary saveset files.

Default ruleset action in custom filters was incorrect [Ref CAP122, 603059]
If a ruleset in a custom filter XML file did not include an explicit ACTION=<message_action> attribute, messages that matched the ruleset were not archived, which was incorrect. This has been fixed. When an explicit ACTION attribute is not specified, the default action for matching messages is now ARCHIVE_ITEM, as described in the Installing and Configuring guide, found below, in the Related Documents section.

User with matching legacyMbxDn can inherit wrong archive [Ref 603041-1]
If a user mailbox was deleted and then a new user mailbox was created with the same legacyMbxDN, the mailbox synchronization task could incorrectly associate the new mailbox with the existing archive.  This has been fixed.

Potentially inconsistent search results [Ref CAP283, 603133, E623771]
When an Enterprise Vault server reached the maximum allowed index connections it was possible for a search to terminate prematurely, yet still return search results. This circumstance had the potential to produce inconsistent search results.  This has been fixed.

Searches could return duplicate results, and fail to show some results [Ref CAP355, 603159, 602549]
Under certain circumstances a search could return duplicate results, and fail to show some results. For example, this could affect an Archive Explorer search that returned more than one page of results, if you sorted the results on a numeric field (including Date).  This has been fixed.


3. Changes affecting users and requiring new User Extensions

In order to obtain the changes described in this section, the Enterprise Vault 6.0 SP3 User Extensions must be installed.

Improvements to Outlook User Extensions [Ref CAP157, 603070, E572217]
The following improvements have been made to the Outlook User Extensions:

 
  • When viewing the contents of an Enterprise Vault shortcut while using Outlook in Cached Exchange Mode, the Delete button was shown as being unavailable.  This has been fixed.

 
  • In some circumstances the Outlook User Extensions ignored the Exchange Mailbox Policy properties Shortcut deletion behavior setting. When this happened then, regardless of the setting, a user who opened a shortcut and then clicked Delete always received a prompt asking whether to delete just the shortcut, or both the shortcut and the archived item.  This has been fixed.

Deletion of mailbox items did not work as expected [Ref CAP115, 603050, 602525, E585654, E588692]
Sometimes, deletion of mailbox items did not work as expected. In some circumstances:

 
  • You could perform a hard delete (Shift+Delete) of a folder or its contents, even if the folder was set to be non-deletable.
  • If you selected multiple items for deletion, the system prompted you to confirm permanent deletion of the items, rather than moving them to the Deleted Items folder.
  • You could not delete an empty folder, even if the "Users can delete items from their archives" option was set.

These issues have been fixed.

Unable to hard-delete items in a PST file [Ref CAP106, 603040, E586224]
In Outlook 2003, if you selected multiple unarchived items or single or multiple archived items in a PST file and attempted to hard-delete them by pressing the Shift and Delete keys, the operation failed with the error:

 
Some items could not be deleted.
 
They were either moved or already deleted, or access was denied.
 

 
This has been fixed.

Improvements to Archive Explorer
When using Archive Explorer integrated within Outlook 2000, opening a message and then clicking the Next or Previous buttons could cause Outlook 2000 to terminate unexpectedly. [Ref CAP123, 603039, E430250]  This has been fixed.

Archive Explorer did not obey the Download format setting in the Exchange Mailbox Policy. Items were always downloaded items as .MSG files, regardless of the Download format setting. [Ref CAP123, 603046, 35158]  This has been fixed.

Outlook displayed error on exit if a recalled message was closed with an attachment open [Ref CAP0110, 603045, E574239]
Outlook displayed an error on exit if you closed a recalled archived message while leaving an attachment open.  This has been fixed.

Selecting folder Properties in a non-enabled mailbox caused Outlook to stop responding [Ref CAP0102, 603038]
When using Outlook 2000 or Outlook XP with the Enterprise Vault User Extensions, Outlook stopped responding if you right-clicked an Outlook folder and selected Properties in a mailbox that was disabled or not yet enabled for archiving.  This has been fixed.

Lock on archiving actions ignored [Ref CAP0096, 603037, E568972]
The Enterprise Vault Self-Installing User Extensions did not obey the Lock setting for the Create shortcut and Delete original item archiving actions.  This has been fixed.

Hebrew Archive Explorer prompted user to select folder in wrong pane [Ref CAP0099, 603062]
The initial message displayed by the Hebrew version of Archive Explorer instructed you to select a folder in the left pane, whereas the folder tree appears in the right pane.  This has been fixed.

The Enterprise Vault 6.0 SP3 User Extensions must be installed in order to obtain this change when Archive Explorer is used offline. The Enterprise Vault 6.0 SP3 User Extensions are not required when Archive Explorer is used online.

Empty folder prevents user from archiving folder structure [Ref CAP309, 603146, E626067]
When a user attempted to archive an Outlook folder structure and the selected folder contained subfolders but no items, the user received the following error:

You cannot archive an entire mailbox in Enterprise Vault

This has been fixed.

User Extensions now digitally-signed [Ref 603104 E615276]
The User Extensions add-in to Outlook (Valkyrie.dll) is now digitally signed. This enables User Extensions to be added to the list of trusted publishers in Outlook.

Depending on the Outlook security settings, it was possible for a user who started Outlook to be prompted with a Security Warning for Valkyrie.dll, asking whether to enable macros. (This is a standard Outlook prompt; there are no macros in Valkyrie.dll.)  Because Valkyrie.dll is digitally-signed, a user who receives the security warning can now select Always trust macros from this publisher so that this warning is not shown in the future.

Japanese translation updates [Ref 603130]
There have been some minor text and layout improvements to the Japanese Help and User Extensions dialogs.

Client-driven PST migration created inconsistent Archive Explorer root folder names [Ref CAP136, 603060, E586463]
Client-driven PST file migration used different name formats for the Archive Explorer root folder holding the archived items, depending on how the PST file was identified:

 
  • For PST files listed in the user's Outlook profile, Enterprise Vault used the PST file's display name, for example "My archived emails".
  • For PST files identified by a file system scan, Enterprise Vault used the PST file's full path name, for example "c:\documents\archive.pst".

Enterprise Vault now always attempts to use the PST file's display name when naming the Archive Explorer root folder.

Client-driven migration of PST files that are not in the Outlook profile [Ref 603084]
When Outlook 2000 or Outlook XP were installed, client-driven migration did not migrate PST files that were not in the Outlook profile. When the migration started, the user received the following prompt:

 
This information service has not been configured.
 
Select an existing file to configure, or type the name of a new file to create.
 

This behavior, which was introduced in Enterprise Vault 6.0 SP2, has been fixed.

Client-driven PST migration items were added to offline vault, then downloaded again on update [Ref CAP344, 603167]
When you updated an Offline Vault after a client-driven migration of a PST file, Offline Vault downloaded the migrated items again, even though the migration had already added them to the Offline Vault.  This has been fixed.


4. Changes affecting users and not requiring new User Extensions

The changes describe in this section are obtained as a result of upgrading Enterprise Vault server software and so do not require an updated version of the Enterprise Vault 6.0 SP3 User Extensions.

Archive Explorer displayed no items in offline mode [Ref CAP0069, 603015, 602515, E569869]
Archive Explorer displayed no items in offline mode if the name of the mailbox root container was changed to anything other than 'Top of Information Store'.
This has been fixed.

Default vault not listed first when performing integrated search [Ref CAP0178, 603078, E600755]
If you have access to more than one vault, the integrated search pane displays a list of available vaults to select from. In Enterprise Vault versions prior to SP2 your default vault was listed first. In SP2 the available vaults were listed alphabetically, so your default vault was not always listed first.  The previous behavior has now been restored: the integrated search pane lists the default vault first.

Message shortcut AutoPreview text could appear unintelligible in PST files [Ref CAP0045, 603007, 602518, 601640, E530152]
In Outlook 2000 or 2002, if you moved a message shortcut with a customized body containing non-ASCII text to a PST file, the customized body did not display correctly in AutoPreview. Enterprise Vault always used the Unicode codepage to encode text when creating customized message bodies, but Outlook 2000 and 2002 PST files do not support Unicode.

There is now a Mailbox Policy setting Encode custom body using appropriate codepages in the Archiving General settings on the Advanced tab.
Set Encode custom body using appropriate code pages to On to make Enterprise Vault uses the appropriate ANSI codepage to encode the customized body, ensuring it displays correctly in Outlook 2000 and 2002 PST files when AutoPreview is used.

Setting this option does result in a small performance impact on archiving.

Some words were not searchable [Ref CAP0042]
An Enterprise Vault search would fail to find words containing an embedded font change or certain accented characters.  This has been fixed.

Search applications fail when double quote in archive name [Ref CAP074, 603032, E566770]
If a user had access to an archive that had a double quote ( " ) in its name, then opening the Browser search (search.asp) or the Outlook Integrated search (searcho2k.asp) could result in a Service is not available error. It was then not possible to search any archives.   This has been fixed.

Incorrect SMTP address properties when using Outlook 2000 [Ref CAP023, 603004, E527628]
When using Outlook 2000 to view the address properties of a shortcut then, if the message had been sent to the user's SMTP address, the values shown were truncated to single characters.  This has been fixed.

Incorrect HTTP header caused blank page to be displayed in OWA [Ref CAP020-1, 603006-1, E424725-1]
An invalid character was added to HTTP headers. This caused a blank page to be displayed when a user opened an item in Outlook Web Access (OWA), if HTTP compression was configured on the front-end OWA 2003 Server.  This has been fixed.

Outlook Categories were not indexed [Ref CAP111, 603048]
In Outlook, when users assign one or more Outlook categories to a message, a MAPI property is added to the message to hold the category information. This property was not indexed by Enterprise Vault, unless you had configured custom filtering to specifically include this property.  

The multi-valued MAPI property for Outlook categories is now indexed for all levels of indexing without the need to configure custom filtering. Categories in the Master Category List and custom categories added to the list by the user are supported.  You can now search for all messages with one or more Outlook category assigned. For example, using the browser search:

 
In Internet Explorer, go to the Advanced page of the browser by entering the URL in the form:
 

 
http://<EVwebURL>/search.asp?advanced
 

 
where <EVwebURL> is the address for your Enterprise Vault web application. For example,
 

 
http://mywebserver.example.com/EnterpriseVault/search.asp?advanced
 

 
To search for messages that have particular categories assigned:
 

 
In the Name box beside Other Attribute enter the word, keys.
 
In the Value box, enter the categories that you want to match; the normal search rules apply, so multiple values should be separated by a space.
 

 
For example, to look for messages with the either the Business or Key Customer category assigned, enter Business Key.Customer.
 
To look for messages with the Business category but not the Key Customer category, you would enter Business -Key.Customer.
 

 
Incorrect date in preview pane [Ref CAP230-1, 603071, E597749]
 
Enterprise Vault applications that showed items in a preview pane did not correctly allow for daylight savings time. The items always showed the correct
 
times when opened.  If an item was viewed when the local daylight savings setting was different from the setting when the item was archived, the Sent and
 
Received dates showed incorrect times.  This affected the preview pane in:
 

 
  • Compliance Accelerator
  • Discovery Accelerator
  • Browser Search
  • Archive Explorer

This has been fixed.

Duplicate items in search results [Ref CAP255, 603119]
With Exchange mailbox, journal, and public folder archiving, duplicate messages were displayed in archive search results for messages that had been manually archived, restored and then re-archived using scheduled archiving.  This has been fixed.

'Web Application alias' property not correctly synchronized [Ref CAP306-2, 603150, 35687]
The Web Application alias property was not being correctly synchronized to the mailbox. The Web Application alias property is in the OWA 2003 settings on the Advanced tab of the mailbox policy.  This has been fixed.

Unable to type in search criteria in narrow integrated search pane [Ref CAP093, 603033]
On the integrated archive search page, with search results listed, you could not type in the Look for box if you significantly reduced the width of the pane. This happened if there was only a single archive available to search.  This has been fixed.


5. Changes to OWA support

OWA Extensions updated for Exchange Server 2003 update (KB 911829) [Ref CAP361,603164]
This release provides updated Enterprise Vault OWA Extensions to support the Microsoft update to Exchange Server 2003 SP2 (KB 911829:
 http://www.microsoft.com/downloads/details.aspx?FamilyID=5BC06E8A-08EB-4976-BC68-A03EBE3A2552&displaylang=en ).

You need to install and configure the updated OWA Extensions, as described below. The installation will update the OWA control files in either of the following folders:

  <Exchange install folder>\exchweb\6.5.7651.9
  <Exchange install folder>\exchweb\6.5.7651.25

To update your OWA Extensions:

 
First apply the Microsoft update on all front-end and back-end Exchange 2003 servers.
 
Update the Enterprise Vault OWA Extensions on each of your back-end Exchange 2003 servers, as described in To update OWA Extensions on back-end Exchange 2003 servers of this TechFile.
 
Update the Enterprise Vault OWA Extensions on each of your front-end Exchange 2003 servers, as described in To update OWA Extensions on front-end Exchange 2003 servers of this TechFile.
 

 
To update OWA Extensions on back-end Exchange 2003 servers
 
Perform the following steps on each back-end Exchange 2003 server:

 
1. Load the Enterprise Vault CD-ROM into the CD-ROM drive of your Exchange server.
 
2. Open the Enterprise Vault folder.
 
3. Open the Server folder.
 
4. Double-click SETUP.EXE to start the installation.
 
5. Follow the installation instructions and select the correct OWA Extensions component for this Exchange server.
 
6. To configure the extensions, log on to the back-end Exchange Server computer using an account that has Exchange Full Administrator permission.
 
7. Click Start > Programs > Enterprise Vault > Exchange 2003 Back-end Ext. Configuration (OWA & RPC).
 
8. A command prompt window opens and lists what the configuration program has done.
 
9. When the configuration program has finished, you will see the following line in the command prompt window:
 
Press ENTER to end
 
10. Details of the configuration process are sent to the log file:
 
Enterprise Vault\OWA\BackEnd2003Setup.wsf.log
 
11. Check this log file for any configuration errors.
 

 
To update OWA Extensions on front-end Exchange 2003 servers
 
Perform the following steps on each front-end Exchange 2003 server:

 
1. Load the Enterprise Vault CD-ROM into the CD-ROM drive of your Exchange server.
 
2. Open the Enterprise Vault folder.
 
3. Open the Server folder.
 
4. Double-click SETUP.EXE to start the installation.
 
5. Follow the installation instructions and select the correct OWA Extensions component for this Exchange server.
 
6. To configure the extensions, log on to the front-end Exchange Server computer using an account that has Exchange Full Administrator permission.
 
7. Click Start > Programs > Enterprise Vault > Exchange 2003 Front-end Ext. Configuration (OWA & RPC).
 
8. A command prompt window opens and lists what the configuration program has done.
 
9. When the configuration program has finished, you will see the following line in the command prompt window:
 
Press ENTER to end
 
10. Details of the configuration process are sent to the log file:
 
Enterprise Vault\OWA\FrontEnd2003Setup.wsf.log
 
11. Check this log file for any configuration errors.
 

 
RPC over HTTP limitations [Ref 603075, 35519, 35788]
 
In this release, the following limitations apply when using Outlook 2003 in RPC over HTTP mode:
 

 
The Browser Search link is not displayed on the Enterprise Vault search window. Users can access the browser search by opening a browser and entering the following URL:

HTTP://EV_web_server/EnterpriseVault/search.asp

where EV_web_server/EnterpriseVault is the URL you have configured for the Enterprise Vault web access application.

When using Outlook in RPC over HTTP mode with an ISA Server, clicking the View the original item link in a customized shortcut will give the error:

 
Page cannot be displayed
 

This happens because the client cannot contact the Enterprise Vault Web server directly.  You can view the item by double-clicking the shortcut.

This issue is not limited to configurations that include an Internet Security and Acceleration (ISA) Server. The link will not work in other situations where the client cannot contact the Enterprise Vault Web server directly; for example, if a firewall obstructs the connection.

Archived documents cannot be opened directly from the integrated Search results or properties pages. The documents can be in any type of archive. When you click the document link, Enterprise Vault prompts you to save the document on your desktop computer as a .dvs file. This limitation does not apply to documents that are archived as message attachments.  This behavior is exhibited when Outlook is installed on any of the following operating systems:

 
  • Microsoft® Windows Server® 2003 Enterprise Edition
  • Microsoft® Windows Server® 2003 Enterprise Edition SP1
  • Microsoft® Windows Server 2003 R2 Standard Edition (x64 and 32-bit x86)
  • Microsoft® Windows Server 2003 R2 Enterprise Edition (x64 and 32-bit x86)

The behavior is not exhibited when Outlook is installed on Windows XP.
To open the document, save the document on your desktop computer as a .dvs file, and then double-click the file to open it in the appropriate application.

Archived documents saved on desktop with different filename [Ref CAP307, 603144]
Using an OWA 2003 client to open an archived Microsoft Word or PDF document in your Inbox and save it to your desktop, did not work as expected. The document was saved with a different filename.
 
For example, a Microsoft Word document called example.doc was saved with a filename of the form:
 
17EAD1C6B0E9F934AAF75E24EFA52B5211110000vault.example.com!175000000000000.200605301658150000.1.31001B1FE01F4AFC83D66EC783A179A.doc
 

A PDF document called example.PDF was saved with a filename of the form:

 
1CFA86B8DBD5CB842A2A0C9B8B7E6BF231110000vault.example.com!474000000000000.200605311651180000.0.8B00F8940A8C450FA64FD0A5D867485.EML
 

This has been fixed.

OWA 2003 Premium client limitation [Ref 603087]
In this release, the feature that enables OWA 2003 Premium client users to select a different archive or Retention Category, when archiving an item manually, has been disabled. If a user selects an archive or Retention Category, other than the default, the item will not be archived. This will be fixed in a future release.


6. Changes to File System Archiving

File server fails to shutdown cleanly [Ref CAP116-1, 603053-1, 602527-1, E568059-1]

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

Placeholder shortcuts cannot be created for files with extended attributes [Ref CAP116-2, 603053-2, 602527-2, E568059-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.

Delayed File Write errors when archiving small files [Ref CAP171, 603077, 602532, E599674]
The following error was reported in the Windows event log when archiving small files using File System archiving.
 
Event ID 50
 
Description: {Delayed Write Failed} Windows was unable to save all the data for the file. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
 
The files were archived, but could not be retrieved using the associated Placeholder shortcuts or restored using Archive Explorer.  This has been fixed.

NetApp Placeholder service fails under load [Ref 603096, E601068]
The NetApp Placeholder service could terminate unexpectedly when under heavy load, especially when processing multiple NetApp Filer devices at the same time.  This has been fixed.

Delete item from archive when placeholder is recalled [Ref CAP087, 603093]
A new feature is the ability to delete an item from its archive when that item is recalled using a placeholder.
This functionality is controlled by a new DWORD value, DeleteOnRecall, under the following registry key on each file server that has a Placeholder Service:

HKEY_LOCAL_MACHINE
\Software
 \KVS
  \EnterpriseVault
   \FSA
    \Placeholderservice

The default value for DeleteOnRecall is 0, which means that items are not deleted from the archive. To make Enterprise Vault delete archived items when they are recalled using a placeholder, set DeleteOnRecall to 1 and then restart the Placeholder Service.  In order to obtain this new functionality you must install the Placeholder Service.

FSA synchronization failure when tens of thousands of folders [Ref 603043, E583530]
When synchronizing permissions on volumes with tens of thousands of folders the File System Archiving synchronizer process (EvFileSyncSvr) could become unresponsive and fail to synchronize permissions. This failure could go unnoticed if there were frequent archiving runs because the archiving process would correctly synchronize permissions.  When the problem occurred, the following events were logged: 8390, 8391, 13360.
This has been fixed.


7. Changes to Exchange Server Journaling

Incorrect archiving of calendar items in Exchange Server Journal mailbox [Ref CAP034, 603009, 601643, E544313]
Calendar items in an Exchange Server Journal mailbox were archived but were not removed from the mailbox. Thus they were archived many times, which could result in a reduction in performance when archiving Journal mailboxes.  If you have this problem, you can see that Calendar items are not removed from the Journal mailbox.  This has been fixed. Calendar items are now archived correctly from Exchange Server Journal mailboxes.

Journaling Connector correctly counts retried and re-archived messages [Ref CAP039, 603012, E539560]
When the Journaling task resubmitted a message for archiving, after a temporary storage problem, for example, or re-archived a message that had been restored, the Journaling Connector counted the message as a new message. This could result in seemingly inaccurate figures for the number of messages archived in Compliance Accelerator summary reports.  This has been fixed. The Journaling Connector now recognizes when actions are retries or re-archives, and does not increase the transaction count.


8. Changes to PST migration

Empty PST files not deleted after migration using Policy Manager [Ref CAP098, 603036, E545314]

If PST migration was performed using a Policy Manager script, and the [PSTDefaults] section included DeletePST=true, empty PST files were not deleted after all the items in the file had been successfully archived. This has been fixed.

Note the following actions if Enterprise Vault is not configured to archive calendar items and the PST file contains calendar items.

 
Value of ShortcutMode setting in [PSTDefaults] section PST deleted?
NoShortcuts No. PST will still contain calendar items.
MailboxShortcuts Yes. All items, including calendar items will be moved into the mailbox
PSTShortcuts No. PST will contain shortcuts


Unable to access items in renamed migrated PST folders [Ref CAP089, 603031, 602215, 506083, 507008, E518559]
If you renamed a mailbox folder that had been migrated from a PST file, changes to permissions on that folder did not enable other users to access items that had been archived before the folder was renamed. In Archive Explorer, two folders were displayed; one with the original folder name and one with the new folder name.  This has been fixed. Delegates can now access previously archived items in the renamed folder and only the renamed folder is displayed in Archive Explorer.

'Disable Outlook AutoArchive' option did not work for Outlook XP or Outlook 2003 [Ref CAP097, 603035, E579038]
When migrating PST files, for example using the PST Migration Wizard, the 'Disable Outlook AutoArchive' option did not work for Outlook XP or Outlook 2003.  This has been fixed.

Changed PST Collector or Migrator Task logon account did not persist [Ref CAP199, 603085]
If you specified a logon account for the PST Collector or Migrator Task, Enterprise Vault would only use the specified account until a PST file status changed to 'Ready to copy' or 'Ready to migrate', respectively. At that point, the task would revert to logging on using the default Vault Service Account.
This has been fixed.

Outlook 97-2002 PST files with Japanese folder names could fail to migrate [Ref CAP285, 603137]
If Enterprise Vault 6.0 SP2 hotfix 602-0215 (E518559) was installed, Enterprise Vault failed to migrate Outlook 97-2002 PST files containing Japanese folder names.  This has been fixed.

Changed message when importing PST files [Ref CAP310, 603149]
When performing PST migration using the wizard, it was possible to receive an inaccurate message if you chose all the following options:

 
  • Leave shortcuts in the mailbox
  • Delete the PST
  • Do not archive future calendar items

 
At the end of the migration it was possible to receive the following message:

The wizard has detected that some of the PSTs contain items that are not eligible for archive.
These items have not been archived and remain in the PSTs.

This was incorrect because the PST file had been deleted and the items that were not eligible for archiving had been moved to the mailbox.

This message has been changed to be as follows:

Some of the PSTs contained items that were not eligible for archive.
These items have been moved to the associated mailboxes.

PST migration could fail if messages present in PST root folder [Ref CAP303, 603142]
Importing a PST file to an Exchange mailbox could fail if messages were present in the PST's root folder and you selected the following settings in the PST Migration wizard:

 
  • Create shortcuts in the mailbox.
  • Make the root folder of the mailbox correspond to the root folder of the PST.
  • Use merged folder structures.

When the wizard attempted to import the PST file you could receive the error event "An error occurred while moving items from the PST file to the designated Exchange Server mailbox folder".  This has been fixed.


9. Changes to SharePoint archiving

Error when archiving large documents from SharePoint [Ref CAP046-1, 603049-1]
It was not possible to archive SharePoint documents that were larger than approximately 50MB. Attempting to do so resulted in an error in the SharePoint report log such as the following:

http://portal4/Document Library/LARGE DOCUMENTS/Document1.pdf
*** Error *** - Unable to read data from the transport connection.
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full

This has been fixed.

Error when archiving .ASPX files from SharePoint [Ref CAP046-2, 603049-2]
Some .ASPX files could not be archived. Attempting to archive such files resulted in a 404 Not Found error in the SharePoint report log.  This has been fixed.

SharePoint Server 2003 bug caused corrupt shortcuts [Ref CAP128, 603072, E588003]
With Microsoft SharePoint Server 2003 Service Pack 1, you could change the maximum file upload size from 50 MB to 2 GB. However, if you changed this setting to the maximum, 2048 MB, in the SharePoint Virtual Server Central Administration Web pages, SharePoint stopped working and was unable to upload any files. If Enterprise Vault attempted to create shortcuts on the SharePoint server, while SharePoint was in this state, Enterprise Vault was unable to update properties in the shortcuts and version history links were not created. If users selected to view the version history for one of these shortcuts, a prompt said that there were no archived versions of the document, even if there were.

If you set maximum file upload size to 2048 MB or more, Enterprise Vault will not create shortcuts. If you set the maximum file upload size to 2047 MB, and restart the Enterprise Vault SharePoint task, Enterprise Vault will create shortcuts, as normal.

SharePoint document version not archived if user account deleted [Ref CAP112, 603072, E588003]
If a SharePoint document was created or modified by a user, and then that user account was deleted in Active Directory, Enterprise Vault was unable to archive the document version and logged the following error in the SharePoint archiving report:

Server was unable to process request, user cannot be found

This has been fixed. Documents are archived, even if the user account has been deleted. The fact that the account has been deleted is no longer recorded in the SharePoint archiving report.

SharePoint Site Collection name longer than 64 characters was not configurable [Ref CAP175, 603080, E605175]
If a SharePoint Site Collection name exceeded 64 characters, you could not configure it in Enterprise Vault, and the site auto-discovery function would fail to discover it.  This has been fixed. Enterprise Vault now supports SharePoint Site Collection names of up to 256 characters.

Unable to restore large files to the SharePoint server [Ref CAP127, 603073]
In SharePoint 2003, if you tried to restore a document that was larger than 50 MB using the restore option on the version history page, or from the archive search results page, the following error was displayed:

   Object reference not set to an instance of an object.

You cannot restore such files to the SharePoint server, but you can save the file to your own computer. When you try to restore the file using the restore option on the version history page, or from the archive search results page, the following message is now displayed:

 
This document is too large to restore
 
If you want to download the document to your computer instead, right click the document version
 
and then select the command that will allow you to save the document to your computer.
 

The ability to restore very large files to the SharePoint server will be provided in a future release.


10. Changes to custom filtering

Error reported when applying attachment rule in custom filter [Ref CAP307, 6030151]

If a custom filter rules file contained a rule for processing attachments, filtering failed when processing messages that contained embedded attachments, such as embedded .GIF files. A series of exception messages reporting the failure of the custom filter were sent to the event log. The last of these messages took the following format:
 
Event Type: Error
 
Event Source: Enterprise Vault
 
Event Category: Archive Task
 
Event ID: 3263
 
Date: date
 
Time: time
 
User: N/A
 
Computer: computername
 
Description:
 
An error occurred processing the external filter 'EnterpriseVault.CustomFilter'. No more filters will be processed.
 

This has been fixed.

ATTACHMENT_ACTION="REMOVE" did not work [REF CAP322, 603155]
In custom filtering, if a rule in the XML filter file had the attachment action, ATTACHMENT_ACTION="REMOVE", attachments were not removed from messages that satisfied the rule.  This has been fixed.


11. Changes to Domino archiving

Domino Journaling stops unexpectedly [Ref 603158-1]

It was possible for Domino Journaling to stop archiving unexpectedly and for the task to become unresponsive.  This has been fixed.

Domino Journaling Task searches for incorrect file [Ref 603158-2]
Occasionally, the Domino Journaling Task could generate either of the following errors:

 
Event Type:     Error
 
Event Source:   Enterprise Vault
 
Event Category: Lotus Domino Journaling Task
 
Event ID:       40966
 
Date:           12/10/2005
 
Time:           14:41:37
 
User:           N/A
 
Computer:       MYCOMPUTER
 
Description:
 
A program fault has raised an exception.
 
Exception: Could not find file "D:\Program Files\lotus\notes\xmlschemas\domino_7_0_1.dtd.dtd".
 
Diagnostic: Database:'symantec\mailjrn.nsf' -> NoteId:'51e32'
 
Type:
 
Reference: ProcessAQueuedItem()
 

 
Event Type:     Error
 
Event Source:   Enterprise Vault
 
Event Category: Lotus Domino Journaling Task
 
Event ID:       40966
 
Date:           12/10/2005
 
Time:           14:41:37
 
User:           N/A
 
Computer:       MYCOMPUTER
 
Description:
 
A program fault has raised an exception.
 
Exception: Could not find file "D:\Program Files\lotus\notes\xmlschemas\domino_7_0_1"
 
Diagnostic: Database:'symantec\mailjrn.nsf' -> NoteId:'51e32'
 
Type:
 
Reference: ProcessAQueuedItem()
 

This has been fixed.
 
V-437-40966

EVDominoExporter.exe limited to 250,000 items [Ref 603158-3 , 30516]
When using the EVDominoExporter.exe tool to export archives, it was not possible to restore more than approximately 250,000 items in a single run. Errors such as the following were generated:

 
AllocHandle: OUT OF SHARED HANDLES! -- pid 00001540 Handles used so far 251647,
 
            Maximum handles = 251647, error = 0x107
 
Error saving note: Maximum number of memory segments that Notes can support has been exceeded
 
Exported: 251283/294849, Failed: 1
 

This has been fixed.


12. Other changes

Documentation changes

Changes to the "Application Programmer's Guide" are now listed within the book itself, in a new chapter called Updates to the Enterprise Vault APIs.

Single-instance storage of RTF messages with attachments [Ref CAP0118, 603047, E581359]
Single-instance storage was not being used for RTF messages that contained embedded images or files.  This has been fixed.

OWA extensions support HTTP compression [Ref CAP020-2, 603006-2, E424725-2]
Enterprise Vault OWA 2003 extensions now support the use of High Compression for HTTP on OWA 2003 servers.

NetApp filer placeholders open after restart [Ref CAP016, 603005, E493842]
If you restarted Enterprise Vault services while the NetApp filer was stopped, archived items could not be accessed when the filer was restarted. Attempting to open a placeholder shortcut on the filer caused "Access denied" errors.  This has been fixed.

In a Building Blocks environment, tasks did not start after failover [Ref CAP228, 603095, E608578]
In an Enterprise Vault environment using Building Blocks, archiving tasks did not restart after Enterprise Vault failed over to the standby computer. The following message was sent to the event log by the archiving task:

 
Event Id 3220
 
Description:
 
Could Not detect the MSMQ service
 
Error: 0xc00e0014
 
Check that the MSmq services are running.
 

This has been fixed. After failing over to the standby computer, the archiving tasks will start automatically.  Note:  You need to install this release on each Enterprise Vault server computer in the Building Blocks environment.

Exceeding the indexing backlog threshold caused problems [Ref CAP081, 603111]
If the threshold value for the number of archived items pending indexing was exceeded, a number of problems could occur:

 
  • Enterprise Vault would send journal mailbox items to the 'Failed to Store' folder, instead of archiving them.
  • Events could be logged very frequently (every minute) until the backlog was cleared.
  • When File System Archiving, events could indicate the index backlog had been cleared when this was not the case.

The indexing architecture has now been modified and, as a result, the indexing backlog threshold is no longer required, avoiding these problems.

Large numbers of 7264 and 7288 events in application logs [Ref CAP231, 603082, E607602]
When Enterprise Vault was archiving many items under heavy load, large numbers of 7264 and 7288 events could sometimes be logged, indicating Indexing Service errors. This related to the threading model of an internal component of the Indexing Service.  This has been fixed.

Disabling synchronization for new user mailboxes [Ref CAP041-2 603041-2, 603153]
When migrating mailboxes from one Exchange Server to another, it can be useful to make Enterprise Vault automatically assign migrated mailboxes to existing archives.  There is a new DWORD registry value, SynchInMigrationMode that enables you to control whether the automatic association takes place. Create SynchInMigrationMode under the following registry key:

HKEY_LOCAL_MACHINE
\Software
 \KVS
  \Enterprise Vault
   \Agents

Give SynchInMigrationMode a value of 1 to make Enterprise Vault assign new mailboxes to archives that are associated with the same legacyMbxDN values.

Give SynchInMigrationMode a value of 0 to use the default behavior, in which Enterprise Vault does not assign new mailboxes to archives that are associated with the same legacyMbxDN values.

SynchInMigrationMode affects only the association between user mailboxes and archives; it does not affect the association between journal mailboxes and their archives.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.


Errors when archiving to NetApp SnapLock device [Ref CAP237, 603106]
Sometimes, when archiving thousands of copies of the same item to a NetApp SnapLock device, numerous 6881 errors were logged. The failed messages were moved to the 'Failed to Store' folder.  The errors were as follows:

 
Error 6881
 
Unable to complete archive request
 
Reason:   Access is denied.  [0x80070005]
 

This behavior, which was introduced in Enterprise Vault 6.0 SP2, has been fixed.

MAPI error MAPI_E_FAILONEPROVIDER when synchronizing mailboxes [Ref CAP306-1, 603150]
When synchronizing mailboxes it was possible for Event 3227 to be logged repeatedly. For example:

 
The MAPI error MAPI_E_FAILONEPROVIDER (0x8004011D) has occurred whilst synchronizing
 
the properties of mailbox /o=First Organization/ou=First Administrative Group
 
/cn=Recipients/cn=testdisabled.
 
The mailbox will not be synchronized until the next scheduled run.
 
AgentExchSynch.cpp
 
(CAgentExchSynch::OpenUserAndStore) [lines {1407,1414,1419,1423,1449,1455}] built Feb 11 13:30:13 2004
 

This has been fixed.

Multiple error events on synchronization if mailboxes became inaccessible [Ref CAP340, 603160]
If mailboxes became inaccessible, for example because the mailbox store was temporarily dismounted, then on synchronization Enterprise Vault generated several exception errors for each mailbox.  This has been fixed.  With this release, no error events are logged in the event log, but error statements are now shown in DTrace for each attempt at synchronizing a mailbox in the unavailable store.

 

Attachments

ev60_sp3_284461.zip (116 MBytes)

Supplemental Materials

SourceEvent ID
Value40966
Description

A program fault has raised an exception.
 


SourceUMI
ValueV-437-40966
Description

A program fault has raised an exception.
 



Legacy ID



284461


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


Terms of use for this information are found in Legal Notices