Hi. I've got some fairly good experience w/Talend on a previous project, but am having an issue with using a t_AccessInput to grab a table from an access db. Environment: Windows XP Talend 3.0.2 JDK: 1.6.011 Access Version: Office 2003 I can do this on my development box, but if I use another box where Talend is installed on a minimal OS, I get the following error message when trying to run the job: Starting job testjob at 11:13 12/03/2009. Exception in component tAccessInput_1 java.sql.SQLException: Data source name not found and no default driver specified at sun.jdbc.odbc.JdbcOdbc.createSQLException(Unknown Source) at sun.jdbc.odbc.JdbcOdbc.standardError(Unknown Source) at sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(Unknown Source) at sun.jdbc.odbc.JdbcOdbcConnection.initialize(Unknown Source) at sun.jdbc.odbc.JdbcOdbcDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at test.testjob_0_1.testjob.tAccessInput_1Process(testjob.java:402) at test.testjob_0_1.testjob.runJobInTOS(testjob.java:661) at test.testjob_0_1.testjob.main(testjob.java:577) Job testjob ended at 11:14 12/03/2009. The job just queries all from a table (select * from table1), and the schema is just the first two columns, an int and a string. It can't seem to connect to the db either if I hit the ... button next to the db name - it just flashes something real quick then never responds. Is this a driver issue? Any ideas? Thanks, Eric
java.sql.SQLException: Data source name not found and no default driver specified
As the message said, If you use a ODBC source name in your computer, you must re-create the ODBC source name into destination computer also.
Best regards
I'm not using an ODBC data source name. I'm simply pointing to the access database file via the property of the t_Access control (on both boxes btw - see attached image).
So, ODBC data source names are not the issue. (that would've been too obvious)
There's a bug, a setup issue, or something else wrong and I was hoping that someone had some real experience with this?
Is there a "default" driver that Talend is not mapping to correctly? It would seem that my development box has the same set of ODBC drivers as the test box though...
Thanks, Eric.
Richard,
Thanks for the update w/your issues as well.
OK - just some more info in general. As I mentioned in my last post(s) on this topic, the access connection works fine on my (developer) box but not on another box that I installed for a low-tech user. Like I said - I can use it fine w/direct MS Access connectivity without setting up an ODBC DSN - just point to the file and, as Emeril would say - BAM - it works fine. On the other box, we had to setup a DSN and use a generic ODBC connection.
I figured it was all the dev software on my box, the JDK, whatever...so I installed many of the products that are on my dev box onto the other box just to see what would happen (I'm like a dog w/a bone when it comes to this kinda stuff - I just won't let it go)... I installed:
SQL Server 2008 Express
Visual Basic.NET Express, Visual C# Express
JDK 1.6.011
Latest version of MS Access
Still no go on the other box. I couldn't mirror my box because I have just way too many developer tools to install, so it's obviously something else.
Today I am installing it on yet another analyst's box cuz she needs some quick functionality w/xml files and access db's as well (gee this is a great product btw that really keeps these analysts off my back for little mundane tasks like spinning tables into xml docs!). So, I'll post again after this 3rd install and keep the thread alive.
I was hoping that Volker would reply on this, but with some recent acquisitions @ Talend and changes on the Board of Directors, my guess is Volker is downright slammed right now - and soon to be a very rich man, I would bet! haha! schweet, as Cartman would say!
Cheers, Eric.
