TestStand GUI (TestExec.exe) randomly reports error -17500 (TestStand SeqEdit R6025-pure virtual call)

[morngoose]

Using Labview 2009 and TestStand 4.1, I have developed a test solution.

Found that I get the intermittent Error -17500 appear while running my sequence file using the TestExec.exe (TestStand simple user interface), which then abort testing.

I then used the TestStand Sequence editor to run my seq file, and again, I get an intermittent failure, but this time it reports:

Microsoft C++ Runtime Library Error, R6025 - pure virtual call - seqedit.exe

Seems this must be a Labview/TestStand bug.

Anyone ever come across this ? Very annoying bug this as it stops our production line.

Thanks

[dug9000]

Do you have any dll calls or only LabVIEW VI calls? Do your LabVIEW VIs call into dlls?

This error can happen if a dll is unloaded and then called into or if memory is getting corrupted, there are probably other things that can cause this error as well.

It's much easier to have such bugs in C/C++ dlls then it is with LabVIEW VIs, that is why I'm asking what type of code modules you are using.

If the problem is easily reproducible, can you try narrowing down which part of your sequence is required for the problem to occur? Also, if you are using the LabVIEW runtime can you try switching to running your code modules in the labview development environment and see what happens. For example, does the LabVIEW process now crash instead of the TestStand one?

Hope this helps,

-Doug

[morngoose · Accepted solution]

Thanks for your reply.

The problem went away when I changed the Labview adaptor in TestStand from the Labview Engine back to to the Labview Developer.

I had to install the Labview license on this PC to use the Developer license, but at least this got rid of the problem.

I would have expected the Labview Engine, or TestStand for that matter, to be more stable than this.