Trados Studio - Cannot change the phase of files in server-based projects when using upper case in Windows user name

Article Number:000022269 | Last Updated:5/10/2024 12:24 PM

Scope/Environment

Trados GroupShare 2020
Trados GroupShare 2017
Trados Studio 2022
Trados Studio 2021

Symptoms/Context

The following message is received in Trados Studio when a Windows user with the Translator/External Translator role tries to change the file phase:

You cannot change the selected file phase because you do not have the required permission.

User-added image

The Trados Studio log file:

ERROR [2021-05-10 12:36:43,803] SDL.ApiClientSDK.GS.UserManagementV2Client - 
Server returned unsuccessfull status code : InternalServerError, Message : 
StatusCode: 500, ReasonPhrase: 'Internal Server Error', Version: 1.1, 
Content: System.Net.Http.StreamContent, Headers:
{
  X-Frame-Options: SAMEORIGIN
  Permissions-Policy: clipboard-read=self, clipboard-write=self
  X-Content-Type-Options: nosniff
  X-Permitted-Cross-Domain-Policies: none
  Cross-Origin-Embedder-Policy: require-corp
  Cross-Origin-Opener-Policy: same-origin
  Cross-Origin-Resource-Policy: same-origin
  Referrer-Policy: no-referrer
  Date: Fri, 10 May 2024 09:36:43 GMT
  Server: Microsoft-IIS/10.0
  X-Powered-By: ARR/3.0
  Content-Length: 83
  Content-Type: application/json; charset=utf-8
}{"Message":"User 'DOMAIN\username' does not have global permission 'manageRoles'"}
 Exception TraceId : 
ERROR [2021-05-10 12:36:43,806] SDL.ApiClientSDK.GS.UserManagementV2Client -
 An error occured: 
INFO [2021-05-10 12:36:43,809] SDL.ApiClientSDK.GS.UserManagementV2Client - 
Calling GET http://servernamehere/api/management/v2/users?name=DOMAIN\username

Resolution

The solution is to manually update the Domain name in the Trados GroupShare database, to no longer include uppercase letters.
The change is to be done in the sts.users table in the YourDatabase_SDLSystem database.

Root Cause

The Windows user Domain name contains at least an uppercase letter. This is a Bug raised with our Development team under Defect ID: CRQ-4531.

Reference

Send Article Feedback