Last revised May 26, 2005
This file contains system requirements and last-minute product information and updates to the documentation.
What's New
Upgrade Path
System Requirements
Known Issues
The most considerable improvements, additions and changes to the product implemented in this version include the following:
Upgrade to Reporting Console 7.2 Service Pack 2 (SP2) is supported for the Reporting Console versions 5.2, 6.0, 7.0, 7.1, 7.2 and 7.2 Service Pack 1.
For details, see the Upgrade Path section of the Quest Reporting Console 7.2 Quick Start Guide.
| Platform | Intel x86 |
| Operating system | Microsoft Windows 2000 Service Pack 3 or higher, -OR- Microsoft Windows XP Service Pack 1 or higher, -OR- Microsoft Windows Server 2003 |
| Memory | min. 128 Mbytes (256 Mbytes recommended) |
| Hard disk space | 40 Mbytes |
| Microsoft Internet Explorer | 5.5 or higher (Microsoft Task Scheduler and Windows Scripting Host 5.5 required) |
| Microsoft SQL Server | 7.0 or higher (remote or local) |
| Microsoft Data Access Components | 2.6 (or higher)* |
* In case you have Microsoft SQL Server 7.0 as the Master Server to which the Microsoft SQL 2000 Server instances must be linked, then MDAC 2.7 should be installed on the computer running SQL Server 7.0.
For list of required user rights and permissions refer to the Reporting Console 7.2 Quick Start Guide.
The following is required to process and preview OLAP cubes:
| Process | Microsoft SQL Server 7.0 OLAP Services SP2 or higher -OR- Microsoft SQL Server 2000 Analysis Services SP1 or higher |
| Process | Microsoft SQL Server 2000 Analysis Services Manager SP1 or higher (same version of Service Pack is required on server and client side in case SQL Server 2000 Analysis Services is used on server side) |
| Preview | Microsoft Office 2000 (or higher) Web components, Microsoft SQL Server 2000 Analysis Services Manager SP1 or higher |
To display the OLAP toolbar when working with the cubes in the Chart view, Microsoft Office XP Web Components are required.
To save reports in Microsoft Visio (.vsd) format, Microsoft Visio 2000 or higher is required.
The following is required for viewing reports saved in corresponding formats:
For report publication, Microsoft SharePoint Portal Server 2001 or 2003 is required.
| Microsoft Internet Information Services | 5.0 or later with VBScript and JScript support |
| Microsoft Data Access Components | 2.6 or later |
| Microsoft Internet Explorer | 5.0 or later with JScript support |
To view reports in certain formats, you must have the corresponding software installed (for example, Adobe Acrobat Reader for PDF files.)
To enable searching in reports saved in PDF and RTF formats, the following Indexing Service plug-ins should be installed:
| Microsoft SharePoint Portal Server | 2001 only |
| Microsoft Data Access Components |
2.6 or later Note: The Reporting Web Part cannot be installed if
you use MDAC 2.7 Service Pack 1 on the server side, unless you have
Microsoft SharePoint Portal Server 2001 Service Pack 2 installed. |
| Microsoft Internet Explorer | 5.0 or later with VBScript and JScript support |
| B000001 | The Report Library can be installed under a terminal session only if:
|
| B000002 | The program shortcut may not work after installation until you restart your computer. |
| B102540 |
You may receive the following error message:
"Cannot connect to the database. There is already an object named <...>" as a result of a scheduled reporting task if you configure more than one task to concurrently compile reports from a database that has never been used to build reports yet. |
| B000003 | If SQL Server is stopped while report compilation is in progress, the connection cannot be restored, even after SQL Server restarts. Use the Refresh Database Connections command to re-establish the connection. |
| B000004 | If the connection to the OLAP database is dropped when a cube is refreshed, Reporting Console waits until the connection is re-established. |
| B000005 | Rows containing NULL values are always excluded if an excluding filter is applied to the report column containing the NULL value. |
| B000006 | Reports saved in Microsoft Word (.doc) format can only be viewed in Microsoft Word in Print Layout or Web Layout view mode. |
| B000007 | Large reports may not be saved correctly in Microsoft Word (.doc) format. |
| B000008 | Consider using the Export pages to multiple files option when saving large reports to HTML format. Otherwise, reports may not be saved correctly. |
| B000009 | When saving a hyper-report to PDF file, use the Save each report into separate file option. Otherwise only the parent report will be saved, and the Save and print Hyper-reports recursively option will be ignored, even if it is selected. |
| B000010 | When running Reporting Console on Windows Server 2003, you may get an Internet Explorer Enhanced Security Configuration error. To correct this, add the "about:ReportingConsole.exe" site to Trusted sites and restart Reporting Console. |
| B000011 | When running Reporting Console on Windows Server 2003, you cannot publish reports to a Microsoft SharePoint Portal Server site unless it is added to Trusted sites. |
| B000012 | The scheduled task hangs if you attempt to schedule report publishing to a SharePoint Portal Server from a Windows Server 2003-based computer without sufficient permissions. |
| B000013 | The Reporting Console fails to update the Report Library automatically from the web site, if operating on Windows 2000 Datacenter Server. For details, see Microsoft Knowledge Base Article 823193. |
| B000014 | When appending large reports with large number of bookmarks to a PDF file using the Merge reports into one file option, the file may be damaged. |
| B000015 | When displaying a chart, values along the Y axis may differ from the ones you expect. Press Ctrl key and on the ChartFX toolbar click Reset - minimal and maximal scale units will be adjusted automatically. |
| B101417 | When you use the runas command to run Reporting Console, include the /profile parameter into the command line. |
| B000016 | Before installing the Web Portal on Microsoft IIS 6.0, you must allow ASP extensions (ISAPI extensions status is set to Allowed by setup). |
| B000017 | You may have to reload the Web Portal if the connection to the configuration database is broken. |
| B86341 | Reporting Web Portal cannot be used with Microsoft IIS running on a 64-bit platform. |
| B112851, B112506 |
A Reporting Web Portal installation cannot be repaired correctly with the Repair option in its setup. You may have to completely uninstall Reporting Web Portal and install it anew. When re-installing, specify the existing configuration database created by your old Reporting Web Portal installation in order to preserve its configuration. |
| B000020 |
You may get the following error when installing the Reporting Web Portal
with Microsoft Internet Information Services (IIS) 6.0: Could not create an application at the specified location. To fix the problem, complete setup, and create the application manually:
|
| B113661 |
If you specify an account that has an empty password for use by the
Indexing service, this will not affect the Reporting Web Portal
functionality but you won't be able to change that account or its
password. The following error will be displayed on the Indexing and
Notification Account tab of the Administration page: "Internal error. Enhanced error Information. Number: -2147024894. Description: " If this happens, you will have to remove Reporting Web Portal and install it again. In order to preserve Reporting Web Portal configuration settings, specify the same database to the setup when re-installing. |
| B113660 | When you upgrade an existing Reporting Web Portal installation to version 7.2 and do not use the Browse ("...") button on the Database step of the setup wizard, you will receive an error when you click Next on that step. To continue with the installation, click the Browse button and provide credentials for the account under which you want the setup to access the Reporting Web Portal database. When it is configured, click Next and proceed with the installation. |
| B113668 | When specifying a database for Reporting Web Portal, make sure it is a separate database dedicated to this product and not the one it will share with any other products of Quest Software. Otherwise the operation of other products sharing the database with Reporting Web Portal may be seriously affected. |
| B000019 | The Reporting Web Part setup may not work correctly due to certain Microsoft SharePoint Portal Server configuration settings. For details see MSDN Knowledge Base article 316231. |
The information in this publication is furnished for information use only, does not constitute a commitment from Quest Software Inc. of any features or functions discussed and is subject to change without notice. Quest Software, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this publication.
Copyright © 2005 Quest Software, Inc.