A Crystal report is connecting to a secure Oracle 9i database using JDBC. When attempting to view the report in the Java Reporting Component (JRC) thick-client viewer, you are prompted for the database logon information. After submitting the logon information, the following exception occurs:
at com.businessobjects.crystalreports.viewer.core.rs.a.r(Unknown Source)
at com.businessobjects.crystalreports.viewer.core.rs.a.v(Unknown Source)
at com.businessobjects.crystalreports.viewer.core.rs.a.if(Unknown Source)
at com.businessobjects.crystalreports.viewer.core.rs.a.do(Unknown Source)
at com.businessobjects.crystalreports.viewer.core.bh.a(Unknown Source)
at com.businessobjects.crystalreports.viewer.core.ag.a(Unknown Source)
at com.businessobjects.crystalreports.viewer.core.be.a(Unknown Source)
at com.businessobjects.crystalreports.viewer.core.af.run(Unknown Source)
This is a known issue with the Java Reporting Component XI Release 2.
This issue has been assigned Track ID ADAPT00568353.
When a Track ID has been assigned to an issue, this indicates it has been reported to Business Objects for possible inclusion in future hot fixes or file updates. Refer to the list of Track IDs that accompanies a hot fix or file update to verify that a particular issue has been corrected.
As of the publish date of this article, there is no file update to correct this issue.
To work around this issue, pass the database logon information programmatically.
ORACLE DATABASE JDBC JRC XIR2 XI R2 NULL POINTER EXCEPTION THICK-CLIENT Crystal Reports XI Release 2 Oracle Database using JDBC Connection Thick-client Viewer , c2019373 , KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , Bug Filed