https://community.qlik.com/t5/Official-Support-Articles/Can-t-launch-the-CommandLine/ta-p/2150663 <DIV class="talend-tkb-migrated-content"><DIV class="lia-message-template-content-zone"> <H2>Overview</H2> <P>The commandline cannot be started. When trying to launch it, it would crash.</P> <P>&nbsp;</P> <H2>Environment</H2> <P>This behavior is occurring in version 5.3.1 and below.</P> <P>&nbsp;</P> <H2>Symptoms/Description</H2> <P>In the commandline log file you will see a specific error message (located in the <STRONG><EM>Commandline_Installation_directory</EM>/commandline-workspace/.metadata and named .log)</STRONG></P> <PRE>!ENTRY org.eclipse.core.resources 2 10035 20YY-MM-DD HH:MM:SS.XXX !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.</PRE> <P>&nbsp;</P> <H2>Resolution</H2> <P>This behavior can be resolved by:</P> <UL><LI>Renaming the current <STRONG>commandlineworkspace</STRONG> to <STRONG>commandline-workspace-back</STRONG> (for example)<BR />then</LI><LI>Re-starting the commandline</LI></UL> <P>&nbsp;</P> <H2>Related Jira Issues</H2> <P><A href="https://jira.talendforge.org/browse/TDI-25392" target="_blank">TDI-25392</A> - Have the possibility for the commandline to restart even after the corruption of its workspace</P> <P>&nbsp;</P> <H2>Bookshelf references</H2> <P>View the documentation to learn more about the commandline: <A href="https://help.talend.com/#/search/all?query=Installing+CommandLine&amp;filters=EnrichProdName%253D%2522Talend+Data+Fabric%2522%2526EnrichVersion%253D%25226.3%2522" target="_blank">Installing Commandline</A></P> </DIV></DIV> Fri, 09 Feb 2024 19:06:24 GMT TalendSolutionExpert 2024-02-09T19:06:24Z https://community.qlik.com/t5/Official-Support-Articles/Can-t-launch-the-CommandLine/ta-p/2150663 <DIV class="talend-tkb-migrated-content"><DIV class="lia-message-template-content-zone"> <H2>Overview</H2> <P>The commandline cannot be started. When trying to launch it, it would crash.</P> <P>&nbsp;</P> <H2>Environment</H2> <P>This behavior is occurring in version 5.3.1 and below.</P> <P>&nbsp;</P> <H2>Symptoms/Description</H2> <P>In the commandline log file you will see a specific error message (located in the <STRONG><EM>Commandline_Installation_directory</EM>/commandline-workspace/.metadata and named .log)</STRONG></P> <PRE>!ENTRY org.eclipse.core.resources 2 10035 20YY-MM-DD HH:MM:SS.XXX !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.</PRE> <P>&nbsp;</P> <H2>Resolution</H2> <P>This behavior can be resolved by:</P> <UL><LI>Renaming the current <STRONG>commandlineworkspace</STRONG> to <STRONG>commandline-workspace-back</STRONG> (for example)<BR />then</LI><LI>Re-starting the commandline</LI></UL> <P>&nbsp;</P> <H2>Related Jira Issues</H2> <P><A href="https://jira.talendforge.org/browse/TDI-25392" target="_blank">TDI-25392</A> - Have the possibility for the commandline to restart even after the corruption of its workspace</P> <P>&nbsp;</P> <H2>Bookshelf references</H2> <P>View the documentation to learn more about the commandline: <A href="https://help.talend.com/#/search/all?query=Installing+CommandLine&amp;filters=EnrichProdName%253D%2522Talend+Data+Fabric%2522%2526EnrichVersion%253D%25226.3%2522" target="_blank">Installing Commandline</A></P> </DIV></DIV> Fri, 09 Feb 2024 19:06:24 GMT https://community.qlik.com/t5/Official-Support-Articles/Can-t-launch-the-CommandLine/ta-p/2150663 TalendSolutionExpert 2024-02-09T19:06:24Z