LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 1003 when running .exe

I am having a problem with error 1003 when I run a built application.  I have searched the forums and found many others with this problem, but they encounter the problem while building the application, not while running the built .exe.
 
I have a top level VI (AutoRun.vi) that calls 3 VIs in sequence.  All three are called in the same manner.  The first two work fine, but I get this error with the third sub vi.  This is how I call the subvi:
 
Use App.kind, check for "Run Time System" (strip app path twice), or "Development System" (strip app path once)
Build path to combine stripped path and file name of subvi to open
open vi reference
Invokee Node - Open FP
         Activated - T
         State - Standard
Invoke Node - Run VI
          Wait until done - T
          Dispose ReF - F
Invoke Node - Close FP
Close VI Reference
 
The error I get is:
Error 1003 occurred at Invoke Node in AutoRun.vi
Possible reasons:
LabView: the VI is not executable
 
I do not get this error while running in the development environment.  Only when I run it as a .exe.  Also I have had no problems with this code in the past.  I just made a small change and now I have this problem.  I have gone back to the old code and have the problem with it too. 
 
I build the app by starting the app builder, selecting the top level VI, adding dynamic VIs and select all 3 subvis.  The front panel of the second VI is not visible while running.  I have to go in and manualy change the "Remove Panel" in the build settings for this VI from the default yes to no.  If I do not do this I get an error while trying to run the built application.  I have no idea why this happens either, but making this change fixes the problem.  After this I select build.
 
BTW, I have LabView 7.0
 
0 Kudos
Message 1 of 3
(3,172 Views)
I still have no idea what was causing this problem. But I went back and killed labview, then opened and resaved the .vi that was causing the problem, then tried again and everything works now. 
0 Kudos
Message 2 of 3
(3,167 Views)
Hello,
 
Not sure what happened on your end, but if the problem comes back repost and we'll explore it!
 
Best Regards,
 
JLS
Best,
JLS
Sixclear
0 Kudos
Message 3 of 3
(3,154 Views)