Topic: cmd line exec failed: No Suitable driver found for jdbc:sqlserver
Go back to forum.
|
Topic by
2009-08-19
08:10 |
cmd line exec failed: No Suitable driver found for jdbc:sqlserver
Hello,
I've tested connection to MS SQL server 2008 in DataCleaner, was able to run profiling for my test table and then saved the file as my_profiler.dcp. When I am running it in cmd I am getting the following error:
I've downloaded and registered sqljdbc_2.0 but it doesn't help. All ideas will be highly appreciated. |
|
kasper
2009-08-19
09:17 |
And if you open "my_profiler.dcp" from within the DataCleaner GUI application, it works fine? I would expect the same error in the desktop application basically it's saying that there are no drivers installed that accept URLs that start with "jdbc:sqlserver".
|
|
dluvishis
2009-08-19
18:49 |
When I open my_profiler.dcp I am getting an error:
Column "#" is the first column in the table I am interested in. I've tried excluding it from the my_profiler.dcp, but got the same message regarding the first column mentioned as well. After I click Ok on the Error Message, I can see all schemas on the sidebar, but no tables there. I am connecting to the database using username "DataCleaner". |
|
kasper
2009-08-19
21:31 |
Mysterious ... I think I have an explanation for the error you are getting now, but as far as I can see it's not related to the original error message (the one relating to no suitable driver).
Regarding your last entry (the issue about the first column in your table) I want you to know that just as of yesterday we found a bug relating to SQL server schema exploration so I think this may very well fix things for you. Asbjørn fixed the bug today but we still need to look at a few other issues before we make a release so hold on a few days and I'll keep you posted! |
|
Log in by clicking the login link at the top of the screen |
Go back to forum.
