java.io.IOException: Cannot run program "/var/lib/tomcat6/C:/Program Files/Java/jdk1.7.0_01/bin/java" (in directory "\var\lib\tomcat6\C:\Jenkins\workspace\TEST-Fitnesse-AM\Java"): CreateProcess error=123, The filename, directory name, or volume label syntax is incorrect

Jenkins JIRA | Ashok Manji | 5 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    When running a Fitnesse build on a Windows slave via a Linux master, the command to execute fitnesse is adding "/var/lib/tomcat6/" to the string. This "/var/lib/tomcat6/" string would be coming from the Linux master, but cannot figure out from where. How can I prevent this setting from being pulled across to the Windows slave? Console Output: C:\Jenkins\workspace\TEST-Fitnesse-AM>exit 0 hudson.plugins.fitnesse.FitnesseBuilder: {fitnessePortLocal=8085, fitnesseTargetPage=FrontPage, fitnesseTargetIsSuite=true, fitnessePathToJar=Java/fitnesse.jar, fitnesseJavaOpts=, fitnesseHttpTimeout=60000, fitnesseJavaWorkingDirectory=Java, fitnessePathToRoot=FitNesseRoot, fitnesseStart=True, fitnessePathToXmlResultsOut=fitnesse-result.xml} Starting new Fitnesse instance... [Java] $ "/var/lib/tomcat6/C:/Program Files/Java/jdk1.7.0_01/bin/java" -jar /var/lib/tomcat6/C:\Jenkins\workspace\TEST-Fitnesse-AM/Java/fitnesse.jar -d /var/lib/tomcat6/C:\Jenkins\workspace\TEST-Fitnesse-AM -r FitNesseRoot -p 8085 java.io.IOException: Cannot run program "/var/lib/tomcat6/C:/Program Files/Java/jdk1.7.0_01/bin/java" (in directory "\var\lib\tomcat6\C:\Jenkins\workspace\TEST-Fitnesse-AM\Java"): CreateProcess error=123, The filename, directory name, or volume label syntax is incorrect at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.<init>(Proc.java:244) at hudson.Proc$LocalProc.<init>(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) at hudson.Launcher$ProcStarter.start(Launcher.java:338) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:932) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:899) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: CreateProcess error=123, The filename, directory name, or volume label syntax is incorrect at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.<init>(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) ... 17 more Build step 'Execute fitnesse tests' marked build as failure Finished: FAILURE

    Jenkins JIRA | 5 years ago | Ashok Manji
    java.io.IOException: Cannot run program "/var/lib/tomcat6/C:/Program Files/Java/jdk1.7.0_01/bin/java" (in directory "\var\lib\tomcat6\C:\Jenkins\workspace\TEST-Fitnesse-AM\Java"): CreateProcess error=123, The filename, directory name, or volume label syntax is incorrect
  2. 0

    [JENKINS-11860] user.dir system property from master (linux) being pulled across to slave (windows) - Jenkins JIRA

    jenkins-ci.org | 11 months ago
    java.io.IOException: Cannot run program "/var/lib/tomcat6/C:/Program Files/Java/jdk1.7.0_01/bin/java" (in directory "\var\lib\tomcat6\C:\Jenkins\workspace\TEST-Fitnesse-AM\Java"): CreateProcess error=123, The filename, directory name, or volume label syntax is incorrect
  3. 0

    When running a Fitnesse build on a Windows slave via a Linux master, the command to execute fitnesse is adding "/var/lib/tomcat6/" to the string. This "/var/lib/tomcat6/" string would be coming from the Linux master, but cannot figure out from where. How can I prevent this setting from being pulled across to the Windows slave? Console Output: C:\Jenkins\workspace\TEST-Fitnesse-AM>exit 0 hudson.plugins.fitnesse.FitnesseBuilder: {fitnessePortLocal=8085, fitnesseTargetPage=FrontPage, fitnesseTargetIsSuite=true, fitnessePathToJar=Java/fitnesse.jar, fitnesseJavaOpts=, fitnesseHttpTimeout=60000, fitnesseJavaWorkingDirectory=Java, fitnessePathToRoot=FitNesseRoot, fitnesseStart=True, fitnessePathToXmlResultsOut=fitnesse-result.xml} Starting new Fitnesse instance... [Java] $ "/var/lib/tomcat6/C:/Program Files/Java/jdk1.7.0_01/bin/java" -jar /var/lib/tomcat6/C:\Jenkins\workspace\TEST-Fitnesse-AM/Java/fitnesse.jar -d /var/lib/tomcat6/C:\Jenkins\workspace\TEST-Fitnesse-AM -r FitNesseRoot -p 8085 java.io.IOException: Cannot run program "/var/lib/tomcat6/C:/Program Files/Java/jdk1.7.0_01/bin/java" (in directory "\var\lib\tomcat6\C:\Jenkins\workspace\TEST-Fitnesse-AM\Java"): CreateProcess error=123, The filename, directory name, or volume label syntax is incorrect at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.<init>(Proc.java:244) at hudson.Proc$LocalProc.<init>(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) at hudson.Launcher$ProcStarter.start(Launcher.java:338) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:932) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:899) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: CreateProcess error=123, The filename, directory name, or volume label syntax is incorrect at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.<init>(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) ... 17 more Build step 'Execute fitnesse tests' marked build as failure Finished: FAILURE

    Jenkins JIRA | 5 years ago | Ashok Manji
    java.io.IOException: Cannot run program "/var/lib/tomcat6/C:/Program Files/Java/jdk1.7.0_01/bin/java" (in directory "\var\lib\tomcat6\C:\Jenkins\workspace\TEST-Fitnesse-AM\Java"): CreateProcess error=123, The filename, directory name, or volume label syntax is incorrect
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    jdk install via jenkins doesn't work???

    Google Groups | 5 years ago | phil swenson
    java.io.IOException: Cannot run program "D:/jenkins/work/tools/jdk6/jdk.exe" (in directory "D:\jenkins\work\tools\jdk6"): CreateProcess error=87, The parameter is incorrect
  6. 0

    hg clone fails, hg pull succeeds

    Google Groups | 5 years ago | Ron
    java.io.IOException: Cannot run program "hg" (in directory "c:\jenkins\workspace\Sonar"): CreateProcess error=267, The directory name is invalid
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.io.IOException

    CreateProcess error=123, The filename, directory name, or volume label syntax is incorrect

    at java.lang.ProcessImpl.create()
  2. Java RT
    ProcessBuilder.start
    1. java.lang.ProcessImpl.create(Native Method)
    2. java.lang.ProcessImpl.<init>(Unknown Source)
    3. java.lang.ProcessImpl.start(Unknown Source)
    4. java.lang.ProcessBuilder.start(Unknown Source)
    4 frames
  3. Hudson
    Launcher$RemoteLaunchCallable.call
    1. hudson.Proc$LocalProc.<init>(Proc.java:244)
    2. hudson.Proc$LocalProc.<init>(Proc.java:216)
    3. hudson.Launcher$LocalLauncher.launch(Launcher.java:707)
    4. hudson.Launcher$ProcStarter.start(Launcher.java:338)
    5. hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:932)
    6. hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:899)
    6 frames
  4. Hudson :: Remoting Layer
    Request$2.run
    1. hudson.remoting.UserRequest.perform(UserRequest.java:118)
    2. hudson.remoting.UserRequest.perform(UserRequest.java:48)
    3. hudson.remoting.Request$2.run(Request.java:287)
    3 frames
  5. Java RT
    ThreadPoolExecutor$Worker.run
    1. java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    2. java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
    3. java.util.concurrent.FutureTask.run(Unknown Source)
    4. java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    5. java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    5 frames
  6. Hudson :: Remoting Layer
    Engine$1$1.run
    1. hudson.remoting.Engine$1$1.run(Engine.java:60)
    1 frame
  7. Java RT
    Thread.run
    1. java.lang.Thread.run(Unknown Source)
    1 frame