Permanent restart request

[Anonymous]

Hi,
I installed TOS_DI-20151214_1327-V6.1.1 . I changed default workspace to C:\Users\myuser\talend and restarted it. I launched TOS and exit, then I opened it again. I'm getting restart request every time I opened talend.
  

I've noticed that properties in connection_user.properties doesn't change value.
I have Windows 7 Pro 64bit

[Anonymous]

Hi 
Where is connection_user.properties file? Can you try to close studio, delete the workspace and restart it again to see if the problem still exists?

[Anonymous]

Hi,
There is connection_user.properties but it looks like don't change values. When I change workspace to some other location it changes only timestamp in 1st line. Is there some way to decode values from this file? 
I've installed TOS from zip file in my C:\bin\TOS_DI-20151214_1327-V6.1.1
My workspace is in C:\Users\my_user\talend

[Anonymous]

I too am having the same issue with this version 6.1.1.20151214_1327 except I'm using operating system Ubuntu 14.04 64 bit.
My Talend DI executable folder is /home/rod/TOS
My Workspaces folder is /home/rod/TOSWorkspaces
Every time I start Talend it says "workspace has changed. please restart".
When I click restart my Projects show up ok and jobs load fine.

Java -version 
java version "1.8.0_72"
Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)

[gorotman]

Hi,
I've the same problem too.....
Did someone find a solution?
Update 07/03/2016:
Test done:
- start with new workspace folder
- uncheck asking for workspace on startup
- re-check asking for workspace on startup
- changed permission on installation folder (writing is enable)
- rename workspace folder to simpler, shorter label (then switch between them)
Nothing, tos still recongnizes that workspace is changed and asks for a restart. 😞

[vmunene]

I have the same issue with TOS_DI-20160217_1258-V6.2.0M2 on Centos.
Any luck with finding a workaround?

[vmunene]

The problem seems to related to the working directory that the executable is found.  The workaround I use is to create a sym link to the executable in the folder that I want the workspace in, that way it creates a new workspace in the folder.  Its crude but works.

[gorotman]

I created a ticket for this problem:
https://jira.talendforge.org/browse/TDI-35601

[gorotman]

There already was a ticket "Workspace changed ... restart" on every startup of TOS
It will be fixed in 6.1.2 and 6.2.1 (they wrote it)....
Bye