You are importing a .tmx file into a server-based Translation Memory in Trados GroupShare 2017 Cumulative Update 3.
After a some time the following error is displayed:
Import failed. The file could not be processed.
If you open the details of the stack trace you see further information like the ones below.
One or more errors occurred followed by Response status code does not indicate success: 502 (Bad Gateway)
or
One or more errors occurred followed by A task was canceled
Resolution
Workaround: Upgrade Translation Memories
Instead of running the import with the default import option use the Upgrade Translation Memories option.
For further information about the Upgrade Translation Memory Wizard you can search the SDL Trados Studio help or access the online documentation here.
You import should run successfully and you can see statistics when clicking on Details.
Root Cause
The RWS Development team is aware of this problem and is working on a solution. Until a permanent solution is in place, see the Resolution section for a workaround. When the RWS Development will launch a Service Release and/or Cumulative Update or a Service Pack to fix this issue the AutoUpdate feature will automatically inform you about an update if the fix is in the RWS Client (eg. Studio or MultiTerm). By default, the AutoUpdate feature is active and MultiTerm and/or Trados Studio checks for updates each time you start the application. If you want to check for updates while MultiTerm and/or Trados Studio is open, you can run the Check for Updates feature from the Help tab. If the fix requires to be applied on the server side the Cumulative Update information will be available here -> https://gateway.sdl.com/apex/communityknowledge?articleName=CUs-GroupShare-2017
