The below symptoms are specific to GroupShare 2020 SR1 CU4. This issue was reported also on GroupShare 2017 SR1 CU8.

Online Editor does not show lookups and errors are displayed in the Lookups Panel:

TranslationLookupErrorLabel


An error has occurred in translation lookup for segment number


Confirming a segment results in the following error:

TranslationUpdateError

NOTE! This resolution should be implemented only by qualified IT personnel that has the proper training, understanding and knowledge to configure Windows Server registry keys.
Proceeding with the below changes should be done with extreme caution and all changes should be thoroughly documented in case a roll back is necessary.
Please log a case with SDL Support if you are not sure that these changes are necessary or how to implement them.


Step 1: On the Application Server machine, change the registry keys for SDL Translation and SDL Feedback service exactly as described below:

For SDL Feedback Service:
1. Open the Registry Editor and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SDL Feedback Service\Parameters\
2. Double click on AppParameters
3. Replace Value data: with the following: 
WARNING: If Trados GroupShare was not installed on C:\ Drive, adjust the location of the gs-feedback-service.jar to match the path of the service. (Keep the original path from the existing registry entry). Pointing the registry entries to the wrong file path will cause an error and the service will not start anymore. 

-XX:NewRatio=7 -Xmx1024m -jar "C:\Program Files\SDL\SDL Server\Feedback Service\gs-feedback-service.jar" --spring.profiles.active=std --logging.file="C:\ProgramData\SDL\Service\Logs\gs-feedback-service.log" --server.port=41259 --gs.proxy.location=machinename:41234 --gs-management-service.ribbon.listOfServers=machinename:41234 --translation-memory-service.ribbon.listOfServers=machinename:41235

NOTE! It is recommended to use the Fully Qualified Domain Name (FQDN) of the application server as machinename in the string.

For SDL Translation Service:
1. Open the Registry Editor and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SDL Translation Service\Parameters\
2. Double click on AppParameters
3. Replace Value data: with the following: 
WARNING: If Trados GroupShare was not installed on C:\ Drive, adjust the location of the gs-translation-service.jar to match the path of the service. (Keep the original path from the existing registry entry). Pointing the registry entries to the wrong file path will cause an error and the service will not start anymore.

-XX:NewRatio=7 -Xmx1024m -jar "C:\Program Files\SDL\SDL Server\Translation Service\gs-translation-service.jar" --spring.profiles.active=std --logging.file="C:\ProgramData\SDL\Service\Logs\gs-translation-service.log" --server.port=41258 --gs.proxy.location=machinename:41234 --gs-management-service.ribbon.listOfServers=machinename:41234 --translation-memory-service.ribbon.listOfServers=machinename:41235

NOTE! It is recommended to use the Fully Qualified Domain Name (FQDN) of the application server as machinename in the string.

Step 2: Go to SDL GroupShare Console > Services (Local) and restart SDL Translation Service and SDL Feedback Service.
It is not required to restart all Services or to reboot the server.

Step 3: Go to Internet Information Services (IIS) Manager > Sites and restart the SDL Server website.

This issue appears always in a split installation scenario (Application server and Web server are installed on different machines) but it can also occur in a normal GroupShare installation (Application server and Web server on the same machine) when:
- External server address is only accessible via HTTPS or
- HTTP (port 80) binding is disabled in IIS or
- IIS of internal server has both protocols enabled (port 443 and port 80 - no host header is set)

The development team is aware of this issue and is working on fixing it in a future version of GroupShare.