12-19-2012 08:41 PM
This error still occurs in LabVIEW version 10.0f2.
It occurs after a TestStand sequence completes. The sequence calls LabVIEW modules.
Sorry to revive an old thread.
Were there any clues to the root cause?
12-20-2012 06:10 PM
Ray.R
Several corrective action requests were filed for this issue, and our reports indicate that the bug was fixed in the 2010 SP1 release of LabVIEW. It sounds like the error has to do with the non-DFIR compiler, which was not supported in 2010 and was actually eliminated completely in the 2011 version of LabVIEW. For more on compiler theory, check out this tutorial.
Based on the previous posts in this thread, it sounds like the error may have been lingering after the release of 2010 SP1. If you have access to LabVIEW 2011, I would be interested to see if the issue persists.
02-02-2013 10:44 AM
In my situation, there were two contributing factors, one which was partly discussed in this thread. It was related to the TestExec.ini file. The other situation was related to some residual VI's that... well.. the best way to describe it is that they were out of sync. (long story)