Cognos Portal Services

More documents

Recommendations

Info

Cognos Portal Services Supplementary Troubleshooting Notes for Cognos ReportNet 1.02 Maintenance Release 1 3.4 CPS-WSR-0010 – Soap error 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”. Corrective Actions: - 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. 3.5 CPS-WSR-0010 – Soap error 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 Possible causes: 1 – ReportNet SDK is not properly installed. Corrective Actions: - 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. Corrective Actions: - 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. Cognos Confidential Page 8 of 10
Cognos Portal Services Supplementary Troubleshooting Notes for Cognos ReportNet 1.02 Maintenance Release 1 3.6 CPS-WSR-0041 CPS-WSR-0041 Failed to connect to target "http://:/p2pd/servlet/dispatch". Connection refused: connect Possible causes: 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. Corrective Actions: (Portal Administrator) - 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 Corrective Actions: - 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. Cognos Confidential Page 9 of 10
Page 1 and 2: Cognos Portal Services Supplementar
Page 7: Cognos Portal Services Supplementar

Cognos Portal Services

Create successful ePaper yourself

Delete template?

Save as template?