[resolved] Not able to build any Job. No directory/file is getting generated
Hi Team, While building any job, its not working. I am not even getting any error or something. I have talend open studio for data integration 6.3.0 recently installed on my machine.
Your install path contains blank spaces, specifically this folder : "TCS GE Confidentials" ; Talend does not allow that. Try to install it somewhere else without spaces in the path. You can also rename the faulty folder to "TCS_GE_Confidentials", with underscores instead of spaces.
Hi, What's OS and JDK version? Is there any error message in the log message? Which is located in <Talend Studio installation path>/workspace/.metadata/.log Best regards Sabrina
Hi,
Operating system is Window 7 64 bit SOE Release v 1.4.
and below are some lines which i can see in .log files:
!ENTRY org.talend.platform.logging 1 0 2016-12-28 12:54:47.798
!MESSAGE 2016-12-28 12:54:47,795 INFO org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory - Using NULL lifecycle mapping for MavenProject: org.talend.master.ideation:code.Master:6.3.0 @ C:\Users\974316\Documents\TCS GE Confidentials\TOS_DI-20161026_1219-V6.3.0\TOS_DI-20161026_1219-V6.3.0\workspace\.Java\pom.xml.
!ENTRY org.talend.platform.logging 1 0 2016-12-28 12:54:51.850
!MESSAGE 2016-12-28 12:54:51,847 INFO org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory - Using NULL lifecycle mapping for MavenProject: org.talend.master.ideation:code.Master:6.3.0 @ C:\Users\974316\Documents\TCS GE Confidentials\TOS_DI-20161026_1219-V6.3.0\TOS_DI-20161026_1219-V6.3.0\workspace\.Java\pom.xml.
!ENTRY org.talend.platform.logging 1 0 2016-12-28 12:54:57.568
!MESSAGE 2016-12-28 12:54:57,568 INFO org.eclipse.m2e.internal.launch.MavenLaunchDelegate - C:\Users\974316\Documents\TCS GE Confidentials\TOS_DI-20161026_1219-V6.3.0\TOS_DI-20161026_1219-V6.3.0\workspace\.Java
!ENTRY org.talend.platform.logging 1 0 2016-12-28 12:54:57.569
!MESSAGE 2016-12-28 12:54:57,569 INFO org.eclipse.m2e.internal.launch.MavenLaunchDelegate - mvn -B -s "C:\Users\974316\Documents\TCS GE Confidentials\TOS_DI-20161026_1219-V6.3.0\TOS_DI-20161026_1219-V6.3.0\configuration\maven_user_settings.xml" package -l C:/Users/974316/Documents/TCS GE Confidentials/TOS_DI-20161026_1219-V6.3.0/TOS_DI-20161026_1219-V6.3.0/workspace/.Java/lastGenerated.log -P default-settings,include-java-sources,!include-maven-resources,include-items,include-libs,include-binaries,!include-running-log4j,!include-log4j,include-contexts,!include-test-sources,!include-test-reports,!include-xmlMappings,!include-running-xmlMappings,packaging-and-assembly -DskipTests -Dmaven.main.skip=true
!ENTRY org.talend.platform.logging 1 0 2016-12-28 12:55:01.639
!MESSAGE 2016-12-28 12:55:01,639 INFO org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory - Using NULL lifecycle mapping for MavenProject: org.talend.master.ideation:code.Master:6.3.0 @ C:\Users\974316\Documents\TCS GE Confidentials\TOS_DI-20161026_1219-V6.3.0\TOS_DI-20161026_1219-V6.3.0\workspace\.Java\pom.xml.
Hi, Are you using oracle JDK 1.8? It seems that there is something wrong with your installation. Could you please try to re-install your studio 6.3 to see if it works? Make sure there is no any extra blank space in your installation path. Best regards Sabrina
Hi,
I am using open studio. and JUst downloaded zip file from talend sit and after extraction of that folder, I am simply clicking on TOS_DI-win32-x86 to open it.
I had a similar problem (with the same error log when i tried to build). Does the path of your TOS install directory contain blank spaces ?
I solved it by reinstalling my TOS in "C:/Talend/" instead of "C:/Users/QR/QR My documents/Talend DI/".
Below is path of talend directory:
C:\Users\974316\Documents\TCS GE Confidentials\TOS_DI-20161026_1219-V6.3.0\TOS_DI-20161026_1219-V6.3.0
After installing it again also. same problem i can see.
Your install path contains blank spaces, specifically this folder : "TCS GE Confidentials" ; Talend does not allow that. Try to install it somewhere else without spaces in the path. You can also rename the faulty folder to "TCS_GE_Confidentials", with underscores instead of spaces.
