Connection & schema problem withTOS DI 5.1.1 and MS SQL Server 2008 R2

[Anonymous]

Hello,
I have searched as best I can for any information on the above and have only found other users noting a similar issue and reference to TDI21056 and TDI21382 which refers to Windows XP.
My environment is: Windows 7 PCs (both real and virtual) accessing MS SQL Server 2008 R2 (on Windows Server 2008) and Oracle (on unix) databases on virtual servers. For purposes of some testing, the MS SQL Server databases may be on the local machine. Up until now the Talend versions have been 4.1.2 and 4.2.2 with no connection problems.
I have now upgraded the virtual PC for pre-production testing to 5.1.1 (as this was provided as the latest stable version) and imported all projects from the earlier versions. On trying to update one of the Db Connections to MS SQL Server, it initially stated ?Connection Successful?, then on clicking Finish the following appears:
Access to the data failure{0}
java.lang.RuntimeException: java.lang.ClassCastException: net.sourceforge.jtds.jdbc.ConnectionJDBC3 cannot be cast to net.sourceforge.jtds.jdbc.ConnectionJDBC2
Consequently, it was impossible to make any changes and save them due to this problem.
However, I created a new connection to the MS SQL database which initially tested OK and which I was able to save. Initial testing by changing the job connections was successful provided there was no tMap component to output tables because retrieval of schema does not appear to work. All that shows is the Catalog name which cannot be expanded into the separate tables.
Curiously, testing various existing sub-jobs of old projects that were imported into the new version of Talend proved successful. However, if I went in to Edit the connection to MS SQL Server, exactly the same thing happened as above (i.e. Access to the data failure{0}). I am concluding that provided there is no need to alter any jobs, a straight import into Version 5.1.1 will apparently work.
Unfortunately, I have to make changes and need to be able to retrieve the table schemas.
(An idea of importing the ?old? connection into the new project failed because it did not appear in the list of items even though it was present in the project.)
Is there likely to be a resolution to this problem in the near future at all?
Many thanks
AnneS

[Anonymous]

I am having a similar problem on a Windows Server 2008 Enterprise VM running TOS DI 5.1.1, JRE1.6.0_32, and MS SQL Server 2005. I am running TOS DI 5.0.2 on Windows 7 and MSSQL 2008 R2 without that issue.

[Anonymous]

I am having a similar problem on a Windows 7 running TOS DI 5.1.1, JRE1.6.0_32, and remoute MS SQL Server 2000.
If I am running TOS DI 5.0.1 on Windows 7 and remoute MSSQL 2000,MSSQL 2005, MSSQL 2008 without that issue.

[e-TE]

I've the same issue using win Vista, TOS DI 5.1.1 r84309 and a MSSQL server 2005 express

[e-TE]

I've the same issue using win Vista, TOS DI 5.1.1 r84309 and a MSSQL server 2005 express

I had to go back with version 5.0.2 to ""solve"" this issue... i hope it will be corrected in next version.

[Anonymous]

Many thanks for all your replies. I have now downloaded version 5.0.2 and have successfully imported one project into it. The connections work and retrieval of schemas seems to work.
Unfortunately, another issue has now appeared - I am getting Invalid Object Name for some (not all) of the tables. I've been deleting and re-creating components and links and also re-retrieving the schema - so far no resolution.

[Anonymous]

I'm having the same issue on Win Server 2008 R2 using TOS DI 5.1.1. Trying to hit SS 2005 and I see the schema but when I select a table I get "pending" forever.

[_AnonymousUser]

Access to the data failure{0}
java.lang.RuntimeException: java.lang.ClassCastException: net.sourceforge.jtds.jdbc.ConnectionJDBC3 cannot be cast to net.sourceforge.jtds.jdbc.ConnectionJDBC2

using win 7 64bit and TOS 5.1.1
--------------
Any idea on how to fix this?

[Anonymous]

Hi
It's a bug. Please report it on BugTracker.
Regards,
Pedro

[Anonymous]

Hi Pedro,
Thank you for your response. I have now reported this on bugtracker.
Regards,
Anne