Failed to start an Appium session, err was: Error: Didn't know what to do with response code 404

Issues/Bugs
1

Fail to create appium session… Tried all possible combination with Appium version- 1.3.7.2 and 1.4.0
With emulator and actual device. Same issue. Please help!!!

Log:

2015-08-18 16:41:32:522 - warn: Appium support for versions of node < 0.12 has been deprecated and will be removed in a future version. Please upgrade!
2015-08-18 16:41:32:652 - info: Welcome to Appium v1.4.0 (REV 8f63e2f91ef7907aed8bda763f4e5ca08e86970a)
2015-08-18 16:41:32:653 - info: Appium REST http interface listener started on 127.0.0.1:4723
2015-08-18 16:41:32:654 - info: [debug] Non-default server args: {“address”:“127.0.0.1”,“sessionOverride”:true,“fullReset”:true,“log”:“C:\users\raiak.auth\Desktop\test.log”,“logNoColors”:true,“platformName”:“Android”,“platformVersion”:“19”,“automationName”:“Appium”}
2015-08-18 16:41:32:655 - info: Console LogLevel: debug
2015-08-18 16:41:32:655 - info: File LogLevel: debug
2015-08-18 16:42:26:758 - info: --> POST /wd/hub/session {“desiredCapabilities”:{“browserName”:“Browser”,“platformName”:“Android”,“deviceName”:“emulator-5554”,“launchTimeout”:“300000”,“newCommandTimeout”:“300”,“platformVersion”:“4.4.2”}}
2015-08-18 16:42:26:760 - info: Client User-Agent string: Apache-HttpClient/4.3.6 (java 1.5)
2015-08-18 16:42:26:761 - info: Set mode: Proxying straight through to Chromedriver
2015-08-18 16:42:26:762 - info: [debug] Looks like we want chrome on android
2015-08-18 16:42:26:762 - info: [debug] Creating new appium session 90b8b984-3870-4654-8801-6de88b9a1a24
2015-08-18 16:42:26:764 - info: [debug] Checking whether adb is present
2015-08-18 16:42:26:766 - info: [debug] Using adb from C:\Users\raiak.AUTH\AppData\Local\Android\sdk\platform-tools\adb.exe
2015-08-18 16:42:26:766 - info: [debug] Using fast reset? false
2015-08-18 16:42:26:766 - info: [debug] Preparing device for session
2015-08-18 16:42:26:766 - info: [debug] Not checking whether app is present since we are assuming it’s already on the device
2015-08-18 16:42:26:766 - info: Retrieving device
2015-08-18 16:42:26:767 - info: [debug] Trying to find a connected android device
2015-08-18 16:42:26:767 - info: [debug] Getting connected devices…
2015-08-18 16:42:26:768 - info: [debug] executing cmd: C:\Users\raiak.AUTH\AppData\Local\Android\sdk\platform-tools\adb.exe devices
2015-08-18 16:42:26:847 - info: [debug] 1 device(s) connected
2015-08-18 16:42:26:848 - info: Found device emulator-5554
2015-08-18 16:42:26:848 - info: [debug] Setting device id to emulator-5554
2015-08-18 16:42:26:849 - info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 5)
2015-08-18 16:42:26:849 - info: [debug] executing cmd: C:\Users\raiak.AUTH\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 wait-for-device
2015-08-18 16:42:26:900 - info: [debug] executing cmd: C:\Users\raiak.AUTH\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 shell “echo ‘ready’”
2015-08-18 16:42:27:008 - info: [debug] Starting logcat capture
2015-08-18 16:42:27:124 - info: [debug] Set chromedriver binary as: C:\Program Files (x86)\Appium\node_modules\appium\build\chromedriver\windows\chromedriver.exe
2015-08-18 16:42:27:125 - info: Set chromedriver binary as: C:\Program Files (x86)\Appium\node_modules\appium\build\chromedriver\windows\chromedriver.exe
2015-08-18 16:42:27:125 - info: [debug] Pushing unlock helper app to device…
2015-08-18 16:42:27:126 - info: [debug] executing cmd: C:\Users\raiak.AUTH\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 install “C:\Program Files (x86)\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk”
2015-08-18 16:42:32:759 - info: [debug] executing cmd: C:\Users\raiak.AUTH\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 shell “dumpsys window”
2015-08-18 16:42:32:992 - info: [debug] Screen already unlocked, continuing.
2015-08-18 16:42:32:992 - info: [debug] Forwarding system:4724 to device:4724
2015-08-18 16:42:32:993 - info: [debug] executing cmd: C:\Users\raiak.AUTH\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 forward tcp:4724 tcp:4724
2015-08-18 16:42:33:060 - info: [debug] Pushing appium bootstrap to device…
2015-08-18 16:42:33:061 - info: [debug] executing cmd: C:\Users\raiak.AUTH\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 push “C:\Program Files (x86)\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/
2015-08-18 16:42:33:170 - info: Starting App
2015-08-18 16:42:33:171 - info: [debug] Attempting to kill all ‘uiautomator’ processes
2015-08-18 16:42:33:171 - info: [debug] Getting all processes with ‘uiautomator’
2015-08-18 16:42:33:171 - info: [debug] executing cmd: C:\Users\raiak.AUTH\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 shell “ps ‘uiautomator’”
2015-08-18 16:42:33:357 - info: [debug] No matching processes found
2015-08-18 16:42:33:357 - info: [debug] Running bootstrap
2015-08-18 16:42:33:358 - info: [debug] spawning: C:\Users\raiak.AUTH\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap -e pkg com.android.browser -e disableAndroidWatchers false
2015-08-18 16:42:36:253 - info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
2015-08-18 16:42:36:267 - info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
2015-08-18 16:42:36:280 - info: [debug] [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
2015-08-18 16:42:36:292 - info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
2015-08-18 16:42:36:292 - info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
2015-08-18 16:42:36:292 - info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
2015-08-18 16:42:36:292 - info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
2015-08-18 16:42:36:302 - info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
2015-08-18 16:42:36:453 - info: [debug] [BOOTSTRAP] [debug] Socket opened on port 4724
2015-08-18 16:42:36:460 - info: [debug] [BOOTSTRAP] [debug] Appium Socket Server Ready
2015-08-18 16:42:36:461 - info: [debug] Pushing command to appium work queue: [“getDataDir”,{}]
2015-08-18 16:42:36:515 - info: [debug] [BOOTSTRAP] [debug] Loading json…
2015-08-18 16:42:36:516 - info: [debug] [BOOTSTRAP] [debug] Registered crash watchers.
2015-08-18 16:42:36:529 - info: [debug] [BOOTSTRAP] [debug] Client connected
2015-08-18 16:42:36:547 - info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“getDataDir”,“params”:{}}
2015-08-18 16:42:36:552 - info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
2015-08-18 16:42:36:570 - info: [debug] [BOOTSTRAP] [debug] Got command action: getDataDir
2015-08-18 16:42:36:570 - info: [debug] [BOOTSTRAP] [debug] Returning result: {“value”:"/data",“status”:0}
2015-08-18 16:42:36:574 - info: [debug] dataDir set to: /data
2015-08-18 16:42:36:577 - info: Killing any old chromedrivers, running: FOR /F “usebackq tokens=5” %a in (netstat -nao ^| findstr /R /C:"9515 ") do (FOR /F “usebackq” %b in (TASKLIST /FI "PID eq %a" ^| findstr /I chromedriver.exe) do (IF NOT %b=="" TASKKILL /F /PID %a))
2015-08-18 16:42:36:706 - info: No old chromedrivers seemed to exist
2015-08-18 16:42:36:706 - info: Spawning chromedriver with: C:\Program Files (x86)\Appium\node_modules\appium\build\chromedriver\windows\chromedriver.exe --url-base=wd/hub --port=9515
2015-08-18 16:42:36:750 - info: [CHROMEDRIVER STDOUT] Starting ChromeDriver 2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf) on port 9515
Only local connections are allowed.
2015-08-18 16:42:36:754 - info: Proxying [GET /status] to [GET http://127.0.0.1:9515/wd/hub/status] with no body
2015-08-18 16:42:36:846 - info: Got response with status 404:

Not Found <...

2015-08-18 16:42:40:274 - info: Proxying [GET /status] to [GET http://127.0.0.1:9515/wd/hub/status] with no body
2015-08-18 16:42:40:353 - info: Got response with status 404:

Not Found <...

2015-08-18 16:42:41:988 - info: Proxying [GET /status] to [GET http://127.0.0.1:9515/wd/hub/status] with no body
2015-08-18 16:42:42:069 - info: Got response with status 404:

Not Found <...

2015-08-18 16:42:42:588 - info: [debug] Cleaning up appium session
2015-08-18 16:42:42:589 - error: Failed to start an Appium session, err was: Error: Didn’t know what to do with response code 404
2015-08-18 16:42:42:589 - info: [debug] Error: Didn’t know what to do with response code 404
at JWProxy.command$ (lib/proxy.js:152:11)
at tryCatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:67:40)
at GeneratorFunctionPrototype.invoke [as _invoke] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:231:22)
at GeneratorFunctionPrototype.Gp.(anonymous function) [as next] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:264:19)
at tryCatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:67:40)
at GeneratorFunctionPrototype.step (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\babel-runtime\regenerator\runtime.js:116:22)
at lib$es6$promise$$internal$$tryCatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\es6-promise\dist\es6-promise.js:319:16)
at lib$es6$promise$$internal$$invokeCallback (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\es6-promise\dist\es6-promise.js:331:17)
at lib$es6$promise$$internal$$publish (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\es6-promise\dist\es6-promise.js:302:11)
at Object.lib$es6$promise$asap$$flush [as _onImmediate] (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\es6-promise\dist\es6-promise.js:113:9)
at processImmediate [as _immediateCallback] (timers.js:330:15)
2015-08-18 16:42:42:590 - info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: Didn’t know what to do with response code 404)”,“origValue”:“Didn’t know what to do with response code 404”},“sessionId”:null}
2015-08-18 16:42:42:630 - info: <-- POST /wd/hub/session 500 15868.312 ms - 212

2

simple code snippet:
baseUrl=“www.google.com”;
device=“Android”;
deviceName=“emulator-5554”;
platformName=“Android”;
version=“4.4.2”;

	   DesiredCapabilities capabilities = new DesiredCapabilities();
	   capabilities.setCapability(MobileCapabilityType.BROWSER_NAME,MobileBrowserType.BROWSER);
	   capabilities.setCapability(MobileCapabilityType.DEVICE_NAME,deviceName);
	   capabilities.setCapability(MobileCapabilityType.PLATFORM_VERSION,version);
	   capabilities.setCapability(MobileCapabilityType.LAUNCH_TIMEOUT,"300000");
	   capabilities.setCapability(MobileCapabilityType.NEW_COMMAND_TIMEOUT,"300");

			  driver = new AndroidDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);

driver.manage().timeouts().implicitlyWait(10,TimeUnit.SECONDS);
driver.manage().timeouts().pageLoadTimeout(60,TimeUnit.SECONDS);
driver.get(baseUrl);