"Object reference not set to an instance of an object" in Translation Memory window

Hi everyone,

I have seen this error in the Translation Memory window for a very long time, probably since I began using Studio with version 2017. It happens when one clicks a checkbox to remove an entry in the list. Today I also had it in the Update Main Translation Memories batch task, when selecting the TM to update.

Error dialog in Trados Studio showing 'Object reference not set to an instance of an object' with a red X icon, indicating a null reference exception in the Translation Memory window.

It is "cosmetic", as once the dialog is closed, the checkbox is selected and it is possible to do the intended action. But I thought it was about time to report it.

Stack trace: /cfs-file/__key/communityserver-discussions-components-files/90/sdlerror_2D00_2023715_2D00_1h16m31s.sdlerror.xml

Philippe



Generated Image Alt-Text
[edited by: Trados AI at 11:42 AM (GMT 0) on 29 Feb 2024]
emoji
Parents
  •   

    The error stack indicates that a System.NullReferenceException has been thrown, which is a common runtime error in .NET applications. This error means that you are trying to access a member (like a method or property) of an object which is currently null.  In other words, it's like trying to use a feature of something that doesn't exist in the current context.  However, it's not simple to reproduce...

    It could be a problem related to not being able to see your TMs.  For example, if your TMs are in OneDrive (or some other online location) and the synch removes them as they are not always being used, then when you try to remove them they won't be there and the software throws the NullReferenceException.

    Obviously we should handle this better, especially since everyone uses OneDrive (knowingly and unknowingly) these days so even though we don't support it we should at least handle the error better... if this is even what it is!  I can only guess at this stage.

    I don't think this is common problem, and certainly I don't recall seeing this before, but I'm glad you reported it.  if we can reproduce it we can fix it!!

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
Reply
  •   

    The error stack indicates that a System.NullReferenceException has been thrown, which is a common runtime error in .NET applications. This error means that you are trying to access a member (like a method or property) of an object which is currently null.  In other words, it's like trying to use a feature of something that doesn't exist in the current context.  However, it's not simple to reproduce...

    It could be a problem related to not being able to see your TMs.  For example, if your TMs are in OneDrive (or some other online location) and the synch removes them as they are not always being used, then when you try to remove them they won't be there and the software throws the NullReferenceException.

    Obviously we should handle this better, especially since everyone uses OneDrive (knowingly and unknowingly) these days so even though we don't support it we should at least handle the error better... if this is even what it is!  I can only guess at this stage.

    I don't think this is common problem, and certainly I don't recall seeing this before, but I'm glad you reported it.  if we can reproduce it we can fix it!!

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
Children