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
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Approved Trainers
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
What's New in SDL
Detecting language please wait for.......
after updating to Trados 2019 I cannot access the TMs on WorldServer anmyore.
The credentials have not changed but when I try to login I get the error message: A connection to server XXXXX could not be established for the following reason: Cannot establish connection to the remote server. As mentioned, this is the problem since I updated to Trados 2019, no credentials have been changed. Can you help?
Hi Daniela, while a Support case would be the best way for us to be able to investigate and troubleshoot your issue, can you please answer these questions:
1- From which previous Studio version have you upgraded to 2019?
2- Can you log in to the WorldServer user interface using your credentials?
3- Has the WorldServer customer you are trying to connect to recently upgraded its version? The issue could be related to the upgraded environment rather than a user's local Studio version.
4- Can you provide the URL you are using in Studio (you can slightly modify the first part to make the customer name not recognizable since this is a public page).
thank you for your answer. Here are my answers:
1. From Trados 2017.
2. Yes, this is possible.
3. I have to ask the customer.
4. https://worldserver.XXX/ws/services or http://XXX:8080/ws/services
I tried to replace "ws" with ws-legacy" as I found that somehwere but that does not work.
It worked in Trados 2017, but today I updated Trados 2017 and it does not work anymore. Something must have been changed in Trados.
Thanks and best regards,
Hi Daniela, please send me the complete URL to my email address: firstname.lastname@example.org. If your customer is hosted by SDL, I should be able to verify if there is an issue. If not, I might have to ask for more details. Thanks, Caterina
Okay, thank you!
Just throwing this out there, but maybe it's a firewall issue where 2017 was allowed through but 2019 hasn't been yet.
thank you for your answer! That also came to my mind. Unfortunately, the Trados Support could not help me. We deactivated the firewall to see what happens but the same error was displayed. The IT of the client also checked the configuration of the WorldServer but all is fine on their side. It is really strange.
OK, it was worth a shot. The only other thing that occurs to me is that we are using http:// instead of https://, probably doesn't make a difference either (in fact, I'm getting an error now trying to connect to our TMs "JSON integeger 5242880000 is too large or small", it's not something we really do though).
I now checked the https but that does not work either. I might ask Jerzy Czopik, he sometimes comes up with ideas what could have gone wrong. Again, I really appreciate all your answers! Thank you!