Symantec Enterprise Vault 7.0 - Release Notes (Part 2 of 2)

Article:TECH50056  |  Created: 2006-01-08  |  Updated: 2011-04-21  |  Article URL http://www.symantec.com/docs/TECH50056
Article Type
Technical Solution


Environment

Subject

Issue



Symantec Enterprise Vault 7.0 - Release Notes (Part 2 of 2)


Solution



Overview:
This document provides important information about the Symantec Enterprise Vault 7.0 release and is in two parts.

Information regarding new features, changes and points to note within Symantec Enterprise Vault 7.0 can be found in Part 1:  http://entsupport.symantec.com/docs/286078

Known issues and eLearning course information are detailed below.

For the latest information on supported devices and versions of software, see the Enterprise Vault Compatibility Charts  http://entsupport.symantec.com/docs/276547

For the latest information on Enterprise Vault 7.0 sizing and performance, see the Enterprise Vault Performance Guide  http://entsupport.symantec.com/docs/286420

Contents

3. Known issues
 
3.1  Using Windows Installer
 
3.2  Enterprise Vault servers
 
3.3  Roles-based administration
 
3.4  Exchange Server archiving
 
3.5  PST migration
 
3.6  File System Archiving
 
3.7  Enterprise Vault monitoring and reporting
 
3.8  Enterprise Vault searching in East Asian languages
 
3.9  Enterprise Vault User Extensions
 
3.10 Client-driven PST migration
 
3.11 Archive Explorer
 
3.12 Windows Desktop Search (WDS)
 
4. eLearning courses
5. Pointers to Enterprise Vault documentation


3. Known issues

This section describes known issues with Enterprise Vault servers and clients.

You may want to inform users of the behavior described in section 3.9 Enterprise Vault User Extensions.

3.1 Using Windows Installer

3.1.1 Installing MSI packages from a remote location [Ref 854463]

There is a Windows Installer limitation that may prevent you from installing the Deployment Scanner or Enterprise Vault User Extensions MSI packages when the installation file is in a remote location.

The solution is to copy the package to the local computer and install from there, or to copy the package to a network server that does not require Windows Installer to authenticate during the installation.


3.2 Enterprise Vault servers

3.2.1 Failure to update DCOM on x64-based versions of Microsoft Windows Server 2003 [Ref 842891]

When you run the Configuration wizard for a new installation of Enterprise Vault on an x64-based version of Microsoft Windows Server 2003, the following message may be displayed:

Unable to update DCOM details

A report similar to the following is written to the event log:

Event 10016
The application-specific permission settings do not
grant Local Launch permission for the COM Server
application with CLSID {...} to the user username SID (...).  

This error is not fatal, and the services are created successfully. It is only the DCOM credentials that are not updated.

The same message may be displayed when you attempt to change the Vault Service account.

In both situations, you can use the following steps to force an update of the DCOM details:

1.  When the Configuration wizard has completed, stop the Enterprise Vault Admin service.
2.  Then restart all the Enterprise Vault services.
3.  Start the Administration Console.
4.  Right-click the Enterprise Vault Directory container in the left pane and select Properties.
5.  Click the Service Account tab to display the details of the Vault Service account.
6.  Change the Vault Service account password. You can re-enter the existing value.
7.  Click OK.
8.  This forces DCOM details to be updated.

The cause of this problem is a known Microsoft issue with updating DCOM details on x64-based versions of Microsoft Windows operating systems. See the Microsoft Knowledge Base article  http://support.microsoft.com/?kbid=899965
Do not use the workarounds described in the Microsoft article. Instead, use the steps described above to update DCOM details.

3.2.2 Resource allocation

If you encounter problems that may be due to resource allocation issues, you are recommended to apply registry keys as described in the Microsoft Knowledge Base article Server is unable to allocate memory from the system paged pool  http://support.microsoft.com/default.aspx?scid=kb;EN-US;312362

3.2.3 Size of collection files [Ref 857282]

The default size of a collection file is 10 MB. The Help for the Collections tab of Vault Store Partition properties incorrectly states that the default size of a collection file is 200 MB.

For performance reasons, do not make the size of a collection file larger than 10 MB.

3.2.4 Error on shutting down Admin Service [Ref 32730]

When shutting down the Enterprise Vault Admin Service it is possible for an event such as the following to be logged in the Enterprise Vault event log:

Event Type: Error
Event Source: Enterprise Vault
Event Category: Index Server
Event ID: 8390
Date: 02/11/2006
Time: 07:55:01
User: N/A
Computer: MYSERVER
Description:
The EnterpriseVault.DirectoryConnection object reported an error. General access denied error

The event is generated because it is possible for the Directory Service to shut down before the Indexing or Storage services. You can ignore this event if it is logged when the Admin Service is shut down.

3.3 Roles-based administration

3.3.1 "Failed to load the Authorization store" message when starting the Administration Console [Ref 859608]

If you receive the following message when you start the Administration Console as a user other than the Vault Service account, close the Administration Console and choose the option to save the console settings. Then restart the Administration Console.

Failed to load the Authorization store 'path\EvAzStore.xml'
Reason: The name of the directory machine cannot be blank.
Check that the Vault Directory Service is running and the computer is reachable on the network.

3.4 Exchange Server archiving

Mailbox synchronization for new mailboxes [Ref 32778]

A synchronizing of mailbox permissions for newly-created mailboxes can generate errors in the Enterprise Vault event log. This is because of a timing issue with Exchange Server. The errors are similar to the following:

Event Type: Error
Event Source: Enterprise Vault
Event Category: Archive Task
Event ID: 4167
Date: 14/11/2006
Time: 09:17:28
User: N/A
Computer: MYSERVER
Description:
An exception has been raised.
Internal reference .\AgentExchSynch.cpp (CAgentExchSynch::SynchronizeMailboxEntry) [lines {546,596,617}] built Jun 3 23:34:17 2005  An exception is raised when a process encounters an unexpected fault.

This event is followed by the events 2270 ('A queued operation exceeded the retry count and has been discarded') and 3196 ('An error has occurred whilst synchronizing the properties of mailbox').

The synchronization will succeed at some time in the future, usually within an hour or so.

3.5 PST migration

3.5.1 Hard disk searches fail on NetApp VFiler devices

The PST Locator task cannot perform hard disk searches for PST files on NetApp VFiler devices.

3.5.2 Memory leak when accessing or creating PST files [Ref 764355]

There is a risk of a substantial memory leak when running Microsoft Outlook 2003 SP2 with the Enterprise Vault server or client software. The leak occurs when Enterprise Vault accesses or creates PST files.

For details of the problem and a link to the Outlook 2003 update that removes the risk of the memory leak, see the following support document  http://entsupport.symantec.com/docs/281568

3.6 File System Archiving

3.6.1 New Volume wizard does not list all hidden shares [Ref 849772, 848955]

When you run the New Volume wizard to add a new volume for archiving, the second page of the wizard asks for the name of the share to add. If you click Browse and then choose to list "Hidden" shares, the resulting list shows only drive root hidden shares (C$, D$, and so on). If the hidden share you require is not shown, click Cancel to close the list of shares and then type the name of the share.

3.6.2 Error when synchronizing auto-enable folders [Ref 857290]

When Enterprise Vault synchronizes folder policies an error similar to the following is logged for each auto-enable folder that does not have a folder policy:

** Warning *** - One more Root folders were not synchronized        
Root folder: \\evdemo.demo.local\fsa1\user is not synchronised as it is not marked with a policy

You can ignore these errors when they refer to auto-enable folders.

3.6.3 Unicode characters in ZIP file names are corrupted [Ref 796082]

Unicode characters in the names of ZIP files (or in the names of files stored inside a ZIP file) are incorrectly handled, with the result that you cannot subsequently open such files.

Note that this is a limitation of the ZIP file format, which does not currently support the use of Unicode characters in file names.

3.6.4 Creating an fpolicy on Network Appliance Vfiler systems [Ref 700551]

A limitation with versions of Network Appliance Data ONTAP earlier than Data ONTAP 7.2 prevents Enterprise Vault from working correctly with Network Appliance MultiStore Vfiler systems. Enterprise Vault is unable to create an fpolicy on the filer automatically, and an error message appears in the event log on the Enterprise Vault server.

For details of how to create an fpolicy for Enterprise Vault to use, see the following support document  http://entsupport.symantec.com/docs/280369

3.6.5 "Exception handle" message when installing Placeholder service on a clustered file server  [Ref 859485]

You may receive the following message when you use the Install Placeholder wizard to install the Placeholder service on a remote file server that is a member of a VERITAS or Microsoft Cluster Server cluster:

Inside ThreadToPush exception handle. Unknown error

If you receive this message, close and restart the Administration Console, and then re-run the wizard.

3.6.6 Uninstalling Enterprise Vault Placeholder Services

You must uninstall Enterprise Vault before uninstalling the Enterprise Vault Placeholder service. You may prefer to disable the Enterprise Vault File Placeholder Service instead of uninstalling it.

3.7 Enterprise Vault monitoring and reporting

3.7.1 Monitoring database and Monitoring agents

To troubleshoot problems with the Monitoring database or the Monitoring agents, see the following document on the Symantec Support Web site  http://entsupport.symantec.com/docs/285813

3.7.2 Enterprise Vault Operations Manager

To troubleshoot problems with installing or using Enterprise Vault Operations Manager, see the following document on the Symantec Support Web site  http://entsupport.symantec.com/docs/285814

3.7.3 Enterprise Vault Reporting

To troubleshoot problems with installing or using Enterprise Vault Reporting, see the following document on the Symantec Support Web site  http://entsupport.symantec.com/docs/285815

3.8 Enterprise Vault searching in East Asian languages [Ref 849912]

Enterprise Vault does not currently permit case-insensitive searches for full-width characters in East Asian languages (for example, Japanese). For more information, see the following document on the Symantec Support Web site  http://entsupport.symantec.com/docs/286028

3.9 Enterprise Vault User Extensions

3.9.1 Upgrading Self-Installing User Extensions [Ref 859256]

The installation process currently prompts users to restart their computer before the installation complete page is displayed. If users click Yes on the restart prompt, the End Program dialog is displayed for Outlook. This dialog is displayed because Windows is trying to shut down Outlook but the installer is trying to open the installation complete page. Users can safely ignore the End Program dialog and click No on the "Do you want to save changes?" prompt.

3.9.10 Outlook 2003 in Exchange Cached Mode

When the User Extensions are used with Outlook 2003 in Exchange Cached Mode, manual archive and restore behave as though the Self-Installing User Extensions were installed:
 
  • Archive automatically uses the archiving settings for the current folder, without prompting the user for vault or Retention Category
  • Restore, when using a shortcut, always restores to the current folder (where the shortcut is) and deletes the shortcut
If the user turns off Exchange Cached Mode, manual archive and restore behave normally.

3.9.11 Enterprise Vault icons not displayed

When in Exchange Cached Mode, some computers do not display the Enterprise Vault icons until an archived item is opened. The icons then appear for the current Outlook session but have disappeared when Outlook is restarted. Symantec are discussing the solution to this problem with Microsoft.

3.9.12 Searching archives with delegate access [Ref 858792]

If user A grants user B permission to view an Outlook folder then, when user B searches archives, user A's archive is not visible by default in the list of available archives.

To solve this, user A must edit the mailbox root properties and, on the Permissions tab, add user B and grant the permission Folder visible.

3.10 Client-driven PST migration

3.10.1 Automatic space allocation in client-driven PST migration [Ref 326913]

In Enterprise Vault 7.0 you can configure the Enterprise Vault User Extensions so that they automatically upload PST files so that they can be migrated. Items that will be migrated from PST files can be automatically added to Offline Vault, so they do not need to be downloaded after migration.

There is a setting, Automatically add space to offline archives, that should enable offline vaults to grow automatically to accommodate items added as a result of the PST Migration. Currently this automatic growth does not happen.

If you want migrated items to be automatically added to Offline Vault, ensure that the maximum size of offline vaults is sufficient to accommodate the new items.

3.10.2 Accessing PSTs on mapped drives using RPC over HTTP [Ref 806946]

When a user is connected to Exchange Server using RPC over HTTP, mapped network drives are unavailable. If a user's PST file is on a mapped network drive, client-driven PST migration fails because Outlook is unable to access the PST file.

The user receives Outlook errors similar to the following:

The path specified for the file Z:\myoldmail.pst is not valid.
An error occurred while reconnecting Z: to \\192.168.0.2\pst
Microsoft Windows Network : The network path was not found.
This connection has not been restored.

Client-driven PST migration will continue when the PST file is again available to Outlook.


3.11 Archive Explorer

3.11.1 Archive Explorer may not show old items [Ref 29572]

Archive Explorer uses new indexing properties to find archived items. This means that items archived with Enterprise Vault versions before 3.7 will not appear in Archive Explorer until you replay the archive indexes using the Index Volume Replay utility, which is described in the Utilities guide.

3.11.2 Archive Explorer view of new Exchange Server mailbox archive [Ref 29509]

If there have been no items archived from a newly-created mailbox, Archive Explorer does not show the mailbox's folder structure. This is expected.

The folder structure will be shown after the next run of the Exchange Mailbox archiving task. Alternatively, you can manually archive an item from the mailbox.

3.11.3 Archive Explorer on Windows 2003 [Ref 29233]

When Archive Explorer is first used on Windows 2003 then, if the web site is not in the trusted sites zone, the user must choose to add it to the trusted sites zone. Once this has been done, Archive Explorer must be closed and restarted and will work correctly thereafter.

If Archive Explorer is not restarted, any attempt to access archived items produces an Internet Explorer Script Error similar to one of the following:

An error has occurred in the script on this page
Error: Permission denied
Do you want to continue running scripts on this page?

An error has occurred in the script on this page
Error: Access is denied
Do you want to continue running scripts on this page?


3.12 Windows Desktop Search (WDS)

3.12.1 Administrator privileges required for WDS search of online archive

Searching offline archives using WDS is supported in both the Enterprise Vault User Extensions and the Self-Installing User Extensions. This feature is enabled using an Offline Vault setting in the Exchange Mailbox Policy. Users do not need Administrator privileges on their desktop computer to use this feature.

Additionally, Desktop settings in the Exchange Mailbox Policy enable users to search their online archive using WDS. Microsoft registry restrictions mean that users must have Administrator privileges on their desktop computer to use this feature.

3.12.2 Offline Vault option in WDS
The option Offline Vault will show up in the WDS Location menu for any user, regardless of whether that user has Offline Vault enabled.

3.12.3 Re-enabling WDS plug-in after uninstalling/reinstalling User Extensions

The Enterprise Vault WDS plug-in is installed, but not enabled by default, when you install the User Extensions or Self-Installing User Extensions.

When you enable the WDS plug-in, the evoffline:// search location becomes available in the WDS Locations list.

If you uninstall the User Extensions or Self-Installing User Extensions, the WDS plug-in is disabled and uninstalled, as you would expect. But the evoffline:// search location still appears in the WDS Locations list, even though it cannot be used, because WDS has failed to remove it.

If you then reinstall the User Extensions or Self-Installing User Extensions and do not re-enable the WDS plug-in, the evoffline:// search location will mislead users into thinking that the plug-in is enabled.

So if you uninstall and reinstall the User Extensions or Self-Installing User Extensions, you need to re-enable the WDS plug-in. For details of how to do this, see the Enterprise Vault Installing and Configuring guide.

3.12.4 Duplicate search results in WDS [Ref CAP1077, 798822]

It is possible for WDS to show duplicate search results in either of the following circumstances:

 
  • Searching for email metadata, such as sender, can sometimes result in duplicate results because some text that is in an item in offline vault may also be in the corresponding Outlook shortcut.
  • It is possible for a mail item to be indexed by WDS before being archived and then to be indexed again when it is stored in the offline vault. The duplicate entry disappears when WDS performs its next index scan. If this duplication occurs, only one of the search results will open the actual item.

4. eLearning courses

Enterprise Vault 7.0 includes the following Symantec Education eLearning courses to help you get the most benefit from your investment in Symantec software.

Note: Compliance Accelerator and Discovery Accelerator are optional components of Enterprise Vault.
 
  • Symantec Enterprise Vault 7.x System Administration Fundamentals: provides an overview of the functionality and benefits of Enterprise Vault from a daily administrative point of view. You will learn how to manage Enterprise Vault to increase the efficiency and effectiveness of the product in your environment.
  • Symantec Enterprise Vault 7.x User Fundamentals: introduces Enterprise Vault, and is designed to enable a user to:
  • Describe what Enterprise Vault does and why many companies implement it.
  • Extend the functionality of Outlook using Enterprise Vault.
  • Use the extensions to interact with their archived emails.
  • Take archives offline and use the Outlook Web Access client.
  • Symantec Enterprise Vault 7.x Compliance Accelerator: How to Review and Search E-Mails: discusses compliance and why it is important, in addition to the benefits of using Compliance Accelerator. You will learn how to use Compliance Accelerator to support your organization's compliance policy in searching email messages for specific information. Installation, configuration, and troubleshooting of Compliance Accelerator are not covered.
  • Symantec Enterprise Vault 7.x Discovery Accelerator for End Users: goes through the steps involved in setting up discovery searches, and then what to do with the search results. Installation, configuration, and troubleshooting of Discovery Accelerator are not covered.



Legacy ID



286420


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


Terms of use for this information are found in Legal Notices