Philippe Noth 

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!!

Hi Paul,

Your video convinced me… Now, for the past 4 years 75% of my projects have been Groupshare projects, I wonder whether there is a relationship. I opened a local project I had created myself, and I indeed, I can click any line without getting the error message.

In that same TM window, with every Groupshare project I have this entry below which I could never suppress. Could it be the culprit? Even though I am not clicking of this entry but on a valid TM:

In summary, my TM window typically looks like that:
 

Philippe

Philippe Noth 

Philippe Noth said:

Could it be the culprit?

I'm not really sure, but certainly this additional info may help find the problem.  I'll ask someone in that team for an opinion on this and to see if we can repro.

Philippe Noth 

The issue appears to be the Unknown (sdlmtcloud) TM that is not available. If you do not have that TM in the list you won't be able to reproduce the issue. You need to remove it by following the contents of this article: https://gateway.sdl.com/apex/communityknowledge?articleName=000004789 and check if the issue still appears after loading all of the other TMs back.

Philippe Noth 

Just to add to this... you should probably either clean up your project templates or recreate them as this error is probably coming from your existing project templates that have a reference to a TM that is not longer there.

Thanks for the ideas to fix the issues. 

I had immediately applied Paul Tudoran's suggestion to a Groupshare project I was currently working on and it did not remove the sdlmtcloud entry. However, I wanted to wait for a brand new Groupshare project to report whether it works or not.

Well, I just opened and checked out two new Groupshare projects that were assigned to me. Beforehand, I had renamed the folder containing TranslationMemoryRepository.xml and the whole Studio 2022 folder in Documents. The issue with the invalid entry in the TM remains.

In one project, I have…

But generally, I have…

I am going to ask the agency again. It may come from their side, the way they prepare their projects.

Philippe

That sdlmtcloud entry in the TM window was likely a wrong track…

Today I had a Groupshare project for another end client (= prepared by another PM). Nothing wrong in the TM window but same error as I tried to delete the TM I attached by mistake.

Could be because of the way I name my TMs, with spaces and dashes. Or maybe the file path is too long. Will make some tests along with future projects.

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

As I wrote, this is cosmetics… Functionality is not affected.

Philippe