Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

RRDI - Query Studio - Test Cases Error - Reporting Data Model (IBM Rational Quality Manager)

I have configured RQM Live datasource for RRDI. As per the instruction given in the IBM site.

But when we launch the Query Studio and choose Reporting Data Model (IBM Rational Quality Manager).

And select Test Case. The below error is thrown on screen.

UDA-SQL-0114 The cursor supplied to the operation "sqlOpenResult" is inactive.UDA-SQL-0107 A general exception has occurred during the operation "fetch".CRRRE9000E: Internal Java error, check ri_jdbc.log for detailsRSV-SRV-0042 Trace back:RSReportService.cpp(722): QFException: CCL_CAUGHT: RSReportService::process()RSReportServiceMethod.cpp(263): QFException: CCL_RETHROW: RSReportServiceMethod::process(): asynchWait_RequestRSASyncExecutionThread.cpp(808): QFException: RSASyncExecutionThread::checkExceptionRSASyncExecutionThread.cpp(260): QFException: CCL_CAUGHT: RSASyncExecutionThread::runImpl(): promptPagingForward_RequestRSASyncExecutionThread.cpp(864): QFException: CCL_RETHROW: RSASyncExecutionThread::processCommand(): promptPagingForward_RequestExecution/RSRenderExecution.cpp(670): QFException: CCL_RETHROW: RSRenderExecution::executeAssembly/RSDocAssemblyDispatch.cpp(291): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSLayoutAssembly.cpp(79): QFException: CCL_RETHROW: RSLayoutAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(358): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchChildrenAssemblyForwardAssembly/RSReportPagesAssembly.cpp(179): QFException: CCL_RETHROW: RSReportPagesAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(308): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSPageAssembly.cpp(303): QFException: CCL_RETHROW: RSPageAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(308): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSTableRowAssembly.cpp(177): QFException: CCL_RETHROW: RSTableRowAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(308): QFException: CCL_RETHROW:

And in ri_jdbc.log, we get the following error,

07/02/2014 11:57:30,451 ERROR Thread-41 com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread : com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.dataservices.client.auth.AuthenticationException: CRRRE1404E: The user or password is invalid. Please provide a valid user name and the correct password.
07/02/2014 11:57:30,451 ERROR Thread-41 com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread : com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.dataservices.client.auth.AuthenticationException: CRRRE1404E: The user or password is invalid. Please provide a valid user name and the correct password.
com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.dataservices.client.auth.AuthenticationException: CRRRE1404E: The user or password is invalid. Please provide a valid user name and the correct password.
 at com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread.exeFetch(PageFetcherThread.java:568)
 at com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread.run(PageFetcherThread.java:136)
Caused by: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.dataservices.client.auth.AuthenticationException: CRRRE1404E: The user or password is invalid. Please provide a valid user name and the correct password.
 at com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread.exeFetch(PageFetcherThread.java:519)
 ... 1 more
Caused by: com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.dataservices.client.auth.AuthenticationException: CRRRE1404E: The user or password is invalid. Please provide a valid user name and the correct password.
 at com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread.exeFetch(PageFetcherThread.java:430)
 ... 1 more
Caused by: com.ibm.rational.dataservices.client.auth.AuthenticationException: CRRRE1404E: The user or password is invalid. Please provide a valid user name and the correct password.
 at com.ibm.rational.dataservices.client.auth.FormAuthentication.getContent(FormAuthentication.java:198)
 at com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread.exeFetch(PageFetcherThread.java:422)
 ... 1 more
07/02/2014 11:57:30,451 INFO  Thread-43 com.ibm.rational.drivers.jdbc.xml.RDSStatement : CRRRE1228I: Close this statement
07/02/2014 11:57:30,482 INFO  Thread-14 com.ibm.rational.drivers.jdbc.xml.RDSStatement : CRRRE1228I: Close this statement

Not able to figure out where excatly the issue is. Which username and password is it trying to login with ? and when we do Test Connection in Congos Administrative console for RQM Live data source, why does it pass ?

0 votes



One answer

Permanent link
Hi Chaitra,

Which version of RQM are you using?  The credentials are stored in the XDC file for the RQM Live connection, and those credentials are generated based on the XDC type and Data Collection user you configured when you set up QM.  You can see this configuration under qm/admin -> Reports -> Data Warehouse Connection.  Once there, look at the "XDC Authentication Type" and "Data Collection User or Consumer Key".  If something doesn't look right, re-generate the XDC files under the qm/admin -> Reports -> Downloads -> "Configuration Files for Rational Reporting data sources".

Once you have the XDC file (rqm403-live.xdc), you need to add a DSN on your report server called "RQM Live" if you haven't already.  Use
this topic for that if needed.  The report server already has a connection called "RQM" which points to the DSN "RQM Live" on your OS, so there's nothing needed there.

So in short, for this to work you need to:

1)  Make sure the credentials stored in the XDC file are correct.  This should be done already when the server generates the XDC file when you download XDC files.  If you have the Insight development tools installed, you can actually open the XDC file using the XML Data Configuration tool and see what credentials are stored and test the connection.

2)  Create the "RQM Live" DSN on your operating system (using 32-bit driver manager) that points to your rqm403-live.xdc using the IBM Rational XML ODBC Driver.  If using Linux, you need to configure 32-bit UNIXODBC to create the DSN.

3)  Test the "RQM" connection from the report server (Launch -> IBM Cognos Administration -> Configuration -> Data Source Connections -> RQM -> Test

Once all of those conditions are satisfied this will work.  Hope it helps!

0 votes

Comments

Thanks Benjamin.

I had tried all the steps mentioned by you during intial setup of RQM Live data source.

When I do Test the "RQM" connection from the report server (Launch -> IBM Cognos Administration - Configuration - Data Source Connections - RQM - Test

Its always a success.

But when I go into Query Studio and open Test Cases or any other. It throws the above error.

The problem with testing the connection from Cognos is that it's just testing the existence of the DSN, it's not authenticating through to RQM.  I think your problem is the stored credentials in the RQM Live XDC file are wrong.  If you're willing to install the Insight development tools, you will get the XML Data Configuration tool and can validate this yourself.  Otherwise you can contact support and they can validate the file for you.

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 7,495

Question asked: Jul 02 '14, 12:06 p.m.

Question was seen: 5,474 times

Last updated: Jul 02 '14, 1:47 p.m.

Confirmation Cancel Confirm