Installer Build Error using LV Runtime Engine 2010

I had an executable and installer working that were built in LV2009. Since then I modified my source code and saved as LV version 2010. I rebuilt the executable, but when I tried to run it on the target computer, I got an error message saying that LV Runtime Engine 2010 was needed. So I tried to rebuild the installer using LV Runtime Engine 2010 as an Additional Installer. However, this build was unseccessful and I got a lenghty error msg that I don't understand (see attached).
Thanks in advance.
Solved!
Go to Solution.
Attachments:
Installer Build Error Message.docx ‏13 KB

Hello,
I am building an installer with LV2010 SP1. I have added the runtime engine to be included in the installer. I get the following error
------------------ERROR MESSAGE-----------------------------------
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.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
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'PSUTS' from: C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume\ 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
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
Loading product deployment informationAdding files to installerDone adding filesPreparing to build deploymentCopying products from distributionsCopying distribution 'PSUTS' from: C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume\ 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_CopyItemWindows function FindFirstFile returned an error. Error code: 3*** End Error Report************** Done building deployment
--------------------MESSAGE END------------------
In the additional installer page: I see the installer source location (see attached image file) as 'C:\CBESVN\PSUTS\Software\builds\PSUTS Installer\Volume' which is really my installer's source location. But I am not sure how this location got assigned. I have tried to create new build spec from the same project, still the installer source location stays the same. How do I get this issue solved?
Attachments:
Additional.jpg ‏174 KB

Similar Messages

LabVIEW Runtime Engine 2010 NI_AALPro Error

Hi All,
I have an problem with the executable version of my LabVIEW program. I just created an LabVIEW program in LabVIEW Professional 2010 version to acquire some FFT spectrums so it also use some function palettes of Sound and Vibrations toolkit like Power Spectrum, Peak Search, Power in Band etc.
Then I just created an executable version of the program to run on a different system (Tools>>Build Executable Verion(EXE)). But when I tried to run the executable verion on a different system is showed some errors. I am attaching a printscreen of all errors showed.
So, the executable version of the program is working fine in the develoment system but showed some errors when we try to run it on a different system. We have already installed the LabVIEW runtime engine 2010 as well in the second system.
My one more question is when we build an executable version of a LabVIEW program then it should run on all PC without any other software (Runtime engine) because it got an extension of .exe
so is there any chance or way to build a totally standalone executable version of the program without using any runtime engine as well.
Thanks
Attachments:
error.JPG ‏28 KB
dll & lvlib.JPG ‏41 KB

Hi PSBRRR,
It seems like you didn't include all the dependencies of your VI or project to your build specification. Can you send a screenshot of the Source Files Setting page of the Application Properties dialog box ? You have to add all the VIs and DLLs that are used in the Sound & Vibration toolkit and any others you are using to your executable file or support directory.
For the last question : no you can't. Since LabVIEW 2010, the Run-Time Engine is like the "Java Virtual Machine". The compiled code inside your EXE is interpreted by the "LabVIEW Virtual Machine" included in the LabVIEW Run-Time Engine. That's why it requires the Run-Time Engine to be executed or at least the development environment (previous versions of LabVIEW didn't use this principle but it was also required to have the Run-Time Engine installed).
Regards,
Da Helmut

Installer Build Error

Hi,
I am rebuilding an existing Labview application (originally done in LV8.6) using LabVIEW 2011. The application works in LV2011 as stand alone but when I try to build the installer, I get the error for which the details are in the attached text file.
Please help figure out the issue.
Thanks
Jeet
Solved!
Go to Solution.
Attachments:
Installer builder error.txt ‏4 KB

The issue with installer build is fixed. It wasn't able to read the drivers from the CD drive because the CD drive had gone bad.
We replaced the CD drive and it started working.

Errors while installing runtime engine netframework 4 (32bit)

While installing the update for runtime engine netframework 4 we get diffrent errors. We can't register DLL files.
This is the error we get:
Error 1904. Module C;\Program Files\ SAP BusinessObjects\Crystal Reports for .NET Framework4.0\Common\SAP BussinesObject Enterprise XI 4.0\win32_x86\commonjob.dll Failed to register. HRESULT -2147023898. Contact your Support personal.
same error for:
saxserialize.dll, datadefmodel.dll, cubedefmodel.dll, rptdefmodel.dll, rptcontrollers.dll, requestmodel.dll, clientdoc.dll,
prompt.dll, dtsagent.dll, localcon.dll, crlov.dll, crqe.dll.
Installation ends with installation succesfully. When ignored is pressed.
Hope someone can help to fix these errors. Its not working properly now.

This is the way I resolved a similar issue this week:
In the registry, search for 139E8906DC83 Search HKLM\Software\SAP BusinessObjects. This will lead you to the actual file name.
Download [Process Monitor|http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx]. Se the filter for regsvr32.exe.
Manually (Start | Run regsvr32 <path to the file>) register the dll.
Save the process Monitor log.
Do a search in ProcMon for cryptocme2.dll. Rename this dll.
Try the install again.
- Ludek

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

XML Form Builder Error using JRE Version 1.6.0_05

Hi Experts,
I am trying to create an XML Form using XML Form Builder. But I noticed that the root nodes under the data model area of the said tool is not clickable(even if it has + sign on it)thus hindering me to continue. I encounter this error using jre version 1.6.0_05.
Can someone help with this?
Thanks a lot
Edited by: Leah Mendoza on Oct 9, 2008 2:07 AM
Edited by: Leah Mendoza on Oct 9, 2008 2:07 AM

Hi Leah,
Have you tried double clicking?
If this doesn't solve the issue, you might want to try using a different version of the browser and disable the pop up blocker on your browser.
Please try this out and let me know.
Regards
Mazin

What is needed to run a .llb file using a runtime engine?

I would like to run a .llb file on a computer that doesn't have LabVIEW installed. Is that possible? If so, what is needed to do that? I have tried to install a runtime engine, but can't get it to work. The .llb file is currently running on LabVIEW version 6.0 on another computer, but I don't know with what version of LabVIEW the .llb file was created. The computer on which I would like to run the .llb file has Windows XP.
Thank you for any help!

Mathan wrote:
You have to create an executable with the help of project explorer.
The user has LabVIEW 6 (as he noted in the original message). LabVIEW 6 has no project explorer.
To OP: I am assuming the LLB contains a top-level VI that can be run. Otherwise, this is a moot question. If you want to open the VI and view it, then you need the development version on the target machine. If you want to run the top-level VI in the LLB then you must create an application that you can copy over to the other computer. The other computer requires the LabVIEW Runtime Engine in order to run the executable. To build the application you need the Application Builder. This is a separate product from LabVIEW, but was included with certain LabVIEW editions.. If you do not see a menu option for building the application then you do not have the Application Builder. You would need to contact your local NI sales office to see if you can still buy a copy. I doubt you will be able to, but it's worth a try.
EDIT: Sorry for the duplicate info. I got sidetracked while composing the message, and did not see the additional responses from Dennis.
Message Edited by smercurio_fc on 08-18-2009 09:51 AM

[HELP] Teststand error when using labView runtime engine...

I have an extensive TestStand 3.5 project which I am working on. This project uses a large number of LabVIEW 2012 VI’s. (Note: The version of TestStand cannot be changed). When TestStand 3.5 LabVIEW Adaptor is configured to “Development System (Active Version: 12.0)” all the sequence run and perform as expected.
When I change the TestStand 3.5 LabVIEW Adaptor is configured to “LabVIEW Run-Time Engine 12.0” then I get an -18002 error in the first VI called by the sequence and nothing runs. Now this sequence contains a standard library VI in it “Check if File or Folder Exists.vi”.
From research I realised that I needed to deploy the software properly. So created a LabVIEW project with all the sequences and VI’s in it and a “Source Distribution”. I also unchecked “Exclude files from vi.lib”, “Exclude files from instr.lib”, and, “Exclude files from user.lib”. After building the project I get a “data” folder full of VI’s and control files (273 of them).
Next I created an “Installer” and added build to the correct place. I can see the “data” folder in the source files section.
When I install this distribution kit on a PC, which happens to have full LabVIEW 2012 development on it, all the files install but the “data” folder is missed out!!!
If I then attempt to run the installed top level sequence I get the same -18002 broken VI error as before. If I manually copy the “data” folder into the same place as it was built it makes no difference.
Anyone got any suggestions?
Christopher Povey
Senior Test Systems Engineer for BAE Systems.

Bit of additional information:
I created a blank LabVIEW 2012 project. To this I added one VI which included a call to "Check if File or Folder Exists.vi". Then added one TestStand 3.5 Sequence which contained a call to the VI above.
I then added a build to the project and built the project. This resulted in a folder with the sequence file, my VI and a Data folder containing the "Check if File or Folder Exists.vi". When I tried to run the TestStand sequence with LabVIEW Run-Time Engine selected it failed as before.
Next I added another LabVIEW step to my sequence calling "Check if File or Folder Exists.vi" from the "Data" folder. It then worked!
I then modified my VI and added the MD5 checker VI (forget the exact name). It added some files to the dependences in the LabVIEW project. I rebuilt it and ran it again and again it worked. I did not need to add the additional VI's in the "Data" folder to the sequence file.
If I remove the LabVIEW step to my sequence calling "Check if File or Folder Exists.vi" though it breaks again.
This is not ideal though as it is a bit chicken and egg. In order for the project to work I need to add one of the VI's from the generated "Data" folder into a sequence in the project, but I can't do that until I build the project to create the "Data" folder!
Christopher Povey
Senior Test Systems Engineer for BAE Systems.

Installer build error LV2010

Hello,
I am using LV2010 32bit, vision tools, database tools, Win7 64bit.
I am getting the following error when I try to build an installer. The executable builds without any problems only the installer:
CodeSignAPI.lvlib:Get Signing Error String.vi<ERR>
Error: The Timestamp Authority URL specified does not point to a valid Timestamp Authority server, or an unknown error occurred.
<b>Complete call chain:</b>
     CodeSignAPI.lvlib:Get Signing Error String.vi
     CodeSignAPI.lvlibign with Certificate.vi
     IB_MSI.lvclassign_Setup.vi
     IB_MSI.lvclass:Build.vi
     CDK_Engine_Main.vi
     CDK_Build_Invoke.vi
     CDK_Build_Invoke.vi.ProxyCaller
Loading product deployment information
*** Abort requested.
*** Error Details:
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
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
Copying files...
Scanning files...
Updating files...
Creating merged database...
Creating installer files...
Build complete successfully.
Copying additional setup files
Compressing installer files
Done building deployment
Solved!
Go to Solution.

Well the error message clearly suggest that there is something wrong with the "Windows Security" section of you installer's specs, try removing the settings from that section and see if it builds properly, then if it does you know where you have to dig.
Good luck
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Build error using daqmx vi's crashes LV

I am trying to build an executable in LV 8.2 (it worked in 8.0) using daqmx create channel. The build is not successful and sometimes gives no reason and other times tells me to allow debugging. I allow debugging and the executable tells me I need full development to fix error. I should be running professional development. Sometimes I get a LV crash where LV has encountered a problem and needs to close.

brianpt,
Thanks for posting to the NI forums. Do you still have issues if you try to build an application that does not contain any DAQmx code? What version of DAQmx do you currently have installed? What is the exact error that you are seeing? Are you using the LabVIEW Professional Development system?
Regards,
Neil S.
Applications Engineer
National Instruments

Using LV2009 to produce EXEs for Runtime Engine 8.6

Hi,
I am currently running LabVIEW version 8.6. However, having purchased this less than a year ago, I think I am eligible to upgrade to v2009 for free.
At the moment, if I produce an EXE file using the Application Builder, my colleagues are able to run this on their machines using the LabVIEW Runtime Engine version 8.6.
If I upgrade to LabVIEW 2009, will all my colleagues who use the runtime engine also have to upgrade to the Runtime Engine 2009, or will I have the option to build an EXE file that is compatible with version 8.6 of the Runtime Engine.
Many Thanks,
Dan
Dan
CLD

There are no option for build "8.6" compatible application from LabVIEW 2009 (other than save for 8.6 and build in 8.6).
For LabVIEW 2009 - builded application you will need according version of the Run-Time Engine.
Important point, that Run-Time Engine version 2009 will not replace version 8.6. It means, if you have PC where Run-Time 8.6 installed, and after that on this PC you will install Run-Time 2009, then you can run both 8.6 and 2009 - builded applications.
Andrey.

Multiple installs of runtime engine?

Are there any problems with multiple installs of LabVIEW 7.0 runtime engine.
That is, if I create an executable application with the runtime engine installer present and distribute it to a person who already has the 7.0 runtime engine installed, does this present any problems? Will the runtime engine actually be installed the second time? Will there be multiple entries in the Windows add/remove list?

The installer is designed to work that way. Multiple installs of the same version of the runtime engine should only increment the reference count on the files. When you install your built application you will not see an entry for the runtime engine in the Add/Remove Programs (ARP) list.
If you are familiar with MSI terminology, this behaviour is because the LV RTE that is included in your installer is just the merge module not the MSI. When you install the LV development environment, the RTE is installed from a separate MSI. Because your built app installer will use the merge module, the only way to uninstall the RTE will be by uninstalling your app.
Naren

Runtime engine files 8.2

Hi,
Since most users of my written program are users with "restricted right" acounts under Windows XP I copied the Runtime engine files of LV7.11 manualy by copying the
"Program Files\National Instruments\LabVIEW 7.1\Shared\LabVIEW Run-Time\7.1" files to the harddisk and run a build executable from that directory. Since this application looks in its own directory for support-files this worked fine for LV7.1.
Last week I converted my program to the LV8.2 version. When I tried to copy the RTE8.2 file in the same way as I did before, the program would start-up. It asks for a NIINI32.DLL file. When I include this file it does not return any errors, but the program doesn't start. Can anyone tell me whether their is a different way to run a exe-file build by LV-application builder by copying files manual in stead of running the RTE-installer?
Thanks in advance,

I know that NI did the run time engine to minimize space when installing multiple application. But i'm agree with you, we should have another way to build executable without the runtime engine. Some people dont know what it the runtime engine and uninstall it. afther that they just cant use the program anymore. The other reason, it that a VI use just some Kbyte and the run time engine that include almost everything, need some Mbyte.
If somebody know, please tell us......
Benoit Séguin
Software Designer

Cannot load Runtime engine verion 7.0, only 8.0 and later versions are supported

Hi,
I am new to using third party labview drivers. I have a labview driver for Chroma 63600 loads that I want to use in TestStand 2012.
However when I load the vi. I get an error 'cannot load Runtime engine verion 7.0, only 8.0 and later versions are supported'
I have Labview Runtime Engine version 7.0 Installed on my Windows 7 machine.
Could anyone please let me know, How I could resolve this issue?
Please see attached driver for Chroma Loads
Solved!
Go to Solution.
Attachments:
chr63600_LabView_V11.zip ‏866 KB

To avoid more confuison,Here is the scenario,
The version that was on the driver attached is from the driver manufacturer.
I do not have any version of labview INSTALLED on my system. I am using the driver in Test Stand 2012 using a labview adapter.
I make sure I match the VI version and the run time engine version on TestStand 2012 to load the VI.
But for this specific driver, I was not successful in loading the VI at all.
As I understood that only 8.0 OR LATER are supported on TS 2012, I have asked to upconvert the driver to work with 8.2.1 Labview runtime engine.
I have now got a.LLB file of the driver mass compiled in Labview 2012 from discussion boards( and also attached here). I have tried the mass compiled LLB file on TS2012 but still have issues loading the VI as it moans about different version of SUB VIs.
However I am still trying to fix this version incomaptibilies. Any help would be much appreciated

Windows Runtime Engine

Hi,
running a job using Windows Runtime Engine and a script in VBScript will cause no action, in job log and system log no entry. It seems this runtime is not working.
The dispatcher is configured and running. All jobs with java runtime engine are running properly.
Any ideas what needs to be configured?
Thanks for replies

Hi Ralf,
could you please provide more information: Do you try to test-run the job?
I remember having had this problem, too.
I think I solved it by reading the error messages in the DOS prompt when starting a test.

Installer Build Error using LV Runtime Engine 2010

Similar Messages

Maybe you are looking for