Hello all,
Thank you for your reply Rob, I also suspect that the problem is related to "second-tier" subVI calls made by the first-tier subVIs. Here are answers to the questions you asked in your post:
-Yes, I am calling the VIs with absolute paths. To be more specific, I use the "VI Path" property of the VI (before exe) or "Directory Path" property of the Application (for exe).
-The three large subVIs that are called dynamically all share several subVIs. I suspect the problem is somehow related to this. To clarify, all three VIs use several specific VIs that I have written to open/read/write/close an industry-formatted file. I verified that the three main subVIs all call the common subVIs from the same locations on disk, i.e. the same subVI should not be included twice under different file locations. For a quick test, I dropped the file-editing subVIs into the 4th subVI (which never fails to open/close) and rebuilt the application. The results are the same: The 2nd, 3rd, and 4th VIs can all be opened and closed multiple times with no error. The first VI can be opened and closed once with no error, but then none of the first three VIs can be opened again (error 1003). Meanwhile, the trusty 4th VI can still open and close after the error begins, now with the several common VIs included in its code.
-I have the debug license, but I'm a little confused by what you suggested. At this point I am not running the subVIs (via invoke node) in order to produce the error, I need only try to open and close a reference to the VIs. I'm not sure if you meant to trace the execution of the subVIs when running them or if you had something else in mind. Can you please elaborate?
I am attaching an image of the block diagram of the top-level VI in case that helps. In the meantime I will continue investigating subVIs and attempt to identify any more useful symptoms. Thanks Rob (and anyone else!), I really appreciate your help.
