Forum Discussion

Occasional Contributor

5 years ago

ReadyAPI-x64-3.2.0 does not launch in WIN10 64

Hello friends, First time installation of ReadyAPI-x64-3.2.0 does not launch or Failed to start ReadyAPI in WIN10 64 I've gone through existing solutions but didn't match to my issue. T...

Failed to start ReadyAPI error on launch

richie
5 years ago
Hi ssirapu,

The fact you say when you tried installing v3.1.0 and got the same behaviour as when you installed v3.2.0 is indicative that theres some environmental clash on your laptop.....i.e. ReadyAPI! showing no visible boot up.

I did mention this in my last but i dont think i was clear. When you try and launch ReadyAPI!, if you launch taskmanager (not taskbar), and select the processes tab, does an entry appear equating to ReadyAPI!? Im just wondering that 1. Do you get a ReadyAPI! instance appearing in taskmanager and 2. If there is anything maxing out the resource usage on your laptop. I know pre_fetch on win10 can bring disk usage up to 100% for maybe 10/15mins after boot (along with swap file usage) depending on your setup (especially if youre running an I5 processor) and so if ReadyAPI! startup is sequenced after other stuff thats maxing out your resource usage, it could take a long time to start....perhaps even 20mins (i once had a ReadyAPI! instance on a rubbish VM that took 20mins to boot), but it might still start. So wondering when you say its not starting is it just that it'll take a long time to start but still might.
Whats the spec of your laptop? RAM? processor?

Is the java run time (jdk not jre as i remember i think some groovy needs libraries available only in the jdk not the jre) you have installed 64bit as well? It is essential that the 'bit type' (sorry...dont know the correct term for this) either 64bit or x86 (32bit) of your installed java instance is the same bit type as your ReadyAPI! instance. I thought that Smartbear still made 32bit ReadyAPI! but from the page Rao supplied it doesnt appear so anymore, so just make sure your java is 64bit as well.

Finally if reinstalling hasnt helped, and the other stuff i mentioned doesnt help, id raise a support call to Smartbear (i cant provide the link cos im typing this on my phone, but the support link is at the top of the forum page) .

Hope the comments my have helped,

Rich

ssirapu

Occasional Contributor

I've downloaded Windows installer (64-bit) from the below url

https://support.smartbear.com/downloads/readyapi/

Thanks,

Srini

richie

Community Hero

5 years ago

Hi ssirapu,

The fact you say when you tried installing v3.1.0 and got the same behaviour as when you installed v3.2.0 is indicative that theres some environmental clash on your laptop.....i.e. ReadyAPI! showing no visible boot up.

I did mention this in my last but i dont think i was clear. When you try and launch ReadyAPI!, if you launch taskmanager (not taskbar), and select the processes tab, does an entry appear equating to ReadyAPI!? Im just wondering that 1. Do you get a ReadyAPI! instance appearing in taskmanager and 2. If there is anything maxing out the resource usage on your laptop. I know pre_fetch on win10 can bring disk usage up to 100% for maybe 10/15mins after boot (along with swap file usage) depending on your setup (especially if youre running an I5 processor) and so if ReadyAPI! startup is sequenced after other stuff thats maxing out your resource usage, it could take a long time to start....perhaps even 20mins (i once had a ReadyAPI! instance on a rubbish VM that took 20mins to boot), but it might still start. So wondering when you say its not starting is it just that it'll take a long time to start but still might.
Whats the spec of your laptop? RAM? processor?

Is the java run time (jdk not jre as i remember i think some groovy needs libraries available only in the jdk not the jre) you have installed 64bit as well? It is essential that the 'bit type' (sorry...dont know the correct term for this) either 64bit or x86 (32bit) of your installed java instance is the same bit type as your ReadyAPI! instance. I thought that Smartbear still made 32bit ReadyAPI! but from the page Rao supplied it doesnt appear so anymore, so just make sure your java is 64bit as well.

Finally if reinstalling hasnt helped, and the other stuff i mentioned doesnt help, id raise a support call to Smartbear (i cant provide the link cos im typing this on my phone, but the support link is at the top of the forum page) .

Hope the comments my have helped,

Rich

ssirapu
Occasional Contributor
5 years ago
Hi richie,, Thank you for coming back with suggestions.

I just noticed ReadyAPI disappear in "TaskManager" in less than few seconds.
I installed JDK (jdk-14.0.1_windows-x64_bin.exe), and set to path variable as well.

Am I missing something, please advise?

Thanks,
Srini
- nmrao
  Champion Level 3
  5 years ago
  How is it showing 1.8 when 14 is set in environment variables?
  - richie
    Community Hero
    5 years ago
    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/132854
    
    Soapui-settings.xml
    https://community.smartbear.com/t5/SoapUI-Pro/Failed-to-start-ReadyAPI-error-on-launch/td-p/196424
    
    You 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
ssirapu
Occasional Contributor
5 years ago
you are a star richie Thanks a lot

Solution:
Is the java run time (jdk not jre as i remember i think some groovy needs libraries available only in the jdk not the jre)
Yes issue has been fixed after remove default jre runtime and set to JDK.

nmraoThank you for spoting default settings