A new session could not be created. (Original error: Requested a new session but one was in progress) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 37 milliseconds

jyotidgs1 · June 1, 2017, 11:33am

I am using Appium - 1.4.0.0
Windows- 10
Android Ver- 5.1
Device - Real MOTO G
My code : ( Very Basic to test )

package TestCase;

import java.net.MalformedURLException;
import java.net.URL;

import org.openqa.selenium.By;
import org.openqa.selenium.Platform;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.remote.BrowserType;
import org.openqa.selenium.remote.DesiredCapabilities;
import org.testng.annotations.Test;

import io.appium.java_client.android.AndroidDriver;
import io.appium.java_client.remote.MobileCapabilityType;

public class mobile_loginPage {

@Test
public void login() throws MalformedURLException{
	
	
	DesiredCapabilities capabilities1 = new  DesiredCapabilities();
	
	capabilities1.setCapability(MobileCapabilityType.BROWSER_NAME,BrowserType.CHROME);

	
	
	
	
	 capabilities1.setCapability("launchTimeout", "100000");
	 capabilities1.setCapability(MobileCapabilityType.PLATFORM,Platform.ANDROID);
	 capabilities1.setCapability(MobileCapabilityType.PLATFORM_NAME,"Android");
	 capabilities1.setCapability(MobileCapabilityType.DEVICE_NAME,"TA9330BEFX");
	 capabilities1.setCapability(MobileCapabilityType.VERSION,"5.1");
	 capabilities1.setCapability("appWaitActivity", ""); 
	 
	 URL url= new URL("http://127.0.0.1:4723/wd/hub"); 
	 
	WebDriver	driver = new AndroidDriver(url, capabilities1);
	
	driver.get("http://www.facebook.com");
	driver.findElement(By.name("email")).sendKeys("[email protected]");
	 
	// enter password
	      driver.findElement(By.name("pass")).sendKeys("xxx123");
	      driver.findElement(By.id("u_0_5")).click();
	      
	      driver.quit();
	
}

}
APPIUM Server log:

info: → POST /wd/hub/session {“desiredCapabilities”:{“appWaitActivity”:“”,“browserName”:“chrome”,“platformName”:“Android”,“launchTimeout”:“100000”,“deviceName”:“TA9330BEFX”,“version”:“5.1”,“platform”:“ANDROID”},“requiredCapabilities”:{},“capabilities”:{“desiredCapabilities”:{“appWaitActivity”:“”,“browserName”:“chrome”,“platformName”:“Android”,“launchTimeout”:“100000”,“deviceName”:“TA9330BEFX”,“version”:“5.1”,“platform”:“ANDROID”},“requiredCapabilities”:{},“alwaysMatch”:{“platformName”:“Android”},“firstMatch”:[{“browserName”:“chrome”}]}}
error: Failed to start an Appium session, err was: Error: Requested a new session but one was in progress
info: Client User-Agent string: Apache-HttpClient/4.5.3 (Java/1.8.0_102)
info: [debug] Error: Requested a new session but one was in progress
at [object Object].Appium.start (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:139:15)
at exports.createSession (C:\Program Files (x86)\Appium\node_modules\appium\lib\server\controller.js:188:16)
at Layer.handle [as handle_request] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\layer.js:82:5)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:110:13)
at Route.dispatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:91:3)
at Layer.handle [as handle_request] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\layer.js:82:5)
at C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\index.js:267:22
at Function.proto.process_params (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\index.js:321:12)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\index.js:261:10)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:100:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: Requested a new session but one was in progress)”,“origValue”:“Requested a new session but one was in progress”},“sessionId”:“9a275c68-e887-4afc-9d89-16a15e778095”}
info: ← POST /wd/hub/session 500 1.304 ms - 250

KIndly let me know how to resolve it .

wreed · June 1, 2017, 5:15pm

Your previous session did not close properly. Use the task manager to find and kill it. You can also do it from the command line:

jyotidgs1 · June 2, 2017, 10:59am

Thanks Wreed for your reply!!

I had already killed all the existing session but still i have the same error.

I am stuck with this issue.

Kindly help if any one of you have work around it…

wreed · June 2, 2017, 8:10pm

Are you saying that the computer is reporting that a process is running, but it is not in fact running? In that case you will have to reboot before BSOD.

jyotidgs1 · June 6, 2017, 9:17am

Thanks Wreed for your reply.
But the issue doesn’t seem to be related to BSOD.

@Anyone : Guys pls help, i am stuck here :

info: → POST /wd/hub/session {“capabilities”:[{“desiredCapabilities”:{“browserName”:“chrome”,“platformName”:“Android”,“version”:“5.1”,“deviceName”:“MotoG”,“platform”:“ANDROID”}},{“requiredCapabilities”:{}}],“desiredCapabilities”:{“browserName”:“chrome”,“platformName”:“Android”,“version”:“5.1”,“deviceName”:“MotoG”,“platform”:“ANDROID”},“requiredCapabilities”:{}}
info: Client User-Agent string: Apache-HttpClient/4.5.3 (Java/1.8.0_102)
Error: ENOENT, no such file or directory ‘D:\Jyoti Singh\APPIUM\Andriod SDK\android-sdk-windows\build-tools’
at Object.fs.readdirSync (fs.js:654:18)
at exports.getDirectories (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\helpers.js:100:18)
at [object Object].ADB.checkSdkBinaryPresent (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:97:25)
at [object Object].ADB.checkAdbPresent (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:134:8)
at Function.ADB.createADB (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:73:7)
at [object Object].androidCommon.initAdb (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\android-common.js:1083:9)
at C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:610:21
at C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:249:17
at iterate (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:149:13)
at async.eachSeries (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:165:9)
at _asyncMap (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:248:13)
at Object.mapSeries (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:231:23)
at Object.async.series (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:608:19)
at [object Object].ChromeAndroid.start (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\chrome.js:85:9)
at [object Object].Appium.invoke (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:285:17)
at [object Object]. (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:124:14)
at [object Object].ChromeAndroid.configure (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\chrome.js:73:3)
at [object Object].Appium.configure (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:250:15)
at [object Object]. (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:118:10)
at [object Object].Appium.start (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:129:5)
at exports.createSession (C:\Program Files (x86)\Appium\node_modules\appium\lib\server\controller.js:188:16)
at Layer.handle [as handle_request] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\layer.js:82:5)
info: [debug] The following desired capabilities were provided, but not recognized by appium. They will be passed on to any other services running on this server. : version, platform
info: Set mode: Proxying straight through to Chromedriver
info: [debug] Looks like we want chrome on android
info: [debug] Creating new appium session e71b45ed-6680-44b4-8f85-13972cee1ac8
info: [debug] Checking whether adb is present
info: ← POST /wd/hub/session 500 7.436 ms - 160
info: → POST /wd/hub/session {“desiredCapabilities”:{“browserName”:“chrome”,“platformName”:“Android”,“version”:“5.1”,“deviceName”:“MotoG”,“platform”:“ANDROID”},“requiredCapabilities”:{}}
info: Client User-Agent string: Apache-HttpClient/4.5.3 (Java/1.8.0_102)
TypeError: Cannot call method ‘removeAllListeners’ of null
at [object Object].ChromeAndroid.stop (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\chrome.js:163:21)
at [object Object].Appium.stop (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:375:15)
at [object Object].Appium.start (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:133:10)
at exports.createSession (C:\Program Files (x86)\Appium\node_modules\appium\lib\server\controller.js:188:16)
at Layer.handle [as handle_request] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\layer.js:82:5)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:110:13)
at Route.dispatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:91:3)
at Layer.handle [as handle_request] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\layer.js:82:5)
at C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\index.js:267:22
at Function.proto.process_params (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\index.js:321:12)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\index.js:261:10)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:100:14)
info: Found an existing session to clobber, shutting it down first…
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
info: Shutting down appium session
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
info: ← POST /wd/hub/session 500 2.093 ms - 101
info: → POST /wd/hub/session {“capabilities”:[{“desiredCapabilities”:{“browserName”:“chrome”,“platformName”:“Android”,“version”:“5.1”,“deviceName”:“MotoG”,“platform”:“ANDROID”}},{“requiredCapabilities”:{}}]}
error: The following desired capabilities are required, but were not provided: platformName, deviceName
info: Client User-Agent string: Apache-HttpClient/4.5.3 (Java/1.8.0_102)
error: Failed to start an Appium session, err was: Error: The following desired capabilities are required, but were not provided: platformName, deviceName
info: [debug] Got configuration error, not starting session
info: [debug] Cleaning up appium session
info: [debug] Error: The following desired capabilities are required, but were not provided: platformName, deviceName
at [object Object].Capabilities.checkValidity (C:\Program Files (x86)\Appium\node_modules\appium\lib\server\capabilities.js:145:13)
at [object Object].Appium.configure (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:238:35)
at [object Object]. (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:118:10)
at [object Object].Appium.start (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:129:5)
at exports.createSession (C:\Program Files (x86)\Appium\node_modules\appium\lib\server\controller.js:188:16)
at Layer.handle [as handle_request] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\layer.js:82:5)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:110:13)
at Route.dispatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:91:3)
at Layer.handle [as handle_request] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\layer.js:82:5)
at C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\index.js:267:22
at Function.proto.process_params (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\index.js:321:12)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\index.js:261:10)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:100:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: The following desired capabilities are required, but were not provided: platformName, deviceName)”,“origValue”:“The following desired capabilities are required, but were not provided: platformName, deviceName”},“sessionId”:null}
info: ← POST /wd/hub/session 500 2.576 ms - 314
info: → GET /wd/hub {}
info: [debug] Responding to client that we did not find a valid resource
info: ← GET /wd/hub 404 1.222 ms - 47
info: ← GET /favicon.ico 200 2.939 ms - 1150
info: → GET /wd/hub {}
info: [debug] Responding to client that we did not find a valid resource
info: ← GET /wd/hub 404 0.748 ms - 47
info: → GET /wd/hub {}
info: [debug] Responding to client that we did not find a valid resource
info: ← GET /wd/hub 404 0.475 ms - 47
info: ← GET /favicon.ico 200 0.207 ms - 1150
info: → POST /wd/hub/session {“capabilities”:[{“desiredCapabilities”:{“browserName”:“chrome”,“platformName”:“Android”,“version”:“5.1”,“deviceName”:“MotoG”,“platform”:“ANDROID”}},{“requiredCapabilities”:{}}],“desiredCapabilities”:{“browserName”:“chrome”,“platformName”:“Android”,“version”:“5.1”,“deviceName”:“MotoG”,“platform”:“ANDROID”},“requiredCapabilities”:{}}
info: Client User-Agent string: Apache-HttpClient/4.5.3 (Java/1.8.0_102)
Error: ENOENT, no such file or directory ‘D:\Jyoti Singh\APPIUM\Andriod SDK\android-sdk-windows\build-tools’
at Object.fs.readdirSync (fs.js:654:18)
at exports.getDirectories (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\helpers.js:100:18)
at [object Object].ADB.checkSdkBinaryPresent (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:97:25)
at [object Object].ADB.checkAdbPresent (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:134:8)
at Function.ADB.createADB (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:73:7)
at [object Object].androidCommon.initAdb (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\android-common.js:1083:9)
at C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:610:21
at C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:249:17
info: [debug] The following desired capabilities were provided, but not recognized by appium. They will be passed on to any other services running on this server. : version, platform
at iterate (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:149:13)
at async.eachSeries (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:165:9)
at _asyncMap (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:248:13)
at Object.mapSeries (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:231:23)
at Object.async.series (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\async\lib\async.js:608:19)
at [object Object].ChromeAndroid.start (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\chrome.js:85:9)
at [object Object].Appium.invoke (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:285:17)
at [object Object]. (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:124:14)
at [object Object].ChromeAndroid.configure (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\chrome.js:73:3)
at [object Object].Appium.configure (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:250:15)
at [object Object]. (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:118:10)
at [object Object].Appium.start (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:129:5)
at exports.createSession (C:\Program Files (x86)\Appium\node_modules\appium\lib\server\controller.js:188:16)
at Layer.handle [as handle_request] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\layer.js:82:5)
info: Set mode: Proxying straight through to Chromedriver
info: [debug] Looks like we want chrome on android
info: [debug] Creating new appium session 61d02867-1a37-4514-b00a-9de6499b0057
info: [debug] Checking whether adb is present
info: ← POST /wd/hub/session 500 2.362 ms - 160
info: → POST /wd/hub/session {“desiredCapabilities”:{“browserName”:“chrome”,“platformName”:“Android”,“version”:“5.1”,“deviceName”:“MotoG”,“platform”:“ANDROID”},“requiredCapabilities”:{}}
info: Client User-Agent string: Apache-HttpClient/4.5.3 (Java/1.8.0_102)
TypeError: Cannot call method ‘removeAllListeners’ of null
at [object Object].ChromeAndroid.stop (C:\Program Files (x86)\Appium\node_modules\appium\lib\devices\android\chrome.js:163:21)
at [object Object].Appium.stop (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:375:15)
at [object Object].Appium.start (C:\Program Files (x86)\Appium\node_modules\appium\lib\appium.js:133:10)
at exports.createSession (C:\Program Files (x86)\Appium\node_modules\appium\lib\server\controller.js:188:16)
at Layer.handle [as handle_request] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\layer.js:82:5)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:110:13)
at Route.dispatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:91:3)
info: Found an existing session to clobber, shutting it down first…
at Layer.handle [as handle_request] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\layer.js:82:5)
at C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\index.js:267:22
info: Shutting down appium session
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\index.js:261:10)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:100:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
info: ← POST /wd/hub/session 500 0.798 ms - 101
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
at next (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\express\lib\router\route.js:104:14)
info: → GET /wd/hub/status {}
info: [debug] Proxying command to null:null
info: [debug] Making http request with opts: {“url”:“http://null:null/wd/hub/status”,“method”:“GET”}
info: [debug] Responding to client with error: {“status”:13,“value”:{“message”:“An unknown server-side error occurred while processing the command.”,“origValue”:“Did not successfully proxy server command”},“sessionId”:null}
info: ← GET /wd/hub/status 500 2262.189 ms - 176
info: → GET /wd/hub/status {}
info: [debug] Proxying command to null:null
info: [debug] Making http request with opts: {“url”:“http://null:null/wd/hub/status”,“method”:“GET”}
info: [debug] Responding to client with error: {“status”:13,“value”:{“message”:“An unknown server-side error occurred while processing the command.”,“origValue”:“Did not successfully proxy server command”},“sessionId”:null}
info: ← GET /wd/hub/status 500 2253.987 ms - 176
Killed Node Server.
Node Server Process Ended

jyotidgs1 · June 6, 2017, 9:21am

In Eclipse console the error :

org.openqa.selenium.SessionNotCreatedException: A new session could not be created. (Original error: The following desired capabilities are required, but were not provided: platformName, deviceName) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds

wreed · June 6, 2017, 10:14pm

Does this directory exist? The problem could be the space in the path.

jyotidgs1 · June 7, 2017, 8:46am

Yes , you were right, directory didn’t exist.
I have change the directory and set the path accordingly.
But now the issue i am facing is
info: → POST /wd/hub/session {“capabilities”:[{“desiredCapabilities”:{“browserName”:“chrome”,“platformName”:“Android”,“version”:“5.1”,“deviceName”:“MotoG”,“platform”:“ANDROID”}},{“requiredCapabilities”:{}}],“desiredCapabilities”:{“browserName”:“chrome”,“platformName”:“Android”,“version”:“5.1”,“deviceName”:“MotoG”,“platform”:“ANDROID”},“requiredCapabilities”:{}}

info: Client User-Agent string: Apache-HttpClient/4.5.3 (Java/1.8.0_102)
info: [debug] The following desired capabilities were provided, but not recognized by appium. They will be passed on to any other services running on this server. : version, platform
info: Set mode: Proxying straight through to Chromedriver
info: [debug] Looks like we want chrome on android
info: [debug] Creating new appium session c74c51f5-75d0-427b-83c6-304fab1a6837
info: [debug] Checking whether adb is present
warn: The ANDROID_HOME environment variable is not set to the Android SDK root directory path. ANDROID_HOME is required for compatibility with SDK 23+. Checking along PATH for adb.
info: [debug] executing cmd: where adb
info: [debug] Using adb from D:\Jyoti Singh\APPIUM\Andriod SDK\android-sdk-windows\platform-tools\adb.exe

info: [debug] Using fast reset? true
info: [debug] Preparing device for session
info: [debug] Not checking whether app is present since we are assuming it’s already on the device
info: Retrieving device
info: [debug] Trying to find a connected android device
info: [debug] Getting connected devices…
info: [debug] executing cmd: “D:\Jyoti Singh\APPIUM\Andriod SDK\android-sdk-windows\platform-tools\adb.exe” devices
info: [debug] 1 device(s) connected
info: Found device TA9330BEFX
info: [debug] Setting device id to TA9330BEFX
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 5)
info: [debug] executing cmd: “D:\Jyoti Singh\APPIUM\Andriod SDK\android-sdk-windows\platform-tools\adb.exe” -s TA9330BEFX wait-for-device
info: [debug] executing cmd: “D:\Jyoti Singh\APPIUM\Andriod SDK\android-sdk-windows\platform-tools\adb.exe” -s TA9330BEFX shell “echo ‘ready’”
info: [debug] Starting logcat capture
error: Logcat capture failed: spawn ENOENT
info: [debug] Cleaning up appium session
error: Failed to start an Appium session, err was: Error: spawn ENOENT
info: [debug] Error: spawn ENOENT
at errnoException (child_process.js:988:11)
at Process.ChildProcess._handle.onexit (child_process.js:779:34)
info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: spawn ENOENT)”,“code”:“ENOENT”,“errno”:“ENOENT”,“syscall”:“spawn”,“origValue”:“spawn ENOENT”},“sessionId”:null}
info: ← POST /wd/hub/session 500 172.610 ms - 197

jyotidgs1 · June 7, 2017, 8:50am

Now, eventhough i had set path correctly…still i get the issue
Pls help…

jyotidgs1 · June 7, 2017, 1:50pm

Now i manage to overcome above issue :
But facing following issue:
A new session could not be created. (Original error: Could not proxy command to remote server. Original error: Invalid attempt to destructure non-iterable instance) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds

rickesnick · June 7, 2017, 2:04pm

Tried using the “Allow session Override” option in the appium server?

wreed · June 7, 2017, 7:06pm

Eclipse is notorious for not reading environment variables. You have to set them in Eclipse itself or tell it to specifically read them. But you must have figured this out.

I wonder if the problem is that the old version (from 2 years ago) just doesn’t work. Could you try the latest (as of this writing):

jyotidgs1 · June 8, 2017, 7:08am

Thanks for suggestion…

I had already selected “Allow session Override”…
But of no help!!

jyotidgs1 · June 8, 2017, 7:10am

@wreed

Thanks for your help…
I had upgraded Appium to 1.4.16.1
But no help…

Now, as you said will try to downlaod latest APPIUM- DESTOP version

jyotidgs1 · June 8, 2017, 11:53am

With Appium 1.4.16.1 , its working now!!

Solution: ALL i did was upgraded to 1.4.16.1 and then i was getting another issue that it was not able to create session "
Chrome was opening and abruptly getting closed with saying just “data:” in URL…

Then i, upgraded my chrome version to 58 along with that chrome driver to 2.29…
Place the same in C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win.

And it worked … Kudos!!
Thanks to Wreed and rickesnick for your help!!