Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 1003, The VI is not executable

My VI is dynamically loaded by a main VI.  Inside my VI, there are some calls to my .NET assemblies for additional execution.  Everything works under LabView host environment.  However, when I run the main VI exe, the dynamic loading fails with error 1003.  The message is "Error 1003 occurred at Open VI Reference in RW_Main.vi"  (the RW_Main.vi is the entry vi of the main VI)  The Possible reason(s) is "LabVIEW: The VI is not executable".

 

When I remove all the calls to my .NET assemblies, the main VI can load my VI successfully.  I try to put my .NET assembly DLL files in different folders (the same folder as the main VI exe, the folder of my VI) but no success.

 

Please give me some hint what I should look for.

 

Thanks

 

0 Kudos
Message 1 of 12
(5,985 Views)

One thing that you could try is to generate a keystoke.  You can do this by calling into the user32.dll in Windows.  Here is an example of how to do this.  Once your report is open, you can call to the DLL and generate a INSERT keystroke.

 

Brandon Treece

Applications Engineer

National Instruments

0 Kudos
Message 2 of 12
(5,976 Views)

Sorry for the last post, it was meant for another thread.  Anyways, is there anyway that you could post a screenshot of your block diagram, or post your code?  I think this will be very helpful in figuring out what is going on.

 

Brandon Treece

Applications Engineer

National Instruments

0 Kudos
Message 3 of 12
(5,968 Views)

The attached screen shot is the code which load my vi dynamically.

0 Kudos
Message 4 of 12
(5,961 Views)

There have been some issues that have arisen very similar to your issue in older versions of LV. 

 

What version of LV are you using? 

 

Thanks,

Sam S

Sam S
Applications Engineer
National Instruments
0 Kudos
Message 5 of 12
(5,934 Views)

It is version 7.0.

 

0 Kudos
Message 6 of 12
(5,928 Views)

This KnowledgeBase article discusses this issue, and what to do to get around it.  I hope that you find it helpful.

 

Brandon Treece

Applications Engineer

National Instruments

0 Kudos
Message 7 of 12
(5,902 Views)

I followed the KB suggestion but I still get the same problem.

0 Kudos
Message 8 of 12
(5,879 Views)

Another thing that you can try is to enable de-bugging in your application.  This will make your application larger, but it could solve the issue.

 

Brandon Treece

Applications Engineer

National Instruments

0 Kudos
Message 9 of 12
(5,812 Views)

You can also try this KnowedgeBase article.

 

Brandon Treece

Applications Engineer

National Instruments

0 Kudos
Message 10 of 12
(5,809 Views)