SDL Trados GroupShare 2017 - tune the application server after installation of Cumulative Update 3 or 4

You have installed Cumulative Update 3 or 4 for SDL Trados GroupShare 2017 and you observe that some tasks in GroupShare are not working and/or performance is not optimal.

Symptoms can be seen...

• ...when running an import/export or anything else related to Translation Memories and the task fails or is cancelled
• ...that for some instances the CPU usage of the Sdl.RestApi.Host.exe service is raising

For the symptom that the SDL Rest Api Service consumes a lot of CPU when certain tasks are starting please apply the steps below.
 

Workaround: Increase the 'ReportActitivityInterval' value in the "Sdl.RestApi.Host.exe.config" file for the SDL Rest Api Host Service:

Note: The following steps are applied automatically when installing GroupShare 2017, CU4 Refresh (build 5104) or newer.

1. In the Services Console stop the SDL REST API Host Service" and SDL TM Agent Service.
2. In the Processes tab of the Task Manager ensure the Sdl.RestApi.Host.exe is not running anymore. 
   Note: If it is still running, please end the process. 
3. Go to the folder: C:\Program Files (x86)\SDL\SDL Server\TMService 
4. Locate the Sdl.RestApi.Host.exe.config file and create a backup of this file. 
5. Now open the original Sdl.RestApi.Host.exe.config in a XML/Text editor.
6. Copy the following element: <add key="ReportActivityInterval" value="2147483647" />
7. Paste the copied element in between the opening <appSettings> and closing </appSettings> element. 
8. Save the changes and (re-)start the "SDL REST API Host Service" and "SDL TM Agent Service". 

 

 

For imports and/or export tasks that are failing from within the Studio Client apply the steps below.

Increase the Server Farms' Proxy timeout in the IIS:

1. Open Internet Information Services (IIS)
2. Expand Server Farms
3. For all sub-nodes (eg. GroupShareRestApi) make the timeout change under Proxy
4. Increase the timeout from default 30 to 60, 120 or even 180
   
   
   
   
    

This can help with e.g. import over the Clients. If you still encounter issues during imports you can try the workaround described in the following article:
 

• SDL Trados GroupShare 2017 CU3 - Import of .tmx file into server-based Translation Memory failed with 'Import failed. The file could not be processed'

This issue affected GroupShare 2017 CU3 and CU4. It has been rectified in Cumulative Update 4 Refresh (build 5104).