Subvi execution issue after building .exe

Hi all,
I've seen a lot related to this topic but haven't found anything specific to my situation.
I built a simple wrapper to launch different subvi's depending on if it is saturday or not.
The vi works perfectly fine as a vi in LV2012. But when I build the application, both cases execute-that is, both subvi front panels appear and i get a message warning me that I can't run multiple instances of the same subvi.
I expect it to execute either the true or false case and open the correct subvi once and be done with it. Not sure why both cases try to execute more than once only after I build the application. Ideas?
Solved!
Go to Solution.
Attachments:
wrapper.png ‏15 KB

ben64 wrote:
To begin with, you will never get a TRUE (Sat) output because you wired 3 to the offset input of the String Subset function. It should be wired to the length input.
None of this can explain the observed behavior, mo matter how buggy the comparison is. Only one of the cases will execute. It is never possible that "both cases execute" as described.
What is the exact error message? Can you attach the full toplevel VI? What else is in there?
Once you build an application, the toplevel VI will run when opened, of course. Is this handled correctly in the code?
Can you attach the full project, including the build specs?
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

After build exe file . the config.ini file change the path

i have config.ini in my proj
after build exe file i get that error
Error 7 occurred at Open VI Reference in Open Config.vi->Start Main.vi.
VI Path: C:\IRP Burn SW\Labview Proj\EXE Build\SWDL.exe\IRP Burn SW\Labview Proj\configuration.vi
in my proj configuration file locat in : C:\IRP Burn SW\Labview Proj\Config File\config.ini
how can i solved this problem ?

http://digital.ni.com/public.nsf/allkb/FD7DE8BC8FFC256C862565F4006BE363

Slow update of shared variables on RT (cRIO) after building exe

Hi,
I've been struggling with this for the past few days. I am having a problem with slow updating of shared variables on my RT project....but only after building the application into exe's.
The application consists of an RT target (cRIO 9073) sampling inputs at a rate of 1sec. I have a host PC running the front panel that updates with the new acquired values from the cRIO. These values are communicated via shared variables.
Once the cRIO samples the inputs, it writes the values to the shared variables, and then flags the data as 'ready to be read' using a boolean shared variable flag. The hostPC polls this boolean shared variable and updates the indicators on the front panel accordingly.
Now, this worked fine during development, but as soon as I built the RT exe and host exe's, it stopped working properly and the shared variables ended up being updated very slowly, roughly 2-3sec update time.
To give you some more background:
I am running the Labview 2010 v10.0.
I am deploying the shared variable library on the RT device (as the system must work even without the hostPC). I have checked that its deploying using Distributed System Manager, as well as deploying it into the support directory on the cRIO and not the exe itself.
I have also disabled all firewalls and my antivirus, plus made sure that the IP's and subnets are correct and its DNS Server address is set to 0.0.0.0.
There are 25 shared variables all in all, but over half of those are config values only used once or twice at startup. Some are arrays, plus I dont have any buffering and none of them are configured as RT FIFO's either.
The available memory on the cRIO is about 15MB minimum.
What strikes me is that it works fine before building exe's and its not like the cRIO code is processor intensive, its idleing 95% of the time.

Thats exactly what I'm saying, it takes 2-3seconds to update the values.
I have tried taking out the polling on the PC side, and registered an event on the changing of that shared variable and that doesn't do anything to change the slow update time. Even if I stop the PC, and just monitor the shared variables in DSM it updates slowly.
I also tried utilising the "flush shared variables" vi to try to force the update....that does nothing.
I wire all the error nodes religously. Still no luck.
Its very strange, I'm not too sure whats happening here. These things should be able to update in 10ms.

Report Execution issues after cube comperssion

Hi Everyone.
We had performance issues with respect to report execution in SAP portal. After the analysis we have realised that the cube is growing in its size and reached 200 million already.
As per SAP suggestion, we had compressed the cube and the reports started running faster than before.
Now, after the release we have realised that some report executions with hierarchy expansion are caused exception in BEX web application.
Below is the error that we receive
When verified the query, we identified that "Active" was set to "Suppress Zeros" query properties and when we modified it is " Active ( All values =0)" it was working fine.
Could not figure out the reason behind this.
Any quick response is much appreciated.

Just wanted to help others on this issue if they face in future.
We are basically in patch 3 and SAP recommended to upgrade the system to patch 10 to solve this issue.
We are still in the process of doing this as it needs approvals, testing etc to be done.
Hope this will be solved after this upgrade and I will post the result in this blog.
Stay tuned .

Can go back the Main VI after build exe file (by Application builder)

Dear all,
I am writing some vi similar to the vis below.
It work properly at the vi mode, but after I build it to a exe file
(by Application builder). I found when it go back to Main Menu from
Sub Menu, it will close the vi automatically.
Can anyone tell me how to slove this problem?
Here are the vis.
Attachments:
mainmenu.vi ‏31 KB
submenu.vi ‏11 KB
Menu&SubMenu.exe ‏63 KB

Hi,
The problem is that the executable closes the first window, because there is
no reference open to its front panel. A solution might be to pass the
reference of the main VI to the sub VI.
You can also use FP.state iso FP.open. This alows you to hide the front
panel, without automatically closing the vi. I'd prefer this over the first
solution.
Regards,
Wiebe.
"MusicIsLive" wrote in message
news:[email protected]..
> Dear all,
>
> I am writing some vi similar to the vis below.
> It work properly at the vi mode, but after I build it to a exe file
> (by Application builder). I found when it go back to Main Menu from
> Sub Menu, it will close the vi automatically.
>
> Can anyone tell me how to slove this pr
oblem?
>
> Here are the vis.

SMTP Error after Building EXE

After working on this for a few hours, I give up. I'm trying to send an email when an item errors. I am able to get my code to run fine when it's a VI, but when it's an EXE, I get the following error:
Error calling method System.Net.Mail.SmtpClient.Send of ObjectId handle: 0xA971168 for obj 0x30E9943[System.Net.Mail.SmtpClient] in domain [Application.exe for Run] and thread 8748, (System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
Inner Exception: System.Net.Mail.SmtpException: Failure sending mail.
Inner Exception: System.Net.WebException: Unable to connect to the remote server
Inner Exception: System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 10.80.4.119:25
) in testEmailVI.vi
I've traced the issues to SMTP Client Send. Any ideas of what might be going wrong? I'm including my project and exe.
Thanks in advance!!
Attachments:
SMTPTestVI.zip ‏167 KB

As already mentioned you have to allow TCP access for you application in the Windows Firewall (or whatever you use in it's place). By default Windows Firewall blocks all network access for an executable and should show a dialog the first time you run the executable. If you happen to be a fast clicker who dismisses any and all dialog boxes without really reading them you easily can end up telling Windows Firewall to block your executable from accessing the network.
It doesn't matter if you do the network communication through .Net, WinSockets or whatever else network API, as the Firewall hooks into the lowest level socket interface and blocks based on executable, not used interface.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Frankenmac - Weird Issues After Build

A friend of mine has been putting together a "new" iBook out of spare components from other iBooks. He has a G4 800MHz logic board, bottom case, top case, and Combo Drive from one iBook, a DC-In Board from another, a display assembly from a third, and a hard drive from somewhere else. He put it all together, and this is what happens:
When it tries to boot, the fan comes on and stays on
The eject button doesn’t work
When you press the F5 button, the number lock light comes on
The display only comes on, maybe, one out of twenty startup attempts
Could it be that the logic board is no good, or could it be some other hardware issue? The PMU has been reset several times and a couple of hard drives have been tried.
Any thoughts or suggestions would be appreciated.

Hi Chris,
Have you tried booting from the CD? Do you hear any beeping noises? The display may have been install incorrectly; did you remember to reconnect the display data cable? You may want to look at Knowledge Base Document #106214 on Troubleshooting Startup Issues. Do you have access to another Mac? Can you hear the hard drive spinning? You may be having a problem with the reed switch. There are many problems that could be causing this; do you know that all the parts were working when you got them?
Jon
Mac Mini 1.42Ghz, iPod (All), Airport (Graphite & Express), G4 1.33Ghz iBook, G4 iMac 1Ghz, G3 500Mhz, iBook iMac 233Mhz, eMate, Power Mac 5400 LC, PowerBook 540c, Macintosh 128K, Apple //e, Apple //, and some more... Mac OS X (10.4.5) Moto Razr, iLife '06, SmartDisk 160Gb, Apple BT Mouse, Sight..

Issue with building solution file using devenv.exe

Hi,
I am facing an issue while building my solution file (developed in Visual Studio 2010) using devenv.exe from command line. The error is as below.
C:\Code\trunnk\common\Controller\Controller.vcxproj : error : The expression "[System.IO.Path]::Combine(C:\Code\trunk\common\Controller\, "C:\Code\trunk\out/Release/x64"\Controller.exe)" cannot be evaluated. Illegal characters in
path. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets
Could you please help me in understanding the above error and fixing it.

Thanks for all the information. Currently i've tried to use both modules (TextCodepageConversionBean and XMLAnonymizerBean) in my Sender File Adapter, but for now without any result...
To describe the situation: i am using flatfiles which i am fetched from the file system (NFS) by the Sender File Adapter. To translate the characters to the XML strucutre, the File Content Conversion protocol is been used.
The content conversion defines the structure base on the first two characters on each row in the flat file. This worked fine till one of our suppliers is delivering BOM characters like "EF BB BF" in the beginning of the file.The content conversion is not able to recognize my header characters in this situation, which will normally start with "01".
Any suggestions?

Missing subVi after build in llb

I have a top level application that dinamycally calls some Vi contained in a llb library.
Running the app from source works fine. If I build an application the dinamycally loaded VIs open with the broken arrow. If I click the arrow I see that some subvi are missing:
Block Diagtram Errors:
Poly VI 'Read From Spreadsheet File.vi': subVi is missing
SubVI 'Merge Errors.vi': subVI is missing
I build the application including the llb as 'Always included' under source files.
What should I do to have all the llb subVI included or correctly linked ?
thank you
Gianpiero
LV 8.5 + DSC

Ciao Gianpiero,
you can take a look at this document:
Creating a Source Distribution, Application Distribution, or LLB in LabVIEW 8.0
Hope this can help.
Regards,
Andrea N.
Andrea N.
Systems Engineer ATE & RF - Mediterranean Region
National Instruments Italy

Issues with creating EXE in LV 9 (w/ patch)

When creating an executable in LV 9 (with the new patch installed), it is taking around 7 to 8 minutes to create the executable... where as in LV 8.5 it only took around 1 minute (same VI no changes).
After the EXE is done I go into my build folder and find the following folders: NI_HTML, NI_report, NI_Standard Report (these all containing actual VIs (not executables) from the above folder llbs. This never occurred in 8.5 nor in 7...what's going on here? I've got a few customers waiting on the EXE and am just stalled due to this.

This is a joke right? "cleaner method of distribution"?
So I have to do more work to upgrade NI's lower level LLBs in LV 9 when in the 1st place I paid NI to upgrade from 8.5 to 9... doesn't seem close to an upgrade (in regards to plug & play quality) to me! The resource page that supposedly shows you how to fix this issue is vague! ??????? Geesh.
Maybe this is a better way to do things with the "Object Oriented Program" & Classes... though, for a someone only a few years deep in LV...this is not efficient at all (NI is going to start killing it's marketable value if they make this any more difficult).
"Solution:
The Report Generation Toolkit 1.1.3
released with LabVIEW 8.6 was rewritten using LabVIEW classes and
LabVIEW Object Oriented Program. Because of these changes and the
improvements in performance, there are some files that currently are
added explicity to the build directory. Therefore, the behavior is
expected and the executable will run without problems. In a pursuit of
a cleaner method of distribution when configuring the Build
Specifications for executable, all the generated folders can be placed
into one support directory."

Grayscale printing selection lost upon building exe

Issue: the selected grayscale printing, reverts back to color printing after building an executable. How can I have grayscale printing be the default in my executable?
Development package: Labview 6.1.
Operating system: Windows XP
Thanks,
Hathi

You need to add an INI file for the EXE called App.ini where App is the name of the EXE without the .exe. If you alreayd have an INI named that, then add this section to the INI. If not, then create the INI file with the following section:
[App]
colorPrinting=False
Again, App is the name of the EXE without the .exe.

Error 7, report generation toolkits do not work after building.

Hallo guys:
one problem. help!
I tried to build my programs with application builder, unluckly builded exe application does no work well as before, i checked some similar post from this forum, and added that NIReprot.llb in my project and rebuild, the problem still takes place, my program append some text, tables, and charts into a word template with that Report Generation Toolkits, but it always gives out error 7 and 'NI_Word.lvclass:new report subVI.vi -> NI_report.lvclass:New Report.vi -> Creat New Report.vi ->...'error information.
is there anyone can give me some clues about this annoying problem.
thanks a lot!!!
Solved!
Go to Solution.

When you say "attached all this library to my project", it is not clear whether you answered the question about including the dynamic VIs in your build specifications. See attached image. You will need to select the files in your project and set them to Always Included. Have you done this?
Attachments:
alwaysincluded.JPG ‏46 KB

Print VI front panel to file does not work after building executable.

I am using a property and invoke node to print the front panel of my VI to an HTML file. It works fine in the development mode. After Building the application, this subvi will no longer
print the front panel. Is there some special files that included in the build??

You can use the Report Generation VIs to generate the HTML report. Specifically, you could use Append Front Panel Image to Report.vi and Save Report to File.vi to save the image of the panel to an HTML report.
Check out the examples in examples\reports to get a better idea how to use these VIs if you've never used them before.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

MS office report function does not work after building the appication

I use the MS office report function with a custom excel template my application.
It works properly in de developstate, but after building the application it does not work .
I use office 2000 and Windows XP

jmq wrote:
I use the MS office report function with a custom excel template my application.
It works properly in de developstate, but after building the application it does not work .
What error message if any did you get? It could be a couple things:
1. Did you include the Report Toolkit's dynamic vis in the app's build process?
Ref: Error 7 when Running an .EXE Using VIs from Report Generation Toolkit for MS Office
2. How are you giving the path to you custom template, as a relative or an absolute path? The path will be different for the .exe. You have to strip twice.
Ref: Why Can't My Executable Load My Included File When I Use Relative Path Encoding?
=====================================================
Fading out. " ... J. Arthur Rank on gong."

Build EXE error in excel dispose report

I have seen much discussion about path-relative-to-current vi problems when building EXE apps.
I am compiling an EXE which happens largely successfully, but when it encounters the Excel Dispose Report vi at the end of my Excel report creation section, it stops with 'error 7 at open vi reference in Dispose report ...excel quit vi ... file not found'. It works without a problem in the un-compiled version. I am just using the standard Excel Dispose Report vi out of the report generation library.
Can anyone enlighten me about how to clear this problem?
Fred

Fred,
Did you include the dynamic VIs? See: http://digital.ni.com/public.nsf/allkb/C38CE3F30542D65B86256F0E00740DD8
More confirmation it is dynamic VI issue: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

Subvi execution issue after building .exe

Similar Messages

Maybe you are looking for