vi broken when run in "no visible window applications" but does not have issue when run in sequence editor or TestStand example UI

[LCS__S]

Hi, I have a non-visible window application (contain ApplicationMgr, SequenceFileViewMgr, ExecutionViewMgr and SemiconductorModuleManagerFactory). There is no error when I run a test program sequence file in TestStand sequence editor, however I got a "vi broken" error when I run using my custom UI. This happen to when I configure the LabVIEW adapter to RTE or even Development System. I check the vi that causing the error, I do not see the "broken run arrow" in LabVIEW and I am able to run the vi. I am guessing that the issue happen when LabVIEW not able to find nidcpower.llb or nidcpower_64.dll when I run the sequence file using custom UI.

What is the possible root cause and what is the different when I run using custom UI compare to run in sequence editor?

Environment: LV 2020 64bit , TestStand 2021 64bit

Thanks in advance

[UnholyPenguin]

Try changing the version/bitness of the TestStand LabVIEW adapter.

I think I misread the question.  Not sure I understand it, sorry.

[Oli_Wachno]

Sounds tricky....is the NIDC Power related code the first LabVIEW Code which gets executed? If you comment out "Init DCStuff", will you see other broken VIs then?

[LCS__S]

Update on my findings:

I realize that I need to configure the complete file path of the dll file for "Call Library Function Node". the default value was nidcpower_*.*

The vi file that use the dll is "niDCPower Initialize With Channels.vi"

Is there any configuration that can configure where the LabVIEW runtime will search for the dll so that I can remain the default value as nidcpower_*.*

But I am also curious that why this error does not appear when I run the sequence file using sequence editor (also using LabVIEW runtime)