List of known issues in InTrust 9.5 - Legacy Reporting. (21866)

The following is a list of issues known to exist with Legacy Reporting at the time of Quest release:InTrust 9.5.

CR0111870
Only the printers installed on the computer where InTrust Manager is installed can be selected for printing out results of a reporting job.

CR0112378
The following objects are not affected by upgrade of InTrust: Report Libraries, Report Storages, Reporting Tasks.

CR0111924
You may receive the following error message:
"Cannot connect to the database. There is already an object named <...>"

as a result of a reporting job if more than one job are running concurrently to compile reports from a database that has never been used to build reports yet.

CR0111928
In reporting jobs configured to process more than one OLAP cube, only the first cube is processed successfully. Processing of the second and the following cubes in a job fails with the following error: "The server threw an exception." This problem affects reporting jobs processed by InTrust Servers installed on Windows 2000 SP4 machines only.

CR0153928
The 'Weekly Alert Reporting' job in the 'Weekly Alert Database Reporting and Cleanup' predefined task does not have the target database specified for the 'InTrust Configuration 9.5' Schema. To use this reporting task, you will have to manually reconfigure it to specify the InTrust configuration database for this Schema.

CR0149014
If the SQL Server login in a reporting job uses a default language other than "English" and the Date Range filter in any of the job's reports is set to Interval, the job produces an error such as the following:
The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value
To avoid the error, set the default language for the job's SQL Server login to "English".

CR0171107
When a reporting job is configured to send a notification to a Notification Group, it may fail to do so with the following message logged to the session results:
Warning: Couldn't find the specified Operator(s) in the configuration database.

The workaround is to specify individual Operators and not Notification Groups in the properties of a reporting job. You may use MS Exchange distribution lists to create InTrust Operator e-mail accounts that will send notifications to multiple recipients.

CR0187570
The following legacy reports for Sun Solaris will not work for event data collected with InTrust 9.5 and higher versions:
Failed logins
Successful logins
Failed logins of privileged users
Successful logins of privileged users
Solaris syslog events

CR0111923
You may get the following error while clicking Configure on a legacy Reporting job:
The 'jobname' is opened by another user or access is denied.

Make sure the job you want to configure is not running at the moment, then click Configure again..

CR0111887
Legacy Reporting jobs do not start when the system disk is full on the computer where the InTrust Server is installed and no event is logged to the InTrust event log.
When trying to open the job properties, the following error is displayed:
Cannot display job properties because one or more of the required user interface components are missing.