TestStand in developer mode cannot find <vilib> VIs, but the VIs run in LabVIEW

[DLMC]

I am migrating NI2010 LabVIEW and TestStand code up to modern times.  I have mass compiled the VIs to a clean state and have opened the sequence file in TestStand in developer mode.

The first VI that called a core <vilib> VI fails to find that VI.  This is what it says:

General_Message.vi

Loading:

<vilib>:/Utility/error.llb/Clear Errors.vi

Searching:

D:/Program Files(x86)/National Instruments/Shared/LabVIEW Run-Time/2022/Xerces License/Copyright Information

Here is the TestStand SeqEdit_BrokenVILog file description:

{
mode: "VI_BROKEN";
callSite: "CheckVIRefsForMissingDependencies";
timestamp: "2025-10-17T09:32:28.684542";
vi: { name: "-----------------.vi"; path: "C:\-----------------\LabVIEW Modules\-----------------.vi";}
missingRefees: [ { refType: "VIVI"; refIdent: { name: "Clear Errors.vi"; path: "<vilib>:\Utility\error.llb\Clear Errors.vi";}; }
];
callchain: [ { name: "-----------------.vi"; path: "C:\-----------------\LabVIEW Modules\-----------------.vi";},
{ name: "-----------------.vi"; path: "C:\HL_Com_Module\LabVIEW Modules\-----------------.vi";}
];
callers: [ { name: "-----------------.vi"; path: "C:\-----------------\LabVIEW Modules\-----------------.vi";}
];
dependencyIdent: { name: "Clear Errors.vi"; path: "<vilib>:\Utility\error.llb\Clear Errors.vi";};
}

Why is it looking in the Run-Time when I am in Developer mode?  What button did I push wrong?  I have done five previous migrations from NI2010, this is the first time I have seen this.  Could one of the sub-sequences be telling it to use the Run-Time directory?  I have definitely configured the adapter to be Developer mode.

I was testing with the RTE when I completed the packages for the prior code, then switched back to Developer mode to start on this code.

Any ideas?

Be well,

DLC

This is the sixth 10 year old NI2010 based 

[Oli_Wachno]

Telling from the fist error message, it is looking into subfolder of the 2022RTE ( didn’t you previously write something about modern times 😉), but rather regarding license related stuff.

Can you run a simple LV exe on this computer? 

Something HelloWorld-ish? Calling Clear Errors just for fun?

[DLMC]

---

@Oli_Wachno wrote:

Telling from the fist error message, it is looking into subfolder of the 2022RTE ( didn’t you previously write something about modern times 😉), but rather regarding license related stuff.

Can you run a simple LV exe on this computer? 

Something HelloWorld-ish? Calling Clear Errors just for fun?

---

Yeah, I noticed that, and yes indeed, that is me.

I can run the "offending" VI directly in Labview with no issue.  I have the search directories set up the same was as I did with my other projects as well.  So there must be something that I inadvertently did when I was testing in RTE mode that I didn't undo, but I don't find it in my notes or in my searches.

So, to avoid burning the candle on this any longer, I put the code into a source distribution, pointed the sequence file at that and am happily debugging along.  I was going to end up there anyway, so why not just start there...  I guess some battles are just not worth fighting.

be well,

DLC