Contributions
Errors setting up project JDBC connection
I'm having some problems trying to set up a connection to a MS SQL database. I registered a database at project level using drivercom.microsoft.sqlserver.jdbc.SQLServerDriverand successfully tested the connection. Testing the connection from Configuration Connection in a new JDBC connectionfails with a pop-up message containing:com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'x'.ClientConnectionId:aae75905-259a-45cf-a62a-7df67cddd431.As of this morning, in a new JDBC request the same database connection is listed twice in the Configuration Connection drop-down for some unknown reason. An error also appears in the Ready! API logThe JDBC driver [com.microsoft.sqlserver.jdbc.SQLServerDriver] is already registered.when testing the connection (successful or unsuccessful) from the project database level or JDBC request step level. If I select <None> from the Configuration Connection drop-down and replace the PASS_VALUE with the actual password in the connection string then the connection tests successfully and I can view the tables in the database, but I don't really want to be doing this for a number of reasons. The Ready! API log still reports the same error as noted above though, but it doesn't seem to affect the functionality of the step. Edit: Since writing this a moment ago, I have noticed something else odd: I set up a new JDBC connection at project level and selected the same driver (com.microsoft.sqlserver.jdbc.SQLServerDriver), I successfully tested the connection, then visited the JDBC step to try this new connection. When I select this new connection the driver selected isweblogic.jdbc.mssqlserver4.Driverand as this is greyed out I have no control over this selection. Any help appreciated, Thanks8 years agoPlace ReadyAPI QuestionsReadyAPI Questions782Views0likes0CommentsRe: Lots of errors in log from Test Suite and in TestRunner
Yesterday a pop-up message was alerting me to failures but this morning the pop-up shows a 'Execution finished successfully' and I get the XML output I was expecting. So from what I can see, there is nothing stopping me from running these tests using Launch TestRunner - I'm still seeing a bunch of errors but at least my tests are successfully running now. The other errors in the general logs also appear to have gone this morning too; obviously a dodgy environment. Thank you1.2KViews0likes0CommentsLots of errors in log from Test Suite and in TestRunner
Hello, I've only been using SoapUI for a few days but I'm getting a lot of error messages that I can't seem to resolve; Test Suite: I've created a few testREST requests and added them to a test suite, but when I just click on a test step it adds errors to the error log that I don't know how to resolve and can't find anything useful when searching the internet. An extract is in attached file 1.txt: TestRunner: I don't know if any of these are related to TestRunner, but when I launch this I get what is in attached file 2.txt: It looks like I have files missing, or it's maybe struggling to create the files, but if anybody is able to help me resolve some of these errors it would be greatly appreciated. From what I can see, this doesn't seem to affect the running of the test suite when I set this to run from the GUI, so my next question is: does any of the above really matter? I will be venturing into Groovy Scripts in the next few days in case this makes a difference... Thanks1.3KViews0likes2Comments