ReportClientDocument throws - Unexpected database connector error

[Former Member]

Hi,

We are getting a weird exception in Websphere 6.1 server when we try to open a crystal report using ReportClientDocument object. It is throwing an unexpected database connector error when we try to change the datasource of the report. It would be great if some one can help us with the solution.

Code:

ReportClientDocument reportClientDocument = new ReportClientDocument();

reportClientDocument.open(REPORT_NAME, 0);

Tables tables = reportClientDocument.getDatabaseController().getDatabase().getTables();

ITable table = tables.getTable(0);

reportClientDocument.getDatabaseController().setDataSource(resultSet0, tableName0 , tableName0+"_ResultSet");

P.S: The same code works fine in Tomcat 6.0 server.

Exception:

[1/11/11 17:34:10:141 GMT+05:30] 00000037 SystemOut O Connection logon successfully

[1/11/11 17:34:10:145 GMT+05:30] 00000037 SystemOut O Rowset restart: moveToStart true

[1/11/11 17:34:10:145 GMT+05:30] 00000037 SystemOut O Rowset execute

[1/11/11 17:34:10:168 GMT+05:30] 00000037 SystemOut O detected an exception: Unexpected database connector error

at com.crystaldecisions.reports.queryengine.Table.u7(SourceFile:2409)

at com.crystaldecisions.reports.datafoundation.DataFoundation.a(SourceFile:1234)

at com.crystaldecisions.reports.dataengine.dfadapter.DFAdapter.a(SourceFile:344)

at com.crystaldecisions.reports.dataengine.dfadapter.CheckDatabaseHelper.a(SourceFile:66)

at com.crystaldecisions.reports.dataengine.datafoundation.CheckDatabaseCommand.new(SourceFile:100)

at com.crystaldecisions.reports.common.CommandManager.a(SourceFile:71)

at com.crystaldecisions.reports.common.Document.a(SourceFile:203)

at com.crystaldecisions.reports.dataengine.VerifyDatabaseCommand.new(SourceFile:76)

at com.crystaldecisions.reports.common.CommandManager.a(SourceFile:71)

at com.crystaldecisions.reports.common.Document.a(SourceFile:203)

at com.businessobjects.reports.sdk.requesthandler.f.a(SourceFile:175)

at com.businessobjects.reports.sdk.requesthandler.DatabaseRequestHandler.a(SourceFile:373)

at com.businessobjects.reports.sdk.requesthandler.DatabaseRequestHandler.if(SourceFile:352)

at com.businessobjects.reports.sdk.JRCCommunicationAdapter.do(SourceFile:1291)

at com.businessobjects.reports.sdk.JRCCommunicationAdapter.if(SourceFile:661)

at com.businessobjects.reports.sdk.JRCCommunicationAdapter.a(SourceFile:167)

at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.a(SourceFile:529)

at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.call(SourceFile:527)

at com.crystaldecisions.reports.common.ThreadGuard.syncExecute(SourceFile:102)

at com.businessobjects.reports.sdk.JRCCommunicationAdapter.for(SourceFile:525)

at com.businessobjects.reports.sdk.JRCCommunicationAdapter.int(SourceFile:424)

at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(SourceFile:352)

at com.businessobjects.sdk.erom.jrc.a.a(SourceFile:54)

at com.businessobjects.sdk.erom.jrc.a.execute(SourceFile:67)

at com.crystaldecisions.proxy.remoteagent.RemoteAgent$a.execute(SourceFile:716)

at com.crystaldecisions.proxy.remoteagent.CommunicationChannel.a(SourceFile:125)

at com.crystaldecisions.proxy.remoteagent.RemoteAgent.a(SourceFile:537)

at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.if(SourceFile:605)

at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.a(SourceFile:1688)

at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.new(SourceFile:2650)

at com.crystaldecisions.sdk.occa.report.application.b9.onDataSourceChanged(SourceFile:301)

at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:962)

at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:2834)

at com.crystaldecisions.sdk.occa.report.application.DatabaseController.setDataSource(SourceFile:2557)

at com.crystaldecisions.reports.sdk.DatabaseController.setDataSource(SourceFile:87)

[Adam_Stone · Accepted solution]

It appears that you are trying to pass a resultset to the report, only things i can think of is, either the jar file needed for that type of connection is missing, or maybe the app servers are using different versions of java which causes it to act differently.

[Former Member · Accepted solution]

The exception is thrown by the JRC framework since u201CNULLu201D value is passed to an object whose data type is u201CMemou201D in the report.