You are not logged in.

Unanswered posts



Important! This site has been replaced. All content here is read-only. Please visit our brand-new community at https://community.talend.com/. We look forward to hearing from you there!



#1 2013-12-09 22:52:24

ddctf
Member
213 posts

ddctf said:

Could not find or load main class workspace.job_1_0.job on remote comp

Hi, got this error when running an autonomous Job today

Error: Could not find or load main class workspacename.jobname_1_0.jobname

It works on my local machine when run from terminal (whether or not Talend is open), but not on another machine that doesn't have Talend on it

I have looked at other errors, doesn't look like we have any spaces in the path

Also I did look in our .Java folder /TOS_xxxxxx/workspace/.Java/classes/workspacename/

Which has a folder for each Job I have opened (tried clearing it out, but don't see how that affects the remote machine)

Does the remote machine also have a similar folder somewhere that needs clearing out?

It worked before on the remote machine – seems to have broken when I changed the workspace name by exporting and importing; seems I need to update something on the remote machine to reflect this?

Thank You smile

Last edited by ddctf (2013-12-09 23:34:39)

Offline

#2 2013-12-09 23:06:04

JohnGarrettMartin
Member
893 posts

JohnGarrettMartin said:

Re: Could not find or load main class workspace.job_1_0.job on remote comp

This kind of error is usually due to some issue in your code generator at the time of export-- Have you tried bouncing Talend and re-exporting the job to the remote machine?

Offline

#3 2013-12-09 23:10:53

ddctf
Member
213 posts

ddctf said:

Re: Could not find or load main class workspace.job_1_0.job on remote comp

Hi, what do you mean by bouncing Talend? Thanks smile

Offline

#4 2013-12-10 18:37:49

ddctf
Member
213 posts

ddctf said:

Re: Could not find or load main class workspace.job_1_0.job on remote comp

Also, the workspace name is actually all uppercase but the error showed a lower case, not sure if that matters:

Error: Could not find or load main class workspacename.jobname_1_0.jobname

Where the actual workspace name is WORKSPACENAME

Offline

#5 2013-12-13 18:59:00

ddctf
Member
213 posts

ddctf said:

Re: Could not find or load main class workspace.job_1_0.job on remote comp

Hi, still hoping to find a solution to this question

Offline

#6 2014-01-08 18:23:03

ddctf
Member
213 posts

ddctf said:

Re: Could not find or load main class workspace.job_1_0.job on remote comp

Hi, just following up

I exported the job and imported it to a fresh Talend install on another computer, then built the job and now I have two errors when attempting to run the autonomous job on the remote computer:

"myJob_run.sh: 2: cd: can't cd to ."

Also started this thread to discuss this since this one wasn't active

Offline

#7 2014-01-15 21:47:09

mairabay
Member
14 posts

mairabay said:

Re: Could not find or load main class workspace.job_1_0.job on remote comp

My problem was similar to yours: I had a project that was working (I have a linux machine). Then I did a git pull from someone else's changes (made on a windows machine). And that's when Talend started giving me the "Could not find or load main class" error.
There are no spaces anywhere.
The solution I found was to run Talend as a super user (sudo sh /home/... /launch-tos.sh)
Hope this helps others!

Offline

#8 2014-01-16 16:43:27

mairabay
Member
14 posts

mairabay said:

Re: Could not find or load main class workspace.job_1_0.job on remote comp

mairabay wrote:

My problem was similar to yours: I had a project that was working (I have a linux machine). Then I did a git pull from someone else's changes (made on a windows machine). And that's when Talend started giving me the "Could not find or load main class" error.
There are no spaces anywhere.
The solution I found was to run Talend as a super user (sudo sh /home/... /launch-tos.sh)
Hope this helps others!

I got the error below today, just a few minutes after opening talend as a non-root user.
This proves that the issue is indeed with the permissions (at least in Linux)
mini_125632_talend-error.png

Last edited by mairabay (2014-01-16 16:44:20)

Offline

Board footer

Talend Contributor Agreement - Talend Website Privacy Policy