Purchase your Section 508 Compliance Support guide now!

Purchase your Section 508 Compliance Support guide now!

CRX-API-0005

Problem(Abstract)
We have a master detail report comparing data submissions for a particular table. Where there is a difference between any particular column (eg a customer name change) we're trying to use a condition (query1.description <> query2.description) to highlight it. We get an error when we run the report.

Symptom
CRX-API-0005 An error on or around the position '0'. The variable named '' is invalid.

Cause
A report expressions (in this case, the conditional expression) can only look up data items that are in its direct context. That means that the place where it is evaluating the condition has to be within a
container that is associated to a query, and we can only look up values from the "nearest" container. So imagine that you're the expression, and you're sitting in a box. That box may be inside of another box, but you don't really know because all you can see is the box you're in.

Resolving the problem
Make the data we want to evaluate part of the second query. Take a simple example from our Go Sales and Retailers of a nested list, in which the outer list shows Product Line and quantity, and the inner
list shows order methods and quantity. If we want to put a condition on the Order Method based on a comparison between the order method quantity and the product line quantity, we'd need to add a second data item to the order method query that calculates the total for each product line. Now both values are in one query, and we can evaluate them in one expression.

DPR-ERR-2002

Problem(Abstract)
Testing all datasource connections fail with an error, even though connection parameters are correct.

Symptom
DPR-ERR-2002 Unable to execute the request because there was no process available within the configured time limit

Cause
This error can occur if the Cognos 8 encryption folders are not longer valid.

Resolving the problem
Regenerate the encryption information by following these steps:
1. Stop the Cognos 8 service.
2. On the Cognos 8 server(s), navigate to the /configuration directory and backup the csk, signkeypair, and encryptkeypair directories. Also, rename or delete up the cogstartup.xml file in same directory.
3. Launch Cognos Configuration.
4. From the File menu select Export as... and save the settings as crnstartup.xml.backup (or similar) to the configuration folder. Note: This will create an unencrypted version of your Cognos Configuration settings exposing any passwords in the configuration.
5. Close Cognos Configuration
6. Delete the csk, signkeypair, encryptkeypair directories.
7. Rename the exported configuration file to cogstartup.xml.
8. Launch Cognos Configuration.
9. From the File menu, select Save. This will recreate the csk, encryptkeypair and signkeypair directories and re-encrypt all the configuration information.
10. Start the Cognos 8 service.

DPR-ERR-2079

* Support & downloads

DPR-ERR-2079 Firewall Security Rejection. Your request was rejected by the security firewall.
Technote (troubleshooting)

Problem(Abstract)
Error occurs when running a report.

Error Message:

Cognos 8 An error has occurred.

DPR-ERR-2079 Firewall Security Rejection. Your request was rejected by the security firewall.

Please try again or contact your administrator.


Environment
Distributed (2-server) environment, with Cognos Application Firewall (CAF) enabled on both servers.

Resolving the problem
Within Cognos Configuration, set all of the URI settings to fully qualified URI's:

Example of Gateway URI: http://machine-name.domain-name.com:80/cognos8/cgi-bin/cognos.cgi
Steps:Open Cognos Configuration and edit all of the URI settings so that they are fully qualified in all Cognos environments.

CMM-SYS-5999 error

* Support & downloads

Clicking Metric Studio link gives CMM-SYS-5999 error
Technote (troubleshooting)

Problem(Abstract)
Clicking on the Metric Studio link in Cognos Connection returns CMM-SYS-5999 error.

Symptom
CMM-SYS-5999 The Metrics Management Service encountered an internal error.

An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID:2007-04-13-10:54:01.043-#15

From the cogserver.log file:

'java.lang.StackOverflowError'
WHILE Executing page 'null', from pageMap 'Unknown, since pid 'null' doesn't exist in any of the page maps', via request:

QUERY_STRING='errURL=%2fc8mr2%2fcgi-bin%2fcognos.cgi%3fb_action%3dxts.run%26m%3d portal%2fwelcome%2fwelcome.xts&so.cognosNamespaceId=xOg__&so.directoryId=iCD4C77 FE7F6F42859251DE3632D98B9F&so.adminId=i6F92C402655F42F685F4CDCD211A6F95&ui.gatew ay=%2fc8mr2%2fcg i-bin%2fcognos.cgi&so.cmRootId=iEFF596A10F784107B687615044260EC7&encoding=UTF-8& m=portal%2flaunch.xts&so.configurationId=i06C9B1C033CC4BB88AAC88861FA49C72&b_act ion=mms.run&ui.tool=MetricStudio&so.contentId=i18AAE103ABFB42FB967073771E8B2718& so.myFoldersId=iE8E8AB490F9F4ECEBFDE6B1B966F19DA&ui.backURL=%2fc8mr2%2fcgi-bin%2 fcognos.cgi%3fb_action%3dxts.run%26m%3dportal%2fwelcome%2fwelcome.xts&ui.action= new'
Parameters = {
errURL=['/c8mr2/cgi-bin/cognos.cgi?b_action=xts.run&m=portal/welcome/welcome.xts ']
so.cognosNamespaceId=['xOg__']
so.directoryId=['iCD4C77FE7F6F42859251DE3632D98B9F']
so.adminId=['i6F92C402655F42F685F4CDCD211A6F95']
ui.gateway=['/c8mr2/cgi-bin/cognos.cgi']
so.cmRootId=['iEFF596A10F784107B687615044260EC7']
encoding=['UTF-8']
m=['portal/launch.xts']
so.configurationId=['i06C9B1C033CC4BB88AAC88861FA49C72']
b_action=['mms.run']
ui.tool=['MetricStudio']
so.contentId=['i18AAE103ABFB42FB967073771E8B2718']
so.myFoldersId=['iE8E8AB490F9F4ECEBFDE6B1B966F19DA']
ui.backURL=['/c8mr2/cgi-bin/cognos.cgi?b_action=xts.run&m=portal/welcome/welcome .xts']
ui.action=['new']
}

Cause
This error can occur if the user account or role does not have access permissions for any of the existing metric packages in Cognos Connection.

Resolving the problem
An administrator must set the appropriate permissions for the metric package for the user or the role Steps:1. Log in as an administrator to Cognos Connection.
2. Click on the Set Properties icon for the metric package.
3. On the Permissions tab, add the appropriate role and permissions.