Return
-
Title
Installation Issues and limitations are known to exist in MessageStats 6.1.1 -
Description
The following Installation issues and limitations are known to exist in MessageStats 6.1.1.
-
Resolution
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.
1. 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 either the 32-bit version of ASP.NET 1.1 or ASP.NET 2.0, see the Microsoft Knowledge base 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.
2. 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 MessageStats_Setup to continue the installation.(CR0179216)
3. 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.
4. The Distribution List Membership recurrence setting in previous versions of MessageStats is not migrated to this version. As a result, you must explicitly set the Distribution List Membership check box on the applicable organization property page.
5. 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.
6. When upgrading from Quest MessageStats 5.x to the current version of MessageStats, you must re-enter your SMTP gateway and From address in order for Report Subscriptions to function properly.
7. 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 1.1 or version 2.0.
8. MessageStats does not support case sensitivity on SQL Server. Some non-Latin database collations can cause SQL Server to observe case sensitivity.
9. Quest Software does not support installation of MessageStats for scenarios where the installation files have been encrypted.
10. Quest Software does not support the installation of MessageStats on domain controllers or Exchange servers.