Hi Stephanie Tavares

I took a look at what information we have under TQA and error value cannot be null. 

There where several circumstances using TQA that caused that error but most are now resolved and fixed.
What version of Trados Studio are you using?

There is still an outstanding issue that is still open.  It relates to if you enter double quote ("") during TQA. This is marked under CRQ 22501.

While I have no fix or solution for you, I hope this information is still helpful

Lydia

Hi Lydia Simplicio ,

has there been any progress on your side regarding the TQA error message mentioned in this thread?

We're currently facing this problem with one of our linguists being unable to generate TQA reports for the same exact reason.

Both our project managers and translators work with Trados Studio 2021 (SR2 - 16.2.12.9338) and have access to the same TQA configuration as part

of a dedicated customer template. Every now and then, Studio seems to randomly introduce these ghost comments, and I don't really see a pattern here, let alone incorrect user manipulations on our side.

We've already successfully implemented a workaround based on https://gateway.sdl.com/apex/communityknowledge?articleName=000019639

but I was wondering if your developers are aware of this issue and might be able to implement a fix in a future update.

Looking forward to your feedback!

BR,

Julian

Hi Julian Hamm 

Since CRQ 22501 was raised, the cause and fix was identified and as the KB noted: 

I have added Daniel Brockmann to this post to see what is being done development side if anything as the CRQ is still open

Have a good day

Lyds