SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
Language Technology Partner Group
SDL Academic Partners
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
To SDL Training
Training & Certification
What's New in SDL
Detecting language please wait for.......
Dear SDL support,
I am having an issue, after updating Trados 2019 to the new Service Release 2,
I cannot access the SDL Language Cloud, nor my own termbases. I am properly logged in.
Even after following all of the suggestions given in this thread:https://community.sdl.com/product-groups/translationproductivity/f/sdl_language_cloud/20918/after-update-trados-studio-2019-i-am-not-able-to-install-and-use-language-cloud Still I cannot access it, though I have a valid SDL Language Cloud Tentant ID.
Hello Leonardo Alvarez ,
It would be good to know if you were previously using the Beta version (available in 2017- but removed in the 2019 version).
The BETA version allowed you to use a number of TB's- whereas these are now limited (depending on your package you are subscribing to) in 2019 (could be the cause of the error message).
Therefore, it may be necessary to update your subscription options.
If the problem persists, please log a support ticket.
Thank you for your reply. As far as I can gather, I was not using the Beta version. Currently I have the Freelance Plus license, and should be able to use 5 termbases. I am only using 2 at the moment.
I had not used Trados for a while, maybe 6 to 7 months, but when I used it last time, I had no problem accesing my own Termbases.
So, am I doing something wrong?
Dear Steven, I am now able to access my own termbases, so the problem is fixed. The problem was that the "SDL Cloud Terminology" was enabled, but I believe it does not support my language pairs (Jap-Esp), so I disabled it and that did it.
Before the update it was enable but not functioning anyways, but now it was not letting me log in.In any case, I am able to use my own termbases as before. Best regards, Leonardo
I have SDL Trados Studio 2015 and I keep getting a message that SDL Cloud is not connected. It is not translating. How can I have SDL Cloud connected to the server?