Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MySQL 4.1 + CF7 Migrane

Status
Not open for further replies.

CryoGen

MIS
Apr 15, 2004
86
US
I recently installed MySQL 4.1 and CF7, but I'm having trouble with the driver connection.

I'm trying to use MySQL's connector J v. 3.0.17 but I haven't had any luck. I also tried with the latest driver, mysql-connector-java-3.1.11-bin, but it didn't work and read on one of the CF message board that it was flaky (it recommended trying v3.0.17).

It doesn't matter which driver I use, I get this error when I try to create the datasource:

Code:
Connection verification failed for data source: curves
java.sql.SQLException: No suitable driver available for curves, please
check the driver setting in resources file, error: null
The root cause was that: java.sql.SQLException: No suitable driver
available for curves, please check the driver setting in resources
file, error: null


I didn't install CF on my C: drive because of space issues. It was installed on my D: drive (same physical drive, different partition), which is also where MySQL 4.1 is installed. I'm not sure whether that matters or not. Here's the configuration:

D:\CFusionMX7\
CF DSN: trick4
JDBC URL: jdbc:mysql://localhost:3306/trick4
Driver Class: com.mysql.jdbc.Driver
Driver Name: mysql-connector-java-3.0.17-ga-bin.jar
User Name: root
Password: root

The driver for MS Access works fine. I have several running and they test fine when I verify the DSNs. I'm perplexed. I have found threads on this board that have solved similar problems (most notably this one: but it did not solve mine. Any help is appreciated.
 
Anyone? I still haven't resolved this. Help desperately needed.
 
This doesn't seem related but its worth a try:


From the error message though, it seems as if your connection string is not correct. In JDBC it will look for a driver which recognises your connection string if it doesn't find one it usually returns an error like the one you have I would double check that as well.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top