Hi Ralf Lemster,
Only yesterday we had the same problem, we have Studio 2019 SR2 (Build 15.2.4.1693) - Groupshare 2017
We get this error:

and not able to enabled it, we have no idea what caused it, which we did to fix the problem, in Studio, under File\Setup\Servers we removed the server connection and added it again, so if you have templates to create projects, you also have to detach the server memories in it and reattach them again. Hope this will fix your problem :)

Belkacem

Hi Ralf Lemster,
Only yesterday we had the same problem, we have Studio 2019 SR2 (Build 15.2.4.1693) - Groupshare 2017
We get this error:

and not able to enabled it, we have no idea what caused it, which we did to fix the problem, in Studio, under File\Setup\Servers we removed the server connection and added it again, so if you have templates to create projects, you also have to detach the server memories in it and reattach them again. Hope this will fix your problem :)

Belkacem

Hi everybody, this happens normally if you keep Studio open overnight. For some reason SDL changed the behavior (for security reasons, they claim), so that Studio is not able to connect to your TMs, even if you are connected with the server. You just need to close and reopen Studio.

It should work.

Kind regards,

Angelo

Thanks, Angelo - will someone from SDL confirm that?
(Leads me to the 'bug or feature' question...)

Hi there - confirmed - but we are looking at changing the interval from 12 hours (really too short) to a longer period, I think 30 days. This is what other web apps seem to be doing - Jira, Confluence, SDL community etc. Thanks, Daniel

Thanks, Daniel - I have no problem with a 30-day auto-disconnect, but this one has caused quite a lot of inconvenience in our daily GroupShare project...

How quickly can this be changed?
Cheers, Ralf

PS Bonus question: does this only affect Studio 2019 or 2017 as well?

Thanks Ralf - I need to add our product owner Maria Sarau  to give additional insight to both questions. I think it would be good to implement a "best practice" (I know it's not really appropriate to call this "best practice" but still...) to exit Studio in thee evening and restart in the morning. If everyone sticks to this policy, you won't see this problem. But I know habits are hard to change so just saying. Thanks, Daniel

Fair enough - but what do we do if we're working all night...? ;-)
Seriously: this also appears to be happening intraday if the machine was in Save Energy mode.

Hi Ralf,

I can confirm that the connection to server TM is lost after 12 hours. This has been logged with development against: CRQ-10873. And yes, it affects both Studio 2017 and Studio 2019.

Thanks,

Maria

Hi Maria, it looks like we still experience this issue in Studio 2021, what is even more annoying is that if you use templates the connection error message is showing up for each of the TMs listed in them...