Issue:
When running MessageStats Reports on an IIS server on which SharePoint has been installed, the following error message appears: "Microsoft .Net Framework version 1.1 must be installed on the IIS server that hosts this application".
Workaround:
This error occurs because the Microsoft SharePoint Installer tightens security on the IIS server to a point that prevents MessageStats Reports from operating correctly.
The recommended solution is to create a second virtual IIS server on the computer that will host MessageStats Reports and install MessageStats Reports on a virtual server other than the server which 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: http://support.microsoft.com/default.aspx?scid=KB;EN-US;828810
Issue:
A COM or ADO error occurs when trying to export more than 65,536 rows to Excel.
Workaround:
This is a limit of the Excel file format. To work around this problem, select another file export format, such as CSV or TSV, or apply a filter to the report that reduces the total number of records in the report.
Issue:
An access denied error occurs when accessing the Subscription dialog box on Windows 2000 servers where SP4 and .NET Framework has been installed.
Workaround:
This happens because the IWAM account is not granted the rights to impersonate users for ASP.NET 1.1.
This is a known issue with Microsoft. Please refer to the following knowledge base article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;824308
Issue:
When running a long-running report on a Windows 2003 Server, a log in prompt will appear due to a time out. After entering the user credentials, the Internet Explorer 401.2 error page displays.
Workaround:
This problem occurs on servers with a heavy 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:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/71490aae-f444-443c-8b2a-520c2961408e.mspx
Issue:
The reports Notification functionality in Quest MessageStats 4.3 has been replaced with a new feature called Subscriptions. How can Notifications from 4.3 be migrated to Subscriptions in the 5.5 version?
Resolution:
To migrate the Notifications that were configured in the 4.3 version, complete the Report Notifications migration procedure, which is available in the Upgrading Quest MessageStats section of the Quick Start Guide.
For further information about Report Subscriptions, refer to the information located in the Reports Online help, or in Chapter 8 of the User Guide.
Issue:
Opening a comma-separated value (CSV) format exported report with Microsoft Excel results in invalid square brackets being added to the file name.
Workaround:
To work around this issue, use the Save As option to save the report before export it.
Issue:
By default, times are not displayed in Excel.
Workaround:
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.
Issue:
After upgrading from Quest MessageStats 4.3 to 5x, the number of size buckets on the Server Message Size Distribution report has been increased from 10 to 13 buckets. Data currently in the Greater than 2Mb bucket will be stored in the 2Mb to 5Mb bucket, and all other buckets will remain empty until new data is added to the database.
Issue:
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.
Issue:
If two identical mailbox display names appear on a report that contains a graph, the graph groups the mailboxes together.
