Skip to Content
0
Former Member
Jun 10, 2009 at 09:54 PM

NullPointerException thrown by ReportClientDocument.verifyDatabase

147 Views

We are using the JRC with Crystal Reports XI Release 2, to display reports inside a Java Swing application.

A report which was previously working is now giving the following error:

[Thread-11] INFO com.businessobjects.reports.sdk.JRCCommunicationAdapter - JRCAgent1 received request: verifyDatabaseRequest
[Thread-11] ERROR com.businessobjects.reports.sdk.JRCCommunicationAdapter - JRCAgent1 detected an exception: java.lang.NullPointerException
        at com.businessobjects.reports.sdk.a.e.a(Unknown Source)
        at com.businessobjects.reports.sdk.a.e.a(Unknown Source)
        at com.businessobjects.reports.sdk.a.e.do(Unknown Source)
        at com.businessobjects.reports.sdk.a.h.new(Unknown Source)
        at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown Source)
        at com.crystaldecisions.proxy.remoteagent.y.a(Unknown Source)
        at com.crystaldecisions.proxy.remoteagent.r.a(Unknown Source)
        at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.if(Unknown Source)
        at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.do(Unknown Source)
        at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.verifyDatabase(Unknown Source)
        at com.crystaldecisions.sdk.occa.report.application.bd.onDataSourceChanged(Unknown Source)
        at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(Unknown Source)
        at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(Unknown Source)
        at com.crystaldecisions.sdk.occa.report.application.DatabaseController.setDataSource(Unknown Source)
        at com.crystaldecisions.reports.sdk.DatabaseController.setDataSource(Unknown Source)

We have tried a number of different things, including:

- Turning off the "Verify on First Refresh" setting in the report options

- Verifying the database in the report editor, then saving the report and rebuilding the app

- Removing each field from the datasource bean one by one, until none remain

None of these approaches has worked.

Does anyone know if we can programmatically tell the JRC not to do the verifyDatabase() which is resulting in this error?

Or is there any way to get more visibility into exactly what is causing the NPE?

Thanks in advance for any tips.