Skip to main content



      Home
Home » Archived » BIRT » Problem creating new data source for mysql-connector-java-3.1.7-bin.jar - where are the logs?
Problem creating new data source for mysql-connector-java-3.1.7-bin.jar - where are the logs? [message #41894] Wed, 01 June 2005 00:50 Go to next message
Eclipse UserFriend
I am attempting to create a new data source for a report using this
driver. I can use manage drivers to identify the jar, and then I can see
the driver class in the "New Data Source" dialog, but attempts to test
the connection result in the error:

No Suitable Driver

Reason:
java.sql.SQLException occurred

Details:
No suitable driver

I have tried a number of connect Strings in the URL space. The database
is on 10.10.10.224 on my local network (mysql client connects to it fine
on the command line with the same user name and password), and I have
tried strings like:

10.10.10.224
mysql:10.10.10.224
jdbc:mysql:10.10.10.224
jdbc:mysql:10.10.10.224:3306
jdbc:mysql:10.10.10.224:3306/dbname

etc. Am I missing something about the connection string?

I would normally troubleshoot driver connection problems myself, but I
cannot seem to drag any further information out of Eclipse?BIRT about
the exception, in particular the Exception message and stack trace. I
can't find them in the log. Where does BIRT log errors and Exceptions?
Re: Problem creating new data source for mysql-connector-java-3.1.7-bin.jar - where are the logs? [message #41925 is a reply to message #41894] Wed, 01 June 2005 03:39 Go to previous message
Eclipse UserFriend
OK, I had an error in the URL... still, for future reference it would be
nice to know where the full detail of the Exception could have been found.
Previous Topic:Progress DB Connectivity
Next Topic:Can no longer run reports against the BIRT Sample Database
Goto Forum:
  


Current Time: Wed Sep 17 22:29:25 EDT 2025

Powered by FUDForum. Page generated in 0.03901 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top