Error -41 LV8.6 application builder

Hi,
I am trying to build an installer and I am getting this error -41 (unknown origin). I am using Visa with three instruments.
Here is what is says :
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_InitializeDistribution.vi >> NI_MDF.lvlib:MDFConfig_SetBuildDir.vi
C:\Documents and Settings\Nusi\Mes documents\recherche\labview\Builds\rho_ac\rho AC "version light"
Chargement des informations sur le déploiement des produits
Chargement des informations sur le déploiement des produits
Chargement des informations sur le déploiement des produits
Chargement des informations sur le déploiement des produits
*** Erreur : Une erreur interne de cause inconnue a eu lieu (code d'erreur -41)).
*** Fin du rapport d'erreurs
For the details I got :
Visitez la page de demande de support sur ni.com/ask_fr pour en apprendre davantage sur la résolution de ce problème. Utilisez les informations suivantes comme référence :
any ideas ?
thanks a lot

Your description reminds me on some unexpected errors which I had while building my application. But I don't remember exactly what happened. On point were missing external files. This does not affect the building of the application but the installer cannot finish. I suggest to look carefully thru your project and see whether there a missing files. The other time I think there was a VI being not part of a class or something like that. But that should be detected while building the application. So I don't remember it exactly but I hope it will help you to find the problem yourself.
Regards

Similar Messages

How could install a exe file to C:\Test using LV8.0 Application builder?

I built a project file and created an installer. But the proble is I don't know how to setup the project properity to install the executable file into the folder C:\Test. Can anyone help me?
The attached is the project image.
Attachments:
14.JPG ‏89 KB

sloved.

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

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

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)

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 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!?

During an application build I received an error 7 for a missing source NI vi 1d linear evaluation.vi

During an application build, I got "Error 7 occurred at c:\Program Files\National Instruments\LabVIEW 6\vi.lib\Analysis\8numerc.llb\1D Linear Evaluation.vi - source does not exist".
This existed in Labview 5.1.1. Was it deleted in 6.0?

No, this VI is in the following location "Functions >> Analyze >> Mathematics >> Array Operations>>1D Linear Evaluation.vi"
Perhapse this in a package (Advanced Analysis) that is not included in your version of LabVIEW. You may need to upgrade to get these VIs, or you can copy them over from your Labview 5.1.1 installation.
-Jim

Objheap.cpp error in application builder

Hello everybody.
I am trying to build my application but I get the error: error in objheap.cpp line 474.
I have seen in previous answers in the discussion forums that someone got the same error, but not in the application builder but when trying to open the main.vi of the application in the development system. I have read that the reason for that was that a vi became corrupted.
But this is different. The error message is the same, but I can open the main vi of my application in the development system with no problems. I only get the error message when I run the application builder trying to build the application.
Anyone can help me?
Thanks in advance

Even though VI runs fine in the development environment, it may still be corrupted. It might be the case that there is an error in the vi.lib VIs. I recommend copying the block diagram of the VI in question to a new VI and rebuilding. If that does not help, consider a reinstall of LabVIEW or posting your VI to see if others can build it.

Error 10 occurred When createing an executable with application Builder?

Problem: I am using the LabVIEW Application Builder to create an executable from my VI. When I run the Application Builder, I receive the following error:
Error 10 occurred at Copy in Win Install Copy Redistribution Files.vi->Win Install Create.vi->Dist Call Create Installer.vi->Builder Application.vi
Possible Reason(s)
Labview : Duplicate Path
or
NI-488 : New I/O attempted with old I/O in progress
Why do i receive this error and how can i resolv this issue?

Jiang,
It sounds like this could be an overwrite issue. From the file path you specified, I can tell you that the error is occurring in creating the installer for your executable. Are you specifying an installer directory where you have already created an installer of the same name? If so, is that directory read only? Make sure that write privileges are enabled for you installer directory, and if that doesn't fix anything, try specifying a different installer directory.
If none of these suggestions take care of the problem, please post a simple example that illustrates the problem (i.e. a simple VI and a copy of the build file). We can then try to replicate the problem and troubleshoot it. What version of LabVIEW are you using?
Regards,
E. Sulzer
Applications Engineer
National Instruments

ORA-28112: failed to execute policy function - Error in Application Builder

Hey all,
I've added a policy function to one of my tables and now I'm getting this error when I try to update a report region that references that table.
"Query cannot be parsed within the Builder. If you believe your query is syntactically correct, check the ''generic columns'' checkbox below the region source to proceed without parsing. ORA-28112: failed to execute policy function"
If I remove the policy then everything works fine. My application also runs fine with the policy in place. I just get these errors in the application builder when updating a report or an LOV that references the secure table.
The parsing schema is APPL_USER.
Here is the policy function:
FUNCTION DOCUMENT_TABLE_POLICY (object_schema IN VARCHAR2 DEFAULT NULL
,object_name IN VARCHAR2 DEFAULT NULL)
RETURN VARCHAR2 IS
v_nt_seq NUMBER;
BEGIN
IF user = 'APPL_USER' OR INSTR(user, 'ITFC_') = 1 THEN
RETURN NULL;
END IF;
IF V('APP_USER') IS NOT NULL THEN
IF V('F_NT_SEQ') IS NOT NULL THEN
v_nt_seq := V('F_NT_SEQ');
ELSE
SELECT NT_SEQ
INTO v_nt_seq
FROM APPL_USERS
WHERE UPPER(NT_ID) = UPPER(V('APP_USER'));
END IF;
RETURN '(DOCUMENT_TYPE, MANAGED_BY_ELEMENT, PROGRAM_CODE, CONTRACT_NUMBER) IN (SELECT DISTINCT R.DOCUMENT_TYPE, USL.ELEMENT, USL.PROGRAM_CODE, USL.CONTRACT_NUMBER FROM IPRACA_USERS_SECURITY_LINK USL, IPRACA_SECURITY_ROLES R WHERE R.SECURITY_ROLE_SEQ = USL.SECURITY_ROLE_SEQ AND USL.NT_SEQ = ' || TO_CHAR(v_nt_seq) || ')';
END IF;
--UNAUTHORIZED USERS CAN SEE NO DATA
RETURN '1=0';
END;
This is how I setup the policy:
BEGIN
DBMS_RLS.ADD_POLICY(
object_schema => 'APPL_USER'
,object_name => 'APPL_DOCUMENT'
,policy_name => 'APPL_DOCUMENT_POLICY'
,function_schema => 'APPL_USER'
,policy_function=> 'APPL_SECURITY.DOCUMENT_TABLE_POLICY'
END;
Any help would be greatly appreciated!
Thanks,
Jonathan Hart
APEX 3.1.1

Thanks.
After looking at it again, I think that may be the problem, too. I guess the APP_USER is set when in the application builder and the Builder is running the report query as it is being parsed which is causing the error. I added a Begin - Exception block around that query and everything seems to work now.
Thanks again!

Error in Application Builder

Hi Friends,
I have installed Oracle Apex 3.1 successfully. When i click application Builder i am gettin the following error. I hope i have installed full version. Is there a way to chek whether i did only runtime only?
application=4000 workspace=10
Error ERR-1014 Application not found.
OK
Looking forward to your assisting :)
Thank You

That's not good. Maybe you installed the runtime-only version.
Scott

Stand-alone application generates error with function 'Ramp Pattern' (bug in application builder?)

Hello,
in my program a main.vi links to a sub-VI via 'open VI reference' and 'invoke node'. In this sub-VI the function 'Ramp Pattern' is used. The program itself runs normally, but if I build a stand-alone application using application builder I get an error message 'error 1003 occurred ..'. I believe this error is directly related to the build specifications which are as follows: the main.vi is referenced in a main build specification, the sub-VI in its own specification where the target is a LLB.
I appended an example-program that exhibits the error (when executing 'Application.exe' and pressing 'calculate ramp'). The error does not occur when disabling the 'ramp pattern' function and rebuilding the application.
I would rate this to be a bug in the application builder and would appreciate any help on how to solve this problem. However, due to the structure of the whole program the sub-VI has to remain in its own LLB.
Attachments:
RampPattern.zip ‏198 KB

There can be reasons why a VI might appear broken when loaded from an executable. For example, if you have different versions of the same VI or enum that differ in such a way as to break the calling VI, that can cause a broken arrow when loaded from the executable. If you have DLLs being called and the runtime engine can't find the DLL, that can cause a broken arrow that you might not see otherwise. Finally, there is a bug related to a VI appearing broken when its not.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Error "cannot find terminal hotpoint in wire..." during application build.

Hello,
I'm trying to compile a TestStand 2.0.1 Custom LabVIEW Operator Interface with the LabVIEW 6.1 application builder. During the build process I get six(6) error prompts 'cannot find terminal hotpoint in wire...' and the builder stops and prompts another error that says the one of the VI's 'is not executable'. However, I can open the VI and there are no errors on it and no asterisk on the titlebar. There is only one strange thing I noticed in the VI Hierarchy browser, where for this VI and some others, it display an untitled (new) VI not connected to anything (!?) that does not appear in the block diagram. If you reopen the VI, the mysterious VI is gone.
The interesting thing is that I can successfully build the application if I try it with another Windows XP sp2 computer with the same exact LabVIEW and TestStand versions. Could anyone help me out here and let know what this error means. I can't find any reference to it here or in google. Thanks!

Thanks to Kevin in tech support for investigating these errors. I did find after much work one of the VI's that is causing the "terminal hotpoint in wire..." error. It's a GET EXE STRINGS.VI in the custom OI. I have screen shots of it, but I don't know how to load them here... Anyway, it appears to happen on this particular VI because it has more than 20 connector pain terminals, but not all of the connections appear to be setup in the connector pane. However, this does not prevent the VI or the calling VI (TestStand - Execution Display) from running normally or even displaying a broken arrow (Why Not?). I changed the VI and removed the unused connections and the problem seems to be gone. I still need to find one more VI that is doing this. I also don't know why my Laptop is able to build the OI application OK w/o errors and other PC's always stop the application builder because of these errors.
Any other insight on this issue is greatly appreciated. Thanks,
David A. Gaud

Error -41 LV8.6 application builder

Similar Messages

Maybe you are looking for