Error in import of TMW translation memory to Studio 2014
Thread poster: Ofra Hod

Ofra Hod  Identity Verified
Israel
Local time: 03:36
Member (2011)
English to Hebrew
Oct 15, 2015

I have SDL Trados Studio 2014 Freelance (version: SP2 - 11.2.4422.11).

A few days ago I upgraded to Windows 10.

Now, when I get a TMW file from a client, I open it, click "Quick Upgrade" and see that the 1st two steps succeed, but the 3rd fails with the error: "No region-specific language could be found for the specified language".

An SDLTM file is created but it's empty.


Any ideas?


Direct link Reply with quote
 

Amnon Shapira  Identity Verified
Israel
Local time: 03:36
Member (2011)
English to Hebrew
Use a TMX version Oct 15, 2015

Shalom Ofra,
You need to get a TMX version of your TM. To creat one, you can either use a Trados 2007 version, if you have one available or ask your client to convert it for you. Once you get it, you will be able to generate the new TM.
the error you have encountered is somthing that results from the upgrade to W10 and as far as I know SDL staff are working on it.


Direct link Reply with quote
 

Ofra Hod  Identity Verified
Israel
Local time: 03:36
Member (2011)
English to Hebrew
TOPIC STARTER
Same error with TMX Oct 15, 2015

Thank you, Amnon. I thought it was a great idea to use an interim TMX file but then I got the same error.

I hope SDL staff come up with a solution soon. In the meantime I will ask my client to convert the TM for me.


Direct link Reply with quote
 

Ofra Hod  Identity Verified
Israel
Local time: 03:36
Member (2011)
English to Hebrew
TOPIC STARTER
error details (in case anyone in SDL can look into this) Jan 16, 2016

Studio lets me save the error details in XML format, and I did. Here they are (partially displayed, I am afraid, because I can't figure out how to display XML here):


Import failed. The file could not be processed.

System.Exception, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

Sdl.TranslationStudio.TranslationMemoryManager
-2146233088
b__3()
at Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
at Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]>

Sdl.LanguagePlatform.Core.LanguagePlatformException, Sdl.LanguagePlatform.Core, Version=1.6.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888

Sdl.LanguagePlatform.Core
-2146233088




SDL Trados Studio
11.0.0.0
11.2.4422.11
Microsoft Windows 10 Home
NULL
1033
1255
Hod-PC\Hod
4.0.30319.42000
HOD-PC
True
4158708 MB


Direct link Reply with quote
 

gbock
United States
Local time: 17:36
English to German
+ ...
Solution Jan 17, 2016

The solution was to replace the deprecated locale code IW (usesd by Trados 2007) in the TMX file with the correct local code HE (used by Studio).

Here is a list of all locale codes supported by Studio: http://producthelp.sdl.com/kb/Articles/3610.html


Direct link Reply with quote
 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

Error in import of TMW translation memory to Studio 2014

Advanced search







Déjà Vu X3
Try it, Love it

Find out why Déjà Vu is today the most flexible, customizable and user-friendly tool on the market. See the brand new features in action: *Completely redesigned user interface *Live Preview *Inline spell checking *Inline

More info »
SDL MultiTerm 2017
Guarantee a unified, consistent and high-quality translation with terminology software by the industry leaders.

SDL MultiTerm 2017 allows translators to create one central location to store and manage multilingual terminology, and with SDL MultiTerm Extract 2017 you can automatically create term lists from your existing documentation to save time.

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search