Cognos ReportNetTM Installation and Configuration Guide

Appendix B: Troubleshooting
Unable to Start Cognos Configuration Because the
Configuration Data is Locked by Another Instance of
Cognos Configuration
You may get an error message that the configuration data is locked by another instance of
Cognos Configuration although there is no other instance running.
When you start Cognos Configuration, it checks to see if the crnstartup.lock file exists in
crn_location/configuration. The file may exist if a previous instance did not shut down properly or
if another instance of Cognos Configuration is running.
If another instance of Cognos Configuration is running, you should exit that instance. Otherwise,
any changes you make to the local configuration may result in errors. If no other instance of
Cognos Configuration is running, delete the crnstartup.lock file in crn_location/configuration.
Unable to Save Your Configuration
You may be unable to save your configuration because you are missing a resource. For
example, you delete a resource such as the Cognos namespace, a cryptographic provider, or
the content store. You can replace the default database type for the content store with Oracle or
DB2. You cannot replace the Cognos namespace.
Steps to Recreate the Cognos Namespace
1. Start Cognos Configuration.
2. In the Explorer window, under Security, right-click Authentication and then click New
resource, Namespace.
3. In the Name box, type a name for the resource.
4. In the Type box, click Cognos, and then click OK.
The Cognos namespace appears in the Explorer window.
5. From the File menu, click Save.
Error Trying to Encrypt Information When Saving Your
Configuration
When you save your configuration using the configuration tool, you may see an error message
that the cryptographic information cannot be encrypted. An error occurred when requesting a
certificate from the Certificate Authority.
Before you can encrypt your configuration settings, the computer where Content Manager is
installed must be configured and running. On UNIX, ensure that you copied the appropriate JAR
files to the installation location of your Java Runtime Environment.
Fonts Do Not Appear Properly in the Configuration Tool
User Interface
You may notice that some characters in the user interface of the configuration tool do not appear
properly. Because the configuration tool is a Java application, it needs a properly configured
Java environment to find the fonts required for the user interface.
To resolve this problem, see your Java documentation, or change the font in the user interface.
Installation and Configuration Guide 109