Dynamically called VI becomes broken inside an executable. Error 1003 from "Open VI Reference".

[N8D11]

Here's the problem. Dynamically called VI becomes broken inside an executable in debug executable mode Error 1003 is occuring from "Open VI Reference" Block. The computer has all of the necessary drivers, NI-VISA and NI-DAQmx. This executable is a new release of software that currently works on the PC in question. I can using NI-VISA Remote Server control the instruments from my PC using the executable. But when I put the executable on the PC I am getting this error. The only way I have been able to get this to work properly is to build the executable from the console I believe the project was created in, note that the project file has been moved to a network drive and it still works. All of the stations I have opened the project in show the VI that is being called is runnable. I've tried building the executable from the console I am deploying to and the same thing happens.

I am honestly at a loss for ideas why this is occuring. Is this something about the way LabView works internally that may be causing this problem?

I have trolled this forum for idea's and none have made sense to me.

Any input would be greatly appreciated.

[JackDunaway]

Two ideas:

1. Mass compile the project to ensure all linkages are ironed out
2. Include the dynamically launched VI's into the "Always Included" section of the build spec

Report back on if either of these actions solves your problem.

[srikrishnaNF]

Hi N8D11,

  If you are using "open vi reference" function,possibly you must have wired the vi path control.When you create executable ,the open reference vi may be unable to find that vi ...The solutions for the problem is to include that vi also in the project and while building,,you just put the directory to data...In the program you give that new data directory..

Thanks and regards,

srikrishnaNF

[N8D11]

I've tried both of these options with no sucess, but I'll try them again.

[srikrishnaNF]

hi N8D11,

  Can you just post your code or provide a screen shot of your vi.

Thanks and regards,

srikrishnaNF

[N8D11]

Attached is the VI, that calls the dynamic VI, sometimes we open two copies each controlling an oven and a power supply and taking turns on shared equipment.

[Tejinder_G.]

Hi N8D11,

Have you seen this article? 

Hope this helps!

[srikrishnaNF]

Hi N8D11,

  Actually the path which you are adding to the open vi refernce function should not be when you hhave included the vi during the build process...Because after included into the exe that vi's path will be changing to /application.exe/your dynamicvi.vi..So you have to use proper strip path/build path and creat a proper path.

Thanks and regards,

srikrishnaNF

[N8D11]

Yeah, I've seen this article. I am curious why this exact code/executable can work on one machine yet not work on another machine that successfully runs a previous version. The only difference from the previous version is the machine performing the build. The build specification is the same as it is opened from a network drive. Only one PC can build this application and not get this error, all of the other computers build the application and this error occurs.

The reason I am trying to fix this is the one PC that can build it is one of the target PC and not the development PC, therefore when changes need to be made often this PC is in use(generally for 24 hours) and I have to wait to build the application. If I can get it to work on the development PC...

[N8D11]

Is there anything internal to LabView compiler or application builder that requires the project been started on that particular PC?