• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 21 replies
  • Answers 1 answer
  • Subscribers 437 subscribers
  • Views 2467 views
  • Users 0 members are here
Options
Related

New Trados 2024 SR1 - automatically changing Groupshare project names (locally, not on the server)

Mateusz Fatek

I have recently installed the new SR1 18.1.2.6370 upgrade and I immediately started having major issues.

All my server project names (on Groupshare 2017, which up until the update worked like a charm) suddently started... changing locally on my machine. When I download a server project from my server, it appears on my project list normally (initally). But then, after a second or two, it changes - and takes the name of the first server project on my list. If I have 20 server projects, all have identical names now.

To reiterate - when I download a server project, initially everything is just fine. The problems appears only after a few seconds. No matter if I download projects or if I create them myself - after a second or two of being on the list, all server projects change names. This happens for both my personal GS 2017 server and Groupshares from my clients (they use newer GS versions). This also happens if I manually change project names - after a second from the change they revert to the erroneously-assumed name, too. This means I cannot change the name of any server project at all.

This does not seem to affect local projects for some reason - those work normally. Until I publish them to the server - at which point they do change their names after a second or two, too.

I tried reinstalling Studio, I tried uninstalling and manually installing it again. For some reason SR1 stopped working as a Groupshare compatible tool for me. Has anyone else experienced this? Is there a workaround for this?
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0 in reply to Philippe Druart

    Oh, that is worrisome - that GS 2020 does not work with SR1, too? That is proposterous to me.
    We decided to use SR1 with GS 2017 since we do not havbe that many projects there and this error does not affect project names on the server's side (everything in GS looks normal, translators get proper project names on their end - and it probably is the same with GS 2020). We simply use the project's folder's path as reference which project is which - this helps (a suggestion). So even if you have a lot of project names, using the project file path helps and allows identifying everything.

    My observation is, however, that if you try to make any changes to project settings (in the case of GS projects), initially you do get a disconnection error. But after two or three attempts to reconnect, everything connects properly, settings do get updated and propagated further along to linguists working on their projects. So ultimately this issue should be resolvable, because it is a BUG, and not a CRITICAL error, but I am not certain if RWS will ever get to fixing it...
    emoji