Workarounds: Setup problems in RRDI 2.0.3

The table of contents lists the known problems, workarounds, and limitations related to the Setup functionality in the RRDI 2.0.3 release.

Workarounds

Use the links below to learn more about the issues and workarounds in this release:


Problem Summary

When Internet Explorer version 7 is used for running the Setup Wizard, the registration page might not be laid out properly.

Problem

The input fields for RRDI Setup Server URL, User ID and Password might be at the far right of the web browser display area or invisible.

Workaround

There are 2 ways to work around this issue:

Complete the following steps:

  1. Solution 1: Use a newer version of Internet Explorer (version 8 or above), or another type of web browser supported by RRDI.
  2. Solution 2: Expand the display area of the web browser so those input fields are visible. Select the checkbox for confirming the RRDI Setup Server URL first. Then enter the information in those 4 text input fields, and click Initialize at the end.

Related Information

The following links point to related information:

Return to the top of the page


Problem Summary

When Microsoft SQL Server is used for configuring the content store database, the Setup wizard might create an invalid connection for the report server.

Problem

When a named database instance on Microsoft SQL Server is used as a content store database for the report server, the Setup wizard might create a 3-part property (including server hostname, instance name, and port number) in the content store configuration object for connecting to the report server. However, the 3-part property is an ill-formed connection object, which leads to a report server connection failure.

Workaround

Complete the following steps:

  1. Start IBM Cognos Configuration.
    • On Windows, click on Start > All Programs > IBM Rational Reporting > IBM Cognos > IBM Cognos Configuration.
    • On Linux and AIX, run [RRDI-Install-Directory]/cognos/[bin64-or-bin]/cogconfig.bat
  2. In the IBM Cognos Configuration window:
    1. In the Explorer view on the left-hand-side, go to Local Configuration > Data Access > Content Manager > Content Store.
    2. In the Database – Resource Properties view on the right side, select the Database server with port numner of instance name property, and change its value to the database server name with either port number or instance name, but not both.
    3. Select File > Save.
  3. Stop and restart the report server to reestablish the report server connection.

Related Information

The following links point to related information:

Return to the top of the page


Problem Summary

During the RRDI server rename, the Configure Rational Reporting User Authentication step might fail if an existing WebSphere Application Server profile is reused.

Problem

During the RRDI server rename process, you must complete the steps in the RRDI Setup wizard after the server name is changed. If you choose to reuse an existing WebSphere Application Server profile in the Configure Application Server Profile step, the subsequent Configure Rational Reporting User Authentication step might fail. (Note: If you created a new WebSphere Application Server profile, the subsequent Configure Rational Reporting User Authentication step would succeed.)

Workaround

Complete the following steps:

  1. During the Configure Rational Reporting User Authentication step, ignore the error message in the “Starting the Rational Reporting server…” sub step and click Next.
  2. Finish all remaining setup steps (including the Build and Deploy Reporting Components step) in the scenario.
  3. Rerun the Configure Rational Reporting User Authentication step. The configuration will complete successfully.

Related Information

The following links point to related information:

Return to the top of the page


Problem Summary

When a 32-bit Oracle database client is used on AIX for RRDI server configuration, the Copy operation might fail in the Configure Database Management System step.

Problem

In the Configure Database Management System step of the Setup wizard, the Copy operation performs validation checks on the database client installation. On an AIX system, this operation might fail with the CRRRA0209E error even if a 32-bit Oracle client is installed on the system.

Workaround

Complete the following steps:

  1. Make a backup copy of the [Oracle-Client-Install-Location]/inventory/ContentsXML/oraclehomeproperties.xml file.
  2. In the original copy of the oraclehomeproperties.xml file, replace the “<ARU_ID>212</ARU_ID>” entry by “<ARU_ID>46</ARU_ID>”.
  3. Run the Copy operation on the Configure Database Management System step so the proper client library would be copied. Click the Next buton on the page to continue the setup process.
  4. Restore the [Oracle-Client-Install-Location]/inventory/ContentsXML/oraclehomeproperties.xml file from the backup copy.

Related Information

The following links point to related information:

Return to the top of the page


Feedback
Was this information helpful? Yes No 0 people rated this as helpful.