When exporting a Task in WorldServer, the error 'Found unsupported language: Serbian' (or any other language) appears

When exporting a Task in WorldServer, the error

Found unsupported language: Serbian

appears. This happens for any project with any source or target language using a Multiterm Term Database. You will also see the same error when trying to open the Multiterm Term Database by clicking on its name under Tools > Term Databases

Note: the error could point to a different language too.

Workaround:

when exporting to WSXZ package, next to Multiterm Information, change the default setting from Content to Link Only. The export will work.

Resolution

If you change a Multiterm Term Database in Trados Groupshare for which a connection exists in WorldServer by adding new languages or by replacing the TD with a new one with new languages and renaming it to the same name as the old one, in order for these new languages to work correctly in WorldServer, you need to map them to WorldServer locales.

The mapping will only appear if you re-connect the new or changed Multiterm Term Database. To do so, under

Management > Linguistic Tool Setup > Term Database Setup 

you need to select the Multiterm Term Database and click on Disconnect. Then click on Connect to create a new connection to the same or a new Multiterm Term Database. During the connection, you will be prompted to map the languages to the WorldServer locales as described in this article: Adding/modifying the languages of an MultiTerm TermBase to be accessible to WorldServer

Once the mapping is done correctly, the export will work without errors and you will be able to open the Multiterm Term Database from Tools > Term Databases

The error is related to the Multiterm Term Database associated with the project and task you are trying to export. A new Multiterm Term Database has been added to a WorldServer environment, but the mapping of the Multiterm languages with the WorldServer Locales has not been done. This might happen when in Multiterm, a new Term Database has been created with the same name as a previous Multiterm Termdatabase that is connected to Worldserver. The connection to that Multiterm Database will still appear in WorldServer, but the new language(s) will throw an error because the mapping - which is a mandatory step when creating a connection to a new Multiterm Term Database- has not been done.