“Object reference not set to an instance of an object” when creating a new Termbase using Multiterm Desktop 2024

Hello,

Although this used to work smoothly, but for some reason, when trying to create a new termbase --> create a new termbase definition from scratch -->adding language fields (En & Ar) --> Next till ending the wizard since there are not descriptive fields. This used to work all the time. However, now the error "Object reference not set to an instance of an object" is appearing.

I closed the converter, multiterm desktop and trados, then repeated the steps and still facing the same issue.

Any guided help is highly appreciated.

Thanks!

Katia



Removed AI Suggestion
[edited by: Katia Freywat at 5:18 PM (GMT 0) on 15 Nov 2025]
emoji
Parents
  • Probability score: 0.6  

    Question improvement suggestion: Provide the exact version of MultiTerm Desktop you are using, as well as any recent changes made to your system or software that might have led to this issue.  

    In the meantime, based on the information you have provided, here is a suggested answer to your question:  

    Hello Katia,  

    Step 1: Ensure that you are using the latest version of MultiTerm Desktop 2024. Check for updates within the application to make sure you have the most recent fixes and improvements.  

    Step 2: Try resetting your MultiTerm settings. Sometimes, corrupted settings can lead to unexpected errors. You can do this by navigating to the settings folder and renaming it, which will force MultiTerm to create a new settings folder upon restart.  

    Step 3: If the issue persists, consider uninstalling and reinstalling MultiTerm Desktop. Make sure to back up your termbases before doing this to avoid any data loss.  

    Step 4: Check if there are any specific language settings or configurations that might be causing the issue. Sometimes, having multiple language fields can lead to conflicts.  

    Step 5: If none of the above steps work, you may want to try creating the termbase on a different machine or environment to see if the issue is specific to your current setup.  

    I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

    RWS Community AI

    emoji
Reply
  • Probability score: 0.6  

    Question improvement suggestion: Provide the exact version of MultiTerm Desktop you are using, as well as any recent changes made to your system or software that might have led to this issue.  

    In the meantime, based on the information you have provided, here is a suggested answer to your question:  

    Hello Katia,  

    Step 1: Ensure that you are using the latest version of MultiTerm Desktop 2024. Check for updates within the application to make sure you have the most recent fixes and improvements.  

    Step 2: Try resetting your MultiTerm settings. Sometimes, corrupted settings can lead to unexpected errors. You can do this by navigating to the settings folder and renaming it, which will force MultiTerm to create a new settings folder upon restart.  

    Step 3: If the issue persists, consider uninstalling and reinstalling MultiTerm Desktop. Make sure to back up your termbases before doing this to avoid any data loss.  

    Step 4: Check if there are any specific language settings or configurations that might be causing the issue. Sometimes, having multiple language fields can lead to conflicts.  

    Step 5: If none of the above steps work, you may want to try creating the termbase on a different machine or environment to see if the issue is specific to your current setup.  

    I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

    RWS Community AI

    emoji
Children
No Data