Setup:
I have some class member VI calls I'm trying to use in a TestStand sequence. The classes have the following inheritance:
Parent class "A" has descendants "B" and "C". Descendant "B" has class "D" as a descendant as well.
This is under Windows 7, LabVIEW 2015 SP1, LabVIEW 2015 SP1 RTE, and TestStand 2016.
Problem:
I can't use a class member call from classes C and D in the same sequence under the Run-time engine. If I try to do so, I get the well-known error -17600. However, if I use a class member call from just C it works, and a class member call from just D it works. The entire sequence also works with both in it if I switch adapters from the RTE to the LabVIEW development environment. I've done the usual things that are recommended for error -17600:
- Clearing the object cache
- Did a mass recompile of all classes
- Verifying all dependency paths are in search directories
- Running the update VI tool
- Load them both in LabVIEW at the same time to ensure they get all their dependencies from the same locations
As an additional restriction, these two classes are from a site-wide library that we use extensively in our pure LabVIEW code. I can do bug fixes and such if I find something wrong, but I can't split apart their family tree or anything major like that, as their code needs to be in sync with and compatible with all existing programs that use the code.
I'm not allowed to post the contents of these classes, but they're basically configuration classes, using DLLs (both .NET and non-.NET) to get setup information from a SQL database and parse it out into a LabVIEW format. They also use assorted other classes from other libraries we use frequently.
