Quest® Archive Manager
Maintenance Release Version 4.1.1
Build 436
Release Notes
October 2009
Doc ID 281
Quest® Archive Manager is an archiving and management solution that enables
email and file data to become a true asset for the organization by capturing,
indexing, and storing it for mailbox management, compliance, and knowledge
sharing.
These Release Notes document the Archive Manager 4.1.1 Maintenance Release, and are intended as an addendum to the Archive Manager 4.1 Release Notes. The Archive Manager 4.1.1 Maintenance Release includes the following:
Note: Please see the Quest_ArchiveManager_4.1.1_ADCConfig.pdf file for information about configuring the Active Directoroy Connector.
The changes listed above require the configuration settings listed in the Configuration Settings section below. If the configuration settings have not been added, please add them in the Archive Manager Configuration Editor.
In addition to the software requirements listed in the Installing the Archive Retrieve Tool for BlackBerry Users chapter of the Administration Guide, the following requirements also apply:
proxycfg -d -p " " "*"
This command tells the technology stack to send Windows authentication to all servers when running Archive Retrieve. Or, instead of using "*" for all servers, you can list the servers that host Archive Manager Websites.
The following is a list of issues addressed and enhancements implemented in this release of Archive Manager.
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
64916 |
|
When using the configuration option Active Directory Connector Root to specify Organizational Units (OUs) to process, the Active Directory Connector treats all users who are not in the last OU in the list as deleted. |
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
35880 |
|
The Remove from Folder feature on the context (i.e., right-click) pop-up menu was able to remove only items selected in the first page of multi-page search results from a custom or virtual mailbox. The Remove from Folder option was not available on the second and subsequent pages of those multi-page results. |
|
Archive Manager |
4.1 |
53691 |
|
When selecting a message to print, a screen comes up that can't be adjusted or expanded. |
|
Archive Manager |
4.1 |
55490, 61951, 65938, 66188 |
|
Rtf messages go into an infinite loop when there is a mismatch of ole placeholders and corresponding attachments. Symptoms include:
|
|
Archive Manager |
4.1 |
64353 |
|
LDAP authentication requests to Active Directory for logging into the Website are passed in clear text, causing a security concern. Add an enhancement to enable LDAPS (Secure LDAP). |
|
Archive Manager |
4.1 |
67983 |
|
Fonts names containing the word script in them did not retain their styles after HTML conversion. |
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
63812 |
|
Data Loader cannot load an .xml file if the Body column of the MessageData table is NULL when using the recovery setting. |
|
Archive Manager |
4.1 |
64369 |
|
Non-message items with 8k or larger source properties don't load. |
|
Archive Manager |
4.1 |
65118 |
|
The Data Loader fails when it encounters two records in Active Directory with the same Legacy DN, one with a deleted mailbox and one with an active mailbox. |
|
Archive Manager |
4.1 |
65194 |
|
The Data Loader is generating an exception error which causes it to stop running. |
|
Archive Manager |
4.1 |
65197 |
|
Messages containing many levels of embedded messages cause the Journal Data Loader to hang. |
|
Archive Manager |
4.1 |
65563 |
|
Exclusion Rules fail when using Header and a Header value. |
|
Archive Manager |
4.1 |
69641 |
|
The Data Load service can't load EML files with certain characteristics, so it moves them to the Error folder. The characteristics are that the EML files have a winmail.dat attachment (indicating that they were mail from Exchange tunneled over SMTP), and that an attachment is inside of the winmail.dat attachment. |
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
64756 |
|
Archive Manager version 4.1 no longer deletes stubs from Exchange mailboxes. |
|
Archive Manager |
4.1 |
64827 |
|
Messages with date-warning properties in the header are incorrectly checksummed. |
|
Archive Manager |
4.1 |
64935 |
|
Add enhancement to include IPM.Document in the stubbing policy. |
|
Archive Manager |
4.1 |
65192 |
|
Add an enhancement so that when a message has been deleted by retention, or excluded by an exclusion rule, the ESM will now delete the message from Exchange. |
|
Archive Manager |
4.1 |
65696 |
|
The Exchange Store Manager (ESM) generates the following error: Property is too large to read into memory. |
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
65610 |
|
The Exchange Utility does not see all available Exchange servers in a domain. |
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
63039 |
|
The Full Text Index Service fails to index some.docx files due to a problem with the IFilter that caused a timeout to occur. |
|
Archive Manager |
4.1 |
64624 |
|
The Full Text Index Service returns the following error: |
|
Archive Manager |
4.1 |
65193 |
|
The Full Text Index Service is aborting when messages have NULL bodies. |
|
Archive Manager |
4.1 |
66148 |
|
Attached docx files with several embedded images cause an issue with the iFilter so that all available CPU resources are consumed. |
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
65226 |
|
The GroupWise Store Manager (GSM) cannot extract all data from some GroupWise mailboxes. |
|
Archive Manager |
4.1 |
66133 |
|
The GroupWise Directory Connector (GDC) processing speed is insufficient in production. |
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
65218 |
|
Messages that were migrated to Exchange from GroupWise with the Microsoft tool and are stubbed cannot be reconstructed. |
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
65191 |
|
Centera errors are being reported by the Retention Engine when attempting to delete attachments out of the Centera store. |
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
64682 |
|
The Search Exporter is not able to parse multiple Contexts in the NDS tree when authenticating. |
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
69189 |
|
Program revisions have substantially reduced lost handles and other errors that appeared in the BlackBerry Enterprise Server (BES) logs. |
|
Archive Manager |
4.1 |
68962 |
|
A code enhancement has corrected an erroneous internal program flag that caused the BES to utilize handles without releasing them. This eventually caused the BES server to stop processing messages. |
The following is a list of issues addressed and enhancements implemented in this release of Archive Manager.
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
69460 |
|
The Archive Manager Offline Client QsArchiveOfflineExt.adm template file incorrectly lists AfterMailService.asmx in the Web Service URL example. The correct example is as follows: http://SERVER:PORT/defaultinstance/offlineclientendpoint.asmx.
|
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
66567 |
|
Scrolling through stubbed messages in the Outlook Form preview pane can cause OutlookOL 2007 with KB961752 or Office 2007 with HotFix 2 applied to crash. The preview pane is now disabled by default for stubbed messages. |
|
Product Name
|
Product Version |
Defect ID |
Associated Case Number |
Problem Description |
|
Archive Manager |
4.1 |
68371 |
|
The Enable Store Management box is checked by default in the mailbox for the journal user. This box needs to be unchecked so that the mailbox is not processed by the Exchange Store Manager (ESM). Journal mailboxes should be processed by the journal data loader. |
Two Archive Manager databases should not be installed to the same SQL server instance. It is fine to install two Archive Manager databases to the same machine if the machine has two or more SQL Server instances running, and each will host a single Archive Manager database.
The Archive Manager Version 4.1 Planning and Installation Guide for Exchange states that Exchange 5.5 is supported as a target email server. Exchange 5.5 is not a supported email server.
If you are moving from one database server to another database server, such as SQL 2000 to SQL 2005, the AfterMail_Temp table and the Archive Manager database must use the same collation setting. The collation setting must contain Case Insensitive (CI) and Accent Sensitive (AS). Set the value to: SQL_Latin1_General_CP1_CI_AS
Archive Manager is not certified for use on clustered GroupWise host systems, i.e., systems that are set up for parallel processing, load balance, or fault tolerance.
When the GDC cannot find the Internet email address for a user by an eDirectory lookup, it outputs debug information into the GDC log. This information can also be seen when the GDC service is run in console mode. This is debug logging, and not indicative of a serious issue.
XML files generated by the ESM, Journal Data Loader, Search Exporter, and PST Importer in version 4.1.1 are not backward compatible with XML files generated in previous versions of Archive Manager, including version 4.1.
The following configuration setting can be added and edited in the Archive Manager Configuration Editor.
The Convert EV Stubs setting tells the ESM that mailboxes may contain Exchange Vault (EV) stubs that need to be converted to Archive Manager stubs. The feature is disabled (0 or False) by default. When this configuration setting is enabled (1 or True), the ESM performs an extra scan for EV stubs in each folder that has a strip policy. The scan for EV stubs ignores the strip policy’s age and size restrictions.
The following configuration settings can be added and edited in the Archive Manager Configuration Editor.
The Full Text Index Attachment Time Out configuration setting is in minutes, and the default setting is 15 minutes. It allows the Full Text Index to break an attempt to fetch an attachment from the attachment store and put it into its list for delayed retrieve.
The default IFilter Timeout Minutes setting is 5 minutes. When a timeout happens, the Full Text Index Service gathers the text extracted and uses that for indexing the attachment. The Full Text Index Service reports a warning and then continues to process.
The working directories for optimization are specified using the following configuration settings:
The default value is "Full Text Index Location" with \OptMessage appended to the end.
The default value is "Full Text Index Location" with \OptAttachment appended to the end.
The following commands can be used to optimize the Full Text Index Service. Regularly scheduled optimizations help maintain the health of your index. You can optimize indexes independently by including -skipmsg or -skipatt.
For example, to optimize the message index, enter the following at the command line:
To optimize the attachment index, enter the following at the command line:
The following configuration settings can be added and edited in the Archive Manager Configuration Editor.
GroupWise Directory Connector (GDC):
This section contains information about installing and operating this product outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe.
This release has the following known capabilities or limitations: Tested against French OS, SQL and Exchange.
The Archive Manager 4.1.1 distribution zip file contains the following:
Top-level Folder:
Documentation Folder:
PreReqs Folder:
Please see the Planning and Installation Guide (for either Exchange or GroupWise) for full instructions and application notes to install the current version of Archive Manager. The Planning and Installation Guide also provides valuable pre-installation planning information, process checklists, and pre- and post-installation process instructions that are necessary for a successful Archive Manager installation.
To upgrade from Archive Manager Version 4.1.0.366, run ArchiveSetup.exe.
The Upgrading chapter of the Planning and Installation Guide (for either Exchange or GroupWise) provides full instructions and application notes for upgrading to the current version of Archive Manager from an earlier version. The current version of Archive Manager supports upgrades only from version 4.1.0.366, and HotFixes which specify in their release notes that they are applicable to that specific build.
Important: Be sure to review your ADC configuration files after updating to this release, as some configuration items have changed. For more information and instructions, see the Quest_ArchiveManager_4.1.1_ADCConfig.pdf that accompanies this release. The user must manually create this file in the Archive Manager installation directory, according to the instructions in that PDF document. Any existing configuration files (sometimes referred to as ADC.xml or Domains.xml) must be updated for this release. The filename is not critical, but the placement of the file and the .xml extension are.
The Archive Manager Administration Guide INCORRECTLY states the following in the System Maintenance chapter:
To optimize the Full-Text Index:
This step is NOT optional. You MUST turn off both the FTI service and FTS service prior to optimization.
Run the following optimization command from the Windows console:
It is important that the only supported method of optimizing an Archive Manager index is by using the command above. Using other index optimization or analyzer tools that appear to run successfully against Archive Manager indexes may cause other index-related issues. If an incorrect approach for optimization is implemented, more extensive and time-consuming recovery steps will be required to attain a healthy and functional indexing state for the database.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA | |
| Web |
Please refer to our web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest
product or who have purchased a commercial version and have a valid maintenance
contract.
Quest Support provides around the clock coverage with SupportLink,
our web self-service. Visit SupportLink at http://support.quest.com/.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs,
online services, contact information, and policy and procedures.
The guide
is available at: http://support.quest.com/pdfs/Global Support Guide.pdf. This guide is available in English only.
© 2009 Quest Software, Inc.
ALL RIGHTS RESERVED.
This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchase or personal use without the written permission of Quest Software, Inc.
If you have any questions regarding your potential use of this material, contact:
| Quest
Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 Email: legal@quest.com |
Refer to our web site for regional and international office information.
Quest, Quest Software, and the Quest Software logo are trademarks and registered trademarks of Quest Software, Inc. Other trademarks and registered trademarks that may appear in this document are the property of their respective owners.
This product includes the copyrighted software of the following third-party suppliers:
Infragistics NetAdvantage 2005© Copyright 2004 Infragistics, Inc.
HTTP Compress© Copyright 2002-Present Ben Lowery (compress@blowery.org).
MAPI33.NET Library© Copyright AdEx Solutions, Inc. 2004.
EasyMail .Net Edition© 2002 Quiksoft Corporation
EasyByte RTF-2-HTML© 2007 EasyByte Software Limited
BalloonWindow© 2002-2003 Peter Rilling
Janus Controls© 2006 Janus Systems SA
Portions© 2004 Apache Software Foundation, under Apache License 2.0.
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.
The library is released under the GPL with the following exception:
Linking this library statically or dynamically with other modules is making a combined work based on this library. Thus, the terms and conditions of the GNU General Public License cover the whole combination.
As a special exception, the copyright holders of this library give you permission to link this library with independent modules to produce an executable, regardless of the license terms of these independent modules, and to copy and distribute the resulting executable under terms of your choice, provided that you also meet, for each linked independent module, the terms and conditions of the license of that module. An independent module is a module which is not derived from or based on this library. If you modify this library, you may extend this exception to your version of the library, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version.
Note: The exception is changed to reflect the latest GNU Classpath exception. Older versions of #ziplib did have another exception, but the new one is clearer and it doesn't break compatibility with the old one.
Bottom line: In plain English this means you can use this library in commercial closed-source applications.