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

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
jftdarr
Contributor II
Contributor II

Data Viewer not working Talend v7

OS windows 10 Enterprise

JAVA_HOME:  C:\Program Files (x86)\Talend-Studio\jre1.8.0_131

Talend Version:  7.0.1

 

Recently my Talend Jobs have started giving me an error when attempting to use data viewer or to guess schemas.  

 

The error message is:

Preview Error!
Exception in thread "main" java.lang.Error: Unresolved compilation problem:
at collibra_dd.preview_data.Preview_Data.main(Preview_Data.java:1417)

 

When loading an excel file the preview gets the following error:

Exception in thread "main" java.lang.Error: Unresolved compilation problem:

at collibra_dd.shadowfileinputtodelimitedoutput_0_1.ShadowFileInputToDelimitedOutput.main(ShadowFileInputToDelimitedOutput.java:2165)

Preview error. Some settings must be changed.
Note: Preview errors are generally due to a wrong encoding setting.
org.talend.designer.runprocess.shadow.ShadowFilePreview.preview(ShadowFilePreview.java:90)
org.talend.metadata.managment.ui.utils.ShadowProcessHelper.getCsvArray(ShadowProcessHelper.java:383)
org.talend.repository.ui.wizards.metadata.connection.files.excel.ExcelFileStep2Form$PreviewProcessor.nonUIProcessInThread(ExcelFileStep2Form.java:1042)
org.talend.commons.ui.swt.thread.SWTUIThreadProcessor$1.run(SWTUIThreadProcessor.java:74)

 

I have followed steps in other discussion threads without any success.  

 

Labels (6)
1 Solution

Accepted Solutions
jftdarr
Contributor II
Contributor II
Author

Update - I was finally able to resolve the solution by creating a new workspace and migrating the jobs over to the new workspace (after updating JAVA_HOME) and jdk.

View solution in original post

3 Replies
jftdarr
Contributor II
Contributor II
Author

@manodwhb Thank you - I tried again (I have tried those steps a few times in a few different ways and continue to have the same problem).  

jftdarr
Contributor II
Contributor II
Author

Update - I was finally able to resolve the solution by creating a new workspace and migrating the jobs over to the new workspace (after updating JAVA_HOME) and jdk.