Executable created with App Builder cannot be executed

[Georg01]

Dear forum,

I am trying to build an executable from a rather big Labview Project with a lot of LVOOP classes. I am using labview 8.5 FDS.

The program runs fine when executed from the development environment and compiles without error. When i try to run the executable, I get a dialog box with a long list of error messages like "VI has an error of type 4E348, 4A348, 302208, 2208, etc., LabView FDS is required to resolve the error" (actually I am using a German version of LabView, so let me quote the German error message: "VI hat einen Fehler vom Typ 4E348. Zur Behebung des Fehlers ist das Labview Full Development System erforderlich")

Any information would be highly appreciated

Thanks

Georg

[jtagg]

Hi Georg,

A few questions first about your application:
- What drivers (DAQmx, IMAQdx...) does your application use (with versions)?
- Do you use any special toolkits in your application? If yes, which ones?
- LabVIEW FDS does not include the Application Builder. Did you purchase it separately?

If I understand you correctly, you have created an application that works fine on the development system.
Do these errors appear when you run the executable on the dev machine?
Or did you deploy it to another machine and get the errors there? Did you just copy the files over manually or did you create an installer?

I'm sorry, that's a lot of questions, but they will help me to narrow down where the problem could be coming from.

It seems though that in general such an error occurs when:
- incorrect driver on target machine
- bad linkage in VI hierarchy

Here are a few links that may be helpful:
http://digital.ni.com/public.nsf/websearch/545B6BCD4D16EE6F862570AE007401DD?OpenDocument
http://digital.ni.com/public.nsf/websearch/862567530005F09C8625675F006BA71B?OpenDocument

Let me know if any of this helps!

Joseph Tagg
National Instruments

[Georg01]

Hi Joseph,

thank you for your reply.

I am using NiDAQmx version 8.6.0f5 as the only hardware driver. LabView FDS is version 8.5, the application builder was purchased seperately. I also have installed Advanced Signal Processing Toolkit, version 7.5.0, but my application does not make any use of it (current status, will change in the future).

These errors appear when I try to run the executable on my development machine (just the executable and using an installer) AND on a newly set-up target machine (deployed using an installer). On both machines WindowsXP SP2 with all updates is installed, on the target machine I have installed the most recent NiDAQ drivers, downloaded from National Instruments web site.

From my feeling, I'd rather attribute those errors to bad linkage or some strangely resolved dependencies of the SubVIs in my application (1400+). I did quite a lot of re-arrangement in the project tree during the development. Would it help if I build up the project from scratch, adding the Main VIs, SubVIs, and Classes step by step?

From what I have observed I don't think the two links you mentioned apply to my problem.

best regards

Georg

[jtagg]

Hi Georg,

Thanks for the information!
I just wanted to let you know that I'll look into it more next week after Easter.

Have a great Easter week-end!

Best Regards,
Joseph Tagg
National Instruments

[jtagg]

Hi,

I've been looking into the issue and although I have no concrete solution, it seems that many similar cases were related to OOP.
I think that it might be a good idea to go through your VI structure and make sure there are no dependancy problems, especially relating to OOP.

Your idea to try to recreate the project from scratch by including all files sounds like a good idea at this point. In the meantime, I will look into this some more and let you know once I've found anything.

Best Regards,
Joseph Tagg
National Instruments

[jtagg]

Hi Goerg,

Any luck in distributing your application? Did rebuilding the project one piece at a time help?
Please let me know where you are at, and what helped if it now works.

Best Regards!

[Georg01]

Hi Joseph,

I just finished rebuilding the project today (have been busy with some other job last week) and now the project builds and runs perfectly (at least on my development machine). Now I can go through the rest of my testing and debugging process.

Thank you very much for your help.

Probably I should give a short explanation on how my application is designed:
I am developing a general-purpose control, data-acquisition and on-line data-processing application for a number of test-rigs in our company. I have chosen a modular design with plugin architecture where functionality for control, daq, etc. is provided as plugins. These plugins are implemented as user-defined classes which inherit from class templates. In this way it is very easy to add functionality e.g. for specialised control or data post-processing. The downside is that there is a lot of method overloading and this might have been the reason why the build process failed. Now I re-arranged all the classes in a "virgin" directory tree and the build process works.

By the way, I changed the way my plugins are loaded from static to dynamic. This is significantly reducing the time to start-up my application.

regards

Georg

[jtagg]

Hi Georg,

I'm glad to hear that it now works!

Thanks for the information, I will store it for future cases that may be similar.

have a great day!
Best Regards!

[BruceAmmons]

I just had the same problem.  I am using LV 8.6 and OOP classes.  Everything worked fine in the development system, but the executable came up with several VIs missing from the general error handler and the same final error message.

I decided to force LabVIEW to recompile all the VIs using shift-ctrl-run arrow.  After saving all the files and building a new executable, the executable appears to work fine.  It must have relinked whatever was missing.

Bruce

[Kenneth]

I am having a similar problem, but it did not go away when I recompiled everything.

Development machine:

Win XP Pro; LV 8.5.1f4 Pro; DAQmx 9.0.2

source in LV runs fine, custom built app runs fine.

Up to yesterday, I could copy the program to a target with a Zipped EXE file and run it.

Target machine:

Win 7; Custom LV Application; DAQmx 8.9.5

At this point, the built application fails to load and reports: 

"VI has error type 4A438"

Tech support suggests that LabVIEW 8.5 and Windows 7 don't play nice.  I am not using OOP's but I have been experimenting with XControls in a separate LVProject.  I also added a feature to create a custom DAQmx scale.