Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
isari
Contributor II
Contributor II

Error on Vanilla Windows and Talend Installation

Dear Community,

 

I've been running Talend OS DI since 2018, starting from 6.5.1 (x64).

 

With a clean reinstall of Windows 10 Pro (20H2) I've decided to upgrade my setup to OS DI 7.3.1.

Problem is that, the Talend seem to be opening up,,seem to be getting module updates, designing jobs and metadata, BUT throws out NULL error on ALL jobs, even with the (default Job priorTest 0.1).

 

Here's what I've tried so far...

Create another workspace;

Update the Java to Oracle's 8U271 x64;

Switch to Zulu JDK 11.0.9.1 x64;

Install TOS 6.5.1 x64 along with 7.3.1 x64;

AND even install BOTH of these Talend SW on an external USB...

 

But in every case the outcome is this NULL error below.

 

Pls check the attached screenshots, before the the error log below:

 

java.lang.NullPointerException

at org.talend.designer.codegen.model.CodeGeneratorInternalTemplatesFactory.getTemplatesFromType(CodeGeneratorInternalTemplatesFactory.java:131)

at org.talend.designer.codegen.CodeGenerator.generateContextCode(CodeGenerator.java:387)

at org.talend.designer.core.runprocess.Processor.updateContextCode(Processor.java:704)

at org.talend.designer.runprocess.java.JavaProcessor.generateContextCode(JavaProcessor.java:1846)

at org.talend.designer.runprocess.ProcessorUtilities.generateContextInfo(ProcessorUtilities.java:1004)

at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:605)

at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:2068)

at org.talend.designer.runprocess.RunProcessContext$1.run(RunProcessContext.java:601)

at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:440)

at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:356)

at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:474)

at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:240)

at org.eclipse.ui.internal.progress.ProgressManager.run(ProgressManager.java:966)

at org.talend.designer.runprocess.RunProcessContext.exec(RunProcessContext.java:548)

at org.talend.designer.runprocess.ui.ProcessComposite.exec(ProcessComposite.java:1448)

at org.talend.designer.runprocess.ui.views.ProcessView$RunAction.run(ProcessView.java:700)

at org.talend.designer.runprocess.ui.actions.RunProcessAction.run(RunProcessAction.java:63)

at org.talend.designer.core.debug.JobLaunchConfigurationDelegate$1$1.run(JobLaunchConfigurationDelegate.java:98)

at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)

at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3919)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3550)

at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)

at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)

at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)

at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:636)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)

at org.talend.rcp.intro.Application.start(Application.java:280)

at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)

at org.eclipse.equinox.launcher.Main.run(Main.java:1501)

 

Question: What can possibly go all wrong in this setup? Could you pls guide me?

 

Thanks in advance and Regards,

 

Ilke

Labels (2)
1 Solution

Accepted Solutions
isari
Contributor II
Contributor II
Author

Ok, good news is that an expert from Algeria had helped me to find the answer with 2 hours of dedicated effort...

 

Basially, Talend did dislike the Operating System display language: It was set to Turkish both in Windows and Linux (Debian) systems and all of them had failed for no apparent reason,whereas at least 3 different Java JDK's were introduced and Java was working fine with other apps...

 

But, as soon as the OS display language is changed to English (US) Talend had started functioning again, unbelieveable!

 

@Talend, please invest in some efforts and either document or correct this functional error,so that more people may not suffer...

View solution in original post

2 Replies
isari
Contributor II
Contributor II
Author

Hello,

 

It's surprising for me to see that no one has any comments still for that issue...

 

Please mention, if I'm missing any pointers in order to get a reply from the community...

 

 

isari
Contributor II
Contributor II
Author

Ok, good news is that an expert from Algeria had helped me to find the answer with 2 hours of dedicated effort...

 

Basially, Talend did dislike the Operating System display language: It was set to Turkish both in Windows and Linux (Debian) systems and all of them had failed for no apparent reason,whereas at least 3 different Java JDK's were introduced and Java was working fine with other apps...

 

But, as soon as the OS display language is changed to English (US) Talend had started functioning again, unbelieveable!

 

@Talend, please invest in some efforts and either document or correct this functional error,so that more people may not suffer...