My company has encountered a problem with our latest Crystal Reports rpt file that is preventing us from fetching the report from our BOE server. The report was developed with Crystal Reports 2008 v12.x and is being hosted on a compatible BOE server. When our server tries to fetch the file from BOE, we get an "Invalid pointer" error:
2014-01-23 13:43:29,538 ERROR [ReportContent.jsp] (http-0.0.0.0-8443-3) com.crystaldecisions.sdk.occa.managedreports.ras.internal.ManagedRASException: Cannot open report document. --- Invalid pointer
cause:com.crystaldecisions.sdk.occa.report.lib.ReportSDKServerException: Invalid pointer---- Error code:-2147467259 Error code name:failed
detail: Invalid pointer
The report works 100% perfectly in the Crystal Reports editor's print preview feature, connecting to the exact same database. The problem seems to occur at some point while adding new content into the report's embedded SQL, and it seems to fail even after benign changes to the code.
For example, I reverted to an old version of the report file that still worked, and I added a single line break into the SQL. The report file immediately started producing the "Invalid pointer" errors after I added the line break. The kicker is that I go back into the file and manually revert the SQL code changes I made to restore it to match the working file's SQL code, and the report file still continues to break. It appears that once the file has started breaking with "invalid pointer" errors, it seems to be broken forever.
We are encountering this issue after 5 months of development on this report, and we're suddenly finding ourselves unable to publish the report for our customers. None of our most experienced Crystal Reports developers have encountered this problem before, and we're up a creek here with no clue on how to fix it or even troubleshoot it.
If we can't get a solution in the next few days, we will need to immediately terminate all usage of Crystal Reports going forward. This problem has caused our company to miss our deadlines, and we're on the verge of switching to another reporting solution.
I'm really hoping somebody here can give us a hand before our management decides to do anything drastic.
Thanks in advance,
-David Eirich
