• State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 434 subscribers
  • Views 1461 views
  • Users 0 members are here
Options
Related

Attempting to Upgrade Translation Memory in Studio 2021 SR1 – Exception thrown by target of an invocation

Lajos Illich

Hi,

Although I did upgrade my TMs when I switched to 2021 from 2019 (in which I'd also  upgraded, which didn't really seem to make any difference in 2021), the little orange thingy started reappearing for every previously upgraded TM. I did the upgrade again for one of my TMs a while ago, and the orange warning symbol did go away. Of course, TM size roughly doubled again, eve though it had already been upgraded in ST2021 before.
Anyway, I just tried to upgrade another TM, and it failed hard. I've tried repairing Studio, as well as all the MS Visual Basic C++ programs on my PC, to no avail.

Here goes the full error pop-up:

Error message in Trados Studio showing 'Exception has been thrown by the target of an invocation' with details about missing method in mscorlib.dll and issues in TranslationMemoryMigrationUI.

Now, it looks to me like mscorlib.dll is missing. I've no idea where it may have gone to, I certainly did have it before. I know that for a fact, since I've been having a separate bug, and it also involved that dll file.

Any ideas would be appreciated, and a solution, too. Thanks!

Generated Image Alt-Text
[edited by: Trados AI at 2:54 AM (GMT 0) on 29 Feb 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Doctec B.V.

    If your version didn't change, but the error message started popping up just out of the blue, probably you need to install NET Framework 4.8.0. I did both: installed NET Framework 4.8.0 first and then the compatibility pack. I tried to upgrade a TM after the first step (once I installed NET Framework 4.8.0) to no effect. Then I installed the compatibility pack and rebooted my computer. However I am not sure whether it was NET Framework or compatibility pack that helped because I did not reboot after I installed NET Framework. Maybe it could work if I rebooted as soon as I installed NET Framework.