One Star

Problem starting Talend: Java was started but returned exit code=1

Hello,

 

I accidentally moved the TOS_BD-win-x86_64.exe file into another directory and tried running it from there and it wouldn't run.  After trying to put it back to it's rightful directory, I've been getting errors similar to this one.  

 

I'm able to open up the 32-bit exe version but not the 64-bit exe, which isn't useful for me since all my work utilizes components built up in the 64-bit version.  I've even recently tried to reinstall Talend but to no avail, and received the following message as below.  

 

I'm not sure how to proceed to correct this, nor have I been able to find a workaround to this solution that has yet to work.  

 

Can someone please help, or help guide me to a sight that help?

 

I'm running the following java version: java -version
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) Client VM (build 25.131-b11, mixed mode)

 

TOS_BD-win-x86_64 response to running .exeTOS_BD-win-x86_64 response to running .exe

1 ACCEPTED SOLUTION

Accepted Solutions
Five Stars

Re: Problem starting Talend: Java was started but returned exit code=1

Adding JAVA_HOME to system level environment variable did solve the problem.

11 REPLIES
Moderator

Re: Problem starting Talend: Java was started but returned exit code=1

Hi,

Did you have the Java run time and not the JDK? Could you please download the 64 bit JDK and installed it to see if it works?

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Five Stars

Re: Problem starting Talend: Java was started but returned exit code=1

Was there a solution to this?  I get the same message, and I have both JDK and JVM installed (for browser).

Do you look for an environment variable by name such as JAVAHOME or JAVAPATH?

Employee

Re: Problem starting Talend: Java was started but returned exit code=1

Environment variable for Java is usually JAVA_HOME.  You should check whether you have Java 1.8 32 bit or 64 bit installed.  Generally, people tend to install 32 bit JRE because of browser needs (if their browser is 32-bit).  Install the 64-bit JDK and point your JAVA_HOME to the JDK.

Make sure the search order of the JDK bin folder in the PATH appears first for the JDK.

Five Stars

Re: Problem starting Talend: Java was started but returned exit code=1

OK. I don't have JAVA_HOME, as that is no longer required in Win10.
I do have 64 bit for Oracle FMW products.
I will set and report back.
Five Stars

Re: Problem starting Talend: Java was started but returned exit code=1

Adding JAVA_HOME to system level environment variable did solve the problem.

Moderator

Re: Problem starting Talend: Java was started but returned exit code=1

Hi,


stnieman wrote:

Adding JAVA_HOME to system level environment variable did solve the problem.


Could you please mark this topic as resolved?

Many thanks!

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Five Stars

Re: Problem starting Talend: Java was started but returned exit code=1

I am looking for a way to 'resolve' the topic, but it is not obvious.  Where is the 'Accept the solution' button you mention?  

Moderator

Re: Problem starting Talend: Java was started but returned exit code=1

Hello,

The "Accept as Solution" button is right underneath user's post.

Please see my screenshot.1.png

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Five Stars

Re: Problem starting Talend: Java was started but returned exit code=1

 

 That button is does not show up.  Permissions issue?

 

Capture.PNG

 

 

Ten Stars

Re: Problem starting Talend: Java was started but returned exit code=1

Usually only the topic creator can accept a solution.
Five Stars

Re: Problem starting Talend: Java was started but returned exit code=1

That makes sense.

So much for those clock cycles poking around for a button.