We're seeing a bit of a strange problem - I wasn't sure whether to place it in the TS discussion forum or here. Anyway, we have a sequence file (TS4.0) that contains a number of calls to LV8.5 VIs. When logged in as technician, we'll run some tests, and we'll get an error message saying "Error Message: LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located...[Error Code: -18002]. I know this sounds simple - just go fix the broken code dummy. However, if we log in as Admin, the problem is not there. Then, if we log back in as Technician, the problem doesn't appear. Now this doesn't always happen, but it happens enough that we can't send this out to our customer like this.
One of our guys did some digging and he said, Even though the error is seen in TestStand upon loading this particular VI, it appears to be traceable to NI_FileType.lvlib and more specifically to the GetFileType.vi contained therein. The issue might be deeper than this. It appears the libraries "C:\Program Files\National Instruments\Shared\Variable Manager\dialog (and/or dialogs)\NI_FileType.lvlib" and C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\lvfile.llb\NI_FileType.lvlib" can "mirror" each other as attempts to load various polymorphic LV vi's (including check if file exists.vi) periodically leads to cross loading (i.e. loading from an alternate location when I start them up even on my office PC).
I'm wondering if anyone has seen anything like this, or knows a way to specify that LV use a particular version of GetFileType.vi
