Error 1003 - The vi is not executable. Simulated DAQ-cards.

[cmh]

Hi all,

I am updating an application written in LabVIEW 7.1 for a customer. The code is not made by my company and is pretty horrendous but it works. I can not develop the code on the machine that it is supposed to run on so I have to do it on my own computer which means that I have to simulate two DAQ-cards that the program needs. I have pretty much finished the program and I want to test if I can build an exe-file. This is where I run in to trouble an get the error message:
Error 1003 occurred at \\Server1\Users\martinh\LabVIEW Data\app\internal.llb\_Main.vi
Possible reason(s):
LabVIEW:  The VI is not executable.

I know that this has been discussed at length here and that one has to look out for global variables, dynamically loaded VI:s etc. My question is, does anyone think that the simulated DAQ-cards give me trouble? Do they use some VI:s placed somewhere odd which I need to include when I build the application?

Sincerely
Martin

[RobBoyer]

Hi Martin,

I had the same exact problem recently, and it turned out not to have anything to do with global variables or dynamically loaded VIs, etc.  What may shed some light on the actual issue is if you force a re-compile of the VI that the builder is complaining about.  (To do this, hold down shift and control, and hit the run button on the VI.)

In my case, this cause the dreaded "broken arrow" to appear and I discovered the root cause to be an ActiveX function call that needed to be relinked to resolve a version conflict.  In your case, maybe you do not have some necessary software component that the code is expecting to exist?

Good luck,

Rob

[cmh]

Hi Rob,

Thanks for the answer. I had no luck with the recompiling, the arrow is still whole but the same error appear when I try to build an exe file.
Further suggestions are welcome as I continue the hunt for the source of the problem.

/martin

[RobBoyer]

Sorry to hear that didn't help.  Maybe you could suggest to the customer to rewrite the code using a development environment that works as advertised?  🙂  jk - sort of.

[AndreasE]

Hi Martin,

I suggest you try what is suggested in this link, some of the information is already covered in the posts above but some might be new.

http://digital.ni.com/public.nsf/allkb/705C2ECA081F3C7986256C0F00559B02?OpenDocument

If you are using the office toolkit, it might be an idea to masscompile the _office folder and you might also need to uncheck the "Disconnect type definitions and remove unused polymorphic VI instances".

Good Luck

[cmh]

Just to let you know, the problem has sort of been solved. Converting the whole thing from LabVIEW 7.1 to 8.5 revealed that one and the same  subVI was loaded from two different locations, this might have caused the trouble. It had nothing to do with global variables or simulated DAQ-cards. Maybe it could generally be a good idea to convert to 8.5 if possible since this version seems to be better at discovering and providing information regarding errors when building exe-files?

/martin