VI not found in instr.lib when using Project path

[OnlyOne]

Hello,

why can teststand not find the VI when i insert the project path to an instrument driver saved in instr.lib?

When i delete the project path then it can be found.

The blinking red error says

"Labview: (Hex 0x7) Datei nicht gefunden. Die Datei befindet sich an einem anderen Speicherort oder wurde gelöscht. Verifizieren Sie in der Befehlszeile oder im Datei-Explorer, dass der Pfad korrekt ist."

Also when i change from adapter=runtime to adapter=development it is working.

Thanks

[Oli_Wachno]

Do you have your instr.lib in the TestStand search path list?

[OnlyOne]

Yes, inclusive SubDirs

[Oli_Wachno]

No Project Path works with RTE

Project Path works with DevSystem

Did I get that right?

[OnlyOne]

Thats correct.
When i change to DevSystem it is working.

[Oli_Wachno]

I remember having seen this before... yet I don't remember the context 

Using Google I found https://forums.ni.com/t5/LabVIEW/LabVIEW-runtime-lvproj-and-Teststand-deployment/td-p/3747113

yet this seems to be deployment related.

What is your motivation for defining the lvproj in the module adapter? 

[OnlyOne]

The reason was that teststand is using the correct file.

Currently, after removing the project path, it is finding and using the wrong Initialize.vi.

[Oli_Wachno]

Valid UseCase!

You've found a strange behaviour there: when trying to reproduce this, I was successful using stuff from instr.lib (independently whether contained in search path or not)

I was not able to reproduce this when using some random code from different directories....

I recommend opening a Service Request at NI 🤔

[Oli_Wachno]

Could you please share your findings once you have this problem solved?

[OnlyOne]

The workaround is to put the full path in the vi-field.

I dont have a solution 😞