Hi Paul,

yes, the TMs are on a GroupShare server.

First tried setting the filter under All Language Pairs and then under a specific language (pictures Filter_01 and Filter_03).

Tried Last modified by first with Contains and then with Equal.

Error lists all language pairs where I tried to translate (picture Filter_02). No access to server TMs, although they were included in Project Settings and Active and I could access the server TMs from the Translation Memories view.

The above relates to GroupShare.

(Sorry, I don't have access to the xml file at the moment.)

Tested creating a filter also on a Desktop installation of SDL Trados Studio 2017.

The result was the same: with a filter (see picture Filter_Desktop), the TM was disabled in the first untranslated segment, with the same error message as in GroupShare (picture Filter_02).

After I’d deleted the filter, the problem no longer occurred and the TM works fine.

Hi Varpu Vuorjoki 

I moved your post into the GS forum to see if anyone had any ideas in here too.

I tested a TM set up as you suggested but don't get an error... so I used this:

And then see this sort of effect:

So I believe it "should" work based on my simple test.  It may help if you can get the full error stack as this could point to where the problem is coming from.  Given you get this with file-based and server-based TMs I don't think the condition of the TM is the problem, although it might be worth checking your file-based with the TM Repair app just in case.

In the meantime perhaps someone here might have a better idea?

Hi Varpu Vuorjoki 

I moved your post into the GS forum to see if anyone had any ideas in here too.

I tested a TM set up as you suggested but don't get an error... so I used this:

And then see this sort of effect:

So I believe it "should" work based on my simple test.  It may help if you can get the full error stack as this could point to where the problem is coming from.  Given you get this with file-based and server-based TMs I don't think the condition of the TM is the problem, although it might be worth checking your file-based with the TM Repair app just in case.

In the meantime perhaps someone here might have a better idea?