Hi Anthony Michael 

Could you please post the full stack trace error message? This would help us better understand the issue.Thank you!

Kind regards,

The error message is not in a pop-up window

Please try and see if you can expand it. If not, maybe try the reset (Workaround 2) https://gateway.sdl.com/apex/communityknowledge?articleName=000001414

Kind regards,

Wow, that is way too complicated for me, I'm not a developer. Do you have anyone there who can help? This is ridiculous.

I have found from searching painstakingly through various forums (since your support is excruciatingly slow to respond), that for some reason the memory is getting unclicked in the project settings. When I click on it, the concordance search works, but the memory keeps getting unclicked. Why is this happening?  

Anthony Michael 

Unfortunately this "Object reference not set to an instance of an object" tells us nothing which is why Elisa asked for the stack trace.  If you'd shown a screenshot of how the error surfaced if it's not a popup then we we could hopefully explain where to find the details that would be helpful.

Anyway... this isn't our support.  It's a public forum.  If you had technical support I'm sure it would be fast!

Anthony Michael said:

for some reason the memory is getting unclicked in the project settings. When I click on it, the concordance search works, but the memory keeps getting unclicked. Why is this happening? 

Hard to tell from this minimal information but a guess would be you have the TM stored in OneDrive with cloud only options and so Trados Studio cannot actually find it.  Can you provide the full link to where the TM is actually held?

Or maybe you just don't have access to that memory at all?

It's not in the cloud it is on my company's server.

Anthony Michael 

I think you need to click on the Enabled checkbox:

still doesn't work

The memory itself is still updating and the concordance search works for the target