Dear Guadalupe,

Thank you for raising this topic in the forums.

To be able to dig into this further, please let me know what is the used Trados GroupShare application version: https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0026418. Additionally, please check if the versions of the Trados GroupShare applications are fully (green) compatible with the used Trados GroupShare application version: https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0039885 . Not to forget: do you see any errors in the Trados Studio log files? The log file can be opened via Trados Studio - File - View Log File section.

If you have a paid SMA (Software and Maintenance Agreement) contract with RWS, please raise a ticket here: https://gateway.rws.com/csm .

Looking forward to hearing from you.

Good morning Darius,

Thanks for the follow-up. I’m attaching screenshots of the Studio log and the TM Server (GroupShare) version.

Dear Guadalupe,

Thank you for the reply on this topic.

I see that you are trying to connect, indeed, to one of our hosted Trados GroupShare hosted servers: LOGS03. I also see that you are not being able to log in the Web interface: wrong username or password.

Please check in the Trados Studio 2019 version - File - Setup - Servers - click on the LOGS03 connection - Edit. Click Next in the first window, and check if the login you are logged in there is the same you are willing to use in the Web Interface. The scope is to find which are the correct login credentials, and make sure these working in the Web interface. If you find the correct ones, then the same login details should be used in Trados Studio 2024 - File - Setup - Servers section. Maybe you have 2 different login details?! 

The log details do not show much.

Looking forward to hearing from you.

Hi again Darius

I was finally able to sign in to the GroupShare web portal (it seems there was a temporary login issue) and I can access the site without a problem. I have confirmed the exact same credentials used in Studio 2019 (Servers > LOGS03) and in the web portal.

However, with those same credentials in Studio 2024, the server TM in GroupShare projects remains disabled / cannot be enabled. Notably, I can still open the same server TM via Translation Memories → Maintain in Studio 2024; the problem appears only when a GroupShare-delivered project tries to attach/enable its TM. Credentials are the same

Is there anything else I can do on my side? And is it possible that Studio 2024 handles access/login/permission discovery differently from 2019 when enabling a project’s server TM?

For context: I saw the same behavior once with a trial of Studio 2022 on a clean install back then, which is why I stayed on 2019 at the time. I’m now fully on Studio 2024, and the issue persists.

Many thanks again

Lupe

Hello again Guadalupe,

There is nothing changed regarding the login/permissions/discovery on/with Trados Studio 2019/2022/2024.
If you work in Trados Studio 2024, and have a Trados GroupShare project opened in the Projects list: Simply go to Project Settings and remove the Server-Based Translation Memories from there. And add them back. Are these shown as enabled now?

Additionally, when you open a project from Trados GroupShare, in Trados Studio 2024, do you save the project locally or on a shared drive?

If the above does not help, I suggest you rename 3 Trados Studio 2024 config files: simply open a File Explored and type %appdata% in the link bar. Then browse to this path: C:\Users\computerusernamehere\AppData\Roaming\Trados\Trados Studio\Studio18. Make sue that the application is closed, then please rename the following config files:

BaseSettings.xml

plugincache.xml

UserSettings.xml

Or, uninstall the 2024 version, and download the installer from here: https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0027380. Once the installer is downloaded, right click on it and select Run As Administrator.

I hope this helps.

Best regards

Hello again Darius!

I tried all the steps mentioned and these didn't work: I always save the project folder locally and I renamed those config files.

I also performed fresh installs as suggested and, finally, this problem appears to be OS-specific.
On Windows 10 (clean, fully updated) with a fresh Studio 2024 install, the GroupShare project TM stays disabled and the problem persists.
On Windows 11 (clean install) with the same account and server (LOGS03), everything works as expected—the TM enables and projects open normally.

So credentials/server/permissions seem fine; the behavior is specific to Win10 + Studio 2024 on my side. I will keep investigating and post any new findings here.

Thanks for your help!

Best regards

Hello again Guadalupe,

I am glad to hear that the problem is not happening while using Win11+Trados Studio 2024 SR1. This is very strange, and very confusing to me, and it looks like an isolated issue - as I have not heard about so scenarios.

When you re-installed the application, did you do this while right clicking on the installer - Run As Administrator? Do you have any antivirus/firewall tool installed on your machine that might act/work differently on different Windows OS environments? I am currently out of ideas, what more can be checked. But if this works on Win11, I believe you will stay on this version - given the fact that Windows 10 support ends on October 14, 2025.

Best regards

Hi Darius,

Yes—this is exactly why I posted: it’s a strange, split behavior—parts of Studio work (e.g., I can open the same server TM via Translation Memories → Maintain), but GroupShare project TMs won’t enable, which is unusual enough to ask the forum .

To clarify the setup and what I’ve tried:

• Install method: in both Windows 10 and Windows 11 I installed Studio via Right-click → Run as administrator.

• Security software: no third-party antivirus, no VPN/proxy, and Windows security features are largely disabled/default—nothing extra running that could interfere.

• Environment: I work on a Macintosh using virtual machines and Parallels to virtualize the OS. That’s how I reproduced the issue across multiple, both clean and legacy, instances from scratch.

I will keep sharing any new findings since I am keen to keep a stable Win10 setup for Studio 2024 if possible due to a separate issue with ITD files not being processed in Studio24 in Windows 11 after installing StudioPowerPack2024_18.1.2.180 (I’ll open a different thread for that ). Besides, Windows 10 runs noticeably better on my hardware and I still rely on some legacy tools (e.g., Transistor) that can’t be installed on Windows 11.

Thanks again!!

Lupe

Hi Darius,

Yes—this is exactly why I posted: it’s a strange, split behavior—parts of Studio work (e.g., I can open the same server TM via Translation Memories → Maintain), but GroupShare project TMs won’t enable, which is unusual enough to ask the forum .

To clarify the setup and what I’ve tried:

• Install method: in both Windows 10 and Windows 11 I installed Studio via Right-click → Run as administrator.

• Security software: no third-party antivirus, no VPN/proxy, and Windows security features are largely disabled/default—nothing extra running that could interfere.

• Environment: I work on a Macintosh using virtual machines and Parallels to virtualize the OS. That’s how I reproduced the issue across multiple, both clean and legacy, instances from scratch.

I will keep sharing any new findings since I am keen to keep a stable Win10 setup for Studio 2024 if possible due to a separate issue with ITD files not being processed in Studio24 in Windows 11 after installing StudioPowerPack2024_18.1.2.180 (I’ll open a different thread for that ). Besides, Windows 10 runs noticeably better on my hardware and I still rely on some legacy tools (e.g., Transistor) that can’t be installed on Windows 11.

Thanks again!!

Lupe