01-18-2008 07:08 AM
01-21-2008 02:30 AM
02-12-2008 10:32 AM
Does anyone had the same problem ?
What is the solution (if any) ?
06-04-2008 11:22 AM
06-04-2008 12:27 PM
06-04-2008 01:44 PM - edited 06-04-2008 01:45 PM
I noticed that if I turn my DWarns on (LabVIEW.ini, DWarnDialog = TRUE) I get a proptype.cpp (486) DWarn every time I build the executable. This may be related. It has already been CARed (ID 111803).
After rebooting my machine, I was able to build and run the executable without the weird dialog.
NI/AE: what conditions are met in the LabVIEW source code to show this dialog?
Steven: I do work in Utah. MGI is based in Clearfield, but we have clients all up and down the Wasach Front and some across the nation. You do LabVIEW development for AutoCon down in Salt Lake? We host every other LabVIEW users group meeting. You should come next time.
06-04-2008 06:44 PM
01-13-2009 11:58 AM
I am getting the same error message. I did look up on the NI website and forums. I found this link to be releavent. I did get the aplication running when I built it as directed. But I keep on running into this issure very often. I do have labview Runtime Engine installed. I am using Labview 8.0
I did look up my Labview.ini but it did not have DWarnDialog to set the ststua to true
I have had applications running on these machines for like over 2 years now and have never run into this message. I have been seeing this only after the holidays.
I would appreciate any feedback on this.
Thanks,
Nevil
09-02-2010 10:49 PM
Sorry for being late to the party, but I've recently come across the "This is the application template and cannot be run alone" message after building an executable. I'm using LabVIEW 2009 and have tried bundling my dependencies into an .llb and setting the /3GB flag in the boot.ini file as described in the knowledgebase article here. I've tried rebuilding multiple times without success - always the same message. Has anyone figured out a solution to this problem?
Thanks,
Jason
05-09-2012 05:06 PM
I was getting this error over and over on one specific VI I was trying to compile into an application. I ultimately just tried rebuilding the same VI until it would finally work, which would normally take 12-15 rebuilds, very frustrating.
I eventually rewrote the VI to include some additional features, but I changed two things which made everything much better. In the first VI, I would have wires spanning multiple frames (in a flat-frame sequence); in the second VI I instead just used local variables.
Also, in the first VI I had a 3D mesh plot, which I removed in the second VI.
I don't know which of the above two changes affected how the application builds, but it works everytime I try to build it now. Also, the size of the final application dropped drastically (1st VI was ~10 MB, 2nd VI was ~0.6 MB), even though I had more things going on in the second VI.
I hope this information helps someone.