Report server

Using the Rational® Common Reporting Report Server.
Problem starting the reporting server
The error could be caused by port conflict. To determine if this is the case:
  1. Determine the port used by your [Server] profile:
    1. Open the AboutThisProfile.txt file in the [RCPR_installation_directory]/AppServer/profiles/RCPR/logs directory.
    2. Look for port numbers for HTTP transport port and HTTPS transport port.
    3. See the list of default ports for your WebSphere® Application Server instance (Default ports of).
  2. If there is a conflict in the ports:
    • Configure the other application to run on a different set of ports.
    • Change the ports assigned to your [ Server] profile.
To change the ports assigned to your [ Server] profile:
  1. Start the WAS console, log in, navigate to Servers > Application servers > [Server] > Ports, and click Details.
  2. Click the conflicting port (for example, WC_defaulthost or WC_defaulthost_secure), specify the new port number, click Apply, and save the settings to the master configuration.
  3. Navigate to Environment > Virtual Hosts, select default_host, and in the Properties section, click Host Aliases.
  4. Click the appropriate * links and change the conflicting ports. Click Apply and save the settings to the master configuration.
  5. Close the WAS console.
  6. Start Cognos® Configuration, navigate to Local Configuration > Environment, and change the conflicting ports to match the WAS ports assignment.
  7. Navigate to Local Configuration > Environment > Portal Services, and change the conflicting ports to match the WAS ports assignment.
  8. Click Save and close Cognos Configuration.
  9. Restart the Rational Common Reporting Report Server.
Problem accessing the IBM® Cognos 8 Web application
If you cannot access the IBM Cognos 8 Web application at http://localhost:9080/ RCPR, open http://localhost:9080/rqmreporting in your browser. If you get an error:
  1. Start Cognos Configuration and click Local Configuration > Data Access > Content Manager.
  2. Right-click Content Store and click Test.
  3. If the test is unsuccessful, click Details to read the detailed error message.
There could be several reasons why the Content Manager is not able to connect to the content store. The most common reason is that the content store configuration settings you specified in Cognos Configuration are not valid. Make sure the database name is correct, the port number is correct and the user credentials specified to access the database are valid.

For a list of error and warning messages that are specific to the content store, see Chapter 3 in the Cognos 8 Business Intelligence Troubleshooting Guide.

Manually uninstalling IBM WebSphere Application Server
See the instructions at the IBM WebSphere Application Server information center, Uninstalling manually section (http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.express.doc/info/exp/ae/tins_uninstman.html)
During deployment, access to entries is denied
Before the deployment, make sure that Reports Administrator role has read and write permissions to the Cognos namespace.
When logging on to an active directory security source, you are prompted to change passwords even if the password is valid or the password is successfully changed.
Ensure that the server name or named account for starting the Cognos service is set up in the Active Directory properties as an authority for delegated administration. Without these permissions, Cognos is unable to read all user properties from the Active Directory server. For more information, see the Active Directory documentation.
When logging in to the Rational Common Reporting Report Server with your user ID, the logon fails
If the Content Manager service runs under the local system account and runs on a computer that is not part of the Active Directory Server domain, qualify your user ID using the domain name. For example, domain\user ID.
A member of a newly-created group cannot see some of the entries. The user name does not appear in the banner area.
The namespace that the user belongs to must have traverse rights to the Query Users group. To add Traverse permission:
  1. Log on as a system administrator and start Cognos Administration.
  2. Click the Security tab and click Set Properties next to the namespace.
  3. Click the Permissions tab. If it is not already there, add the Query Users group to the namespace
  4. Select the Query Users checkbox for and ensure that Traverse permission is granted.
  5. Click Apply, and click OK.
  6. Test with a user.

Feedback