• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 432 subscribers
  • Views 6609 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

"Multiterm is unable to retrieve the multimedia object" error in connecting a Termbase to a Trados project

Yukihiko Okada

I am trying to connect Termbases to a Trados project that I have built. I can always to do it except for one client. I get the following error message:

General error occurred. Multiterm is unable to retrieve the multimedia object.

Here is my situation.

Windows 10 (up-to-date as of October 24, 2019)

Trados 2019 SR2 - 15.2.4.1693

MultiTerm 2019 - 15.0.4.56053

(I have uninstalled Trados and MultiTerm, downloaded and installed the latest versions. I checked and installed the updates.)

I have connected Termbases to numerous Trados projects and it always goes well except for this client and with my Windows 10 laptop. Even with this client, I can built Trados projects with Termbases on my Windows 7 desktop. 

I need to connect several Termbases to a project for this client. I can connect some of the Termbases (one that I created, and one supplied by the client), but not others due to this error (mostly client-supplied, but one TB that I recently (about a week ago) generated from client's Excel glossary could not be connected). 

Source files are in MS Word and MS Excel. I have worked on many jobs from this client (I am using WIndows7 machine) and they always give me the same error as far as I tested on my Windows10 machine. 

The language pair is from Japanese to English (US).

Does anyone have a solution? Thank you for looking!

Yuki Okada


[locked by: Steven Whale at 11:59 AM (GMT 0) on 28 Oct 2019]
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Lydia Simplicio

    Hi Steven,

    Thank you very much for your answer. Emil notification did not come and I am sorry for the late reply.

    The problem has just been resolved. The solution was along the same line as what you suggested.

    Some of the client-supplied TB and xlsx were named using Japanese. I changed those file names and folder names to ones using only English alphabets, and now I am able to connect them to my Trados project all right!

    The friendly names were not changed and these TBs are displayed with those original Japanese friendly names in my Trados Studio project. 

    An additional piece of information is that I am using an North-American English Windows10 with Japanese enabled. I can see those Japanese folder and file names with Windows explorer but there may be something that MT and Studio got confused. 

    As I said the same problem does not happen with my old Windows7 machine. 

    It is still a mystery, but I know what to do now at least.