Forum Discussion
r3nrut
14 years agoOccasional Contributor
I've run into this issue today when trying to invoke testrunner using suites that require a JDBC driver. My test cases run fine when running using the soapUI interface but fail using testrunner.
I can tell that the sqljdbc4.jar has been added to the extensions classpath so I'm not understanding the message that is returned.
INFO [SoapUI] Adding [\SmartBear\soapUI-Pro\bin\ext\sqljdbc4.jar] to extensions classpath
16:25:33,143 ERROR [SoapUI] An error occured [No suitable driver], see error log for details
--> java.lang.ClassNotFoundException: com.microsoft.sqlserer.jdbc.SQLServerDriver
I know for a fact that the driver is correct and has worked a thousand times before. Is this a bug in the testrunner code?
I've also read that you have to provide the fully qualified path to testrunner.bat which I have also done and I'm still experiencing this issue.
halp!
I can tell that the sqljdbc4.jar has been added to the extensions classpath so I'm not understanding the message that is returned.
INFO [SoapUI] Adding [\SmartBear\soapUI-Pro\bin\ext\sqljdbc4.jar] to extensions classpath
16:25:33,143 ERROR [SoapUI] An error occured [No suitable driver], see error log for details
--> java.lang.ClassNotFoundException: com.microsoft.sqlserer.jdbc.SQLServerDriver
I know for a fact that the driver is correct and has worked a thousand times before. Is this a bug in the testrunner code?
I've also read that you have to provide the fully qualified path to testrunner.bat which I have also done and I'm still experiencing this issue.
halp!