Export job in v5.0 not working?

One Star

Export job in v5.0 not working?

We are test driving v5.0 and have found a problem.
After creating and successfully testing a job, we are unable to export the job.
Right-click on the job, select "Export Job". Changing the archive directory to c:\test (a directory we are sure we have permissions to). Click Finish.
Progress window does not indicate any errors. No zip file is generated.
Any suggestions? We need the export for deployment purposes.
One Star

Re: Export job in v5.0 not working?

Hi
I have exported several jobs in TOS 5.0.0 and they all work.
How many times did you reproduce this issue?
Could you show me more details? OS version, 32bit or 64 bit.
A screenshot about Export Settings is preferred.
Best regards!
Pedro
One Star

Re: Export job in v5.0 not working?

Pedro
I can consistently reproduce the issue.
I'm running Windows7 Ultimate 32 bit.
I tested my job - the output was correctly written to the c:\test directory, so I know we have proper permissions for the directory.
I run the export job utility - screenshot attached. The messages indicate all is going well, then the message window goes away.
No zip in the output directory.
Screenshot of the job also attached.
Please advise.
One Star

Re: Export job in v5.0 not working?

Hi
It's a bug. You may create issue at bugtracker.
http://jira.talendforge.org/secure/Dashboard.jspa
Best regards!
Pedro

Re: Export job in v5.0 not working?

could you start Talend from the command-line with debug turned on?
like
open a CMD on the folder where you have your Talend installation and run:
Talend-v5.exe -debug
changing Talend-v5.exe with correct name for your installation.
One Star

Re: Export job in v5.0 not working?

I ran Talend from the command line as suggested. Exported the job with the same settings. The progress window said it was finalizing the build, then there was a brief window that said the export was successful, then both windows went away. No zip in the output directory.
Is there a logfile we can examine?
One Star

Re: Export job in v5.0 not working?

I used to have the same problem, and after launching Talend in debug mode, i noticed that an error occured while trying to read a .bat file in Talend home directory, after giving approriate rights to the user on Talend Home directory the problem gets solved.
Here is the error :
>FULL BUILD STATS for: .Java
> compiled 37871 lines in 1853ms:20437.6lines/s
> parse: 174 ms (9.3%), resolve: 1423 ms (76.7%), analyze: 52 ms (2.8%), gener
ate: 98 ms (5.2%)
ERROR: C:\Program Files (x86)\TOS_DI-Win32-r74687-V5.0.1\newjarFolder\Initialisa
tion_0.1\Initialisation\Initialisation_run.bat (Access denied)
java.io.FileNotFoundException: C:\Program Files (x86)\TOS_DI-Win32-r74687-V5.0.1
\newjarFolder\Initialisation_0.1\Initialisation\Initialisation_run.bat
One Star

Re: Export job in v5.0 not working?

Hi COxalass
Thank you for your sharing. Smiley Wink
Regards,
Pedro

Re: Export job in v5.0 not working?

Hi Pedro,
Could you help me out with this error. I ran TOS in debug mode and while i was exporting job this error was found. Please see image.

Regards
Asif
One Star

Re: Export job in v5.0 not working?

In Windows 7, rather than user having permissions, programs are needed to have the permissions to write over the selected location, due to the UAC settings of the OS. That happened to me before when I tried to write an archive on some Program Files location, have you checked to run the TOS as an administrator (don't mean administrator account)? You can do this by right clicking the application, and click the "Run as an administrator" option.

Re: Export job in v5.0 not working?

Yes, It worked with proper rights

Thanks Smiley Happy
One Star

Re: Export job in v5.0 not working?

Thank you for the replies in this thread, I had the exact same problem and giving the proper rights was indeed THE way of fixing this issue.
One Star

Re: Export job in v5.0 not working?

Thanks for the tip about running with -debug.
Another cause for this error can be a long file name, using 5.2.0.
My debug claimed the "filename, directory name or drive letter was invalid".
I shortened the name of my zip file, which helped...