OD 7.1 "check correct JDBC Driver installed"

We have upgraded to OD 7.1. When trying to run Quick or Custom Reports we receive "Please check if the correct JDBC driver is installed."

We have tried sqljdbc and sqljdbc4. No luck.

We are running this on a Windows 2008 SP2 box. SQL 2005 DB

Any thoughts?

Find more posts tagged with

Comments

mart2001

Where did you put those jdbc drivers?

Did you restart od?

Migrateduser

Restarted OD SEVERAL times. We've been trying to resolve this and other issues for weeks.

ThemesReportItems3.zip

mart2001

Have you tried putting the JDBC drivers into
C:\Interwoven\OpenDeployNG\drivers
and possibly:
C:\Interwoven\OpenDeployNG\lib?

Assuming that you have installed OpenDeploy into the C:\Interwoven\OpenDeployNG directory.

Migrateduser

Thank you mart for your responses.

We have tried both of those dirs in the past and no luck

OS_BIRT_442_Topic_36942_XML_Custom_DataSource DEMO ONLY.rptdesign

Migrateduser

This thing has gotten so deep Autonomy now has engineers looking at their code.

Snap 2015-07-23 at 14.00.33.png

Snap 2015-07-23 at 14.02.06.png

Snap 2015-07-23 at 14.08.23.png

Snap 2015-07-23 at 14.10.30.png

Snap 2015-07-23 at 14.15.26.png

Snap 2015-07-23 at 14.18.02.png

Snap 2015-07-23 at 14.18.45.png

Snap 2015-07-23 at 14.22.13.png

Snap 2015-07-23 at 14.24.36.png

Snap 2015-07-23 at 14.27.01.png

Snap 2015-07-23 at 14.30.01.png

Snap 2015-07-23 at 14.32.07.png

YearOverYear4.rptdesign

mart2001

Hi Moody,

Sorry, I wasn't able to help. Our system have OpenDeploy 7.1 on Solaris with Oracle and put the jdbc drivers for Oracle in od-home/OpenDeployNG/drivers and od-home/OpenDeployNG/lib and the report is working for us. Hope you have a good answer from Engineer.

Migrateduser

Our guy here actually fixed the issue!

mart2001

Would you mind shedding some light as how the issue was resolved?

Migrateduser

The issue was with the connection string in the server.xml file. The example in the documentation was for SQL2000. The support person we were working with submitted a documentation change request to add the findings for SQL 2005.

The connection string was missing a semicolon after jdbc:sqlserver in the conn string

jdbc:sqlserver://dbserver:serverport;databaseName=databasename;selectMethod=cursor;

Thus fixing our JDBC error.