William Fuhrmann

First thing is to make sure you have the latest versions installed:

SDL Trados Studio 2021 - 16.0.1.2917
SDL MultiTerm 2021 - 16.0.0.159

It seems I have version 16.0.0.158 on MultiTerm, I'll update it and see if it fixes the issue, thank you Paul.

I have auto update turned on for MultiTerm, and if I try to update it manually by clicking on "Check for Updates", nothing happens.

William Fuhrmann

That's odd... I wonder if this is a just a typo in the version of the installer:

SDLMultiTermDesktop2021_158.exe

What does it say here?

And here in Help -> About:

Indeed, on both that launching image and in the About page it says 16.0.0.158. Is there somewhere where I can manually download and install the .159 version?

William Fuhrmann

I guess i must have picked this up after the Beta ended and not noticed that the release version was actually 158.   Daniel Brockmann can you confirm this for me?

I don't think you need to change anything in this case.  The numbers seem too close together to be an important change.  That's why I think it's more likely me confusing you as I seem to have something different to the version that was released.

Can you share a screenshot of your termbase settings page (where you add your termbase) in Studio?

Yes, sure. I'm not sure if this is what you're looking for as there doesn't seem to be many details here, let me know if you need something else instead.

Hi  - yes I can confirm that 158 is our release version, 159 is identical and got to the beta community by mistake - but it's identical, just from a different source code branch. Intrigued to see if we can help you William - we might need your termbase to reproduce but let's first try to see if we can reproduce in other ways. Also - does the Studio log file tell you anything? You could look at it after you see such a crash (then go to File - View Log File and perhaps share it with Paul or me). Thanks, Daniel

Thanks Daniel Brockmann... that explains things!

William Fuhrmann

William Fuhrmann said:

I'm not sure if this is what you're looking for as there doesn't seem to be many details here

It was... and now we know the problem of languages not being correctly mapped isn't a problem here.

Does this happen with any termbase or just this one?  If it's just this one close Studio/MultiTerm and try deleting these files and then try again:

*.mtf
*.mdf

If it still fails after that try exporting the content to a MultiTerm XML and XDT, then recreate your termbase using the XDT and import the XML.  See if the problem  reoccurs after that.

If it's all termbases ca you confirm where your termbases are stored?  If they are not on your local C: drive try putting one there and see if the problem reoccurs.

Thank you for your inputs. I tried the step of exporting to mtf and mdf and reimporting to a new termbase, but it did not work. My TermBases are all in my C: drive, yes. The old termbase was in my Studio 2019 directory since, even though I created the termbase on the 2021 version, the project it is ascribed to was started on the 2019 version. 
The new termbase after importing was saved in the SDL -> SDL MultiTerm -> Termbases folder instead of on a Trados folder, though I don't think that would make any difference. Still got the error message after loading that new one.

When I first tried just erasing the .mtf and .mdf files, it seemed to work for one term, but then the issue returned again immediately after it. I also noticed yesterday that occasionally I wouldn't get the error message, but that was very occasionally (like 1 out of 15 terms added). I started that termbase yesterday though and it was working fine for a while until this issue began, I'm wondering if it could be some specific term or string of terms that I added which corrupted it somehow? Might there be some limitation in that regard that I'm not aware of?

I don't have any other termbases besides that one so I can't really tell whether that's an issue particular to that termbase or not.

Thank you for your inputs. I tried the step of exporting to mtf and mdf and reimporting to a new termbase, but it did not work. My TermBases are all in my C: drive, yes. The old termbase was in my Studio 2019 directory since, even though I created the termbase on the 2021 version, the project it is ascribed to was started on the 2019 version. 
The new termbase after importing was saved in the SDL -> SDL MultiTerm -> Termbases folder instead of on a Trados folder, though I don't think that would make any difference. Still got the error message after loading that new one.

When I first tried just erasing the .mtf and .mdf files, it seemed to work for one term, but then the issue returned again immediately after it. I also noticed yesterday that occasionally I wouldn't get the error message, but that was very occasionally (like 1 out of 15 terms added). I started that termbase yesterday though and it was working fine for a while until this issue began, I'm wondering if it could be some specific term or string of terms that I added which corrupted it somehow? Might there be some limitation in that regard that I'm not aware of?

I don't have any other termbases besides that one so I can't really tell whether that's an issue particular to that termbase or not.

William Fuhrmann

Is it possible to see your termbase?  If it is please send the *.sdltb only to pfilkin@sdl.com, or make it available via ftp, or dropbox or something like that.

I sent the file to you, saying this now just to make sure you got it. Please let me know what you find.