Forum Discussion

jhobrlant's avatar
jhobrlant
New Contributor
14 years ago

MS SQL No suitable driver

I am running SoapUI 4.5 and LoadUI 2.0, both Beta. In SoapUI I have a JDBC test step against an MS SQL Server. Therefore I had to install the sqljdbc4.jar in the soapUI-4.5.0-Beta1\lib folder. It runs fine there, also as Load test.

It does not run in LoadUI. I copied the sqljdbc4.jar over to loadUI-2.0.0-beta-1\ext. It is loaded during startup:
INFO  [SoapUI] Adding [C:\Program Files\SmartBear\loadUI-2.0.0-beta-1\.\ext\sqljdbc4.jar] to extensions classpath

When running the SoapUI Runner I am getting the famous 
java.sql.SQLException: No suitable driver


Do I have to copy more files? Is it the wrong file/folder?

Joerg

Windows Server 2003 R2 SP2

3 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    14 years ago
    Hi!

    please try the following:

    1) create a groovy teststep first in your testcase
    2) add the following line:

    com.eviware.soapui.support.GroovyUtils.registerJdbcDriver( "com.microsoft.sqlserver.jdbc.SQLServerDriver" )

    (change the name of the driver class if I got it wrong...)

    This is required for the JDBC dirver to be loaded at the right place in the JDBC Classloading mechanism when running your tests in loadUI - let us know how it works out!

    regards,

    /Ole
    SmartBear Software
  • jhobrlant's avatar
    jhobrlant
    New Contributor
    14 years ago
    Hi Ole,

    I added the script in SoapUI. It is running fine there. In LoadUI the "No suitable driver" message is gone now, instead I have a TCP timeout:
    com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host npe-df-2, port 1433 has failed. Error: "Connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.".

    Both machines (Soap/LoadUI and SQL server) are in the same network, and SoapUI load test is doing well.
    Is this an authentication problem? The connection string has username and password:
    jdbc:sqlserver://npe-df-2;databaseName=Magnet_ALNS_Stage3;userName=sa;password=xxxx


    Joerg
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    14 years ago
    Hi,

    Just wanted to let you know that we've fixed this bug internally, so no workaround Groovy TestStep is required. Furthermore, the same JDBC drivers drivers that are bundled with soapUI Pro, now also comes with loadUI.

    These changes will be reflected in the upcoming 2.1 release.


    Regards

    Henrik
    loadUI team