Application builder error coder 21

I get this error code when trying to build an application and include the visa runtime install files
What can i do to fix this error
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.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
Loading product deployment information
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 'LabVIEW 2009, Media 1' from: \\dtads2\it_software$\Labview 2009\DVD 1 of 2\Distributions\LabVIEW\LabVIEW2009\ to: C:\Documents and Settings\brockmaa\Desktop\11164 Carnivore\builds\FVT1_4 test\My Installer\
Copying distribution 'National Instruments Device Drivers - February 2010' from: C:\National Instruments Downloads\NI Device Drivers\Feb10\ to: C:\Documents and Settings\brockmaa\Desktop\11164 Carnivore\builds\FVT1_4 test\My Installer\
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
*** Error: An internal tool or library returned an error. (Error code -21)
Error Messages
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper32.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-ORB' not found for part 'niorbi.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-ORB {F2D3406A-0A97-4EB9-9A09-F20A874C16F9}.xml'.
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-ORB' not found for part 'niorbi64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-ORB {F2D3406A-0A97-4EB9-9A09-F20A874C16F9}.xml'.
*** Error Details:
Error in MDF API function: _MDFBuildDist_Build
Error List
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'NIVISAruntime64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper32.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-VISA_Runtime' not found for part 'VisaSharedComponentsWrapper64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-VISA Runtime 4.6.2 {BEB32B6A-2984-40F3-B24E-DB29311A1DD2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\TDMS' not found for part 'tdms64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI TDM Streaming 2.0 {3DAA4182-08B7-45D9-8620-6B0E13018670}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2008MSMs\VC2008MSMs' not found for part 'VC2008MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2008MSMs {4219AAB9-43BA-4085-8A42-78644B9F96D2}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x86.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\VC2005MSMs\VC2005MSMs' not found for part 'VC2005MSMs_x64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI VC2005MSMs {63E19B33-DD24-4EAB-9E77-6735C2171CE4}.xml'.
While validating input parts.
.\InputParser.cpp(365): InstallerError 120
Input directory 'C:\National Instruments Downloads\NI Device Drivers\Feb10\Products\NI-PAL' not found for part 'palSetup.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI-PAL {79F90480-F2A2-463A-943C-29046520D6BC}.xml'.
While validating input parts.
and so on

Hi brockmaa,
It seems that the files it needs to include the VISA runtime are not being found on your system. Try re-installing the correct version of VISA you need from:
http://www.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:du,n8:3.25.123.1640,ssna...
and try to build the installer again and it should be able to find the correct files.
DylanC

Similar Messages

DPS APP Builder Error Code 1

Hello,
I'm getting an Error Code 1 message when trying to download the test APP from the DPS APP Builder. I've tried re-building the document (a process that takes almost 8 hours in my case as our APP features 110 articles including almost 1000 images), updating it, generating new certificates and any other workaround mentioned in a previous discussion about this same subject. Nothing worked for me.
The only workaround I haven't tried is deleting the folio from ~/Library/Preferences/StageManager.BD092818F67280F4B42B04877600987F01 11B594.1/Local Store/dmp.
Apparently, there's nothing called "StageManager" in my MacBook Pro. Not in this route neither in any other route.
Any idea about how to solve this? (if possible without re-building once again the whole document) We can't wait until the error code 1 bug is fixed in future Adobe updates as we need to submit the APP to Apple next week.
Thanks for your time.

Anyone can help??
Update my latest experimental results.
I found that issue was folio package related.
Because when I use another folio package to the same app item in App Builder, this error message does not appear.
But the original package in exchange, this error information occurs.
Are there helpful to solve this problem?

Application builder error 1041

Dear All,
I have a problem to build a application in Labview 8.5.
It's the first time that I try to build this application in fact it's the first application every I try to build.
I found the following problem.
Authentication: "Error Code Database.vi is password-protected. Enter the password to acces the block diagram."
I do not know the password for this file.
The building errors details I get are:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1041 occurred at Invoke Node in AB_Source_VI.lvclass:Apply_VI_Properties.vi->AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.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: Incorrect password.
Method Name: Lock Stateet
When I start looking for the file that causes the problems I find that it is "Get File Type.vi" it's protected.
This is an NI file and I do not know the password and I do not know why it is locked.
The VI general properties of the file are:
C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\lvfile.llb\Get File Type.vi
File revision is 78
I tried to solve the problem as discribed in tread
http://forums.ni.com/ni/board/message?board.id=170&message.id=297099&requireLogin=False
But that did not work for me. A build with a new file also gives the same error.
So I tried something else in the Build specification there is a menu "source file settings". There is a selection about passwords
You can choose 3 settings 1) No passord change 2) Remove password 3) Apply new password. I changed this setting from 2 to 1.
And I can build the project now. So I change back from 1 to 2 and I should get the error back again. And I did not. How can this happen?
What is going on?
Thanks in advance

Mike, you can't change the password if you don't know the old one. Why do you want to change the password? I do't wanna change the password. The application builder is asking for it and I do not have it. The same problem occured at thread http://forums.ni.com/ni/board/message?board.id=170&message.id=297099&requireLogin=FalseIt looks almost the same but the solutions there did not work. The problem kept occuring. So I tried someting else:
In the Build specifications there is a menu "source file settings" for your project files. I only have 1 main.vi project file
There is a selection about passwords for your source file settings. See attachment 3. You can choose 3 settings
1) No passord change
2) Remove password
3) Apply new password.
I changed this setting from 2 to 1.And I can build the project now. So problem solved.
Then I changed back from 1 to 2 and I should get the error back again. And it did not.
I do not understand why it works and I would like to.
What is going on?
Attachments:
Authentication.JPG ‏13 KB
VIPropertiesProtection.JPG ‏131 KB
SourceFileSettings.JPG ‏52 KB

Installer build error code-21 Labview 8.6.1

While attempting to build an installer I get an error code -21. What is the error and how do I correct it?

I also have this problem. The executable build itself works correctly, but the installer fails to build. There are a number of DLL dependencies, but they are all included and present in the build and in the installer Source Files. I put CDK.EnableLog=True in my LabVIEW.ini and logged the error from the installer build process. Here is an excerpt from the relevant section:
    [LOG ON] Fri Apr 30 13:46:02 2010
<<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
<<<MDFConfig_SetDistributionLanguage>>> Language id: 9
<<<MDFConfig_SetBuildDir>>> Build directory: C:\MyPrograms\MyApp_Working\Install
<<<MDFConfig_SetBuildMode>>> Build mode: 1
    [NMDK BEGIN] Fri Apr 30 13:46:02 2010
     Building developer part
> Adding files to installer
<<<MDFBuildDevPart_SetFileNames>>>
<<<MDFBuildDevPart_SetDefaultInstallDir>>>
<<<MDFBuildDevPart_SetUpgradeInfo>>>
<<<MDFBuildDevPart_SetOtherProperties>>>
>
> **************
> *** Error: An internal tool or library returned an error. (Error code -21)
Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
nmdkSetInformationalProperties returned error code 26024
> *** End Error Report
> **************
>
Adding product dependencies to developer part
>
> **************
> *** Error: Windows SDK function returned an error. (Error code -12)
Closing dist kit
***** About to begin MAXImportConfig:oMAXPartModifications...
No MAX import files specified - nothing to do - returning.
Error in MDF API function: _MDFBuildDevPart_Close
Error in MDF::BuildDeveloperPart::Close.
ERROR: Caught MSI Exception:
<Unable to format error record.>
MSI error code: 6
> *** End Error Report
> **************
>
    [LOG OFF] Fri Apr 30 13:46:02 2010
    [MDF END] Fri Apr 30 13:46:02 2010
     Closing MDF.
I've also tried the same with a simple test application and it build/installs correctly, so I know it is my project somehow. One notable difference is that I previously had namespace conflicts in the executable build that were resolved by the following these instructions:
http://digital.ni.com/public.nsf/allkb/47272B69E2C167DB862574AC006A258B?OpenDocument
I hope someone can help. I need to deploy this application soon.
Regards,
- Ray

Dimension build error codes

Does anyone have a list or know where I can find a list?
I'm seeing 3307 and 3315 and need to figure out what that is causing them
Thanks!

Hi,
There isn't a list for the dimbuild error codes that I know of. They don't even appear in the message.txt file that comes with the API install.
Maybe if you paste the whole line of the error we might be able to help a bit more.
Google found a couple of examples which might steer you in the right direction:
\Record #234 - Property [FAC: Unknown | AMER] changes for member [FAC-1234 | AMER] not allowed (3315)
\\Record #2 - Incorrect Parent [600-20] For Member [600] (3307)
Gee

Application Builder: error in building DLL from a VI

I have a VI which I have been compiling into a DLL for use with Labwindows. Suddenly yesterday the build would no longer compile. Instead the error message (see attached picture) persisted all day no matter what I changed in the VI. Before the error message appeared, the Labview project window went blank for a moment, then showed some "C" code from somewhere, and then back to the project window. It's almost like something blew up in the compile process.
I've tried all suggestions in the error message. Checked data types and names. I believed the VI is wired back to where it was. There is not much to the VI but it does reference some .NET assemblies.
Thanks for any comment or help,
Doug Wendelboe
Attachments:
VI-DLL-Pictures.zip ‏21 KB

Hi Eriquito:
Thanks for your response. I've included some snapshots of appropriate Ap Builder setup pages. My DLL is named "CVIMESQueryTray.dll". I had this compiling quite well up until a few days ago, so Ap Bldr didn't object then.
See if you can spot something in my ApBuilder setup that I might be doing wrong.
Thanks for your help.
Doug Wendelboe
(Hmmm.. I guess I can't attach more than three items, so I ZIPped them into one file).
Attachments:
ApBuilderPics.zip ‏154 KB
ProjectFile.JPG ‏60 KB
ApBuilderPage1.JPG ‏31 KB

Application builder error creating

After install Labview 9.0f2, no longer is possible to build application
Solved!
Go to Solution.

Would you like us to continue guessing, or would you be capable of providing some details?
Such as what the error is?
What was the version of LabVIEW you were using?
What toolkits you are using?
Anything else you can think of?
Remember, we don't have one of those nice troubleshooting scripts that call centers have.

Application builder error 26005

Hello All,
When I try to build my application I get the following error:
L'erreur 26005 s'est produite à Build Application.vi>>Dist Call Create Installer.vi>>Win Install
Create.vi>>MSI DK Open.vi
D:\TMNHe\Exe\TMNHe_Testeur_20090709\Installer.
Raisons possibles:
NMDK_OPEN_CAB_FILE_CREATE_FAILURE
Can anyone help me?
Labview and builder 6.1
Solved!
Go to Solution.

A new installation of builder solved the problem. ?????

Error code 1127 when using teststand deployment utility

I'm have installed on my pc Teststand 3.0 and labview 7.0 -this error occurs during build
Error Code:1127
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Open VI Reference in TestStand - Dist Chg and Save VIs.vi->TestStand - Dist Build LLB Image.vi->TestStand - Build VI Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI Distribution AX Wrapper.vi.ProxyCaller

>>>>>>>ok, I'm getting a different error code: error code 7 instead of a error code 1127 with the error:
Error Code:7 Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW
error: Invoke Node in TestStand - Dist Cmp Settings to Disk Hier.vi->TestStand - Build VI
Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI
Distribution AX Wrapper.vi.ProxyCaller
>>>>>>>>And I did a mass compile of the directory mentioned above and I got this error:
#### Starting Mass Compile: Thu, Jul 15, 2004 9:44:04 PM
Directory: "C:\Program Files\National Instruments\TestStand
3.0\Components\NI\Tools\Deployment Utility"
CompileFolder: error 13 at C:\Program Files\National Instruments\TestStand 3.0\Compon
ents\NI\Tools\Deployment Utility\DeploymentUtility.exe
#### Finished Mass Compile: Thu, Jul 15, 2004 9:44:17 PM

Teststand deployment with LabView VI gives error code 1035

Using Teststand 3.0 deployment tool. My test sequence uses LabView 7.0 VIs. When I build, error code 1035 is output after several minutes along with the message :-
Error Code:1035
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. Labview error:
Invoke Node in Teststand - Diost Chg and Save VIs-> TestSTand - Dist Build LLB Image ->TestStand - Build VI
Distribution.vi->TestSTand - Build VI Distribution AX Wrapper.vi-> TestStand - Build VI DIstribution AX Wrapper.vi.ProxyCaller
++++++++++++++++++++++++
I tried a LabVIEW mass compile of my VI directory and it reported no errors.
I have tried this website for an explaination of this error but there appears to be nothing. System is Windows N
T4 SP6.

Jon, you mentioned this problem got solved in TestStand 3.1. Right we are using TS 3.0 and have that problem caused by LabView's own locked VI's (not to mention LabView VIs with the "/" character in the filename, i had to save those under a different name) . Is there any documention about this problem being fixed in 3.1? This would help me explain the need for the upgrade to the powers that be.
Thanks,
Fernando Marquez
Project Engineer
CSI
Jon Bowers wrote:
There can be a problem in Teststand 3 when deploying with the "Lock vi Diagrams" option checked when your sequence contains vi's that already have locked diagrams. Un-checking this option or removing the vi's which have locked diagrams should allow you to build successfully. This has been fixed in Teststand 3.1.
Jon Bowers
Applications Engineer
NIUK

Need help in getting pxi-7854R to build simple code, returns error:-63040

Hi
Trying to build a labview program, which just reads AIO on the pxi-7854R board that is installed in a PXIe=1062Q
Can you help?
below is the error message:
Error Code: -63040
NI-RIO: (Hex 0xFFFF09C0) A connection could not be established to the specified remote device.
Ensure that the device is on and accessible over the network,
that NI-RIO software is installed, and that the RIO server is running and properly configured.
For NI-RIO 2.3 and later, refer to Software>>NI-RIO>>NI-RIO Settings under the system in MAX.
Prior to NI-RIO 2.3, refer to Software>>NI-VISA>>VISA Options under the system in MAX.

Which NI-RIO driver version do you have installed? Also, this KnowledgeBase article may be helpful in narrowing down the issue:
http://digital.ni.com/public.nsf/allkb/83DF7B9245541FC8862573A100597696?OpenDocument
Daniel K | NI Applications Engineer | Certified LabVIEW Developer

Build error when using custom error codes

When I try to build my application using custom error codes I receive the following error:
Error 1 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.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.
C:\Program Files\National Instruments\LabVIEW 8.5\user.lib\errors\BPMS-errors.txt
This only occurs the first time I attempt to build my application. If I build again immediately after receiving the error, everything works fine. My custom error codes were created using the provided editor, and I have included the file in my project. I have also checked the "Copy error codes" box in the advanced build specification settings.

Hi Donovan,
The attached project is giving me the error previously discussed. Thanks for your help.
Attachments:
BuildError.zip ‏10 KB

Error during Custom Build - error PRJ0019: A tool returned an error code from "Performing Custom Build Step"

Hi All,
I was trying to develop C++ web service using GShop with Visual Studio 2005.I refered a tutorial :-
http://guruce.com/blogpost/hosting-webservices-on-windows-embedded-compact-windows-ce-using-gsoap .
AS per the tutorial i proceeded. But, i stuck-up when making a custom build with Helloworld.wsdl.Here is the output :
1>------ Rebuild All started: Project: HelloWorldWebService, Configuration: Debug Pocket PC 2003 (ARMV4) ------
1>Deleting intermediate and output files for project 'HelloWorldWebService', configuration 'Debug|Pocket PC 2003 (ARMV4)'
1>Performing Custom Build Step
1>'D:\Test' is not recognized as an internal or external command,
1>operable program or batch file.
1>Project : error PRJ0019: A tool returned an error code from "Performing Custom Build Step"
1>Build log was saved at "file://d:\Test Code\HelloWorldWebService\HelloWorldWebService\Pocket PC 2003 (ARMV4)\Debug\BuildLog.htm"
1>HelloWorldWebService - 1 error(s), 0 warning(s)
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========
As given in the tutorial i kept my custom build command line as : -
$(SolutionDir)\gsoap-2.8\gsoap\bin\win32\wsdl2h.exe -s $(InputPath) -o $(ProjectDir)$(InputName).h
and outpouts : $(InputName).h
I kept GSHOP in the project filder :- D:\Test Code\HelloWorldWebService
Kindly help.
Jyotiranjan

Hi Jyotiranjan,
I’m glad to hear that you got it working.
Thank you for sharing your solutions
experience here. It will be very beneficial for other community members who
have similar questions.
Best regards,
Lucy
Lucy Liu [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Labview: resource not found error code 24 when building executable using 8.20 and dsc module

I am trying to build an executable and I keep getting and error and cannot seem to figure out what is wring. The whole error is "LabVIEW: resource not found. An error occured loading "interface 3.vi" Labview load error code 24: this vi cannot be loaded because it is broken and has no block diagram."
I am using LV 8.20 and DSC 8.2. I am trying to create an executable that has the web server running for using remote panels, i have netowrk published shared variables, connecting to a fieldpoint unit, and I am using the NI system tray icon vis to load the program to the system tray.
I have my shared variable library added as a support file, as well as the lvdsc.ini, and the tray icon files. I have sleected "Enable Enhacned DSC run time support" in the app builder, did not remove any type def,etc.
I cannot get the .exe to run on my development machine or another machine, I get the same error. I tried creating an installer that installed the 8.2 runtime, dsc,fieldpoint, variable engine and manager and MAX.
I could not find anything in the help files on the dsc, maybe someone else has some hints. thanks
Kenny

Hi Kenny,
I hope you are doing well today! What is interface 3.vi? Is it possible for you to post your project over here? Also, I would recommend creating a simple DSC application; and would like you to build it. Do you still get errors?
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

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

Applicatio​n builder error coder 21

Similar Messages

Maybe you are looking for

Application builder error coder 21