Application Builde Error

When I build my application in Labview 6.1(Win 2000), the error is "Error 1 occurred at Snd Gen Error Call Chain.Vi\., possible reason:
Labview: An input parameter is invalid", What sould I solve this problem?
Thanks.

Typically, this occurs when vi's have duplicate names. Find all instances of Snd Gen...vi and rename the dupes.
See the handy dandy ni doc strangely titled "What Do I Do When I am Building An Application and I Get Error 1: "Error saving file xxx.vi"?" at:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/283d12080ec1d339862568d2005617b0?OpenDocument
or the Application Builder Troubleshooter at:
http://www.ni.com/support/labview/toolkits/appbuild/
2006 Ultimate LabVIEW G-eek.

Similar Messages

Application builder error 1055

ed. cross-post: http://lavag.org/topic/18047-application-builder-error-1055/
Hello everyone
I have a big problem with building applications lately. The build is running fine until the end, when it throws:
Error 1055 occurred at Property Node in VISL_findDependentVISvr.vi->VISL_findAndProcessVISvrList.vi->VISL_detectAndCopyVISvr.vi->AB_Engine_Copy_CustomIOServer_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Object reference is invalid.
Has anyone seen this error in app builder? Does anyone have any idea how can I resolve this problem?

Lennard, Valko
I'm using LV 2013 f2. Let me give you some more details and... The story how I fixed it:
The project is pretty big (~1500 VIs) and highly object-oriented (~300 classes). It has RT (PXI) and PC part. Some of the classes are shared between PC and RT. The problem with build was present only on PC - build for RT was ok.
I had DSC module installed, but it was not used in this project at all. Despite that, when I found information from Lennards link, I've tried to build it using "Enable Enhanced DSC Run-Time support". It didn't help. I started to wonder if the sharing of classes between RT and PC has something to do with the problem. So I refactored the project, splitted it into two projects (one for PC, one for PXI) and reduced number of shared classes (especially some specific classes, which implement "threads"). Afterwards, the build could be done just fine, but only in those refactored projects.
Now for the plot twist: before refactoring, I've tried to build the project on another computer. It was build without any problems! So I started to look for the differences. First of all, just before the build I've updated one of our internal libraries in VIPM and changed its name - so it was my main suspect (I needed to update dependencies in project as the change of VIPM package name changed it folder in vi.lib). This + disconnecting code from VIs and I though that I've just found another way of destroying LV compiler completely. Still, I couldn't fix it in any way...
As per Valko suggestion I've uninstalled DSC module completely. Once again - my project does not explicitly use this module at all! Removing the module didn't broke anything in the project. And guess what? The build was done without problems! I've even tried to do this build again on the code revision before refactoring, and the build was done!
tl;dr: REALLY NI!!?!? REALLY!? YOU'VE BROKEN SOMETHING IN THE MODULE WHICH I DON"T EVEN EXPLICITLY USE AND MADE ME LOSE FEW DAYS OF WORK JUST TO FIND IT OUT? REEEEAAAAALYYYYY!?

Application builder error.llb

Hi all,
I'm using application builder to compile an executable of my VI. Compile runs without a hitch.
However, when I try to launch the .exe three subvis from error.llb are missing : Not Found Dialog.vi, Details Display Dialog.vi and Set String Value.vi
The compiled .exe seems to be looking for these VIs in instr.lib, which is nowhere to be found in the compile folder.
This happens even on my developpment machine, on which, of course, the VI runs fine from within LabView.
Did I miss something during the compiler setup ?
Thanks in advance for your help !
Nico
Solved!
Go to Solution.

I've had this before, and it was reported by NI as being a bug that comes from loading up a project that was built in an older version of LabVIEW and creating an application from it. For me it was loading a LV8.5 project into 8.6.
The only workaround was to add the three missing vi's to the project, and ensure they are added to the Always Included list within the application builder.
You will find these vi's in Program Files\National Instruments\LabVIEW 8.x\vi.lib\Utility\error.llb. Simply add them to your project somewhere, then in application builder made sure you select them as Always Included in the Source Files section, then rebuild your application.
Message Edited by Thoric on 03-13-2009 03:52 PM
Thoric (CLA, CLED, CTD and LabVIEW Champion)

Application Build Error

When I try to build my application I get the following error: Error 26096 occurred at BuildApplication.vi>>DistCallCreateInstaller.vi>>WinInstallCreate.vi>>WinInstallAddMergeModules.vi>>MSIDKLoadMergeModules.vi C:\Program Files\National Instruments\LabVIEW 6.1\applibs\distkit\redist\Modules\ActiveXContainer.Msm
Possible Reasons:
NMDK_AMM_UNSPECIFIED_MERGE_ERROR

Hi
This behaviour can happen when installing Visual Studio .Net or ORCA because they install a newer mergemod.dll which isn't compatible with the older version that LV 6.1 uses in the Application Builder installer.
This steps should help:
1. Open a command prompt.
2. Change to the "\Program Files\Common Files\Microsoft Shared\MSI Tools" directory.
3. Execute the following command: "regsvr32 /u mergemod.dll". This should report that the unregister was successful.
4. Change to the "\Program Files\National Instruments\shared\Installer" directory.
5. Execute the following command: "regsvr32 mergemod.dll". This should report that the register was successful.
Hope this helps
Luca
Regards,
Luca

Blueprint Application Builder Error.

Dear Gurus,
I went to CRMC_BLUEPRINT transaction code and selected the BluePrint Application Builder. BAB got launched in Internet Explorer. When I select the Application as "Leads" and View as "Lead Manager" and click on "Load Application" I get a java script message saying "SAP data could not be maintained in the customer system". I get this message for any selection of Application and View. Can you pls advice me.
Thanks!
Vivek.

Vivek, get me your email address and will forward you the CRM PC-UI 4.0 Cookbook and I would recommend you to go through the examples and the end of the documentation to get a feel of the concept and how to tackle your questions. Also read the conceptual piece of the blueprint tables and their possibilities. If you have any questions just let us here now and help you gladly. Tiest.
By the way also have a look at my weblog: <a href="/people/tiest.vangool/blog/2005/07/24/pc-ui-and-easy-enhancement-workbench-eew-integration and Easy Enhancement Workbench (EEW) Integration</a> which describes the generic process on how to extend transactions and make them available in PC-UI.
Message was edited by: Tiest van Gool

Application Builder error in LabVIEW 7.0

I am maintaining some legacy code in LabVIEW 7.0. I have recently (perhaps within the last month or so) been getting Error 1003 in Dist Copy Non-VI Files.vi (part of App Builder) when building my code. I've done some testing, including trying to build much simpler VIs, and get the same error. Curiously, this occurs on multiple (Windows XP SP3) machines, both "real" and "virtual", including on two of three installations on a single PC (so it is not hardware-dependent).
I have a strong suspicion that the problem is neither my code nor LabVIEW itself, based on the following logic: 1) This problem arose on multiple PCs at about the same time (i.e. I don't recall seeing this a few months ago, now I see it on almost all of my PCs). 2) There are two PCs where I do not see this error -- when I check the LabVIEW installation files between a PC that "works" and one that doesn't, the differences seem (to me) to be small, more related to "what did I do most recently" or "how much of MAX did I install, which drivers". (3) Using or not using OpenG in my code mades no difference, nor does turning off Anti-Virus scans.
I tried two other things. First, I have a VM that I recently build (which I think is significant) that has both LabVIEW 7.0 and LabVIEW 7.1. The build fails with LabVIEW 7.0, but succeeds with LabVIEW 7.1. In addition, I found a VM, built a year ago and "sitting idle", with LabVIEW 7.0 on it. I fired it up, did not allow Microsoft Update to update anything, and tried the build with LabVIEW 7.0 -- it worked!
My current working hypothesis is that some "patch" installed by Microsoft (.NET? ActiveX?) has clobbered something in the LabVIEW 7.0 Build Application. Unfortunately, the VIs that make up this application are password-protected, so I can't see "inside" to discover what file or other condition is responsible for the error message.
Does anyone have any ideas or suggestions? [Don't suggest "Upgrade to 7.1" -- I'm the only "maintainer" of multiple PCs and multiple applications, some of which run on systems "belonging" to other people. I am in the process of rewriting the code in "modern LabVIEW" (2011) and will port it widely, but until then, it's not practical (or "politically correct") to make the 7.0 -> 7.1 shift ... Besides, my curiousity is piqued!]
Bob Schor
Solved!
Go to Solution.

Good point. The reason for my "laser beams" is several fold. First, I follow a written protocol (I wrote it!) whenever I install or re-install LabVIEW 7.0, so I'm pretty sure that all of the installations "should be consistent" (if not identical). Second, I compared two NI folders in Program Files between a version that worked and one that didn't, and while there were differences, it seemed "not likely" to be an explanation. Third, I'm 99% sure that at least one of the systems that now cannot build (of the eight installs, all by me, that I've checked, only three worked, and one was on a PC that hadn't been turned on in over a year, hence was certainly not updated) was able to build previously (i.e. I don't recall seeing this problem until about a week ago, when I started re-building an update to my legacy application). It is possible that this problem was always present on these systems, but doesn't seem likely.
Nevertheless, before the beginning of next week, I plan to take one of my "failing" systems, uninstall LabVIEW (but not change the OS in any way), reinstall it, and see if I can build. If this still fails, I'll take the "old" system I mentioned above and start bringing it "up to speed" until I "break" the App Builder. Note that it is possible that MicroSoft is not to blame -- I have other software (such as editors, utilities like WinZip, etc.) that have also been updated, and one of them might have clobbered the Builder.
Will let you all know what I find.
Bob Schor

Application builder Error: Windows SDK function returned an error. (Error code -12) *** End Error Report

try to create an installer in Labview 8.6. The build fail and I got this message.
CDK_CreateNewWizard_Invoke.vi.ProxyCaller >> CDK_CreateNewWizard_Invoke.vi >> CDK_InstallerConfiguration_Editor.vi
>> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'NI LabVIEW 8.6.1 Datalogging and Supervisory Control Module' from:
D:\software\application\LabView\NI.LABVIEW\NI-Labview 8.6.1 DSC Module\ to: C:\Documents and Settings\Lidaoling\桌面
\Builds\generate waveform\My Installer\
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
Copying files...
Updating files...
Creating merged database...
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
Done building deployment

Solution

Application Builder Error "Browse to LabVIEW.exe"

LabVIEW gurus...
I am currently building a standalone app from my project. When I run the application (which builds successfully), LabVIEW prompts me to browse to the LabVIEW.exe file. However, I want this app to run on a computer that will not have LabVIEW installed, and so browsing to this file isn't an option.
I know that the reason for this problem is that I'm using 2 call library functions named StrLen and MoveBlock within the LabVIEW.exe library (to access data from a pointer to a pointer).
LabVIEW.exe shows up as one of the dependencies in my project, but I can't figure out how to add it to my build specifications. I tried to build an installer and include the LabVIEW runtime environment, but this doesn't seem to work either.
Any suggestions would be greatly appreciated!
I'm using LabVIEW 8.6.
Thanks,
Jason
Solved!
Go to Solution.

In the dll call simply type LabVIEW without any path. This should work (I used it on 7.1)to automagicallylink it.
The functions are also located in the lvrt.dll which is the main part of the runtime engine.
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

Application builder error

Has anyone seen this error
I get this error after I build an installer and try to run the setup
Message Edited by James R on 05-14-2009 01:24 PM
- James
Using LV 2012 on Windows 7 64 bit
Attachments:
builder_error.jpg ‏48 KB

Hi James,
Did you make sure to include the LV 8.5.1 Run-Time Engine in the installer? The error is saying that dependencies are missing and the product code is for the LabvIEW Run-Time Engine v8.5.1 (I was able to look that up for you). When you say the executables work by themselves, is that on the target machine or development machine? Have you ever been able to build an installer?
Kristen H.
Message Edited by Kristen H. on 05-15-2009 11:18 AM

Build dll error in application builder 8.6.1

Hello,
I get always an error in the LV 8.6 application builder, when I build a dll. There is only one function in it, that has a string and an error input, and nothing else. I attach a screenshot of the VI prototype, and hier is the error description:
Error 1 occurred at Building DLL.
A component needed for Application Builder does not support the required functionality. This might have been caused by installing an older version of LabVIEW after this version was installed. Reinstall the current LabVIEW version to correct this issue.
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
After that I reinstalled LV8.6, I tried to reinstall only the 8.6 app builder, but no success.

Hello,
thank you for the reply.
I have solved the problem. I uninstalled the last installed LV version, this was 8.0. Then ran appbuilder again in 8.6, then I have got an instruction to run applibs\lvdllbuilder\lvdb.exe. Since then works.
regards
Mitulatbati

Error 7 occurred at Open VI Reference with Application Builder

Using Labview 5.1, I am building an application where all the vi's are placed in a single .LLB file. I have one top level vi (with sub-vi's), and one vi that is opened by the Open VI command. The program runs fine with labview installed. I want to make an executable file. I select the top level vi and select the vi that is opened by the Open VI command as a dynamically loaded file. I get an error when I attempt to build the file.
"Error 7 occured at Open VI Reference in Dist Build LLB Image.vi -> Dist Build App Image.vi -> Build application.vi"

Dear Sir;
There are two things that are good to try:
First, create the application in a folder that is closer to the root directory (e.g., c:\myApp). There is a limit to the length (or depth) of the path name to your application's target directory, so, if you are choosing a too long path you might get an error.
Second: The Application Builder reads certain information from the VI in order to determine how to build the executable. To avoid possible errors, either in the build process or in the built executable, make sure the VIs are LabVIEW 5.1 VIs. You can convert your VIs to LabVIEW 5.1 VIs by using the Mass Compile feature (File >> Mass Compile) in LabVIEW before you build your executable. The Mass Compile feature will allow you to select either a directory or a LabVIEW
.llb file to compile.
Regards

Error message "VI is not executable"! Need help with Application Builder

Hello,
I have a problem with an application, built with the Application Builder. I have read some threads about the problem I have, but I still don't know a solution.
When I run my front panel from LabVIEW, everything is good. So, now I created an application (and an installer) to be able to run it on other PCs as well. This application does not work. Everytime I start it on my PC, I get the error "VI is not executable. ...". I read in several forums solutions for this error, but I cannot fix it! I've changed my properties for the builder, but with no success. Perhaps, anybody has more ideas, what's the problem.
To get a better idea from my project, here a little description of it:
In the block diagram there is a while loop which is continuously runned. In this loop I only set some properties for the layout of the front panel, such as decorations which will be hidden/shown and changes of colours of indicators... For the rest, it waits for a click on the button "Start" in the front panel. After that, a DLL is called to communicate with a USB device. Some measurements are carried out and the DLL is closed. I hope, you can get a global idea from my block diagram...
I use LabVIEW 8.5, the DLL is a third-party DLL, which we wrote on our own. But I think the DLL works properly, if it is called from a C# application it works and it works, too, by calling it from LabVIEW when I am in development mode.
It's a project for university and I'm just a beginner in LabVIEW, so I don't have so much experiences in it, but I think i improved my knowlegde about LabVIEW very well in the last weeks!
So, i hope to get an answer soon (the deadline for the project is not soooo far away )
If you need more information, please let it know...
I would be very grateful if there is someone with a working solution...
Kind regards from the Netherlands,
Sebastian

Sebastian,
Your architecture makes it very difficult to debug this and other problems. Does the error message mention which VI is causing the problem? It is very important to wire your error clusters everywhere. In LabVIEW, when a node throws an error (Error.Status = T), future nodes do not execute. At the end, place an error cluster indicator that you can see on your front panel. When an error posts, you can right click the indicator (even in a compiled application) and select "Explain Error".
This is a start, but you really need to push this into a queued-state machine before this gets any more complicated. As it were, if anything in your loop hangs, your whole application hangs. See attached for a queued-message handler (not advisable for actual applications, but you get the point. You would want to have a type defined enum in lieu of strings, and shared data between states differently, etc.)
-Jason
Message Edited by LabBEAN on 01-20-2009 08:36 AM
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs
Attachments:
State Machine.vi ‏18 KB

Application builder page error ORA-06502

We get an intermittent error with the application builder page of application express. The report that normally shows the icons or rows for each application returns the error "report error:
ORA-06502: PL/SQL: numeric or value error: NULL index table key value". is this a know issue? is there anything we can do to fix it?
Tom

Scott,
Thanks for the reply.
I will try my best to explain, following is the navigation:
1. After logging into my workspace --> Click on Application Builder --> Click either on a custom application or sample application --> I get report error: ORA-06502: PL/SQL: numeric or value error: NULL index table key value (Default View of the pages is set to Details)
2. If I change the page[s] View to Icons then there is no error.
3. We bounced the web but still having the error, did not try flushing the shared pool on the server.
HTH
Thanks
Pradeep
PS: How can I upload a screenshot?

Application Builder comes up with generic error #42

Building a large application that has previously built without a problem in LabVIEW 2009 SP1.
The error message returned is -
"Error 42 occurred at D:\EMSolutions\Automation\PTMP\System Measurement Functions\System Measurements.llb\PTMP - Tx Performance.vi
Possible reason(s):
LabVIEW: Generic error."
Would appreciate some clues as to what might cause this error.
Herbert Niesler

Have had it happen to me again and managed to play around a bit and found the following -
1. The error 42 occurs in relation to a Start Up vi (I have multiple startup vi's in this project). Doesn't happen to any other vi.
2. If I remove the offending vi from the project, the error 42 then occurs on another startup vi.
3. Putting that vi back in and making it a startup vi again triggers the problem with that vi.
4. Then I opened the offending startup vi (note that the project was compiled with all startup vi's closed). On building the application the error 42 occurred on another startup vi (the same vi as happend in 2.).
5. When I opened this 2nd offending vi and did a build, I had success.
Now I realise I have not seen the problem before because I usually did a build with all the startup vi's open. Its only recently that I have started doing builds with all front panels closed.
So advice at this stage is - open the front panels of your startup vi's and that should get rid of the error 42.
Herbert Niesler

Build Error While importing standard application into NWDS

Hi all,
I am trying to Import T&E Standard Applications into NWDS.
Two components (tra & tra/tre) have to be synched to the studio. These two are interdependent..
One Component I am able synch and create project perfectly but when i try to do the second one, i am getting Generation BUILD Error...
Help me in this regard..
Thanks
Malla
Edited by: challa mallareddy on May 7, 2009 12:34 PM

Hi,
As per your error, I think you have already created a project with name NewParProject. Give a different name and then check.
Also check if your par file is not corrupt. Download it again and follow below steps in NWDS :
Go to File>Import > Select par file >
>Browse and select the par file>
>Give a project name i.e. ParProjectTest > Finish.
This should work.
Regards
Deepak

Application Builde Error

Similar Messages

Maybe you are looking for