Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
I saw this question being raised a couple of months ago, but it seems the problem still isn't resolved. When working on projects that use a server-based TM at the client side, the condordance doesn't work anymore with the current 18.104.22.16807 update. The client is using Studio 2017 SR1 - 14.1.10016.54660.
The message that is immediately returned is "There was a problem while searching. See the Messages Window for more information."
The Messages window shows: "An error has occurred while using the translation provider xxx. Correction Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was [Pre-Login] initialization=0, handshake=2; [Login] initialization=0; authentication=0. [Post-Login] complete=15000."
This cannot be a timeout error because the message appers the same instant that I hit the Concordance shortcut. Also, I get some fuzzy matches, so the TM is definitely connected, it's just the concordance that doesn't work.
This issue prevents me from accepting jobs from clients who work with a server TM. Does anybody know how to solve this without having to uninstall Studio and reinstalling the previous version? (Is there a more simple rollback?)
Thank you for your question!
Can you send us the completele stacktrace of the error message? You can maximize the error message by clicking on the small window in the bottom left corner of the error message. Please copy paste or attach the stacktrace to the post.
Thank you and best regards,
I just tried this again. Today I get a different message:
""An error has occurred while using the translation provider xxx. Object reference not set to an instance of an object."
The Message windows shows the exact same message. I'm sorry but I don't see a small window in the bottom left corner to click on... I'm so grateful for your help, but I don't know how to obtain that stacktrace...
Best regards, Nina
I think I might have expressed myself incorrectly - I am sending you some steps on how to save the stacktrace:
I hope this helps!
I see. Unfortunately, this is no popup error message. The error appears in the yellow bar below the concordance window which then turns orange.
What GroupShare version are you using?
Hi Ingrid, it's Version 4.0.4318.4