New Project DQM Error

[Jlloyd999]

Gents and Ladies

When I try and start a new project in DQM mode the following appears

BMT-IMP-0002 Failed to execute metadata request. Java Runtime Environment (JRE) version 1.7 is not supported by this driver. Use the sqljdbc4.jar class library, which provides support for JDBC 4.0.
CAF-WRN-2082 An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID:2015-07-06-17:04:45.981-#11

I understand that usually the error relates to not having the drivers installed however I dont believe its as simple as that. I have 3 dispatchers, 2 32 bit and 1 64 bit, I have tested the connections for the JDBC driver and it works fine. The framework tool is actually stood up on a completely seperate box and I havent setup any drivers there as i didnt think any were needed. The distpatcher it connects to is the 64 bit one but I thought that the distpathcers were self aware enough to pass them around. Any thought or suggested would be much appreciated.

Regards

Jon

[cognostechie]

Note sure what you mean by 'tested connections for JDBC driver'. The error is saying that the JAVA version installed is older than required, not the driver version. Have you made a data source in Cognos using JDBC connection and tested that?

[Jlloyd999]

Thanks for your response,

What I mean by tested JDBC connection is that I created the connections in the admin console as tested the JDBC connection for that dispatcher. I ran the test on all 3, 2 failed as the query service was switched off, the 64 bit dispather passed.

[MFGF]

Thanks for your response,

What I mean by tested JDBC connection is that I created the connections in the admin console as tested the JDBC connection for that dispatcher. I ran the test on all 3, 2 failed as the query service was switched off, the 64 bit dispather passed.

I think what cognostechie means is that the test option when creating/amending a data source is just testing connectivity - it doesn't necessarily mean you can see/use content from within the data source itself. A proper test is done by launching FM and importing metadata successfully.

It looks to me like you're using SQL Server? What version of sqljdbc4.jar are you using? What version of java?

MF.

[Jlloyd999]

Thanks!

I didnt realise that the connection in the admin console wasnt proof that it worked. Yes you are correct it is SQL server. The Drivers I have downloaded have a release note of March 2012.... The driver appears to be version 4.0.

I moved the two files to the required locations. By two Files I mean sqljdbc_auth.dll and sqljdbc4.jar. The first I beleive is because we use a service account. These are reference in the databaseDriverLocations file as follows

# Licensed Materials - Property of IBM
# IBM Cognos Products: OQP
# (C) Copyright IBM Corp. 2005, 2011
# US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM corp.

# List of .jar or .zip files. The paths must be absolute and no spaces are allowed.
# For Windows the list of files must be semi-colon delimited and semi-colon ended; double back slashes must be used in the paths (e.g. C:\\my_1.jar;C:\\my_2.jar;).
# For UNIX  the list of files should be colon delimited and colon ended; single forward slashes must be used (e.g. /root/my_1.jar:/root/my_2.jar:).
databaseClasspath=C:\\JDBC\sqljdbc4

# List of directories to load native libraries. The paths must be absolute and no spaces are allowed.
# For Windows the list of directories must be semi-colon delimited; double back slashes must be used in the paths (e.g. C:\\path_1;C:\\path_2).
# For UNIX  the list of directories should be colon delimited; single forward slashes must be used (e.g. /root/path_1:/root/path_2).
databaseJNIPath=C:\\JDBC

as you can see there simple kept in a folder called JDBC.
When you say JAVA what do you mean? I didnt think java needed to be installed? It wasnt on the install documents I assumed as it had its own JVM that it didnt need it, though I must admit im not familiar with that area.