Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Build Job doesn't create the file

I had imported a project from version 5.6 to 6. 
Made some changes. 
But when I try to build a job the files wasn't created. 
I've tryed to create the file in the desktop. 
Labels (2)
31 Replies
Jcs19
Creator II
Creator II

Hi Jcs19,

Is there any error log for your issue? Could you please give us more description about your current situation? The studio 6.0 hangs when you are running a job?
Best regards
Sabrina

No error logs. The job is working well in the studio but cannot be exported.
I am executing TOS_DI-win32-x86.exe
See all my screenshoots for more detail 
  0683p000009MB3N.png  0683p000009MB3S.png  0683p000009MB3X.png
0683p000009MB3c.png
0683p000009MAz8.png 0683p000009MB3h.png
So is it Java 8 problem ?!
Anonymous
Not applicable
Author

Hi Jcs19
From your screenshot, I see a 32-bit JDK has been installed on your machine. What is your Windows edition? 32-bit or 64-bit? We are not sure it is a bug or a Java 8 problem now, we need to test and confirm it with R&D team.
Best regards
Shong
Jcs19
Creator II
Creator II

Hi Jcs19
From your screenshot, I see a 32-bit JDK has been installed on your machine. What is your Windows edition? 32-bit or 64-bit? We are not sure it is a bug or a Java 8 problem now, we need to test and confirm it with R&D team.
Best regards
Shong

I have Windows 7 64 bits
Edit: I updated Java to version 51 (32bits), but I still got the same problem
Anonymous
Not applicable
Author

I am also facing the same issue.
Unable to build Job in Talend 6. I have windows 7 64 bit machine and Java JDK setup properly in Talend java preferences. 
Please let me know the resolution once you are able to find it. Thanks 0683p000009MACn.png
jcesarmn
Contributor
Contributor

Hi -
I was able to fix this issue on my side by modifying the "maven_user_setting.xml" file and adding the information for my proxy (see first screenshot) and also by updating the maven setting file location in preferences screen under maven user settings (window -> preferences -> maven -> user settings) See 2nd screenshot.
The "maven_user_settings.xml" is located in: TOS_DI-20150702_1326-V6.0.0\configuration\maven_user_settings.xml
 
jcesarmn
Contributor
Contributor

Screenshot 1
0683p000009MB3m.png 
jcesarmn
Contributor
Contributor

screenshot #2
0683p000009MAtY.png 
mgchong
Contributor III
Contributor III

Hi Guys,
Could you make sure the following are set

Installed JREs - http://screencast.com/t/pDARyjlQJRYM
Execution Environments - http://screencast.com/t/qFixl8oyNajr

Regards,
MG
Anonymous
Not applicable
Author

upgrade to 6.0.1 (data integrator)
have migrated projects
can't build any standalone job

...\.metadata\log :
!ENTRY org.eclipse.core.resources 4 2 2015-09-28 10:47:06.189
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 0
java.lang.NullPointerException
    at org.talend.core.model.process.Problem$1.run(Problem.java:132)
    at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:187)
    at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:156)
    at org.eclipse.swt.widgets.Display.syncExec(Display.java:4734)
    at org.talend.core.model.process.Problem.getEditors(Problem.java:126)
    at org.talend.core.model.process.TalendProblem.<init>(TalendProblem.java:48)     at org.talend.designer.core.ui.

To see the whole post, download it here
OriginalPost.pdf
Anonymous
Not applicable
Author

? WTF ?
Problem occured when I tried to build an imported project
I resume :
case 1.
- 6.0.1 : new blank project : build ok
case 2.
- 6.0.1 : imported project (by launcher option) from TOS-DI 5.6.2 : build KO
case 3.
- 5.6.2 : export project to file (general - archive file)
- 6.0.1 : new blank project
- 6.0.1 : import from 5.6.2 exported file : build ok
case 4.
- 6.0.1 : imported project (by launcher option) from 6.0.1 (created at case 3) : build KO
case 5.
- 6.0.1 : export project to file (general - archive file)
- 6.0.1 : new blank project
- 6.0.1 : import from 6.0.1 exported file : build ok
So this means, build is always KO after an import by launcher option, of
- 5.6.2 project
- 6.0.1 project imported from exported file from 5.6.2