SOAPUI PRO: Using Add API throws "unable to read location" error
I am attempting to add an api through a json file into readyapi 3.2.5 so I can use it for test cases in soapui pro. But I keep getting this error below in the logs and the api doesn't get added. I've put the file in various locations (C: drive, 😧 drive, desktop) to no avail. What causes this error to occur and how can I resolve it?
Wed Jun 10 16:36:39 EDT 2020: INFO: Importing swagger C:\Program Files\SmartBear\ReadyAPI-3.2.5\memberstore.json
Wed Jun 10 16:36:39 EDT 2020: ERROR: unable to read location `C:/Program Files/SmartBear/ReadyAPI-3.2.5/memberstore.json`
Wed Jun 10 16:36:39 EDT 2020: WARN: Item [null] submitted for display, but no module could display it
Wed Jun 10 16:36:39 EDT 2020: WARN: Item [null] submitted for display, but no module could display it
Dear Rich,
Thanks much for your response. I found and applied a working solution yesterday.
That solutions resonates with what you have mentioned. What I did -
1. In Settings (readyAPI) -> JDBC . Added new Driver and Connection String Template to accommodate Oracle ServiceName (jdbc:oracle:thin:<USER>/<PASSWORD>@<HOST:127.0.0.1>:<PORT:1521>/<ODBC_DSN_NAME>) connection.
2. Since my ServiceName was containing "_" character. I received below warning and hence as suggested added the following parameter to \bin\ReadyAPI.vmoptions file.
"The character '_' is not supported in JDBC connections strings since Java 17.0.3 and since ReadyAPI 3.41.0.
Please remove the invalid characters or please try to use the JVM option -Dcom.sun.jndi.ldapURLParsing="legacy". "3. I received this error message-"java.sql.SQLException: ORA-28040: No matching authentication protocol" , so downgraded the oracle jdbc connecter jar from ojdbc14.jar to ojdbc8.jar in \bin\ext folder.
This solution worked for me and hope this solution helps someone !
Cheers,
Vikash