Hi
ssirapu,
Good spot by Rao there. It looks like you already had jre/jdk 8 installed and then installed v14 (which is totally fine...i have several versions or java on my laptop), but your config hasnt picked up your latest java install.
I found a couple of links for similar issues with ubuntu and MacOS, but id still have a look at these (despite being on different operating systems) and make the changes suggested just in case (disable the internal browser and set the additional config settings)
Internal browser
https://community.smartbear.com/t5/SoapUI-Open-Source/soapUI-startup-crash/td-p/132854Soapui-settings.xml
https://community.smartbear.com/t5/SoapUI-Pro/Failed-to-start-ReadyAPI-error-on-launch/td-p/196424You mention the Path variable i think (which youve screenshotted i think). You definitely need to update your Path variable to point to your jdk (so the OS knows where your java is), but it doesnt appear to be working which is i suspect why when you check the version the OS is looking for (via 'java -version' at command prompt) it finds v8 rather than v14, so that needs looking at, although running on v8 shouldnt be a problem.
However the big thing i noticed from your screenshot of what i think is the Path variable is that its virtually empty. The Path variable always has multiple rows in there.....i have about 20 entries....you have 2 including the latest jdk14!
Can you please screenshot the contents of your soapui-settings.xml file, your vmoptions file, contents of your Path and Classpath env variables and screenshot the list of env variables (just wondering if you have anything like java_home or jre_home set) so we can see what you have installed?
The fact that ReadyAPI! appears to suffer an exception severe enough to immediately shutdown after attempting to start means i dont think much will get written to the ReadyAPI! logs. We cant access the logging via the app obviously, but you can check the log files themselves. On my machine theyre in C://Users/Rich/.readyapi/logs
Have a look at the 'ready-api-errors.log' and 'ready-api.log' and can you also attach these to your next response.
The only alternative to checking the readyapi! logs to determine the issue is actually checking Windows Event Viewer. Its been years and years aince i used this to try and resolve a problem and even then the problem was an MS application (SQLSERVER). There might be something generated in the windows logs folder of event viewer, but i need to do a bit of research on this....i.e. an error might get written to this which indicates what the problem relates to. I dont know for certain, but i doubt event viewer will include events from readyapi!, but as i think theres a conflict with another component on your laptop, this conflicted component might cause an event to get written to the event viewer.
I'll do a bit of reading about event viewer just in case we need to resort to this.
Cheers!
Rich
