JRE home environment variable

Hello,
I just downloaded the Community version .zip from the Camunda website. Extracted it and then started up the start-camunda.bat file. It launches but I get the error: “The JRE_HOME environment variable is not defined correctly” message in a command prompt window.

I have verified that the Environment variables are exactly what they need to be for Windows 7 64 bit: C:\Progra~2\Java\jre1.8.0_211

Additionally, the apache log folder has no log files.

The site can’t be reached.
I am not sure what I may be missing. Any help is greatly appreciated.

Thanks.
J.

@jmalik refer this post,it might be helpful for your issue. Instead of jre try referring to jdk path.

Windows Installation fails

@aravindhrs

I knew about that possible fix but that did not fix it because my Java folder is name ‘JRE’ in Windows 7… If I change the path, it is not going to find the folder. I tried changing the path anyways for kicks, obviously didn’t work.

Does anyone else have any other ideas?

It’s a clean install. It used to work on this system and then this test system was moved from outside the firewall to within the firewall so I could test it in production. Since the move, it has stopped working.

Thanks.
J.

image Here’s the error. The system is Windows Pro 7 64bit.

The JRE path… C:\Program Files (x86)\Java\jre1.8.0_221 which translates to C:\Progra~2\Java\jre1.8.0_211 within the Environment variables. image

  1. First check whether you configured JAVA_HOME or JRE_HOME properly by launching the command prompt.
  2. For example, if you like to use JRE_HOME in windows, type SET JRE_HOME, it will display the path where JRE is available.
    image
  3. Launch the Camunda Server,another command prompt will be launched.
    image
  4. Welcome page will be displayed.

Camunda finally launched and is working. The issue I realized was there were two Java folders. One in \Program Files\ and the other in \Progra~2\ and the environment variable was pointing to the \Progra~2\ instance while it was looking for the other instance.
Anyways, after re-pointing the environment variable to the other Java folder fixed the issue.

A quick search on the web yielded that this is how Java is installed because diff. programs look for Java in one of those two different places. So Beware!

I really appreciate everyone’s input for assistance.
Thank you!
J.