Cognos Portal Services

Cognos Portal Services 

Supplementary Troubleshooting Notes for 

Cognos ReportNet 1.02 Maintenance Release 1



Cognos ReportNet 1.02 Maintenance Release 1 

Copyright © 2003 Cognos Incorporated 

Cognos Confidential Page 2 of 10




Table of Contents 

1 Introduction............................................................................................................... 4 

1.1 Getting Ready ........................................................................................................................4 

2 Troubleshooting - Common Issues......................................................................... 5 

2.1 iViews on 2 Different Pages Always Show the Same Content ..............................................5 

2.2 Action Buttons do not Work Properly .....................................................................................5 

2.3 No Images Appear in Cognos iViews ....................................................................................5 

3 Troubleshooting - Error Messages in iViews ......................................................... 6 

3.1 CPS-WSR-0010 – Soap error................................................................................................6 





3.6 CPS-WSR-0041 .....................................................................................................................9 

3.7 CPS-WSR-0043 ...................................................................................................................10 





1 Introduction 

This document lists common problems encountered with Cognos Portal Services for SAP when 

installed with Cognos ReportNet 1.02 Maintenance Release 1. 

This document is intended to assist portal administrators with possible problems. However, it is 

not an official Cognos publication. Therefore, Cognos does not accept responsibility for any 

kind of loss resulting from the use of information in this document. 

If you require technical assistance with Cognos Portal Services, visit the Cognos support Web 

site (http://support.cognos.com). 

1.1 Getting Ready 

This document assumes the following: 

o You have working knowledge of Cognos ReportNet, Cognos Portal Services, and SAP Enterprise 

Portal 5.0 as it relates to the tasks that are described in the Cognos Portal Services Administration 

Guide for Cognos ReportNet 1.02 Maintenance Release 1. 

o You are familiar with the Cognos Portal Services Administration Guide for Cognos ReportNet 1.02 

Maintenance Release 1. 





Troubleshooting - Common Issues 

2.1 Two iViews Always Show the Same Content 

A user who adds the same iView instance on two different pages might expect to be able to configure one 

instance in one way and the other instance another way. For example, on the first page, the user would 

want a Viewer iView to always show the report “Monthly Sales”, while on the other page, they want it to 

display “Current Expenses”. 

In the SAP Portal, this cannot be done with the same instance of an iView. Settings in one iView will 

always be mirrored in the other. The administrator must configure two different iView instances, otherwise 

settings in one will always be mirrored in the other. The portal administrator should create more than one 

instance of the iView to allow users to have independent iViews of the same kind on one or different pages. 

Settings obtained via “Edit Personalization” are private to each user, even when using the same iView 

instance. 

2.2 Action Buttons do not Work Properly 

In Cognos iViews, none of the action buttons work properly – they all generate a “page not found” error 

when invoked. 

Possible causes: 

1 - Settings in Cognos Configuration were not set properly. 

Corrective Action: 

- Make sure that, under the “Environment” section, all URLs are specified with absolute server 

names instead of “localhost”. The Cognos iViews use the URL defined in “Gateway URL” to 

invoke ReportNet actions. But those actions are invoked from the portal server, not from the 

ReportNet server. 

2.3 No Images Appear in Cognos iViews 

All icons and pagination buttons are only displayed as empty rectangles. 


1 - Settings in Cognos Configuration were not set properly. 


- Make sure that, under the “Environment” section, all URLs are specified with absolute server 

names instead of “localhost”. The Cognos iViews use the URL defined in “WebContent URL” to 

locate image files. 





3 Troubleshooting - Error Messages in iViews 

The following lists some of the common error messages with their possible causes and the suggested 

actions to fix their cause. 

3.1 CPS-WSR-0010 – Soap error 

CPS-WSR-0010 - The SOAP fault "java.io.FileNotFoundException" 

(java.io.FileNotFoundException : http://sottcps3:9300/samples/cps2/applications.xml) 

returned by the target WSRP Producer is not supported by the WSRP Markup Interface 

operation "getMarkup". 

null 


1 – applications.xml could not be found. 

Corrective Actions: 

- Make sure that the ReportNet Software Developer Kit is properly installed. 

- In Cognos Configuration, make sure that the Cognos Portal Services section contains a valid location 

for the “location of applications.xml” property. This can be tested simply by opening a page with a 

Cognos Extended Applications iView, clicking Edit and clicking the link to select an application. If the 

list of applications appears, the property is set properly. If not, the setting is wrong. Usually, only the 

server name and port number need to be changed in that field. The value must be an explicit URL. 


CPS-WSR-0010 The SOAP fault "camAuthUnrecoverable" (CAM-AAA-0034 The namespace 

'Marketing' does not exist.) returned by the target WSRP Producer is not supported by the 

WSRP Markup Interface operation "getMarkup". 

null 


1 – Invalid namespace setting in Cognos Configuration 


- On the ReportNet server, run Cognos Configuration. In the Cognos Portal Services section, make sure 

that the “namespace” is valid. It must refer an existing namespace ID as defined in the 

Security/Authentication section. Note that in that section, you must click on the namespace name to find 

it’s actual ID, which can be different from the displayed name. 






CPS-WSR-0010 The SOAP fault "camAuthUserRecoverable" (CAM-AAA-0055 User input is 

required.) returned by the target WSRP Producer is not supported by the WSRP Markup 

Interface operation "getMarkup". 

null 

Possible Causes: 

1 – Mismatch of logon credentials: There is a mismatch between Cognos Portal Services authentication 

credentials and available ReportNet authentication. 

ReportNet is not configured to accept Anonymous access while the CPS section uses Anonymous as its 

Authentication method. 

If Authentication method is set to Single signon, it is possible that the user can be refused if their portal 

userID does not match one of the valid userIDs in the SAP namespace referenced to under Cognos Portal 

Services > NamespaceID. 


- Follow these steps: 

1. Run Cognos configuration. 

2. Go to the section Cognos Portal Services section. 

o Under Authentication Method, if “Anonymous” (the default) is selected, verify that 

Anonymous access is allowed in the “Cognos” namespace definition section. 

o If the Authentication method is “Single Sign On”, ensure that the namespace ID setting is 

properly specified, and that it references an SAP namespace defined in the Authentication 

section. 

The single sign on authentication method requires the users log into the portal with a user 

ID which is also registered in the specified SAP namespace. To verify this, simply start 

Cognos Connection and logon in the SAP namespace as that user. Make sure you can 

also log on into the SAP portal with that same user ID. 

2 – Single sign on is not configured properly between the SAP Portal server and the SAP BW 

backend. 


- First, verify that the SAP namespace is properly defined in ReportNet and that users can logon to 

ReportNet directly using their SAP BW password. If that fails, see the Cognos ReportNet 

documentation about setting up an SAP BW namespace. 

- Once the above is working, carefully follow the instructions in the CPS documentation appendix about 

Single sign on. This is quite complex and requires an experienced SAP BW administrator and the SAP 

Portal administrator. A trust must be established between the two servers. 






CPS-WSR-0010 The SOAP fault "Client" (The client did something wrong) returned by the 

target WSRP Producer is not supported by the WSRP Markup Interface operation 

"getMarkup". 

null 

Possible Causes: 

1 – Invalid authentication credentials (userID, password) combination in “Logon as”. 


- Open Cognos Configuration and go to the Cognos Portal Services section. 

- If the Authentication method is “Logon as”, 

o Make sure that the namespace ID is correctly specified 

o Make sure that the specified user ID and password are valid. You can test them by simply 

starting a ReportNet session and logging to that namespace with the specified user credentials. 


CPS-WSR-0010 The SOAP fault "java.io.IOException" (java.io.IOException : Server 

returned HTTP response code: 500 for URL: 

http://localhost:9300/samples/cps2/basicnav.jsp) returned by the target WSRP Producer is 

not supported by the WSRP Markup Interface operation "getMarkup". 

null 


1 – ReportNet SDK is not properly installed. 


- Make sure that the ReportNet SDK is properly installed. 

- In Cognos Configuration, make sure that the Cognos Portal Services section contains a valid location 

for the “location of applications.xml” property. This can be tested simply by opening a page with a 

Cognos Extended Applications iView, clicking Edit and clicking the link to select an application. If the 

list of applications appears, the property is set properly. If not, the property setting is wrong. Usually, 

only the server name and port number need to be changed in that field. The value must be an explicit 

URL. 

2 – The JSP is not on the “localhost” or is running on another port. 

The file “applications.xml” contains a URL that specifies the location of each application’s entry JSP file. 

By default, applications.xml defines their location as “localhost:9300”, which refers to the server that is 

currently running ReportNet Report Server. If the ReportNet SDK has been installed on another server, 

the content of applications.xml must reflect the absolute URL for each of the JSP applications. 


- Edit applications.xml. For each JSP, modify the URL to make it absolute by changing “localhost:9300” 

to the specific server & port used to run the JSP’s. 

- If ReportNet is part of a distributed install in which several dispatchers are running, each server must 

either point to the same applications.xml file, or to separate but identical versions of applications.xml, 

which all point to identical versions of the JSP applications. When ReportNet performs automatic load 

balancing, any of the servers can be user to fulfill a request. It is necessary to have a similar 

configuration on all servers. 





3.6 CPS-WSR-0041 

CPS-WSR-0041 Failed to connect to target "http://:/p2pd/servlet/dispatch". 

Connection refused: connect 


1 – The ReportNet server is not running or still initializing 

Corrective Actions 

- Make sure that ReportNet is started properly. 

- Make sure you can access ReportNet directly from a browser. 

2 – The portal server does not have network access to the server running ReportNet 

Corrective Actions: (Portal Administrator) 

- From the portal server machine, start a DOS window and try to ‘ping’ the ReportNet server using the 

same server name/address as in the error message. 

- If there is no response, there is a connection problem between the 2 machines. You need to make sure 

the 2 machines can communicate over an IP connection. 

- If the ping succeeds, make sure that no firewall blocks the configured port (default is 9300) between the 

2 servers. 

3 – The URL for connecting to ReportNet is incorrect. 


- Open the portal in administration mode. 

- Go to Content Admin > iViews and locate the iView instance that causes the problem. 

- Click Edit to configure the instance and select the “Java” tab. 

- Verify that the URL value in _cpsserver is valid. It should indicate the proper server name or address 

and the proper port number of the ReportNet dispatcher. 

http://:/p2pd/servlet/dispatch 

must be set explicitly, “localhost” should not be used., 

defaults to 9300 (the default port for ReportNet’s dispatcher), verify your ReportNet 

installed port by running Cognos Configuration. 

The rest of the URL should be left as written above. 

4 – Java VM conflicts on the ReportNet server 


- On the ReportNet server, ReportNet comes with its own version of JRE. Make sure no other version of 

the Java VM or Java SDK are installed on the server. 

- Verify that there is no system environment variable called JAVA_HOME that can cause such conflicts. 





3.7 CPS-WSR-0043 

CPS-WSR-0043 Failed to read the response from target 

"http://:/p2pd/servlets/dispatch". 

Or 

CPS-WSR-0043 Failed to read the response from target 

"http://cognoscentii:9300/p2pd/servlet/dispatch". 

Server returned HTTP response code: 500 for URL: 

http://cognoscentii:9300/p2pd/servlet/dispatch 

This message indicates that, even though the iView was able to connect to the ReportNet server, 

ReportNet is unable to respond to the request. 


1 – The ReportNet server is not running or still initializing 


- Make sure that ReportNet is started properly. 

- Make sure you can access ReportNet directly from a browser. 

2 – The URL for connecting to ReportNet is incorrect. 


- Open the portal in administration mode. 

- Go to Content Admin > iViews and locate the iView instance that causes the problem. 

- Click Edit to configure the instance and select the “Java” tab. 

- Verify that the URL value in _cpsserver is valid. It should indicate the proper server name or address 

and the proper port number of the ReportNet dispatcher. 

http://:/p2pd/servlet/dispatch 

must be set explicitly, “localhost” should not be used., 

defaults to 9300 (the default port for ReportNet’s dispatcher), verify your ReportNet 

installed port by running Cognos Configuration. 

The rest of the URL should be left as written above.

Cognos Portal Services

Create successful ePaper yourself

Delete template?

Save as template?