Windows 11 enterprise
LavVIEW 2022
TestStand 2021
Using the development environment, not using a deployment on another computer.
Using VIs and sequences ported from NI2010 days.
I have ported VIs from a NI2010 environment, made all VI calls in TestStand relative addresses, made sub-VIs access support files as relative addressing. Have configured the search Directories to include the LV vi.lib directory.
I can run the sequence files using the execute->test UUTs and everything runs.
I have built exe launchers for my OI when the development is chosen, and those run fine.
When I try to run the TestStand sequences using the RTE, I immediately get this error:
mode: "VI_BROKEN";
callSite: "CheckVIRefsForMissingDependencies";
timestamp: "2025-07-18T16:12:47.200056";
vi: { name: "Generic Scan_SN_OrderNumber.vi"; path: "D:\Projects\project\LabVIEW Modules\Generic Scan_SN_OrderNumber.vi";}
callchain: [];
callers: [];
dependencyIdent: { name: "Trim Whitespace.vi"; path: "<vilib>:\Utility\error.llb\Trim Whitespace.vi";};
I have followed all the rules to create a deployable test, why can't the RTE find core labVIEW VIs? I have read through a bunch of other issues like this one, but they never seem to get solved or the OP never says what solved it. I have the lv.lib directory in my search directory, near the top.
I have not changed much in the guts of this code other than to update to newer VIs where old ones were no longer supported or were deprecated. This code all ran in the NI2010 LV/TS system with the RTE. Is there some secret sauce in the newer LV/TS that I need to follow?
Needless to say, I have not tried creating deployed solutions since I can't even get it to run in the dev. environment.
This discussion was great, but even it did not solve my problem:
I note the OP did not report back whether it solved their problem.
This is so basic I have to have missed something obvious. Can someone point it out to me?
be well,
DLC