Release Notes

Quest^® MessageStats is a Windows-based data collection and reporting application that facilitates the analysis of messaging statistics for a number of messaging environments. The core MessageStats application focuses on Microsoft Exchange messaging systems. Through additional report packs, MessageStats can gather and report on parts of other messaging systems such as BlackBerry^® Enterprise Servers, SendMail and PostFix servers, Quest Archive Manager servers, Microsoft OWA (Outlook Web Access), Microsoft Office Communications Server, Lotus Notes servers, and Windows Mobile^® servers.

MessageStats provides comprehensive information regarding critical metrics for resource usage, capacity monitoring and planning, and migration preparedness. It also provides detailed information for monitoring mailbox content and mail flow, allowing you to track capacity and improper usage.

To aid information gathering from wide-ranging messaging systems, MessageStats provides a dynamic task-based gathering engine that allows the collection of information to be intelligently scheduled, minimizing the impact to the messaging system and corporate network. In addition, MessageStats offers the ability to horizontally scale out gathering components so that MessageStats can gather efficiently from remote messaging systems.

With the extensive information that MessageStats gathers, MessageStats provides an extremely flexible web-based reporting engine that allows all interested individuals to view messaging information and to package the information in many different ways. All reports are available by accessing the web site directly, by signing up for automated subscriptions that can be sent to any email address, or through export to a number of supported formats.

New in This Release

This section describes the new features that can be found in Quest MessageStats release 6.5.0:

Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release of MessageStats.

Feature	Resolved Issue	Defect ID
Installer
	Must allow the remote installation or remote upgrade of the MessageStats database component.	TF#39556
	Upgrades from previous version of MessageStats 6.x.x should be supported.	TF#39558
	UDL file creation: Instead of storing the connection string to the database directly in the registry, a UDL file should be created that can be configured by the MessageStats Administrator.	TF#39557
Console	Provide more visible reasons to user for DCOM service account failures.	TF#19260
	When you disconnect from an organization, you should get an option to delete all the tasks for the organization.	TF#33145 CR#0160635
	Using Browse or Cancel clears the previously entered server name on the "Connect to Exchange Organization" dialog.	TF#33277 CR#0162944
	There should be a Back tab on the second page of the Connect to Exchange Organization Wizard.	TF#34847 CR#0219524
	The regions listed under the Regions node and the servers listed under the Task Execution Servers node cannot be sorted.	TF#34840 CR#0219522
	The Connection Server property page allows an empty server name.	TF#34726 CR#0219711
	Message Subject Audit - Entering a blank entry results in an MMC error.	TF#34159 CR#0202236
	Renaming the organization does not affect the task sources listing.	TF#35038 CR#0227436
Gathering	Messages submitted directly through SMTP are counted as external messages in reports.	TF#30016 CR#0052540
	Running multiple default tasks (server-level) at the same time can result in unexpected failures of tasks.	CR#0180136 TF#33542
	The Exchange Mailboxes gathering fails with a log file warning that the object does not have the minimum required properties.	CR#0161751 TF#33225
	The Exchange 2007 tracking log expansion is not detecting all the eligible log files.	CR#0208519 TF#34428
	Add a task log entry for a task cancellation.	CR#0203135 TF#34193
	Provide a better warning in the tracking log expansion if no tracking logs are found.	CR#0227322 TF#35035
	The task activity end time is not always filled with a value for cancelled tasks.	TF#38018
	Provide some additional default-type task templates.	TF#38412
	Service: New service log file is not created for each day, resulting in a single large log file that contains entries for multiple days.	TF#38415
	Large gatherings can cause QMS.EXE to use up all the processing capacity.	TF#40609
	Exchange 2007 tracking log reports are showing "No records found" for the Most Recent filter.	TF#41028
Reports	Table select - User should be able to select a portion of a table or graph in a web report, and then export only that data.	TF#18754
	The error message for "Report not found" is cryptic and unhelpful.	TF#19092
	Allow users to send a report that they are currently viewing to an email address.	CR#0228248 TF#35056
	Pagination is not working properly in some scenarios.	CR#0228247 TF#35055
	Graphs must be centered on multiple reports.	CR#0227903 TF#35047
	Remove the field notes from report subscriptions and exports.	TF#35124
	Allow the user to select and send a graph by email as .png image or as data.	TF#35122
	Exchange 2007 delivery time reports show large negative numbers.	CR#0228722 TF#35066
	MessageStats Reports dates show as garbage when there are no browser regional settings.	CR#0228467 TF#35061
	The following report part cannot be configured: "Time Comparison of Organization Messages Distribution Summary Graphs".	TF#39682
	Large organizations get an arithmetic overflow error on the Executive Summaries \| Service Delivery report.	TF#39666
	Add a new Mailbox Growth report.	TF#40911
Documentation	Update the documentation to reflect .Net 2.0 minimum requirement instead of .Net 1.1.	CR#0228405 TF#19217
Documentation	Update the documentation to explain that you must manually share Exchange 2007 tracking log paths and that MessageStats gathers only from Hub and Edge Transport servers.	CR#0228941 TF#35068

Known Issues

The following is a list of issues known to exist at the time of MessageStats release.

Feature	Known Issue	Defect ID
Installation Issues	When MessageStats Reports is installed on a Windows Server 2008 machine, and if you view the MessageStats Reports using a browser on the same machine as the IIS server, you can receive the following error message: Unable to connect to the database. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. In certain circumstances, you can also see other error messages that indicate permission was denied while trying to access resources on the web server. To correct this issue, you must turn off Internet Explorer Protected Mode for the local MessageStats Reports web site. Add http://machinename to the Trusted Sites security zone Ensure that the Enable Protected Mode checkbox is unchecked (the default setting). If you use other URLs such as http://localhost/MessageStatsReports to access the site, you must also add http://localhost as a trusted site. This configuration change is required only if you view the MessageStats Reports web site on the same computer that hosts MessageStats Reports.
	If you have customized the qmsReports.udl file to support SQL Server authentication, you must make changes to run reports on Windows Server 2008. On Windows Server 2008, saving changes to the qmsReports.udl file has no effect unless you are running with elevated permissions. This occurs because changes to the qmsReports.udl are saved in a per-user area of the file system instead of the per-computer location used by MessageStats Reports. To avoid this issue, you must edit and save the file with elevated UAC (User Account Control) rights. From the Start menu, right-click CMD.EXE, and select Run as Administrator. At the command prompt, enter: Start “c:\program files\Quest Software\MessageStats\qmsReports.udl” Note: If MessageStats is not installed in the default path, modify the command to include the path where it is installed.
	Customers that are using Exchange 2007, but who do not have Exchange System Manager (ESM) for Exchange 2000 or Exchange 2003, should use the Microsoft MAPI+CDO software download (http://www.microsoft.com/downloads/details.aspx?familyid=E17E7F31-079A-43A9-BFF2-0A110307611E&displaylang=en) as their MAPI subsystem provider. This software must be installed wherever ESM would have been installed.
	MessageStats Reports can be installed on 64-bit operating systems, but IIS must be reconfigured for MessageStats Reports to operate correctly. On 64-bit operating systems, you must reconfigure IIS to run in 32-bit mode. For instructions on how to do configure IIS to run the 32-bit version of ASP.NET 2.0, see the Microsoft Knowledgebase Article 894435 (http://support.microsoft.com/?id=894435). This procedure can cause compatibility issues with other web applications on the same IIS Web Server so it is recommended that MessageStats Reports be run only on servers without other web applications.
	During installation, if the installation and service accounts are different, the MessageStats installer requests a reboot. This reboot is required to ensure that the Service Account has the appropriate rights to run the service. Note: On x64 implementations, a reboot is requested and the MessageStats installer does not resume the installation. In this case, you must rerun the Setup.exe file to continue the installation.	CR#0179216
	SQL Server Agent must be running to use the Database Management tasks: database reindexing, defragmenting, or database aging. Note: SQL Express (the personal edition of SQL 2005) does not include the SQL Server Agent. Database Maintenance tasks are not available when running on SQL Express; use either MSDE or full SQL Server.
	There is a known issue in which the MessageStats installer does not verify the server name that is entered for the scheduler service. As a result, an incorrect server name causes an error to occur later in the installation process. To correct this problem, uninstall MessageStats and re-install with the correct name for the scheduler service.
	If you install MessageStats on Windows Server 2003, ASP (Active Server Pages) support is turned off by default. You must enable ASP support in order for MessageStats to install properly. Note: You must have IIS installed and ASP support enabled before installing the .NET Framework version 2.0.
	MessageStats does not support case sensitivity on SQL Server. Some non-Latin database collations can cause SQL Server to observe case sensitivity.
	Quest Software does not support installation of MessageStats for scenarios where the installation files have been encrypted.
	Quest Software does not support the installation of MessageStats on domain controllers or on Exchange servers.
	If you are installing MessageStats Reports on Windows Server 2008, you must reboot the server after the installation is complete.
Gathering Issues	If you run an information store gathering, a mailbox gathering, or a public folder gathering against an Exchange organization, an administrative group, or a routing group that contains one or more Exchange 2007 servers that do not have the mailbox role installed, the gathering for those Exchange 2007 servers will fail. The gathering fails because there is no information store from which to gather data from on those Exchange 2007 servers.	CR#0224526
	Inherited mailbox permissions are retrieved only if ESM is used as the MAPI subsystem provider. If the Microsoft MAPI+CDO download or Outlook 2007 is used, only non-inherited mailbox permissions can be retrieved.
	There is a known issue with the Connectors gathering task when run it is against organizations that contain Exchange 2007 servers. If these organizations contain connectors of the type ‘msExchRoutingSMTPConnector’ that do not have a legacyExchangeDN attribute set, a warning is generated. You can safely ignore this warning.	CR#0201951
	There is a known issue with the MOM gathering if the gathering is run twice for the same day. If the MOM gathering fails, do not re-run the gathering. For information, go to the Quest web site and see the SupportLink solution 18734.	CR#0178106
	MAPI-based gatherings (mailbox, public folder, and content and attachment gatherings) can unexpectedly fail if run on a machine that has both Outlook and Exchange System Manager (ESM) installed. Running Outlook and Exchange System Manager on the same machine is not supported by Quest Software due to conflicts in the underlying MAPI components. Please refer to the following Microsoft Knowledgebase article 266418: http://support.microsoft.com/default.aspx?scid=kb;en-us;q266418.
	You may receive an error using the MessageStats Database Management tools from the Console when the database is on a remote server and you are using SQL 2005. To resolve the issue, you must install SQL Server Management Studio or SQL Server Client Tools (that ship with SQL 2005) on the MessageStats Console.
	For all Public Folder gatherings to be successful from Exchange 2003 servers, you must be running ESM 2003 SP 2 on the Task Execution Server.
	MessageStats requires all public folders to have the Folder Visible permission. MessageStats may generate warnings during public folder gatherings while attempting to open public folders and child folders of public folders without this permission. For more information, see the Microsoft knowledge base article 203646.
	MessageStats does not support directory objects containing both a forward slash ( / ) and an equals sign ( = ) in their common name, regardless of their position or order in the name. ADSI cannot bind to objects containing both these characters in their common name, which prevents MessageStats from gathering all of the required information from the object.
	There is a known issue with the Mailbox gathering for Exchange servers with multiple Mailbox Stores. If not all the Mailbox Stores are available on an Exchange server, the gathering task is completed for the available stores and the status for the task is Successful. However, the information for the mailboxes in the unavailable stores is not added to the database.
	When connecting to a multi-domain organization that contains NT domains with Exchange 5.5 servers, an Exchange 2000/2003 server should be used as the Connect To server for MessageStats to properly gather data.
Reporting Issues	By default, Internet Explorer, when running on 64-bit versions of Windows Server 2008, is configured to run in Enhanced Security mode. This prevents you from viewing MessageStats Reports. To allow viewing of MessageStats Reports from a Windows Server 2008 computer, click the Enable IE ESC link on the main panel of Server Manager.
	MessageStats Reports subscriptions that contain reports with the "Local Time" enabled will use the daylight savings time settings that were in effect at the time the subscription was created or saved. When the daylight savings time change goes into effect in the US in 2007, the data in these reports can be off by one hour during the three week period affected by the change. To correct the problem, load the subscription, view the filter settings panel for each affected report, and resave the subscription. Before you perform this operation, you must apply the Windows time zone update patch (KB933360) on the machine on which Internet Explorer is running. Interactive reports and other features of MessageStats Reports are not affected by this problem.
	MessageStats Reports cannot run on IIS servers on which the Microsoft Media Server has been installed in the root web directory. An error message appears stating, "Microsoft .Net Framework version 2.0 must be installed on the IIS server that hosts this application." This error occurs because the Microsoft Media Server applies configuration options that affect all applications running on the server. The recommended solution is to create a second virtual IIS server on the machine that is to host MessageStats Reports, and install MessageStats Reports on the virtual server that is not hosting Windows Media Server.
	If you are producing reports containing Chinese, Japanese, or Korean characters, you must install the East Asian language pack on the computer hosting MessageStats Reports. You must also install the language pack on any computer to be used to view these reports.
	If you attempt to run MessageStats Reports on an IIS server on which SharePoint has been installed, an error message appears, stating, "Microsoft .Net Framework version 2.0 must be installed on the IIS server that hosts this application." This error occurs because the Microsoft SharePoint installer implements tighter security on the IIS server which prevents MessageStats Reports from operating correctly. The recommended solution is to create a second virtual IIS server on the machine that hosts MessageStats Reports, and install MessageStats Reports on a virtual server other than the server that is hosting SharePoint. MessageStats Reports can also be installed on the same virtual server by following the instructions given in Microsoft Knowledge Base Article 828810: How to enable an ASP.Net application to run on a SharePoint virtual server.
	If you are accessing a long-running report on a Windows 2003 Server, you may be prompted to log in due to a time-out. After you enter the user credentials, the Internet Explorer 401.2 error page displays. This problem occurs on servers with a heavy server load. The workaround is to set the IIS ConnectionTimeout parameter to a longer time such as 15 minutes. For more information about this parameter, see the Microsoft article on ConnectionTimeout.
	By default, times are not displayed in Excel. When exporting reports that contain date/time fields to Microsoft Excel, load the exported file into Excel, select the column containing date/time information, and apply an appropriate Excel format string using the Format \| Cells menu command.
	MessageStats may differ by 1 KB on values reported in either Microsoft Exchange Administrator or Microsoft Exchange System Manager due to the nature of rounding implemented by Microsoft.
	If two identical mailbox display names appear on a report that contains a graph, the graph groups the mailboxes together.

System Requirements

Before installing MessageStats, ensure your system meets the following minimum hardware and software requirements:

Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers 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, Japan.

The release is localized in the following languages: Japanese, French, German, Korean.

Getting Started

Contents of the Release Package

Installation Instructions

Refer to the MessageStats Quick Start Guide for installation instructions and information about required permissions.

For More Information

Contacting Quest Software:

Contacting Quest Support:

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.

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.

This document contains proprietary information protected by copyright. The software described in this document 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 purchaser’s personal use without the written permission of Quest Software, Inc.

If you have any questions regarding your potential use of this material, contact:

Trademarks

Quest, Quest Software, MessageStats, and the Quest Software logo are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

Disclaimer

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.

Minimum Hardware Requirements
Processor	Pentium 4, running at a minimum speed of 2.4 GHz
Memory	2 GB
Hard Disk Space	250 MB of free disk space for the application. This space should exist on a local disk drive rather than a network drive. The space requirement varies depending on the size of the database. Note: If you are migrating an existing database, the free disk space requirement is larger than 250 MB. The space requirement varies, depending on the size of the database. If you are upgrading an existing database, the free disk space must be larger than for a new database. Space requirements also depend on the amount of information you write to the database and the length of time you retain the records. Note: For help in assessing the amount of space sufficient for your implementation, contact Quest Support to acquire a database size estimation tool. To tune your MessageStats database and maximize performance, contact Quest Software Professional Services. You can contact Professional Services through your Quest sales representative.
Other	Sufficient space for the temporary tracking log cache, application logs, and task documents. The size of this cache depends on the number of servers, the number of tracking logs on each server, and the size of each tracking log. The space should exist on a local disk drive rather than a network drive. Monitor supporting a resolution of 1024x768 pixels. Pointing device. You must have a pointing device installed on your computer to access all MessageStats features.
Minimum Software Requirements
Operating System	Windows Server 2003 SP 2, Windows Server 2003 R2, or Windows Server 2008. Note: Windows Server 2008 is supported for the MessageStats Database and MessageStats Reports installations only. You cannot install the MessageStats Console on Windows Server 2008. Note: MessageStats only supports installation on Microsoft Windows XP Professional SP 2 and Microsoft Vista SP1 in evaluation scenarios. If you intend to use Windows XP SP 2, you must open port 80 so that Quest MessageStats can provide access to subscription links. Additionally, Microsoft Vista is the same as Windows Server 2008 in that only the installation of Reports and Database are currently supported. Note: If you are producing reports that contain Chinese, Japanese, or Korean characters, you must install the East Asian language pack on the computer that hosts MessageStats Reports. You must also install the language pack on any computer to be used to view these reports.
MAPI.DLL	Exchange Systems Manager (ESM) 2000 SP 3 or ESM 2003 SP 2 is required. Customers that are using Exchange 2007, but who do not have ESM for Exchange 2000 or Exchange 2003, should use the Microsoft MAPI+CDO software download (http://www.microsoft.com/downloads/details.aspx?familyid=E17E7F31-079A-43A9-BFF2-0A110307611E&displaylang=en) as their MAPI subsystem provider. This software must be installed wherever ESM would have been installed. Note: For non-Exchange environments, you must have Microsoft Outlook installed. For Exchange environments, it is recommended that you have ESM installed. Microsoft does not support ESM and Outlook installed on the same computer. If you have Outlook installed, it is recommended that you uninstall Outlook before you install ESM. If you are running MessageStats 5.x, you may need to stop of the MessageStats Scheduler Service before you uninstall Outlook and install ESM. For more information, contact Quest Support.
MessageStats Reports Server	IIS 5.0 or IIS 6.0 For Windows Server 2008, IIS 7.0 is required. There are also certain IIS role services that must be enabled. See the section titled "IIS Role Services on Windows Server 2008" in the MessageStats Quick Start Guide for more information.
MessageStats Database Server	Microsoft SQL Server 2000 SP4 or SQL Server 2005. Note: MessageStats supports SQL Server Express in test or evaluation scenarios.
Browser	Internet Explorer 6.0 or Internet Explorer 7.0 Note: For the online help and F1 Help to function, you must have at least Internet Explorer 6.0 SP 1.
Additional Software	Microsoft .NET Framework version 2.0 Note: For more information about resolving common ASP.NET configuration problems, see Appendix A: Microsoft .NET Configuration Issues in the MessageStats Quick Start Guide. MDAC (Microsoft Data Access Components) 2.7 SP 2 Refresh. For a distributed install, MDAC must be installed on the IIS Server and console; however, it is not required for the database components.
Presence in reports	To see presence status information in mailbox-specific reports, the person viewing the reports must have Office Communicator 2005 or Office Communicator 2007 installed, configured, and running. Also Microsoft Office Outlook 2003 or the Microsoft Office Outlook 2007 must be installed. The Exchange organization must have Microsoft Live Communication Server 2005 or Microsoft Office Communication Server 2007 configured and running.

Email	info@quest.com
Mail	Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA
Web	http://www.quest.com