Failed to start an Appium session, err was: Error: 'java -version' failed. Error: spawn ENOENT [on hold] #4229

vijay0850 · 2014-12-06T07:35:28Z

Hi Im getting these error message on Appium server please help me to resolve it.

Checking if an update is available

Update not available
Starting Node Server
info: Welcome to Appium v1.3.4 (REV c8c79a8)
info: Appium REST http interface listener started on 127.0.0.1:4723
info: [debug] Non-default server args: {"address":"127.0.0.1","logNoColors":true,"platformName":"Android","platformVersion":"18","automationName":"Appium"}
info: Console LogLevel: debug
info: --> POST /wd/hub/session {"desiredCapabilities":{"app":"D:\AndroidApps\test.apk","platformVersion":"4.2.2","platformName":"Android","deviceName":"0123456789ABCDEF","appActivity":".Main","browserName":"","appPackage":"com.test.Main"}}
info: Client User-Agent string: Apache-HttpClient/4.3.4 (java 1.5)
info: [debug] Using local app from desired caps: D:\AndroidApps\test.apk
error: Failed to start an Appium session, err was: Error: 'java -version' failed. Error: spawn ENOENT
info: [debug] Creating new appium session abc1d4ab-6f9b-4842-a856-7db52c2f0c0c
info: Starting android appium
info: [debug] Getting Java version
info: [debug] Cleaning up android objects
info: [debug] Cleaning up appium session
info: [debug] Error: 'java -version' failed. Error: spawn ENOENT
at C:\Users\elcot\Downloads\Vijay_Important\Appium\node_modules\appium\lib\devices\android\android-common.js:1033:17
at exithandler (child_process.js:633:7)
at ChildProcess.errorhandler (child_process.js:649:5)
at ChildProcess.EventEmitter.emit (events.js:95:17)
at Process.ChildProcess._handle.onexit (child_process.js:795:12)
info: [debug] Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: 'java -version' failed. Error: spawn ENOENT)","origValue":"'java -version' failed. Error: spawn ENOENT"},"sessionId":null}
info: <-- POST /wd/hub/session 500 210.506 ms - 208

The text was updated successfully, but these errors were encountered:

paymand · 2014-12-08T13:02:02Z

I think the error is pretty obvious. Either you don't have Java installed or it is not in the path. You can check that by running java -version in the terminal.

vijay0850 · 2014-12-09T03:07:10Z

Hi,

I have latest version java 8 update 25 in my PC. Still im getting the error on appium. In appium older version it working fine. Please check with this issue

vijay0850 · 2014-12-09T03:35:10Z

Im having the following setup things,

Java 8 update 25
Latest Android sdk
Appium 1.3.4.1
Installed Node.Js
Eclipse luna

All the Path are setup perfectly.But Im getting java-version error :(

paymand · 2014-12-09T11:40:56Z

Did you try running java -version in your Windows command prompt window?

vijay0850 · 2014-12-09T16:29:15Z

yes I did please see below screen shot

paymand · 2014-12-09T16:32:20Z

@sebv: any idea? (looks like spawn cannot find the Java binary)

sebv · 2014-12-09T17:39:17Z

Just check PATH and JAVA_HOME at the time when appium is running.

vijay0850 · 2014-12-09T17:48:37Z

Now I changed the Java version to 1.7. But I still gtting same issue

C:\Users\elcot>java -version
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) Client VM (build 24.71-b01, mixed mode, sharing)

C:\Users\elcot>

JAVA_HOME = C:\Program Files\Java\jdk1.7.0_71

PATH = C:\Program Files\Java\jdk1.7.0_71\bin;%ANDROID_HOME%/tools;%ANDROID_HOME%/platform-tools;C:\Program Files\nodejs\

sebv · 2014-12-09T17:49:56Z

Check the variables when and where appium is running not in a random terminal.

vijay0850 · 2014-12-09T18:01:06Z

You mean this
C:\Users\elcot\Downloads\Vijay_Important\Appium>java -version
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) Client VM (build 24.71-b01, mixed mode, sharing)

vijay0850 · 2014-12-09T18:03:40Z

In error log it showing Java 1.5

info: Client User-Agent string: Apache-HttpClient/4.3.4 (java 1.5)

info: [debug] Using local app from desired caps: D:\AndroidApps\test.apk
info: [debug] Creating new appium session 9ea241fb-f072-484d-8730-57ba33ee49ad
error: Failed to start an Appium session, err was: Error: 'java -version' failed. Error: spawn ENOENT

Shall I try with java 1.5 update?

sebv · 2014-12-09T18:04:48Z

Nope nothing to do with Java version it's the way Java is installed. Did you restart your terminal?

vijay0850 · 2014-12-09T18:05:39Z

yeap now only i restarted my pc

sebv · 2014-12-09T18:07:25Z

If you cannot figure out, just edit C:\Users\elcot\Downloads\Vijay_Important\Appium\node_modules\appium\lib\devices\android\android-common.js and add some debug line 1033:

console.log("Env-->", process.env);

brenol · 2014-12-09T18:43:39Z

Hey guys,

I started having this issue after updating Appium to 1.3.4. I am using Ubuntu 14.10.
I spent a lot of time trying to fix it but I just installed 1.2.4 via npm and it's now working.

I ran:

npm install appium
(This installs 1.3.4, had same issue as the OP)
npm uninstall appium
npm install appium@1.2.4

I also thought my Java had something wrong (spent sometime with the JAVA_HOME and update-alternatives) but it only got fixed after changing Appium version.

FYI:

$ echo $JAVA_HOME
/usr/lib/jvm/java-7-oracle
$ which java
/usr/lib/jvm/java-7-oracle/bin/java
$ java -version
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
java version "1.7.0_72"
Java(TM) SE Runtime Environment (build 1.7.0_72-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode)

Using your tip @sebv I got this from appium 1.3.4:

JAVA_HOME: '/usr/lib/jvm/java-7-oracle'

I also checked on android-common.js in 1.2.4 and I see that this functionality that looks for Java is not there, so I did not add any debug information to it. It seems I'm always falling in the if in line 1040, even though JAVA_HOME is set correctly from what I see.

Thanks!

sebv · 2014-12-09T18:51:50Z

And the %PATH% is correct?

vijay0850 · 2014-12-09T18:54:23Z

yeah as I mentioned early it was correct only

vijay0850 · 2014-12-09T18:55:31Z

info: [debug] Getting Java version

Env--> { ALLUSERSPROFILE: 'C:\ProgramData',
ANDROID_HOME: 'C:\Users\elcot\Downloads\Vijay_Important\adt-bundle-windows-x86-20140702\sdk',
APPDATA: 'C:\Users\elcot\AppData\Roaming',
CommonProgramFiles: 'C:\Program Files\Common Files',
COMPUTERNAME: 'ELCOT-PC',
ComSpec: 'C:\Windows\system32\cmd.exe',
FP_NO_HOST_CHECK: 'NO',
HOMEDRIVE: 'C:',
HOMEPATH: '\Users\elcot',
JAVA_HOME: 'C:\Program Files\Java\jdk1.7.0_71',
LOCALAPPDATA: 'C:\Users\elcot\AppData\Local',
LOGONSERVER: '\ELCOT-PC',
NODEJS: '"C:\Program Files\Nodejs"',
NUMBER_OF_PROCESSORS: '2',
OS: 'Windows_NT',
Path: 'C:\Program Files\Java\jdk1.7.0_71\bin;C:\Users\elcot\Downloads\Vijay_Important\adt-bundle-windows-x86-20140702\sdk/tools;C:\Users\elcot\Downloads\Vijay_Important\adt-bundle-windows-x86-20140702\sdk/platform-tools;C:\Program Files\nodejs;C:\Users\elcot\AppData\Roaming\npm',
PATHEXT: '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC',
PROCESSOR_ARCHITECTURE: 'x86',

vijay0850 · 2014-12-09T18:56:02Z

appium also detected the path of java sdk

sebv · 2014-12-09T19:19:28Z

Try this, need to understand why this would not work.

node -e "require('child_process').exec('java -version', function (err, stdout, stderr) { console.log(arguments); });"

vijay0850 · 2014-12-09T19:20:30Z

where at 1033 line of android common.js file?

sebv · 2014-12-09T19:21:23Z

no just from command line.

brenol · 2014-12-09T19:27:41Z

Hi @sebv,

Just ran your command but I was also debugging on my side here.

My issue is that I have a _JAVA_OPTIONS set on my /etc/environment.

When running that command on cli I got this:

{ '0': null,
'1': '',
'2': 'Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true\njava >version "1.7.0_72"\nJava(TM) SE Runtime Environment (build 1.7.0_72-b14)\nJava HotSpot(TM) >64-Bit Server VM (build 24.72-b04, mixed mode)\n' }

My problem is that on Line 1035 it gets the index from the split (the _JAVA_OPTIONS) and thats why it's not working for me.

Thanks!

vijay0850 · 2014-12-09T19:29:58Z

I got this for ur command @sebv

C:>node -e "require('child_process').exec('java -version', function (err, stdou
t, stderr) { console.log(arguments); });"
{ '0': { [Error: spawn ENOENT] code: 'ENOENT', errno: 'ENOENT', syscall: 'spawn'
},
'1': '',
'2': '' }

C:>

sebv · 2014-12-09T19:34:19Z

Try to change the java -version command to make it work, I cannot think of any reasons why this would not work.

vijay0850 · 2014-12-09T20:00:00Z

Okay no problem I will try with older version of appium. Thanks for all to replying my issues and for helpful suggestion.

vijay0850 · 2014-12-09T20:01:22Z

@brenol can u please help me to run appium in 1.2.4 version please....

brenol · 2014-12-09T20:06:38Z

@vijay0850 did you install appium using npm? I don't have a Windows environment here set up so I can't really help.

If you installed Appium using npm, then you can run this:

npm uninstall -g appium
npm install -g appium@1.2.4

I'm not sure if it'll be added to your path directly but it might.

vijay0850 · 2014-12-09T20:22:36Z

okay i will try this thanks

sebv · 2014-12-09T22:28:19Z

Thought of one thing, maybe it's a permission issue.

vijay0850 · 2014-12-10T03:44:42Z

I already tried with disabling firewall also..... :(

On Wed, Dec 10, 2014 at 3:58 AM, seb vincent notifications@github.com
wrote:

Thought of one things, maybe it's a permission issue.

—
Reply to this email directly or view it on GitHub
#4229 (comment).

Regards,

sebv · 2014-12-10T04:10:24Z

Not the firewall, the actual files permissions, or the permissions of one of the parent dirs.

vijay0850 · 2014-12-11T20:25:15Z

I gave all user permission still im getting java version failed

vijay0850 · 2014-12-14T18:14:08Z

I need solution for these issues.........

vijay0850 · 2014-12-14T18:14:33Z

need to raise new ticket again?

yahman72 · 2015-02-11T15:06:58Z

I had the same issue i.e.

when starting a session appium fails with Error: 'java -version' failed. Error: spawn ENOENT
running java -version, in the same console (= windows command prompt) where appium was running, works fine

The problem was the %PATH% variable, in addition to the JAVA_HOME it must also contain the windows system directories (i.e. %SystemRoot%\system32;%SystemRoot%), because behind the scenes appium uses something in those directories when launching java -version

mervin29 · 2015-03-11T13:13:23Z

Hi Vijay,
I faced the same issue. It got resolved by installing node.js.

stkomitov · 2015-05-25T11:06:20Z

I can confirm that adding %SystemRoot%\system32;%SystemRoot% to PATH variable solves the problem. Thank you @yahman72

beemi · 2015-06-02T21:19:01Z

By adding [%SystemRoot%\system32;%SystemRoot%] to the System PATH,issue Fixed
Thank you

canb0 · 2015-09-04T08:10:58Z

I also have the same problem.
When I run "java -version" there's no problem but when I execute cmd.exe /s /c "java -version" I got an error. I have JAVA_HOME in my PATH variable. How can I debug this problem.

"Specified path cannot be found" (sorry for mistranslation) is captured at the 1st line
I am using Windows 8.1

yahman72 · 2015-09-04T09:13:16Z

Looks like that error has nothing to do with your cmd.exe /S /c "java -version" command.
You have the same error before you have executed your command = probably there's something wrong with your windows environment/installation i.e. just google for that that "Sistem belirtilen..." error message.
For example:
http://stackoverflow.com/questions/13316682/windows-cmd-exe-the-system-cannot-find-the-path-specified

canb0 · 2015-09-04T16:31:03Z

man you're great, that was the problem. My old ansicon installation was in registry and that was the root cause.

mmcintyre123 · 2016-05-31T01:46:21Z

Hi @sebv, I'm having the same issue and at a total loss. I am on Windows 10, have both %SystemRoot%\system32 and %SystemRoot% on my PATH variable, my java location on my path variable, and JAVA_HOME defined. Yet when I try to start appium in the GUI with "Pre-Launch" application, I get

error: Could not pre-launch appium: Error: 'java -version' failed. Error: Command failed:

C:\WINDOWS\system32\cmd.exe /s /c "java -version"
'java' is not recognized as an internal or external command,
operable program or batch file.

which makes no sense to me since java -version works fine in cmd.exe:

$ java -version
java version "1.7.0_79"
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)

So I ran the command you mentioned:

$ node -e "require('child_process').exec('java -version', function (err, stdout, stderr) { console.log(arguments); });"

Which gives:

{ '0': null,
  '1': '',
  '2': 'java version "1.7.0_79"\r\nJava(TM) SE Runtime Environment (build 1.7.0_79-b15)\r\nJava HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)\r\n' }`

I just restarted my computer but still the same error. I am truly at a loss, would appreciate any help. Is it even important to run with the "Pre-Launch" application?

mmcintyre123 · 2016-05-31T02:05:54Z

Noticing this issue was closed I just created a new one - #6542. Would appreciate any help!

reddyontp · 2018-02-07T12:27:03Z

Hi One & all,
Here am getting this issue,not able to fix this issue,can anyone guide ,how to fix this issue. & what is the Cause.
info: [debug] Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: 'java -version' failed. Error: spawn ENOENT)","origValue":"'java -version' failed. Error: spawn ENOENT"},"sessionId":null}

mmcintyre123 · 2018-02-07T16:47:15Z

Did you update to the latest java jdk and jre and add both to your user path? How are you starting Appium? Also check your node version, java version, Appium version. I assume you're using Windows?

mmcintyre123 · 2018-02-07T16:48:10Z

Also confer issue #6542.

reddyontp · 2018-02-08T04:10:16Z

Dear Support Team, Good Day... 1..my java version is : [image: Inline image 1] 2.Did you update to the latest java jdk and add both to your user path? Below given one is path under system variable Answer : C:\Program Files\Java\jdk1.8.0_60\bin;F:\APPIUM Support install softwares\SDK\tools;F:\APPIUM Support install softwares\SDK\platform-tools;%SystemRoot%\system32;%SystemRoot% 3.How are you starting Appium? Ans: After Connect the device with my windows system,Make sure USB debugging ,then Start the APPIUM >after wards run the Script. 4. Node version: V8.9.1 5. Appium Version*:1.4.13.1* *6. I assume you're using Windows? : yes windows* *These are the Details,Kindly Guide Me to solve this issues ,As well kindly Provide Know issues & solutions from your end.Based on that i can Proceed further .*

…

On Wed, Feb 7, 2018 at 10:17 PM, mmcintyre123 ***@***.***> wrote: Did you update to the latest java jdk and add both to your user path? How are you starting Appium? Also check your node version, java version, Appium version. I assume you're using Windows? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4229 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AiHA2Oqo_kvV9uypxBuStPl27adfJTQjks5tSdO0gaJpZM4DFFyp> .

-- *Best Regards,* *ShowriReddy.V* *General Manager* *www.Vedaslabs.com <http://www.vedaslabs.com/>*

mmcintyre123 · 2018-02-08T16:36:08Z

I'm not Appium support - just a user offering tips. But happy to help if I can. I assume the 1.4.13.1 is the version of Appium Server your desktop client is running - is that the latest client version?

The latest desktop client is 1.3.2: https://github.com/appium/appium-desktop/releases/tag/v1.3.2. Have you tried running your tests without the GUI, i.e. from the command line with a later version of Appium Server?

The java version actually didn't show up above, can you post it in text format?

Lastly, can you post your whole (or at least more) log output like the first post above which includes the desired capabilities you are passing in?

Best,
mmcintyre123

mmcintyre123 · 2018-02-08T16:45:27Z

Your client must be out of date. Here is what the latest (1.3.2) looks like. Notice it's using Appium Server version 1.7.2:

lock · 2019-04-24T09:00:20Z

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

triager assigned jlipps Dec 6, 2014

triager added the Needs Triage bugs which are not yet confirmed label Dec 6, 2014

jlipps removed the Needs Triage bugs which are not yet confirmed label Dec 8, 2014

jlipps closed this as completed Dec 8, 2014

frbk mentioned this issue Sep 6, 2015

'java -version' failed. Error: spawn ENOENT #5564

Closed

mmcintyre123 mentioned this issue May 31, 2016

Could not pre-launch appium: Error: 'java -version' failed #6542

Closed

rajabhaskar mentioned this issue Jun 14, 2016

Couldn't launch Appium session due to Error: 'java -version' failed #6582

Closed

lock bot locked and limited conversation to collaborators Apr 24, 2019

Failed to start an Appium session, err was: Error: 'java -version' failed. Error: spawn ENOENT [on hold] #4229

Failed to start an Appium session, err was: Error: 'java -version' failed. Error: spawn ENOENT [on hold] #4229

Comments

vijay0850 commented Dec 6, 2014

paymand commented Dec 8, 2014

vijay0850 commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

paymand commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

paymand commented Dec 9, 2014

sebv commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

sebv commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

sebv commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

sebv commented Dec 9, 2014

brenol commented Dec 9, 2014

sebv commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

sebv commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

sebv commented Dec 9, 2014

brenol commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

sebv commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

brenol commented Dec 9, 2014

vijay0850 commented Dec 9, 2014

sebv commented Dec 9, 2014

vijay0850 commented Dec 10, 2014

sebv commented Dec 10, 2014

vijay0850 commented Dec 11, 2014

vijay0850 commented Dec 14, 2014

vijay0850 commented Dec 14, 2014

yahman72 commented Feb 11, 2015

mervin29 commented Mar 11, 2015

stkomitov commented May 25, 2015

beemi commented Jun 2, 2015

canb0 commented Sep 4, 2015

yahman72 commented Sep 4, 2015

canb0 commented Sep 4, 2015

mmcintyre123 commented May 31, 2016 • edited

mmcintyre123 commented May 31, 2016

reddyontp commented Feb 7, 2018

mmcintyre123 commented Feb 7, 2018 • edited

mmcintyre123 commented Feb 7, 2018 • edited

reddyontp commented Feb 8, 2018 via email

mmcintyre123 commented Feb 8, 2018

mmcintyre123 commented Feb 8, 2018

lock bot commented Apr 24, 2019

mmcintyre123 commented May 31, 2016 •

edited

mmcintyre123 commented Feb 7, 2018 •

edited

mmcintyre123 commented Feb 7, 2018 •

edited