11-16-2007 11:37 AM
11-16-2007 01:01 PM - edited 11-16-2007 01:02 PM
11-19-2007 07:29 AM
Five Stars!
The Labwindows/CVI Runtime Engine got corrupted somehow. Running the repare on the runtime engine fixed our problem.
Please note, we were not using TestStand 2.0 in any way and did not/never had it installed on the machine(TS 4.0 only). We are not sure how the CVI runtime engine got corrupted but we were receiving some "new" files for an operator interface that was copying over new files for TestStand's \cfg directory. That when the problem started to happen.
In either case the solution provided was the fix. Thanks