Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
The solution was to delete all DI jobs in the job conductor and all job files in the server file system (generated jobs, log, ...).
I faced the similar issue with one of the jobs. It started happening ever since the job was migrated from a lower version to v7.3
Tried multiple options, including creation of a new Project, new workspace, etc. etc. whatever I could find on community blogs.
Though, then I decided to create a new job and start copying sub-jobs/flows one at a time from the old job to this new one. Every time I copied a sub-job/flow, I made a run to make sure that this flow is working. I continued in this fashion until all the flows were copied over and successfully executed. Once done, I deleted the old job that was throwing me the error and renamed this new job to the name of the old job.
This worked for me. Hopefully it helps others who are facing this issue too. Looks like something did not work as expected while migration from lower version to higher version of Talend.
Error: Could not find or load main class
I'm using the 6.4.1 DI, and I couldn't find the issue
anyone has an idea about it
Please share your thoughts
Hello @Rajendar Padam
Could you please indicate which java version you're using and please upload the log message, which is located in <Talend Studio installation path>/workspace/.metadata/.log
Best regards
Sabrina
I am using Talend Studio 8.0.1 R2023-05 with OpenJDK 11.0.2. I had been modifying and coding in my project for a few weeks without problem. Right before this problem started, I was fixing a number of discrepancies in my contexts variables. For example, I have DEV, QA and PROD environments. A previous programmer, in this project, had defined DEV, QA, PROD, plus dev, qa, and prd environments for some connections. I cleaned those up to be consistent, but must have confused Talend and got the "Error : Could not find or load main class" message. I restarted Talend Studio (which has worked in the past) - no luck. I restarted my machine and started Talend Studio - no luck. After reading the various solutions here, I decided to take Tarun's response and try something similar. I simply duplicated my main job and ran the duplicated job, and it ran fine! I then deleted the old main job and renamed the duplicated job. I didn't have to copy sub-jobs or flows, one by one, over to my new job. So, that might be an experiment to try before trying Tarun's solution above.