You are not logged in.
Hi,
Quick question, hopefully someone can help. Currenly evaluating Reportserver and it seems great. However, today I tried uploading a Crystal Report that had 2 joined tables and the report will not render.
The following error is displayed:
"The report could not be executed: com.crystaldecisions.sdk.occa.report.lib.ReportSDKException: Unexpected ValueType: ValueType=[255]---- Error code:-2147467259 Error code name:failed
To get help please contact an administrator."
I have followed the instructions for updating the Java Reporting Component (JRC) according to the user manual.
Anyone ever encountered this error before?
Thanks
Adrian
Offline
Hi adrian,
are you able to run a simple crystal report ? For example with the query "select * from yourtable* and showing 2-3 fields ?
Greets,
Eduardo
Online
Hi Eduardo,
Worked it out. Reports that referenced tables with JSON datatypes would work okay in Crystal but would not render in Reportserver (even if the json columns were not used in the query). When I removed those columns the reports worked fine. I'm assuming this is related to Crystal rather than Reportserver. There isnt a setting on the JDBC driver or elsewhere that I have missed?
Thanks
Adrian
Last edited by adrian (2017-03-20 15:03:13)
Offline
Hi Adrian,
interesting, so crystal reports don't work with JSON datatypes, even if the json columns are not used? Which database are you using? and which driver? We will check this.
Cheers,
Eduardo
Online
Hi,
Yes, it seems to be the case that even if the JSON column isnt used in the report the report will not render. Delete the JSON columns and everything works perfectly.
I have tested on reports created on Crystal Reports 2016 and 2011, using PostgresSQL 9.5.5. On my local crystal, 64 bit ODBC Unicode driver.
Let me know if anything else would be helpful.
Adrian
Offline
Hi Adrian,
what is the sql query of your crystal report? does it include the json column, for example "select * from mytable" ?
We are seeing an issue with json columns in dynamic lists as well, we will take a look at this. But please check this. Maybe it is the same issue.
Cheers,
Eduardo
Online
Hi Adrian,
we have modified reportserver so that it now works with JSON/JSONB columns from both PostgreSQL and MySQL. These are interpreted as strings in reportserver. This feature will be included in the next release.
Cheers,
Eduardo
Online