Error 1073 (on Clear Errors.vi) When Building Application in LV 8.2
I have seen numerous posts about this problem when building an application without a block diagram in LV 7.x, however, I am recieving this error on LV 8.2. Whats most disturbing about it, is that it always hangs when processing Clear Errors.vi. I have tried my source on two different machines, to no avail. Also I tried to do a mass recompile of the entire vi.lib again no help. It is very important that this program compiles, however I cannot get past this error. Any suggestions?
My specific error message is here:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1073 occurred at ABAPI Dist disconnect td-poly.vi -> ABAPI Dist Chg and Save VIs.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: This property is writable only when the VI is in edit mode, or this method is available only when the VI is in edit mode.
-Paul
Hello Paul,
I am sorry for not elaborating previously. This issue has been documented previously for further investigation to our R&D group (# 3ZK9LGP2). In the report I found that this error, though vague in the description, is fixed by enabling MathScript Support.
To enable MathScript support, check the checkbox in the application properties for the 'Enable MathScript support' option.
-Bob
-Bob
Similar Messages
-
Why do I get Error 1 when building applications
I'm creating an executable using the Labview 6.1 application builder but I get this error: Error 1 ocurred at Gsim Sintax Check.vi. I didn´t install the Simulation and Control toolkit I copied the vis I needed to use them.
What can I do?
Thanksyen,
Do you get this error at build of the application or from the executable itself? Does the VI run in the development environment?
I would build the executable from the development machine that has the toolkit on it.
Brett B. -
Error 1003 when building executable
Hi, I'm using Labview 2010 on Windows 7 and I'm getting an error when I try to build an executable:
Error 1003 occurred at Open VI Reference in AB_Engine_EXE_Call_Write_Icons.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Create_Build_Application.vi->EBUIP_Global_OnCommand.vi->EBUIP_Global_OnCommand.vi.ProxyCaller
Possible reason(s):
LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.
VI Path: C:\Program Files\National Instruments\LabVIEW 2010\vi.lib\Platform\icon.llb\Read Icons from ICO File.vi
This happens even when I try to build a simple vi, like a random number generator.Same problem here. Error 1003 and error 8 I encoutered often.
For error 8 during build process, I needed to save the executable on a higher level in the file hierarchy.
For error 1003, I did not find a solution. Restarting LabView does not help. Sometimes (but not always) restarting the computer helps. Sometimes I need to reinstall the labview system.
More details: I have a first vi, starting the actual vi with a hidden front panel (second vi). This vi can also be started directly. Sometimes, the build process runs smoothly then when I include the second vi as main vi to start the program.
The program runs fine when the build process succeeds, and it runs fine in LabView. -
Error -30, when building new installer
LabVIEW 2010 sp1, just upgraded and lost the ability to build installer. Error dialog:
LabVIEW 2010 sp1
Win 7 64bit
Thanks in advance.For example, which version of LabVIEW did you upgrade from? Did you modify any of your code? Are you having problems building ANY installers or just a single application?
Original installed version: NI Developer Suite 2010 DS2
Code is unmodified
Application Builder Error occurs from any project.
Currently configured installers cannot be built either. When build configuration is viewed the additional installers section is empty.
I am currently working with an NI Applications Engineer to resolve the issue.
So far, article:
http://digital.ni.com/public.nsf/allkb/1B53A6FDFC20B8058625752400687F42?OpenDocument
has been suggested.
From my team of 6 the 3 that have upgraded have the same issue.
I will update the status once I try this fix. -
Unexpected error (0xE8000001) when building in xcode
help, does anyone get this error message when they build in xcode, [device] and [debug]?
Nope, you're the only one:
http://www.google.com/search?client=safari&rls=en-us&q=%220xE8000001%22&ie=UTF-8 &oe=UTF-8 -
Error 1 when building my application in Labview 2010 Version 10.0f2
I am getting the following error trying to build my application in Labview 2010 Version 10.0f2 and I get the following error:
Error 1 occurred at Invoke Node in AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_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: 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.
Method Name: Linker:Write Info To File
I have searched and can find no real sollutions to this problem. I did the updates and still nothing. Now I can't even build an app with Laview 8.6. I reference several .NET items and refuse to rebuild each and every one of them. My only option at this point is to uninstall all Labview and then reinstall 8.6 so I can do something.
Help if you can.Hello RBrown
I am really sorry for this inconvenience! This is a known issue.
Can you please attempt the following for me:
When you are building an application, under Advanced please check the last box "Use LabVIEW 8.x file layout"
If that doesn't work, you may need to rebuild the LLB in a separate directory with new names, and use it as the build inclusion.
Here are some forum posts strictly for your information:
I have found users that have had similar issues. I am trying to make this workaround work for you.
http://forums.ni.com/t5/LabVIEW/error-1052/m-p/912192
This is a known issue that some customers have already commented on:
http://forums.ni.com/t5/LabVIEW/NI-Please-don-t-put-illegal-vi-names-in-your-toolkits-thanks/m-p/745...
I have filed a corrective action for this issue and I will add you to the list of individuals who need this issue resolved.
Sincerely,
Greg S. -
Error -12 when building installer
OS: Win7
LabVIEW: 2012 SP1
I am having issues with the application builder while trying to build an installer.
The installler has the following "Aditional Installers" selected:
LabVIEW Runtime Engine
NU USI 2.0.1
NI DAQmx Core Runtime 9.8
NI DAQmx MAX Configuration 9.8
NI VISA Runtime
If I remove the "NI DAQmx Core Runtime 9.8" & "NI DAQmx MAX Configuration 9.8" then the installer builds without error. How can I get it to succesfully build with these selected?
I have upgrated the DAQmx from 9.5.5 to 9.8 and performed a mass compile but no luck.
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
Loading product deployment information
Adding files to installer
Validating...
Copying files...
Scanning files...
Updating files...
Build complete successfully.
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'SiriusXM Mad Max' from: C:\Users\bbanacki\AppData\Local\Temp\7ZipSfx.000\Mad Max Installer\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** Error Details:
Error in MDF API function: _MDFDistCopyList_CopyItem
Windows function FindFirstFile returned an error. Error code: 3
*** End Error Report
Done building deployment
Solved!
Go to Solution.Siriusly wrote:
Copying distribution 'SiriusXM Mad Max' from: C:\Users\bbanacki\AppData\Local\Temp\7ZipSfx.000\Mad Max Installer\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** Error Details:
Error in MDF API function: _MDFDistCopyList_CopyItem
Windows function FindFirstFile returned an error. Error code: 3
*** End Error Report
Done building deployment
It looks like your installer build is trying to pull the "SiriusXM Mad Max" distribution from an unusual temp location. If this distribution was hiding inside a 7zip file and has since been altered or deleted, that we certainly confuse the installer builder. Do you know if this distribution contained the DAQmx installers you are trying to build with?
Here are a few things you could try if this is the case.
1. If an installer build ever suceeded while pulling source from this temp location, the location may have been saved as known good source. To undo this saved information, you can delete the file at C:\ProgramData\National Instruments\MDF\Bin\MDFInfo.xml
2. If C:\Users\bbanacki\AppData\Local\Temp\7ZipSfx.000\Mad Max Installer\ is a valid path on your machine, try moving or renaming this folder. This should cause the installer builder to prompt you for source media. This prompt window will allow you to configure which distributions you provide as source for the build (depending on the version of the installer builder tool installed, you may have to click "No" to the question "Do you have all of these installers?" to get to the configuration page).
3. Install the latest version of the installer build tool. A new one released with LV 2013, and it should be available to download either through NI Update Service or on the web somewhere
4. All else fails... post your full installer build log! LabVIEW generates this for us at %temp%\LVProjectName_InstallerName_build.log -
Error 10 when building app with Report Generation _wordsub.llb in the project.
Error 10 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> SDBEP_Invoke_Build_Engine.vi -> SDBUIP_Build_Invoke.vi -> SDBUIP_Build_Rule_Editor.vi -> SDBUIP_Item_OnDoProperties.vi -> SDBUIP_Item_OnDoProperties.vi.ProxyCaller
This is the error I get when a set up _wordsub.llb to use of report generation in a build project.Dave,
thanks for providing me with this information. I didn't hear about this error in the past, but I found a KB, that possibly can help you debugging the application: http://digital.ni.com/public.nsf/websearch/AF12BB5FAC27FE2186256F9400619C84?OpenDocument
Let me know, if it helped you out
Stefan
Impossible is nothing - nothing is impossible -
Hi all,
I saw a couple of thread of other people here having the same "1003 error" when trying to build an exe with LV 7.1.1
The exact text error is :
Error
1003 occurred at Open VI Reference in Dist Copy Non-VI
Files.vi->Dist Build LLB Image.vi->Dist Build App
Image.vi->Build Application.viPossible reason(s):LabVIEW: The VI is not executable.
This is all the more surprising because this error will only happen on my computer !!!
I borrowed a collegue's computer and the build went OK...
After further investigations I noticed only one difference between my collegue's computer and mine : mine has VIPM installed.
Could VIPM possibly be the source of this issue ??
PS : recompling the code (ctrl+shift+run) on my CPU didn't make any change.
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"Hi TiTou,
You've probably solved this by now, but if not...
A few months ago I was trying to distribute two EXEs - both of which made dynamic calls - and this error (among others) was giving me "fits". I think it can happen if the caller has loaded a VI (.ctl or .vi) that also appears in the callee hierarchy - and the version loaded by the caller is incompatable with the callee's diagram(s.) When the callee runs, it has to use same-named VIs already in memory. If you see different behaviour on two different machines, are there two different versions of the caller?
No matter what the problem really is (was,) the attached VI will try to open all the broken VIs in a hierarchy - which can be a huge help in narrowing the problem. Oh yeah, with the (broken) FP open, click on the broken-arrow to see an error-list that can (but-usually-doesn't) display helpful diagnostic info! Compile this into your EXE (caller) so it runs if there's a problem running the callee.
Cheers.
Message Edited by tbd on 01-15-2007 10:58 PM
Message Edited by tbd on 01-15-2007 11:00 PM
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Attachments:
Util.VI.OpenBroken.vi 62 KB -
Error -12 when building installer LV2012
When I try to build an installer from the project menu I immediatly get en error -12. (see attached)
This has happened on several different projects. I can make an .EXE, Zip file and distribution build but not installer. I read the "Why Does My Distribution Build Fail with Various Errors?" article suggested but I admit I don't understand the proceedure or if this pertains to my problem at all.
Thanks
Attachments:
LV Installer error.JPG 63 KBAlina,
Thanks for the tip. I checked out that forum and that is the same problem. Now the question is the same as what he asked. How do I reinstall App Builder? Older versions had it as a seperate CD. 2012 comes on 1 DVD and there's nothing on the install menu that mentions App Builder. I'm guessing I'll just have to reinstall LV as a whole.
Thanks for all the help
Mark -
Errors encountered when building a plugin
Hi all,
I'm new to DSEE and I'm trying out the plugin development.
My DSEE version is 11.1.1.5
Running on 2.6.32-71.el6.x86_64 x86_64 GNU/Linux
Ok, I am trying to build the library of the testpwdstore.c example described in the Developer's Guide Chapter 11 (Writing Pwd Storage Scheme Pug-in), but encountered the errors below:
If I build using 32bit library:
[root@testmachine examples]# gcc -o testpwdstore.so testpwdstore.o -L/home/dsee7/lib/private -L/home/dsee7/lib -lldap60 -lpthread
/usr/bin/ld: skipping incompatible /home/dsee7/lib/private/libldap60.so when searching for -lldap60
/usr/bin/ld: cannot find -lldap60
collect2: ld returned 1 exit status
If I build using 64bit library:
[root@testmachine examples]# gcc -o testpwdstore.so testpwdstore.o -L/home/dsee7/lib64/private -L/home/dsee7/lib64 -lldap60 -lpthread
/usr/lib/gcc/x86_64-redhat-linux/4.4.4/../../../../lib64/crt1.o: In function `_start':
(.text+0x20): undefined reference to `main'
testpwdstore.o: In function `xorenc':
testpwdstore.c:(.text+0x56): undefined reference to `slapi_ch_malloc'
testpwdstore.c:(.text+0x127): undefined reference to `slapi_ch_malloc'
testpwdstore.c:(.text+0x167): undefined reference to `slapi_ch_free'
testpwdstore.o: In function `xor_init':
testpwdstore.c:(.text+0x21a): undefined reference to `slapi_pblock_set'
testpwdstore.c:(.text+0x230): undefined reference to `slapi_pblock_set'
testpwdstore.c:(.text+0x248): undefined reference to `slapi_pblock_set'
testpwdstore.c:(.text+0x25e): undefined reference to `slapi_pblock_set'
testpwdstore.c:(.text+0x274): undefined reference to `slapi_pblock_set'
testpwdstore.o:testpwdstore.c:(.text+0x28a): more undefined references to `slapi_pblock_set' follow
collect2: ld returned 1 exit status
May I know which bit version of lib should I use, and what is the cause of the errors?
Many thanks,
jason
Edited by: 915179 on Feb 16, 2012 11:51 PM
Edited by: 915179 on Feb 16, 2012 11:51 PMHi all,
I'm new to DSEE and I'm trying out the plugin development.
My DSEE version is 11.1.1.5
Running on 2.6.32-71.el6.x86_64 x86_64 GNU/Linux
Ok, I am trying to build the library of the testpwdstore.c example described in the Developer's Guide Chapter 11 (Writing Pwd Storage Scheme Pug-in), but encountered the errors below:
If I build using 32bit library:
[root@testmachine examples]# gcc -o testpwdstore.so testpwdstore.o -L/home/dsee7/lib/private -L/home/dsee7/lib -lldap60 -lpthread
/usr/bin/ld: skipping incompatible /home/dsee7/lib/private/libldap60.so when searching for -lldap60
/usr/bin/ld: cannot find -lldap60
collect2: ld returned 1 exit status
If I build using 64bit library:
[root@testmachine examples]# gcc -o testpwdstore.so testpwdstore.o -L/home/dsee7/lib64/private -L/home/dsee7/lib64 -lldap60 -lpthread
/usr/lib/gcc/x86_64-redhat-linux/4.4.4/../../../../lib64/crt1.o: In function `_start':
(.text+0x20): undefined reference to `main'
testpwdstore.o: In function `xorenc':
testpwdstore.c:(.text+0x56): undefined reference to `slapi_ch_malloc'
testpwdstore.c:(.text+0x127): undefined reference to `slapi_ch_malloc'
testpwdstore.c:(.text+0x167): undefined reference to `slapi_ch_free'
testpwdstore.o: In function `xor_init':
testpwdstore.c:(.text+0x21a): undefined reference to `slapi_pblock_set'
testpwdstore.c:(.text+0x230): undefined reference to `slapi_pblock_set'
testpwdstore.c:(.text+0x248): undefined reference to `slapi_pblock_set'
testpwdstore.c:(.text+0x25e): undefined reference to `slapi_pblock_set'
testpwdstore.c:(.text+0x274): undefined reference to `slapi_pblock_set'
testpwdstore.o:testpwdstore.c:(.text+0x28a): more undefined references to `slapi_pblock_set' follow
collect2: ld returned 1 exit status
May I know which bit version of lib should I use, and what is the cause of the errors?
Many thanks,
jason
Edited by: 915179 on Feb 16, 2012 11:51 PM
Edited by: 915179 on Feb 16, 2012 11:51 PM -
Error message when building an application for Labview PDA
When using LabView PDA module to build an application for a PDA target, I receive the following message: "Error building executable. Unable to create file". Why is this happening?
When looking at the error log, it reads "The system cannot find the file specified."
This happens even when looking at one of the Labview PDA example VI's, so it is not a result of the VI containing functions of features not supported by Labview PDA.
When installing Labview PDA, I installed files as follows, and in this order:
(i) Labview 7.1 (installed previously)
(ii) Microsoft eMbedded Visual C++ 4.0
(iii) Microsoft eMbedded Visual C++ 4.0 SP 3.0
(iv) Microsoft SDK for Windows Mobile 2003-based Pocket PCs
(v) Microsoft ActiveSync 3.8
(vi) NI Labview 7.1 PDA module for PocketPC
(vii) DAQmx Base 1.0 for PDA or later
Any ideas?Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files? I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs. I think I've seen a similar post on the discussion forums in the past that recommended this.
If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman -
I get this error detail when building my Installer - CDK_Item_OnDoProperties.vi.
I am upgrading an application from LV 8.5 to 2009. I am able to build the EXE. But when I build the Installer, I get the following error:
The following file(s) are not found on the system:
<Not A Path>
<Not A Path>
Click on "Details" and get........
CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_PreBuild.vi >> CDK_Engine_FileExists.vi
Thank youGo through all the threads here
and post back whether that helps in solving your problem.
Mathan -
Error 10 when building an application in LV8 and Report generation toolkit 1.1.1
I am trying to build an application using LV8.0.1 and Report generation toolkit 1.1.1 and i get this error.
Error 10 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
Any ideas?
Scientia est potentia!Did you attempt to add the _wordsub.llb and _excelsub.llb files to the application as support files? I believe in LabVIEW 8.0 instead of adding the entire LLBs you should just add the _Word Dynamic VIs.vi and _Excel Dynamic VIs.vi as dynamic VIs. I think I've seen a similar post on the discussion forums in the past that recommended this.
If this suggestion doesn't help, please reply, and attach a simple VI and .lvproj file demonstrating the problem so I can investigate further.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman -
Strange error message when building dvd
Hi
I have a dvd project, at about 80% progress of the build, I get the following error
Has anyone got any idea what this may be.
Many thanks
Chris AndersonHi
Thanks for your reply.
I do have a blu-ray burner, and i was creating a image, the error came up during the transcode. I have 12gb memory - what do you mean by tons ? is 12 enough.
I am working with avchd 1920x1080, that i have successfully used before.
I would then intend to burn the iso file afterwards, so the error is purely in encore, not relevant to burner as such
I did actually go the AME route, then import into encore and it worked fine, so it appears the transcoding in encore is the issue.
It would be helpful offcourse if the error message gave more info or what stage it was at at the time of the error.
Thanks again
Chris
Maybe you are looking for
-
Payment Processing tab in Purchase Order
Hi can anybody help me, How do we get the Payment Processing tab which is used for Retention purpose ? Which SAP Note or package is involved in this as i am unable to find that tab? We have just installed SAP ERP ECC 6.0 EHP4. Kindly guide me. Regar
-
I ordered a phone and added a line for my son on Dec 20. I had problems with my order online, and chatted with an associate who helped me. At one point I had to log out, log back in and re-start my order. Three days later I received two phones and ch
-
Can I connect my Time Capsule wirelessly to my existing wireless network? This is using a non-apple router.
-
Install SUN StorEdge L280 to Solaris 10 x86
Hi, i need help with install & configure SUN StorEdge L280. I have SOLARIS 10 x86 platform on HP DL 380 g3. I need help with this. I dont understend what with this, what drivers is need... On sparc is all ok with veritas netbackup, but on x86...any h
-
Where I can find bitrate info for audio file?
I just upgrade to OS X 10.9.2 and I can't find bitrate informations for audio file in Finder's info window. Is there someone with the same problem?