I recently wanted to have a play around with TOS 3.1.1 so I moved existing jobs from TOS 3.0.4 to 3.1.1.
Unfortunately, jobs aren't running any more on TOS 3.1.1 and when trying to see the module list I constantly reach this error:
org.talend.designer.runprocess.ProcessorException: java.io.IOException: Cannot run program "env": CreateProcess error=2, The system cannot find the file specified
at org.talend.designer.runprocess.perl.PerlProcessor.getCommandLineByCondition(Unknown Source)
at org.talend.designer.runprocess.perl.PerlProcessor.exec(Unknown Source)
at org.talend.designer.runprocess.DefaultRunProcessService.perlExec(Unknown Source)
at org.talend.designer.runprocess.RunProcessService.perlExec(Unknown Source)
at org.talend.librariesmanager.model.service.PerlLibrariesService.checkInstalledLibraries(Unknown Source)
at org.talend.librariesmanager.model.service.AbstractLibrariesService.checkLibraries(Unknown Source)
at org.talend.librariesmanager.model.service.AbstractLibrariesService.resetModulesNeeded(Unknown Source)
at org.talend.librariesmanager.model.service.LibrariesService.resetModulesNeeded(Unknown Source)
at org.talend.librariesmanager.ui.actions.CheckModulesAction.run(Unknown Source)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
.....
I am not sure what the problem is as it is a very "TOS friendly" machine. The same jobs are still working on this machine in v3.0.4 and I used the same export/import process as I previously did numerous times. (previously did from TOS 2.2.3 to 2.2.4, to 2.3.0, to 2.3.1, to .... 3.0.3, to 3.0.4, at least 11 migrations just on this machine)
No changes to the machine either:
Win server 2003
Perl ActiveState v5.8
Java 1.6.0
Any hint on this problem?
Which operating system are you using? I know this had been fixed on Windows server 2003 but I am not sure of the status of the bug report I had created for this problem on Windows server 2008. On Windows server 2003, it had to do with Talend not being able to find the 'env' variable. I was hoping the problem would be fixed in TOS 3.2.0 ...
