Trados Studio 2024 randomly crashes as long as my personal Multiterm Termbase is connected to the project. It happens when I confirm a segment. When it happens, I get an error message ("Object reference not set to an instance of an object") from time to time, but not systematically. As soon as I delete my Multiterm Termbase from the termbase list, the problem does not happen any more.
Please help, as this is very inconvenient to me.
First thing to check might be whether your MultiTerm program is up-to-date? Do you have MultiTerm 2024 running on your computer?
Daniel
Hi Daniel,
Indeed MultiTerm 2024 is running on my computer. I've also already reorganised my personal termbase.
Do you have other suggestions?
Marie-Laure Parent
I suggest you open this termbase in MultiTerm Desktop to see if it works flawlessly there. And if it does, seize the opportunity to reorganize it.
Then reattach this checked and reorganized termbase to your Studio projects and see what happens. If it works, you know it was the state of your termbase.
If you still get the problem, you will know that it is related to Studio. In that case, I would first do a RESET of Studio.
Thank you. I've already reorganized my TB and I still get the same issue. Next step is then to do a RESET of Studio, but how do I do that?
I'm currently facing the exact same issue with Trados Studio 2022 and Multiterm 2022. I’ve moved all my glossaries and translation memories to a different computer, and that has helped prevent Trados from randomly crashing. However, I’m also interested in learning how to perform a Trados reset. I assume the steps for the 2024 version would be similar to those for the 2022 version.
Unfortunately, this situation is unacceptable. I know this isn’t the ideal place to complain, but as translators, we’re all working under pressure. We need and expect software that is reliable and rock-solid, not one that crashes randomly and forces us to waste hours of productivity.
That said, I would appreciate it if you could provide the steps for resetting Trados.
That said, I would appreciate it if you could provide the steps for resetting Trados.
Here you go: gateway.sdl.com/.../communityknowledge
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
That said, I would appreciate it if you could provide the steps for resetting Trados.
Here you go: gateway.sdl.com/.../communityknowledge
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Marie-Laure Parent
JESUS SANCHEZ
Hi everyone
We had the same problem last week with one of our translators. In our case, resetting the user profile did the trick. Maybe you want to try this before doing a full reset.
You can do this by clicking on File > Setup > Manage User Profiles > Reset user settings
You might want to save a backup of your current user profile in the next step.
Be aware: By resetting the user profile (or by doing a full reset), specific user-based settings need to be reapplied afterwards.
Fingers crossed one of the solutions work.
Good luck
Seraina
Translate
