Yes, according to the other discussion thread I gave before. The error comes from LabVIEW using many threads for the activeX objects; and setting it to run in the user-interface thread means that it will only use one thread to manage its activeX objects.
good luck,
~Darin
Darin Gillis
NI - Chief Product Owner - VeriStand