Cognos ReportNetTM Installation and Configuration Guide
Cognos ReportNetTM Installation and Configuration Guide
Cognos ReportNetTM Installation and Configuration Guide
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Appendix B: Troubleshooting<br />
Steps to Change the Font that the <strong>Configuration</strong> Tool Uses in the User Interface<br />
1. Start <strong>Cognos</strong> <strong>Configuration</strong>.<br />
2. From the View menu, click Font.<br />
The text of the Font comm<strong>and</strong> <strong>and</strong> in the Font dialog box is in English.<br />
Tip: The View menu is the second menu from the left. Font is the second comm<strong>and</strong> in the<br />
View menu.<br />
3. In the Name box, click the font that you want to apply to use.<br />
Tip: The Name box is the first box from the left of the dialog box.<br />
4. In the Style box, click the format that you want to use.<br />
Tip: The Style box is the second box from the left of the dialog box.<br />
5. In the Size box, click the font size you want to use.<br />
6. Click OK.<br />
DB2 Returns SQL1224N Error When Connecting from AIX<br />
If your content store is a DB2 database <strong>and</strong> you receive an SQL1224N error on AIX, check the<br />
db2diag.log file for additional information about the error. If the error includes reason code 18,<br />
you may need to change the DB2 configuration to accept more connections. For more<br />
information, see the IBM DB2 support pages for the error SQL1224N.<br />
<strong>Cognos</strong> BI Server Not Available When Opening the Portal<br />
After you configure ReportNet components <strong>and</strong> start the ReportNet service, when you open the<br />
ReportNet Web portal, the following error message may appear:<br />
The <strong>Cognos</strong> BI server is not available.<br />
SoapSocketException: Connection refused<br />
Check the ReportNet server log file for more information. By default, the crnserver.log file is<br />
located in the crn_location/logs directory. If you configured another destination for log<br />
messages, check the appropriate file or database.<br />
Content Manager may not be able to connect to the content store if the content store is not<br />
configured properly. This may occur if<br />
• the content store uses an unsupported character encoding<br />
• the content store uses a database collation sequence that is case-sensitive<br />
• the configuration settings you specified in <strong>Cognos</strong> <strong>Configuration</strong> are not valid<br />
Unsupported Character Encoding<br />
If the following messages appear in the log file, the database you created for the content store<br />
does not use a supported character encoding:<br />
For Oracle:<br />
CM-CFG-5063 A Content Manager configuration error was detected while connecting to the<br />
content store.<br />
CM-SYS-5121 Content Manager cannot start because the database character set is not<br />
supported.<br />
CM-SYS-5126 The content store database server uses the character set US7ASCII.<br />
CM-SYS-5125 The content store database client uses the character set US7ASCII.<br />
For DB2 UDB:<br />
CM-CFG-5063 A Content Manager configuration error was detected while connecting to the<br />
content store.<br />
CM-SYS-5121 Content Manager cannot start because the database character set is not<br />
supported.<br />
CM-SYS-5124 The content store database server uses the code page 1252.<br />
110 <strong>Cognos</strong> ReportNet TM
Change language