JDBC issues on infoview (Tomcat)

Hi All,

I'm experiencing an issue with a report which was originally designed for use with CR 7.5 but then, for security reason, we had to adapt it for use with CRXI.

Basically, when updating the datasource settings, using the native oracle driver available on the Crystal report application, I get an "unrecognised characterset" error message.

A colleague suggested that this is probably an application issue as if instead of the native Oracle connectivity, I update the datasource to use a JDBC connection, I do get results printed on the screen.

However when I load the modified and saved template into infoview, I get a "Failed to open connection" error.

I've been looking into both the tomcat and businessobject documentation but couldn't find anything to help me.

Does anyone has a clue on what do I need to look at in order to fix this issue?

Thanks a lot

LaurenceForgot to mention, BusinessObject is installed under tomcat on a unix machine...|||Open the report and do verify database and try.
Also search for your solution here
http://support.businessobjects.com/

JDBC driver for SQL Server

Originally posted by sdevaraj
hi,
try out this opensource driver for sql server. i found it quite good
www.freetds.org.

bye
:eek:

Hi !

I tried using freeTDS but without any success :( can you please post a sample code using freeTDS driver that uses a CallableStatement and an OUT parameter ?

Thanks !!You can download the new "SQL Server 2000 Driver for JDBC - BETA" on this link.

http://www.microsoft.com/sql/downloads/2000/jdbc.asp

bye
Sevket Guenes|||Originally posted by guenes
You can download the new "SQL Server 2000 Driver for JDBC - BETA" on this link.

http://www.microsoft.com/sql/downloads/2000/jdbc.asp

bye
Sevket Guenes ]

Hi Guenes !!

I have tried the MS SQL JDBC Driver, but I get an exception when using OUT parameters !!! I have posted this problem already !! :(

Any ideas ? Have u tried using SPs with OUT params using MS JDBC Driver ? If you have, can u please post the code ? Thanks !!!|||Hi !!

I've solved the problem with OUT parameters :p !! This seems to be a problem with the ODBC stack of Microsoft !! Problem does not arise with other drivers !! This problem arises not only with the ODBC-JDBC driver but with apps like Visual Basic, VC++, etc with use MS ODBC stack !!

The solution:

Do not return Resultsets with OUTPUT parameters !! This does not work. The solution is to split the stored procedures into two procedures, one returning the OUTPUT parameter (if required) and another returning the resultset. Another workaround would be to include the OUTPUT parameter as another Column in the Resultset !! MS ODBC, JDBC client drivers do NOT allow you to return OUTPUT parameters with resultsets !! If you return either one of them alone no problem comes !!

Hope this helps you people out there facing the same problem ;)

- madhan