Alexandr Shakhotkin said:

We've been getting the following error message - "An error has occurred while using the translation provider. XXXXX (the name of the server-based TM)". Response status code does not indicate success: 400 (Bad Request). Pleasew refer to the attched snip. This message appears when we press F3 concordance search, so it is not working in Trados Studio 2024. However, it worked a month ago. We've tried to use several server-based TMs and still get the same message on different PCs.

Can anyone tell me how to fix it? 

Removed AI Suggestion
[edited by: Alexandr Shakhotkin at 11:58 AM (GMT 0) on 27 Mar 2026]

Hello, Alexandr Shakhotkin mcdvoice

This specific error in Trados Studio 2024 (400 Bad Request during F3 concordance on server-based TMs) is almost never a simple “reinstall fixes it” issue — it’s typically caused by server-side communication or corrupted TM/query parameters, especially since it worked before and now fails across multiple PCs.

This error isn’t your PC — it’s a server TM query failure (400 = bad request).

Quick fix sequence
Reconnect the server TM
Remove TM → reconnect → re-add
(fixes broken session tokens)
Reset concordance settings
Project Settings → TM → Search → reset to default
(invalid filters often cause 400)
Rebuild TM index (server-side)
Ask admin to reindex the TM
(most common real cause)
Test with a new empty server TM
If it works → your TM is corrupted

Server rejects concordance query due to bad index / outdated API / corrupted filters.

If it still fails, tell me if you're using GroupShare or Language Cloud — the fix changes slightly.

Best Regard,
Max Martin

The issue was at the server end, it has been resolved. Thank you for your response.  

The issue was at the server end, it has been resolved. Thank you for your response.