We have already set up templates, file types, workflows, translation engines, tms etc. online.
The error appears AFTER selecting the customer location, template, file type config in the Studio wizard.
It asks us to create a new TM Engine, leads us through the interrogation we have already completed online and then refuses to create the Engine, telling us it is already there. What are we doing wrong here?
Hi Burckhardt Rueffer ,
Can you tell me what version of Trados Studio is installed on your side? You can check this information in Help -> About Trados Studio.
Lately I have seen this issue when creating a project while using the language pair: Source Language: France (France) - Target Language: Spanish (Spain, International Sort) and this has been raised with the product development team: CRQ-31083.
Looking forward for your reply.
Alex J.
Hi Alex Jude
We have a number of translation engines, some include Spanish (Spain, International Sort) but not all. They all include EN-US as source, though. We have not been able to use a single translation engine from within Studio (2022, 17.0.0 and 17.0.3) regardless of the language pairs.
Cheers,
Burckhardt
Burckhardt Rueffer I manage to replicate the same behavior on my side and I have informed the development team about it via: CRQ-31083.
Alex J.
Alex Jude Given that Studio is the default app for many of us in creating projects, it is not good news. Do you have any idea how long it will take to get it fixed? Memsource and XTM are calling 
Burckhardt Rueffer I have made a few tests using the following language pairs and the translation engines were displayed:
English (United States) - French (Canda)
English (United States) - Portuguese (Brazil)
English (United States) - Chinese (Simplified, China)
Unfortunately I cannot tell when this will be fixed but I can confirm that the development team is already working on a fix to overcome this issue.
Alex J.
Alex Jude Thanks for the update. Please let me know if you need any information from our side, like logs etc.
Alex Jude Thanks for the update. Please let me know if you need any information from our side, like logs etc.
Hi Burckhardt Rueffer , I manage to narrow down the root cause. The issue with the Translation Engines not being shown in Trados Studio and the error message "Connection failed to start" being displayed, is caused by the fact that the Cloud user, manually deleted one of the Cloud TMs which was added to the Translation Engine. This is why some of the translation engines with different language pairs are shown and other ones are not displayed.
At the moment the issue could be manually fixed individually for each affected Translation Engine by our product development team. I already informed them about the affected Translation Engines from your Trados Team account and they will make the necessary adjustments so you will be able to use it. My recommandation, if you will see this issue in the future with other Translation Engines, please raise a support case and we will have it sorted with the development team, until the permanent fix will be deployed.
Alex J.
Translate
