Trados Studio crashes in some projects - suspect is something with groupshare access

Hello

In some PCs from my translators I have Trados crashing in some projects but not all. The log is attached and we always see the error - same for the 2 users (husband and wife) in the same house with the same internet connection:

ERROR [2026-01-08 17:36:56,723][Thread:15 ] SDL.ApiClientSDK.GS.UserManagementV2Client - Server returned unsuccessfull status code : InternalServerError, Message : {"Message":"User 'tferro' does not have global permission 'manageRoles'"} Exception TraceId : 

Please find the log attached

Version:

translator 1 - trados 2024 last version

translator 2 - Trados 2024 not updated to last version yet

I saw the article https://sdl.my.site.com/apex/communityknowledge?articleName=000021696

but im not sure it solves the issue. I cant get a pattern. This is because, due to this error, i have done a totally clean new installation in translator 1 but the error reappeared

Could this be somethign in the connection to our groupshare? - its behind a VPN

I tested also giving administrator rights to translator 1 temporarily but the error persists

Anti virus ?

Trados Studio_428.log



Removed AI Suggestion
[edited by: Rodrigo Ruivo at 10:30 AM (GMT 0) on 9 Jan 2026]
emoji
  • Probability score: 0.7  

    Question improvement suggestion: Provide more details about the specific projects that are crashing and any patterns observed, such as file types or project settings.  

    In the meantime, based on the information you have provided, here is a suggested answer to your question:  

    Hello,  

    It seems you're experiencing crashes in Trados Studio related to GroupShare access, particularly with the error message indicating that the user does not have the global permission 'manageRoles'. Here are some steps you can take to troubleshoot and potentially resolve the issue:  

    **Step 1:** **Check User Permissions**  

    - Log into the GroupShare Web User Interface as an administrator.  

    - Navigate to Users > Permissions and edit the roles assigned to the affected users. Ensure that they have the necessary permissions, including 'View Organization'. Save the changes and have the users restart their Trados Studio applications.  

    **Step 2:** **Verify SQL Credentials**  

    - In the GroupShare Web UI, go to System Configuration -> Servers.  

    - Check the Username and Password fields for the affected database server and correct them if necessary. Save the settings and restart the GroupShare services.  

    **Step 3:** **Check Firewall Settings**  

    - Ensure that the firewall on the SQL server is not blocking connections to the GroupShare application server. You can test this by pinging the server from the SQL server. If it times out, you may need to adjust the firewall settings.  

    **Step 4:** **Review Logs**  

    - Analyze the attached log file for any additional error messages or patterns that could provide more insight into the crashes.  

    **Step 5:** **Update Software**  

    - Ensure that both translators are using the same version of Trados Studio. If one is not updated, consider updating to the latest version to avoid compatibility issues.  

    **Step 6:** **Consider VPN Issues**  

    - Since you mentioned that the connection is behind a VPN, check if there are any VPN-related issues that could be affecting connectivity to GroupShare.  

    **Step 7:** **Contact Support**  

    - If the issue persists after trying the above steps, consider reaching out to RWS Support for further assistance, especially if this is a known defect (CRQ-27652) that may be addressed in an upcoming release.  

    I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

    RWS Community AI

    emoji
  • Probability score: 0.9  

    Question improvement suggestion: Include specific details about the current configuration of user roles and permissions in GroupShare, as well as any recent changes made to the system.  

    In the meantime, based on the information you have provided, here is a suggested answer to your question:  

    Hello,  

    Thank you for sharing the log details regarding the permission issue with user 'tferro'. It appears that the user does not have the necessary global permission 'manageRoles', which is causing the crashes in Trados Studio. Here are some steps you can take to address this issue:  

    **Step 1:** **Check User Permissions in GroupShare**  

    - Log into the GroupShare Web User Interface as an administrator.  

    - Navigate to Users > Permissions and edit the role assigned to 'tferro'.  

    - Ensure that the role includes the 'View Organization' permission and any other necessary permissions. Save the changes and have the user restart their Trados Studio application.  

    **Step 2:** **Verify SQL Permissions**  

    - Open SQL Server Management Studio (SSMS) and connect to your database.  

    - Expand the database 'SDLSystem' and check the 'sts.permissions' table.  

    - Ensure that the permission names are correctly displayed in uppercase letters as required. If not, edit the entries to match the expected format.  

    **Step 3:** **Correct SQL Credentials**  

    - In the GroupShare Web UI, go to System Configuration -> Servers.  

    - Verify that the Username and Password fields for the database server are correct. Save any changes and restart the GroupShare services.  

    **Step 4:** **Grant Additional Permissions**  

    - As a workaround, you can grant 'View Organization' permissions on the Root Organization to 'tferro'. This can help resolve the permission issue temporarily.  

    **Step 5:** **Check Firewall Settings**  

    - Ensure that the firewall on the SQL server is not blocking connections to the GroupShare application server. You can test connectivity by pinging the server from the SQL server.  

    **Step 6:** **Review Known Defects**  

    - Be aware that this issue is related to known defect CRQ-27652, which is expected to be addressed in an upcoming release.  

    **Step 7:** **Consult with a Database Administrator**  

    - If the issue persists, it may be beneficial to consult with a database administrator to ensure that all configurations and permissions are correctly set up.  

    I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

    RWS Community AI

    emoji