Prompt_Missing_Products dialog when building installer

Hello again,
Hopefully an easy question! When I open one of my three installer builds for my product, change the version and contact information, and press OK, I get a dialog that I really don't want to copy all of the text for (see screenshot below), but involves the words "Prompt_Missing_Products" and what looks like an upgrade code (but is not the upgrade code listed on that same installer properties page), followed by "Do you want to continue?" with Yes/No. I choose Yes, and everything seems fine. I've seen this a couple times, but not every time, and it's making me nervous, so I hope one of you can explain it.
Full error (warning?) text in this screenshot:
Thanks in advance for any insight,
-Joe

Hi Cody,
Thanks for your reply. I have the bare minimum additional installers selected (just LabVIEW 2010 Runtime and NI-VISA Runtime, which my product uses). Unless I should unselect some of the sub-categories of the 2010 Runtime? I've been assuming I should have them all, but I admit I don't know for sure.
As long as nothing is changed or broken by hitting Yes, then I guess it doesn't matter. Thank you for your reassurance!
-Joe

Similar Messages

How to include help files when building installer

Hi!
How can I include my application help manual (in .pdf format) when building the installer such that the file goes into a designated folder and its link appears in the Start>Programs>App folder ?
Thanks,
Gurdas
Gurdas Singh
PhD. Candidate | Civil Engineering | NCSU.edu

Gurdas,
Add the .pdf as a support file in your executable
Create an installer for the executable
Under the "Files" button on the "Installer" tab select the .pdf and select "create program item".
This will place the .pdf in the start menu program group.
cheers,
Brett

Geting error when build installer

I'm getting Error 33 and dotnet x86 ni language pack error and build stops
how can I solve this issue?
Building executable is fine, but the problem occurs during building installer.
Please advice
regards
Pierre Tannoury
Pevatech International S.A.R.L

thanks for helping,
i still receive another messages but the dotnet error message is gone
please see below the building status and what's errors remaining
CDK_Build_Invoke.vi.ProxyCaller >> 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
Adding files to installer
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...
Updating files...
*** Error: Fatal runtime error. (Error code -10)
*** Error Details:
Access violation! Structured exception code 3221225477
*** End Error Report
*** Error: An internal tool or library returned an error. (Error code -21)
Error Messages
*** Error Details:
Error in MDF API function: _MDFBuildDist_Build
Error List
.\InputParser.cpp(819): IInstallerError 108
Problem with updating Part DataSocket64.msi.
*** End Error Report
Done building deployment

How to include external files when building installer for a standalone executable?

Hi,
I was trying to build a stand alone executable from my Labview project and I was able to do it successfully. Now I would like to include a few external .txt files in the installer. Those .txt files have parameters/constants that will be used by the program, and my program needs to load/read them when running. For now I have to manually copy/paste them into the target machine, but I really hope the installer can do it automatically. I see there is a "data" folder in the installer, and that's where I hope those .txt files can be added into.
How can I do it? Can anyone give me some suggestions? Thanks!
Rgds
Harry
Solved!
Go to Solution.

Norbert,
I could not find "Add file" when right clicking the project. See attached image please. Under "Project" I do have a "Add to project" but there is no option for external files. I did not find "Source" location either.
What did i do wrong? Is there any version requirement here? I have a 2010 base version. Thanks for your help.
Rgds,
Harry

Error code -13 when building installer

Hello,
I need some help! I am trying to create an installer for my application; which was created with no problems; but I keep getting a message about an error code -13. I'm adding an image of the message since it is a long one. I really don't understand what the error means or how to repair it. Any help I could get is appreciated!

Hello rd.mcdt,
The following link has information about a similar problem, could you try to follow the process described on the link? Please look for error code 13 instead error code 30 and let us know if this helps.
Error 30 Occurred at CDK_CreateNewWizard_Invoke.vi.ProxyCaller When Trying To Build a LabVIEW Installer:
http://digital.ni.com/public.nsf/allkb/8E5E6C58C625B88A8625786A005B21E0
Best Regards
David P.
National Instruments
Applications Engineer
www.ni.com/soporte

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 KB

Alina,
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

Error when building Installer with USI 1.5.0 with Labview 8.5

I used to build an installer with Labview 8.2 and included this additional installer USI 1.5.0 but now with labview 8.5 it gives me an error:
"Locate the "NI LabVIEW" distribution. LabVIEW needs to copy a component installed or updated by the distribuiton to conitnue building the installer"
Any advice

Hi reza_sed,
Thank you for contacting National Instruments. When you get this message, are you prompted for a location of this installer (CD drive or something)? Sometimes if components are installed together, certain dependencies are created. You might be able to add the installer to a LabVIEW 8.2 installer with no problem, but the installer cannot be found when using a different version of LabVIEW. You might try uninstalling USI, then copying the install files from the CD or from our website to your hard drive and then installing from there. Then, you should be able to include the additional installer.
Another thing that may be happening is that the LabVIEW Run-Time Engine you have for 8.5 does not support NI-USI. The full version of the Run-Time Engine supports NI-USI, but the web browser only version does not. Make sure you select the full version when installing.
Donovan

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

Microsoft Visual C++ runtime error when building installer

I'm trying to build an installer for a very simple VI I've created in 8.2. Before the build is complete I get a Microsoft Visual C++ runtime error message pointing towards the labview.exe file. I've already tried re-installing LabVIEW and deleting older versions of the LabVIEW Runtime engines with no luck. I recently upgraded my system from LabVIEW 6.1 and I'm using Windows XP. Any suggestions?
Thanks.
LabVIEW 2012 - Windows 7
CLAD

I included waveform storage, runtime engine 8.2, ni-visa-runtime and ni-serial3.1. I tried to create a setup.exe by installer on an other pc. But it's completely the same behavior afterwards. I attached the error message. This message appears after I choose the path and continue the setup. It's the question which file is meaning.
I tried to create a setup.exe by installer without any additional.
The strange thing is it was unsuccessful with following message. Maybe this will be helpful to find the problem.
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_Open.vi
Attachments:
missing file message.JPG ‏15 KB

Include directories with files when building Installer

I want my installer to install the executable in C:\ProductA\SystemTest\Program1
I also want have C:\ProductA\SystemTest\CsvFiles created and have the csv files included.
Is this possible?
How would I go about doing this?
Solved!
Go to Solution.

Take a look at this sample project (LV2013). The build target folder is c:\tmp\csv_test, but it creates all additional sub-folders.
For some reason I cannot attach a zip file to the post, so just create 'files' folder as sub-folder of the project and add some files there. You can have also sub-folders in 'files'
In the destination settings you need to check the 'Preserve disk hierarchy' option.
In Always Included you need to add only the root folder of your CSV files
Attachments:
csv_test.lvproj ‏7 KB
list_files.vi ‏8 KB

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.

Error building installer: this application has requested the runtime to terminate it in an unusual way

Hi,
I build an appliction using LabView 8.2 with Report Generation Toolkit for MS Office V1.1.1 on a WinXP SP3 system without any errors. When I try to build a coresponding Installer, I got the following error message:
This application has requested the runtime to terminate it in an unusual way.
Can anyone help me????
Solved!
Go to Solution.

Hi Gunnar,
Good Morning and I hope your well today. Thanks for your post onto the NI Discussion Forums.
There are several considerations and potential causes of the error. I will try my best to cover some of the potential causes.
Firstly, you've suggested that the Report Generation Toolkit is being used:
When building applications with Report Generation Toolkit VIs, you must complete the following additional steps:
1. From the Source Files tab of the Build Application or Shared Library (DLL) dialog box, click the Add Dynamic VI button to add the following two VIs to the application:
– _Excel Dynamic VIs.vi in vi.lib\addons\_office\_exclsub.llb
– _Word Dynamic VIs.vi in vi.lib\addons\
_office\_wordsub.llb
2. If the application you are building contains the MS Office Report Express VI, you must add any Word or Excel templates that you use to the built application. From the Source Files tab, click the Add Support File button to add the template files to the application. By default, the custom destination for the templates is the same as the path that appears in the Destination directory field on the Target tab with a data subdirectory appended. Do not change the custom destination for the files you add.
For example, if you are using the basic Excel template with the MS Office Report Express VI, add MSOffice_RGT_Template.xlt to the application. The basic template files are located in the templates\Report directory.
Have you done this?
Could you please send an image of your project and your installer options?
The problem was that I use Office toolkit and it was not compiled with LabVIEW 8.2:
I found a forum where the toolkit wasn't complied for LabVIEW 8.2. Could this be an issue I wonder?
I mass compiled the complete directory c:\program files\National
Instruments\LabVIEW 8.2 (it took quite a long time) and afterwards the
directory lvjpeg disapeared.
Have you tried this?
Runtime to Terminate Error:
1. Have you been having any trouble with LabVIEW - crashes or bug installation?
I would suggest repairing your installation of LabVIEW and the toolkit(s) using the Add/Remove Programs.
2. Also would it be possible to try building an installer on another machine?
3. I have seen that not enough Hard-disk space can cause this error - what is the status of yours?
4. Are you using any other drivers such as DAQmx or VISA?
I hope this information starts to help us locate the root cause of the trouble your having, and if you could answer the questions above and try my suggestions that would be great! if you could also gather the extra information about your installer options that would also really help supporting the issue further.
*edit:
5. Also the runtime error would suggest you've selected to include a runtime in your installer options - have you tried de-selecting this and see if it installer builds correctly? If it does, then we could then work on how to add the additional installer to your build.
Message Edited by Hillman on 04-01-2009 10:01 AM
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Build Installer LV8.0 - is this real??

Hi all
I recently received LV8.0. After playing around and test some new features, I wanted to start to bring all testrigs that run under LV to LV8.0. Therefore I chose one of them, made a LV-project, modified the source code, created a application build script and an installer build script. I run the application build script without any problems. OK - everything's fine up to now. But as I wanted to create an installer, it obviously just creates a lot of "nonsense".
I checked some additional installers (Datasocket, LV8.0 runtime engine, MAX 4.0, Fieldpoint, Scope and VISA) to make just one Installer, which would be very nice to handle. When checking NI Datasocket, I saw in the distribution title on the right side (see attachment) LabVIEW 8.0 Real-Time Module. Why???? There is no need to include the rt-module, as I don't use it.
I thought "ok, maybe a wrong string displayed - let's create the installer" and run the build script. While running it asked me for the device driver cd's (ok - could be logical) and out of a sudden it also asked me for the cd of the LV realtime module. Well - I inserted it an continued the build.
In the end I got a directory structure (Volume/bin/lotsOf"pXX") with a size around 650 MB - for a simple application of approximatly 10MB.
When I browse some of these "pXX" directories I discover subdirectories like "p14/LV711RTE", "p15/LVBrokerAux71" and lots of different msi-files (for instance "NIRegistrationWizard.msi" - but why?).
Is there anyone out there who can help me quickly?
Thomas
Using LV8.0
Don't be afraid to rate a good answer...
Attachments:
Installer.JPG ‏167 KB

Thomas,
Thanks, I too have been waiting for us to have the ability to build installers that include all the drivers and related software you need. There was a lot of work that went into it by a team of people here at NI. Their work is being used in LabVIEW, CVI and TestStand now for generating such installers. I'll pass along your complements to the people involved.
So you unchecked DataSocket yet your DataSocket communications are still working? I think that might be due to DataSocket being included through one of the other installers. When you check an item we'll include all the dependencies that you need. Most of the time those dependencies don't show up in the list of additional installers, because they are lower level drivers and software you don't interact with directly and don't need to know about. Some of the items that are dependencies for other installers do appear in the list such as DataSocket, LabVIEW Run-Time Engine and MAX. FieldPoint for instance is dependent on MAX and will include it if you are including FieldPoint. If you check MAX too, the Installer Builder will only include one copy of MAX. I'm not sure which of the other items is dependent on DataSocket but it could be getting included that way. Another possibility is some older LabVIEW Run-Time Engines are being included in your installer because of MAX and they include an older version of DataSocket as part of their installer not as a dependency so it could get included that way, but that would be an older version of DataSocket and not what you are using on your development machine. Since you know you are using DataSocket I recommend checking it, so you know the version you are using will get included.
When you uninstalled LabVIEW Real-Time, the core portion of LabVIEW Real-Time was removed, however any dependencies it had that are also a dependency of another NI Installer would not be removed. As I mentioned earlier LabVIEW 8.0 installed DataSocket and the Real-Time Installer upgraded it. The installers have the necessary logic to know that just because RT installed a newer DataSocket we cannot remove it with RT because LabVIEW depends on it as well. When you ran the RT installer the progress bar probably showed installing part X of Y, and when you uninstalled it there was also a progress bar that showed removing part X of Z. Where Z is a smaller number than Y because some dependencies of other products were updated and they can't be removed until all the installers that need them are removed.
So the next question is "I want to rebuild this installer without having to put the CD in. How can I do that?" The ideal answer would be for us to have a check box on the dialog when you are prompted for the distribution that says something about copying the necessary files to your hard drive and you could choose to uncheck it. We didn't get around to putting that in for LabVIEW 8.0 but if you happen to use CVI you'll notice they have such a check box and as I said we use the same installer building technology so it wouldn't be unreasonable to see that in the future for LabVIEW . But what can you do right now?
One options would be to always copy your CDs over to the hard drive before you install them and leave the installers on your hard drive, that way the last place they were installed from was somewhere on you hard drive that can be found without user interaction. We don't do that by default since copying the LabVIEW CD(s)plus the driver CDs would really use up your free space. This is messy though because you have to uninstall everything and reinstall it.
Another option is to copy the distribution you are being prompted for (the entire disc) to your hard drive and then in the Installer Builder select NI DataSocket and change the Installer location path to the location you copied it to (the top level folder that has a nidist.id file in it). The press OK on the dialog, now the Installer Builder will look in that location for NI DataSocket, until a newer version is installed. We have had some problems with this mechanism not getting all the dependencies from the new location, so it isn't a 100% solution, but I just tried it for DataSocket and it worked.
The first option will catch 100% of the dependencies, where as the second option unfortunately won't.
Kennon

I can not create an Installer, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...

I can not create an Installer on LabView, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...
Solved!
Go to Solution.

Hi Shada this can happen if you are including additional installers to your installer for example DAQmx. When you are doing this the installer has to include other files like MAX (Measuremente and Automation Explorer). Probably when you installed Vision Builder it updated MAX, so when your installer is trying to Include MAX, its asking for the source where it was installed in your computer in this case Vision Builder.
Here you can cache the information so its not asked again, or you can download a newer version fo DAQmx, so it will update MAX and change de dependecy.
You can find more details about this issue in this KB:
KnowledgeBase 3S88PJMY: Why Do I Get A "Missing Distribution" Error When Trying to Build an Installe...
And for keeping a copy here is more info:
How Do I Stop the Missing Distribution Notification Each Time I Build An Installer?
Best Regards
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD

Runtime Error building Installer with NI-VISA Runtime

Greetings, I'm getting this error whenever I check the "NI-VISA Runtime" option in the installer app builder.
Everything builds fine when I check only the Runtime Engine. Shown below is what causes the RUNTIME ERROR and closes Labview Unexpectedly.
Any help you could provide would be very much appreciated.
Regards,
JD

Hi JD,
This is a relatively common error with the Application Builder that can happen for several different reasons, namely registry keys pointing to installations that no longer exist. The easiest way to identify the problem is to get detailed information about the installer build. Here are directions:
LabVIEW has the
ability to create a very detailed log of the events that occur when
building an application or installer. To enable this feature, open up
the LabVIEW.ini file and copy "CDK.EnableLog=true" to the bottom
of the file. Save the changes and close the ini file. The LabVIEW.ini
file is usually located in C:\Program Files\National
Instruments\LabVIEW X.X
Enabling this feature will create a log file in the %temp% directory of your computer (%...% means a computer variable) .
To
find out where this temp directory is located, go to Start>>Run.
Type in "cmd". Then type "set". This will return all of your computer's
variable names.
Look for TEMP in the list of variable names. You should see something like "TEMP=C:\DOCUME~1\user\LOCALS~1\Temp".
Navigate to this directory using Windows Explorer.
You
should see a file named "Name.log" where "name" is the name of your
build specification. For example, you might see "My Installer.log" if
the name of your build specification is "My Installer".
This will give you a more detailed log of the attempted build and, if I'm correct about why this particular build failed, show you which installer is expected at that registry. If the registry points to a directory without the necessary installer (i.e. VISA), simply delete the registry and allow the App Builder to prompt you to to point to the correct location.
Michael K.
| Michael K | Project Manager | LabVIEW R&D | National Instruments |

Prompt_Missing_Products dialog when building installer

Similar Messages

Maybe you are looking for