• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 21 replies
  • Answers 1 answer
  • Subscribers 437 subscribers
  • Views 2452 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 Jerzy Czopik

    Except Studio 2024 works just fine with GroupShare. Just not the latest version. The newest SR suddently causes a series of issues, and the product documentation does not mention GS 2017 as incompatible. It is yellow, as in "there might be some issues", not red in the compatibility table. And up until the latest large update, everything worked just fine - synchronization worked fine, project names, publishing, downloading etc. Now none of those features work - and I do not know or understand why. Except to make people either buy newer GS (which will not be the case with us) or this is the result of not testing back-compatibility.

    Either way, we will not be purchasing the new GS for several dozens of thousands of euro, NOR will be ever be upgrading the current Studio 2024 to anything newer. With this single decision to make the old GS 2017 incompatible, RWS made us resign from the whole environmental after 15 years of using it exclusively...
    emoji
  • 0 in reply to Mateusz Fatek

     

    I understand your frustration, however, in my case TS2024 works fine with GS2021.

    The situation is quite similar to what happened to leaded fuel in the past. You may not remember that, but at some point leaded fuel was prohibited and owner of older cars were forced to switch to newer ones. Your Studio is now nearly 10 years old...

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

    emoji
  • 0 in reply to Jerzy Czopik

    In my particular case, I don't know whether the projects that I work on have been created with GS17. I work as a freelancer and receive projects from PMs through GroupShare. I recently installed Trados 2024 on a new laptop and the new SR1 version was installed by default. This is when the issue started but it does not look like I can do much to fix it on my end, which is frustrating and time-consuming since I normally work on several Trados projects at the same time for different clients.
    emoji
  • 0 in reply to Jesse Good

      

    Just a quick note that it's a good idea to not leave posts marked with verified answers if they are not actually resolved because nobody will look at them!

    But let me just summarise this first to make sure I have it right, and then I can report this for clarification (which I'll do in the next post).

    The Core Problem

    A reported bug in this thread concerning Trados Studio 2024 SR1 (18.1.2.6370) that causes GroupShare project names to duplicate locally, making it impossible to manage multiple projects.  Subsequent updates (CU1/CU2) have introduced a secondary issue, causing the termbase/glossary connection to become unstable or non-functional.  As a result, no recent version of Trados Studio 2024 is fully stable for users relying on GroupShare and MultiTerm.

    Root Cause

    Based on the content of this thread the issue looks to be a backward compatibility failure introduced in the SR1 update, specifically affecting connections to older GroupShare versions like GroupShare 2017.  The pre-SR1 version of Trados Studio 2024 did not have this issue.

    Impact

    If confirmed, this prevents users from working with the latest versions of Trados Studio.  It affects anyone working on multiple GroupShare projects, forcing them to choose between a project list that is unusable or a version with unreliable terminology management.

    Current Status & Workaround based on this thread

    The only viable workaround confirmed by the community is to uninstall SR1 and downgrade to the pre-SR1 version of Trados Studio 2024. This is not a sustainable solution and prevents users from benefiting from any new features or security updates.

    What's needed is an update confirming the problem, and whether a fix is planned to address both the GroupShare project name bug and the subsequent terminology connection issues.

    Paul Filkin | RWS

    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • 0

    We will be pleased to help you with this problem so have logged a support case on your behalf. We do prioritise customers who have a support contract so please keep in mind it could take up to 48 hours, especially over a weekend, but rest assured we will contact you as soon as we can. You will be contacted at the email address used for this Community. Support Case Id : CS0042941.

    Paul Filkin | RWS

    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • 0 in reply to Paul Filkin

    Thank you for replying. I hope this issue gets resolved, as in its current state any new upgrades for Studio are unusable to us (and a lot of others). I will not abandon my GS 2017 just to be able to use shiny new AI-based features in Studio, so basically this issue forces my whole company to either stay with pre-SR1 Studio 2024 licenses or switch to memoQ for good. I do not want either of those options, but knowing how fast RWS reacts to bug reports, it will be at least 10 years, before someone does anything with this... 
    emoji
  • 0 in reply to Paul Filkin

     

    Thank you for reporting this. It is a pretty severe issue.
    I am using the latest Trados Studio 2024 SR1 with Groupshare 2020 SR1 and this issue happens.
    emoji
  • 0 in reply to Paul Filkin

    Hi Paul, hi all,

    I am experiencing exactly the same issue as described in this thread, with a very similar setup.

    Environment:
    - Trados Studio 2024 SR1 (18.1.3.6657)
    - GroupShare 2020 (latest version)

    Issue description:
    When I download or open GroupShare projects, everything initially appears correctly. However, after a few seconds, the new project name is overwritten and become identical, taking the name of the first project in the list.

    This behavior:
    - affects all GroupShare projects
    - does not occur immediately, but consistently after a short delay (a few seconds)
    - makes it definitely impossible to distinguish or manage projects properly > I must work with only one project in the list... 

    Additional notes:
    - I have already tried several standard troubleshooting steps (restart, reinstall, cache reset, etc.) without success
    - the issue is fully reproducible on my side

    At this stage, I have not yet verified whether the project names remain correct in the GroupShare web interface, but the problem clearly appears on the Studio side.

    Is there any workaround or fix available?

    Thank you in advance for your support.

    Philippe
    emoji
  • 0 in reply to Philippe Druart

    Exact same issue as Philippe and others here with an identical setup. Only thing working for me was to downgrade Trados 2024 from SR1 to previous release (18.0.2.3255).
    emoji