You are currently working on UAT 

Error message: "An error has occurred whilst using the translation provider [TM]: The formatter threw an exception while trying to deserialize the message: "

Hello,

I am experiencing some troubles with a project carried on under Studio 2011  - which I have been using for four years now, without having this kind of issue. In my current project, when I make a concordance search, every other time I get an error message: "An error has occurred whilst using the translation provider [TM]: The formatter threw an exception while trying to deserialize the message: " and so on.... It is a very long error message, but unfortunately I cannot copy-paste it (frequent problem with Studio, so inconvenient!). The TM is located on a client's server, whose support team reviewed the issue without finding anything wrong. The strangest part is that sometimes I can benefit from the fuzzy match/concordance search features, but sometimes I can't, in the same file. I found out that the problem is linked to specific words/phrases/segments. No matter how many times I translate them, I never find them back in the TM.

Any idea? Many thanks in advance!

Parents
  • Hi,
    This post is the nearest I can find to my current problem.
    When I launch a concordance search with F3 I get the error message:
    "An error has occurred whilst using the translation provider [TM]. The field types are incompatible."
    I am using a client TM that came with the package, plus my own TM for extra reference content. This is the approach I've been using for years but I've never had this error message before.
    I'm working with Studio 2017 and the client is on 2017. I've tried the client suggestions of reorganising and re-indexing my TM, exporting it into a new TM, opening the package in 2015 instead of 2017. All to no avail.

    Can anyone explain this incompatibility of fields and how to rectify it?
    Thanks!
  • Hi Nicholas, did you manage to fix this problem? I'm having the same issue right now :-(
  • Hi Barbara, I haven't been here for a while so only just saw your question.
    In my case the problem seemed to be caused by having too many system fields in my TM. That's because whenever I'm sent work with a client TM I finish by importing the job into my own large, general TM as a future reference resource. I recreated this TM by excluding the system fields.

    I'll paste in here the information someone gave me that sorted the problem:

    Hallo, Herr Hoyle!
    Wir vermuten, dass sich da über die Jahre durch die TMX-Importe in diesem Feld „Source File“ eine sehr lange Liste an Feldwerten angesammelt hat, und dass es aufgrund dieser vielen Feldwerte in diesem Listenfeld jetzt zu den genannten Problemen kommt.

    Es gibt an sich 2 Möglichkeiten:

    1. Neues TM anlegen; altes exportieren und in neues TM importieren; allerdings mit der Option „Unknown fields: Ignore“ (siehe Screenshot). Das hat allerdings zur Folge dass möglicherweise alle Felder rausfallen und nur noch Ausgangs- und Zieltext erhalten bleiben.

    (This option 1 sorted the problem for me.)
    When I now import tmx files, I do the following:

    In the General Import options,

    uncheck “Use information from bilingual file to update TU system fields.
    Seems to be working so far!
Reply
  • Hi Barbara, I haven't been here for a while so only just saw your question.
    In my case the problem seemed to be caused by having too many system fields in my TM. That's because whenever I'm sent work with a client TM I finish by importing the job into my own large, general TM as a future reference resource. I recreated this TM by excluding the system fields.

    I'll paste in here the information someone gave me that sorted the problem:

    Hallo, Herr Hoyle!
    Wir vermuten, dass sich da über die Jahre durch die TMX-Importe in diesem Feld „Source File“ eine sehr lange Liste an Feldwerten angesammelt hat, und dass es aufgrund dieser vielen Feldwerte in diesem Listenfeld jetzt zu den genannten Problemen kommt.

    Es gibt an sich 2 Möglichkeiten:

    1. Neues TM anlegen; altes exportieren und in neues TM importieren; allerdings mit der Option „Unknown fields: Ignore“ (siehe Screenshot). Das hat allerdings zur Folge dass möglicherweise alle Felder rausfallen und nur noch Ausgangs- und Zieltext erhalten bleiben.

    (This option 1 sorted the problem for me.)
    When I now import tmx files, I do the following:

    In the General Import options,

    uncheck “Use information from bilingual file to update TU system fields.
    Seems to be working so far!
Children
No Data