CreateProcess error=87, The parameter is incorrect

Question

While building with ant, I am getting the following error:

java.io.IOException: Cannot run program \"D:\\Tools\\Java\\jdk1.6.0_12\\jre\\bin\\java.exe\

Answer 1

I received this error as well, but for different cases than what is listed. I get this when attempting to execute JUnit tests in an Eclipse project whose workspace path is too long; moving the project to a shorter path resolved this issue.

Cannot run program "C:\Program Files\Java\jdk1.6.0_26\jre\bin\java.exe": (Long Project Path Path)Error: CreateProcess error=87, The parameter is incorrect

Answer 2

I faced the same problem when launching my GWT application in IBM RAD.

I tried removing duplicate jars, but it didn't solved the issue.

I have changed JRE in the project build path to point to the one which is installed in my machine (C://Program Files->java->...). Earlier it was pointing to the JRE in IBM folder(C://Program Files->IBM->SDP->JDK....)

It worked for me.

Answer 3

I found out the reason for this error,it is pointing out only to the res folder,there is an image folder inside it,it point exactly to it,I am not getting the error.

Regards Rakesh shankar.P

Answer 4

I had this error in a JenkinsFile build during git checkout. It turned out that the Jenkins node config contained an empty environment variable

Removing this empty variable solved the problem. Looks similar to what @bitoiu answered.

Answer 5

I'm encountering the same issue(at least the error and description). All SO search and google search points to the bug stated at https://bugs.eclipse.org/bugs/show_bug.cgi?id=327193 and http://www.eclipse.org/forums/index.php?t=rview&goto=494195&th=156565.

But when I try a simple change to launch the application, it works.

Previously, I'm using the way of "right click -> debug -> Java application" to start the application, and got the error.

I changed the way to manually add a debug configuration in menu "Debug -> Configurations", specify the class you want. Then click 'Debug' in the debug configurations dialog. It works...

Note that I'm using a customized IDE based on Eclipse 3.6.2.

Answer 6

In my case, removing duplicate jars solved the problem.