Salesforce

Error when opening a server-based translation memory: "An error occurred when searching the Translation Memory. The TM may contain invalid Translation Units."

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentTrados GroupShare 2017 SR1
Trados Studio 2019
Symptoms/Context
You encounter the following error message when you open a server-based TM in the Translation Memories view in Studio:

An error occurred when searching the Translation Memory. The TM may contain invalid Translation Units.

User-added image

 
<ErrorMessage>An error occurred when searching the Translation Memory. The TM may contain invalid Translation Units.</ErrorMessage>
  <Exception>
    <Type>System.IO.FileNotFoundException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <FileName>Sdl.Core.Bcm.BcmModel, Version=1.7.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</FileName>
    <FusionLog>WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].[...]


Also, when you open a file for translation in the Editor view, you encounter the following error message in the Messages window:

Error using translation resource [TM Name]. File or assembly "Sdl.Core.Bcm.BcmModel, Version=1.7.0.0, Culture=neutral, PublikKeyToken=c28cdb26c445c888" or a dependency could not be found. The system cannot find the indicated file. 
User-added image
Resolution
Close Studio and run a Repair for the installation by following the steps described here.
Root Cause
Incomplete or incorrect installation of the Trados Studio software after a fresh installation or an update.
The following DLL files may be missing or not updated in C:\Program Files (x86)\SDL\SDL Trados Studio\Studio15.
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by