The issue was caused because of the way java.sql.DriverManager getConnection api works; Any driver class loading issue affects the getConnection api.

Now we have refactored the code to make sure to use the driver directly to connect instead of using DriverManager.

@QA,

Considering the nature of the fix, please make sure that all your existing connections works. And I would highly recommend the following test against couple of db servers:

* Try valid and invalid connections

* Try queries using Query Analyzer

* Try PL/SQL debugging sessions

Verified on ADS 14.0.0-beta-68 for Windows.

In the latest build Error message for Successful test connection in case of Azure and SQL Server is wrong. See attached screen shot

@ranarohitp,

I am unable to reproduce this issue. Test Connection to Azure correctly mentions the driver name. Please see the attached screenshot. And here is my support and Ubuntu Release information.

Product: Aqua Data Studio
Version: 14.0.0-beta-82
Build #: 33525
Build Date: 2013-Aug-12 07:23:24 AM
Operating Environment: Linux (3.2.0-51-generic, amd64) / UTF-8 / en / US / Sun Microsystems Inc. 1.6.0_43-b01
Ubuntu Release: Ubuntu 12.04.2 LTS

Can you please give me more details about your environment?

Is there any database specific native client library installed on your machine like iAnywhere or Oracle OCI client? If yes send me the screenshot of Help > About > JDBC Drivers tab

Aqua Data Studio 14.0.0-beta-80
Build #: 33506
Built on: 2013-Aug-08 12:57:51 PM
Operating Environment:Windows 8 64.

Is there any database specific native client library installed on your machine

Yes i have installed Sybase Central 6.1.0 (64-bit) on my machine.Attached screenshot of Help > About > JDBC Drivers tab of ADS

I am still not able to reproduce this issue. I do not have access to Windows 8 machine, so I tried to simulate the environment using Windows 7. Based on your JDBC drivers tab, I presume you did not copy sajdbc4.jar to <ADS_HOME>\lib\drivers folder. So here is what I followed

Step 1) Installed ADS

Product: Aqua Data Studio
Version: 14.0.0-beta-80
Build #: 33506
Build Date: 2013-Aug-08 12:57:51 PM

Operating Environment: Windows 7 (6.1, amd64) / Cp1252 / en / US / Sun Microsystems Inc. 1.6.0_43-b01
Memory: Max=891,092,992;  Total=384,696,320;  Free=327,651,848;  CPUs=4

Step 2) Installed Sybase Central 6.1.0 64 bit and here is my java.library.path property from Help > About > System tab.

java.library.path    C:\Users\niels\AquaProfile\ads-windows-x64-14.0.0-beta-80\Aqua Data Studio 14.0 - 64bit;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Sybase\ASE-15_0\jobscheduler\bin;C:\Sybase\ASE-15_0\dll;C:\Sybase\ASE-15_0\bin;C:\Sybase\SCC-3_2\bin;C:\Sybase\DBISQL\bin;C:\Sybase\DataAccess\ADONET\dll;C:\Sybase\DataAccess\ODBC\dll;C:\Sybase\OCS-15_0\lib3p;C:\Sybase\OCS-15_0\dll;C:\Sybase\OCS-15_0\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\MySQL\MySQL Server 5.1\bin;C:\Program Files\SQL Anywhere 12\bin64;C:\Program Files\SQL Anywhere 12\bin32;.

Step 3) Selected "Azure" server registration and tried "Test Connection". It shows me the correct status message for Azure.

Your server is accepting socket connections on tzz7eno96w.database.windows.net:1433.
 

Successfully connected to database using MS SQL Database (Azure) driver.

Can you please send me java.library.path property from Help > About > System tab. To copy, select the property and use Ctrl + C. You could also try reproducing the issue on another windows box.

java.library.path    C:\Windows\system32;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Java\jdk1.7.0_21\bin;C:\Program Files\SQL Anywhere 12\bin64;C:\Program Files\SQL Anywhere 12\Bin32;.\iany\lib;.

I presume you did not copy sajdbc4.jar to <ADS_HOME>\lib\drivers folder

No we did not copied it.

Thanks Rohit for the details. But still not able to reproduce this issue. I have requested Tariq to try reproduce this issue.

Btw, your java.library.path has multiple iAnywhere client installations. You should be able to verify the multiple installations using "Test Connection" on a server registration using "Sybase iAnywhere Driver". I configured multiple installations locally but still not able to see the issue. 

I discussed with Asif and tried the different scenarios and was not able to reproduce what Rohit is experiencing.

I am able to reproduce this issue. Here are the steps to reproduce it

1) Create a server registration with Use iAnywhere Driver

2) Select this new server and click Clone.

3) Select different database type say MS SQL Database (Azure) and change appropriate values

4) Click Test Connection, it shows the message saying connected using iAnywhere driver though it is not using it.

When doing Server clone, we were copying all attributes in the advanced panel to be consistent with older versions. So it would also copy the use iAnywhere driver property and in our connection diagnostics we were just checking whether this attribute is set or not to show iAnywhere driver message. The fix is:
   a) in case of Clone with a different db server type, not to copy use iAnywhere driver property since it is only for Sybase IQ
   b) in connection diagnostics we now check whether driver is Sybase IQ along with use iAnywhere driver property
 

Verified on ADS 14.0.0-rc-3 for Windows.