App Builder Installer Build Registry Keys no longer created in Vista.

This board has been a great resource for answers...thank you all for your help.
Last week (7/31/09), an automatic MS Windows Vista Home Premium
upgrade was performed on my development PC. After the upgrade, I
used AppBuilder to build the final version of my application, which writes
3 string keys to the Window's registry. The Installer build completed successfully,
however, when I run setup.exe, I received an OS error stating that I don't
have permission to update the registry. I have full admin rights AND
User Account Control (UCS) is OFF. This error notification occurred 3
times, once for each registry addition attempt.
The installation was working correctly prior to this Vista update and still works in XP.
Any help would be greatly appreciated!
Please note that this is VI independent- the registry keys were created through
the AppBuilder 'Installer' tool.
I worry that this problem will manifest itself with all new LV application installations
that have the Vista upgrade.

Does the installation fail only when you try to install on computers that have the Vista update? Or since you have updated your development computer, when you build the installer again the installation will fail on any computer? Have you tried installing it on more than one computer with the Vista update?
Please attach the installer log for when the installation fails.
http://digital.ni.com/public.nsf/allkb/AB597E885DB7D16B86256E92006DB232?OpenDocument
Cheers,
David Goldberg
National Instruments
Software R&D

Similar Messages

SCCM 2012 Installation Directory Registry Key chaning automatically to Old Installation Path

Hi Guys,
I have recently recovered SCCM 2012 SP1 CAS Site from Primary Site by reinstalling CAS site and database was replicating with Primary sites properly after CAS recovery. But we noticed that after approx. 2 hours of CAS site recovery database replication stopped.
After long digging into SCCM log files we found that SCCM installation directory was pointing to old CAS Site Installation Directory (Which was before recovery) instead of NEW Installation Directory so we changed SCCM CAS Site Installation Directory manually
to new installation path in below registry key and everything was running fine again on CAS Site.
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Identification
But again when we restarted SMS_EXEUTIVE Service, SCCM Installation Directory again changed to old installation patch under above registry location and all is bad again. We are unable to figure out what is causing this and even we formatted our HDD before
installation CAS Site.
Can anyone please help to get rid of this issue. Our while CAS site is down due to this issue.
Thanks.

I think that you have to use the same installation directory in a site recovery scenario.
Torsten Meringer | http://www.mssccmfaq.de

USB/Serial Drivers and App Builder Installer Questions...are drivers included in the Installer with the LV runtime engine?

Hello all,
I'm wondering if someone can help me out with how drivers and all are treated with applications distributed with App Builder, used to create a stand alone, full install of app and labview engine with Installer.
What has happened is, my application was created using the NI branded USB to RS232...and USB to RS485, and they work great.
On the application when running..you fire it up, it finds the USB to serial device, and I have a dropdown that finds the available COM ports to use (along with setting parity, etc).
I've installed on different computers (without previous labview installs) with the installer. They all worked.
The customer has received the installer....and despite us telling them to use the NI branded USB/Serial interfaces..they are trying to work with a different USB/serial cable.
They say the COM ports aren't even showing up when they run the installed application.
So, I'm not sure where to start. Is this a driver issue? Does the App Builder Installer...install the drivers for the interfaces I was using with it? Is there a way for the person to find and install a driver on their own...or would I have to somehow find out a driver for what they use....then, basically redo the App Builder Installer build...to include that driver with the executable I send back out?
I guess I basically need a better understanding of how drivers for external access/communications are handled when you use App Builder to create a stand alone application complete with the labview runtime engine...and nothing else.
Thank you in advance,
cayenne

The main thing is that LV uses VISA to talk to serial port whether native on the machine or from USB dongles that you plug into the computer. It sounds to me like their dongles aren't working.
Can the customer see the ports in the Windows Device Manager? Can they access them through something like hyperterminal? How does your program find the USB/Serial devices?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

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 |

8.6.1 installer build

I have a problem with the installer build in 8.6.1. The short story - I build an executable and then an installer. In the installer I have the 8.6.1 Runtime checked on the Additional Installers page. Every thing is OK (except it prompts me for my disk for something in the 8.6.1 distribution, but that works OK and the build continues). I can modify the application, rebuild the exe, and then rebuild the installer - all OK so far. Now, I exit LabVIEW and install the application on my development machine - I do this to try and see if I have any obvious problems with the application or installer (like missing VIs for dynamic calls or config files) before I take it to the lab. This also works OK. Now, I see something that needs modification. I open LabVIEW, modify the VI that needs it, save, rebuild the application, and then try to rebuild the installer. Only now, the installer opens the Locate Distribution dialog and insists that "LabVIEW needs to copy a component installed or updated by the distribution" and it's pointing to the distribution (my installer) that I am trying to build. This circular dependency can't be resolved and the build fails. Here's some excerpts from the build log
Getting distribution information for NI LabVIEW Run-Time Engine 8.6.1
     This product is cached. Skipping.
Getting distribution information for NI MetaUninstaller
     This product is cached. Skipping.
Getting distribution information for MDF Support
     This product is cached. Skipping.
Getting distribution information for NI Service Locator
     This product is cached. Skipping.
Getting distribution information for Math Kernel Libraries
     This product is cached. Skipping.
Getting distribution information for NI_Logos_5.0
     Product is in volume 1 of distribution with id '{CB09ABD9-FCCC-43BC-B4E1-9DDA6EB98ADB}'
     Product is in volume 1 of distribution with id '{FA21606E-6B91-43A2-83DE-199D5045AE5F}'
     Adding distribution 'LabVIEW 8.6.1'
     Path: D:\Distributions\LabVIEW\LabVIEW861\
Loading distribution information from path: D:\Distributions\LabVIEW\LabVIEW861\
     Product is in volume 1 of distribution with id '{FDAAAF1C-1FFC-4C29-A472-27A929FC8489}'
Getting distribution information for NI TDM Streaming 1.2
     This product is cached. Skipping.
Complete list of distributions and products to copy:
     (0) LabVIEW 8.6.1, Disk 1
          Id: {FA21606E-6B91-43A2-83DE-199D5045AE5F} Volume: 1
          Path: D:\Distributions\LabVIEW\LabVIEW861\
          Products:
          (0) NI_Logos_5.0
               Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936} Flavor: 'Full'
               Path: Products\NI_Logos\
     (1) MA231 Tester
          Id: {CB09ABD9-FCCC-43BC-B4E1-9DDA6EB98ADB} Volume: 1
          Path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
          Products:
          (0) NI_Logos_5.0
               Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936} Flavor: 'Full'
               Path: bin\p9\
     (2) MA231 Tester
          Id: {FDAAAF1C-1FFC-4C29-A472-27A929FC8489} Volume: 1
          Path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
          Products:
          (0) NI_Logos_5.0
               Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936} Flavor: 'Full'
               Path: bin\p9\
And then,
> The source directory for "MA231 Tester" is invalid because it is at the same location as the deployment destination directory (source = "C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\", destination = "C:\MA231 Tester\Software\Builds\MA231 Tester Installer\").
<<<MDFDistCopyList_GetItemInfo>>> Returning info for distribution 1
     Last known path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
     Distribution title: MA231 Tester
I can only fix this by uninstalling my application AND going into the registry and deleting the first entry with the GUID under the NI_Logos_5.0 (which refer to my application) - these entries are in the registry under "HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\Distributions\" - where there are also registry entries for every app I've ever built and installed with LabVIEW - all 300 something. Obviously, the uninstall doesn't do much in cleaning up these things.
So, anybody have any good ideas what to do? OR at least an explanation? I'm leaving soon today and won't have access to email again until Tuesday, 30 June, so if you post and I don't respond immediately please understand that I'm not ignoring the thread.
Thanks,
Mark
This has also been opened as Service Request 7249245

I have a problem with the installer build in 8.6.1. The short story - I build an executable and then an installer. In the installer I have the 8.6.1 Runtime checked on the Additional Installers page. Every thing is OK (except it prompts me for my disk for something in the 8.6.1 distribution, but that works OK and the build continues). I can modify the application, rebuild the exe, and then rebuild the installer - all OK so far. Now, I exit LabVIEW and install the application on my development machine - I do this to try and see if I have any obvious problems with the application or installer (like missing VIs for dynamic calls or config files) before I take it to the lab. This also works OK. Now, I see something that needs modification. I open LabVIEW, modify the VI that needs it, save, rebuild the application, and then try to rebuild the installer. Only now, the installer opens the Locate Distribution dialog and insists that "LabVIEW needs to copy a component installed or updated by the distribution" and it's pointing to the distribution (my installer) that I am trying to build. This circular dependency can't be resolved and the build fails. Here's some excerpts from the build log
Getting distribution information for NI LabVIEW Run-Time Engine 8.6.1
     This product is cached. Skipping.
Getting distribution information for NI MetaUninstaller
     This product is cached. Skipping.
Getting distribution information for MDF Support
     This product is cached. Skipping.
Getting distribution information for NI Service Locator
     This product is cached. Skipping.
Getting distribution information for Math Kernel Libraries
     This product is cached. Skipping.
Getting distribution information for NI_Logos_5.0
     Product is in volume 1 of distribution with id '{CB09ABD9-FCCC-43BC-B4E1-9DDA6EB98ADB}'
     Product is in volume 1 of distribution with id '{FA21606E-6B91-43A2-83DE-199D5045AE5F}'
     Adding distribution 'LabVIEW 8.6.1'
     Path: D:\Distributions\LabVIEW\LabVIEW861\
Loading distribution information from path: D:\Distributions\LabVIEW\LabVIEW861\
     Product is in volume 1 of distribution with id '{FDAAAF1C-1FFC-4C29-A472-27A929FC8489}'
Getting distribution information for NI TDM Streaming 1.2
     This product is cached. Skipping.
Complete list of distributions and products to copy:
     (0) LabVIEW 8.6.1, Disk 1
          Id: {FA21606E-6B91-43A2-83DE-199D5045AE5F} Volume: 1
          Path: D:\Distributions\LabVIEW\LabVIEW861\
          Products:
          (0) NI_Logos_5.0
               Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936} Flavor: 'Full'
               Path: Products\NI_Logos\
     (1) MA231 Tester
          Id: {CB09ABD9-FCCC-43BC-B4E1-9DDA6EB98ADB} Volume: 1
          Path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
          Products:
          (0) NI_Logos_5.0
               Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936} Flavor: 'Full'
               Path: bin\p9\
     (2) MA231 Tester
          Id: {FDAAAF1C-1FFC-4C29-A472-27A929FC8489} Volume: 1
          Path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
          Products:
          (0) NI_Logos_5.0
               Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936} Flavor: 'Full'
               Path: bin\p9\
And then,
> The source directory for "MA231 Tester" is invalid because it is at the same location as the deployment destination directory (source = "C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\", destination = "C:\MA231 Tester\Software\Builds\MA231 Tester Installer\").
<<<MDFDistCopyList_GetItemInfo>>> Returning info for distribution 1
     Last known path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
     Distribution title: MA231 Tester
I can only fix this by uninstalling my application AND going into the registry and deleting the first entry with the GUID under the NI_Logos_5.0 (which refer to my application) - these entries are in the registry under "HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\Distributions\" - where there are also registry entries for every app I've ever built and installed with LabVIEW - all 300 something. Obviously, the uninstall doesn't do much in cleaning up these things.
So, anybody have any good ideas what to do? OR at least an explanation? I'm leaving soon today and won't have access to email again until Tuesday, 30 June, so if you post and I don't respond immediately please understand that I'm not ignoring the thread.
Thanks,
Mark
This has also been opened as Service Request 7249245

Error-33 building installer

I am done with a project and I am trying to build an installer for it. I have not been successful. I have all the files needed inside the project. I tested it and run the main Vis and there's no error. But when Im trying to build the installer, I select my source files and se the Additional installers to automatic selection I get this error each time:
Forgive me if it's too long! can someone explain to me what that means.
CDK_CreateNewWizard_Invoke.vi.ProxyCaller >> CDK_CreateNewWizard_Invoke.vi >> AB_CreateNewWizard_Invoke_CORE.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
*** Error: Input data from a source data file has errors. (Error code -33)
Error Details:
Error loading source distribution info for product 'NI .NET Framework 2.0 Language Pack x86 Installer' from registry.
Error in MDF:istributionSourceCollection::LoadProductSourceFromNISysInfo
Could not extrapolate product location on distribution because paths do not match
Path of part on distribution: Products\DotNet20langpack_x86_Installer\DotNet20x86langpack.msi
Path of part in product: DotNet20x86langpack\DotNet20x86langpack.msi
*** End Error Report
*** WARNING ***
Ignoring 'NI .NET Framework 2.0 Language Pack x86 Installer' because there is an error in this product's installation data. Updating, repairing, or reinstalling the product may resolve this issue.
*** Error: Input data from a source data file has errors. (Error code -33)
Error Details:
Error loading source distribution info for product 'NI .NET Framework 2.0 Language Pack x86 Installer' from registry.
Error in MDF:istributionSourceCollection::LoadProductSourceFromNISysInfo
Could not extrapolate product location on distribution because paths do not match
Path of part on distribution: Products\DotNet20langpack_x86_Installer\DotNet20x86langpack.msi
Path of part in product: DotNet20x86langpack\DotNet20x86langpack.msi
*** End Error Report
*** WARNING ***
Ignoring 'NI .NET Framework 2.0 Language Pack x86 Installer' because there is an error in this product's installation data. Updating, repairing, or reinstalling the product may resolve this issue.
*** Error: Input data from a source data file has errors. (Error code -33)
Error Details:
Error loading source distribution info for product 'NI .NET Framework 2.0 Language Pack x86 Installer' from registry.
Error in MDF:istributionSourceCollection::LoadProductSourceFromNISysInfo
Could not extrapolate product location on distribution because paths do not match
Path of part on distribution: Products\DotNet20langpack_x86_Installer\DotNet20x86langpack.msi
Path of part in product: DotNet20x86langpack\DotNet20x86langpack.msi
*** End Error Report
*** WARNING ***
Ignoring 'NI .NET Framework 2.0 Language Pack x86 Installer' because there is an error in this product's installation data. Updating, repairing, or reinstalling the product may resolve this issue.
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
*** Error: Input data from a source data file has errors. (Error code -33)
Error Details:
Error in MDF API function: _MDFDistCopyList_CopyItem
Error in MDF:istributionSourceCollection::LoadDist
Could not extrapolate product location on distribution because paths do not match
Path of part on distribution: Products\LabVIEW_RT_TraceToolkit_Support_90\LabV90\RTETT_LV_90.msi
Path of part in product: LabVIEW_RT_TraceToolkit_Support_90\RTETT_LV_90.msi
*** End Error Report
Done building deployment

In regards to needing to put in the CDs, LabVIEW will ask you to do so unless you actually transfer the installers to your computer. When you install LabVIEW, it uses the installers on the CD to install to your machine. It won't copy the installer files to your computer by default, as this would waste several GBs of space. You would have to physically copy them from the disk or download them from ni.com/donwloads to get them on your desktop. (This is true for any program, which is why you need installation disks to install or build installers unless you have the installer files on your computer.)
In regards to the error, which XML file in the link I posted previously matched yours? Revision A or Revision B? Can you please post the precise error with Revision A replacing your XML file and the precise error with Revision B replacing your XML file? I would expect the file paths listed to be slightly different.
Could you also post the precise path of the "NI .NET Framework 2.0 Language Pack x86 Installer {F8ECD2D6-659C-49EB-8454-5F8F7B526FCF}.xml" file on your computer?
Regards,
David R
Applications Engineer
National Instruments

Labview 8.2 application builder - installer deletes previously installed programs

Problem Description :
I've been developing with LabView for 8+ years and recently had to upgrade from 6.1 to 8.2 because of compatibility issues with LabView, MAX, DAQ and SERIAL. LabView had always been so intuitive and efficient, but that has changed to some degree sometime after 6.1 IMO. I won't get further into that, but I am having several problems with Application Builder and particularly, with creating an Installer and installing test programs. I haven't seen many posts on this subject so I assume I am doing something wrong.
In 6.1, I could build a program and create an installer in minutes, and all in the same step - Click on Build and the installer was created. I could also locate my files anywhere I wanted. Unfortunately the process in 8.2 is no where as simple as one has to create a build and installer separately. So far, I haven't been able to distribute my installer files where I want them according to our internal procedures. The build portion works fine and I can locate my files as needed, but not so for the installer (at least I haven't figured it out yet). The main problem is that I have some common DLLs that I'd like to locate in a common directory for all of my programs, but it seems like I'm stuck putting them in the installation directory of every program that I write. Again, it is fine in build. There doesn't seem to be any flexibility in changing the location of the files in the installer. I did see a post somewhere that mentioned that DLL files must be located in the system directory if you don't want them included in the build or installation. I would just like to install the dlls to a common directory and not include them in every installation directory. Just like I did in LV 6.1!
This is a relatively minor problem compared to what happens when I try to install the programs.
I have five separate programs for which I have recently built and created installers with the limitations that I've described above. I can install one program on my machine and it runs properly. If I try to install any of the
other four, they will delete the previous installation - all the files are deleted (they all have different names). What I think is going on is that the installer thinks that these five programs are the same and simply overwrites the previous installation. One reason I believe this, is because I tried an installation and it failed with the error message that there was already a higher version installed. The higher version it was referring to was almost certainly the one program I could install, but certainly not a higher version of the one I was trying to install (it didn't exist yet). After I uninstalled the one program, I could install any other four. It doesn't matter if I install on the build computer or the target computer (ATE).
What am I doing wrong? Please help me to resolve this problem.
I wan't the build and install files in the same exact location:
Example of my five programs and the locations of build and install:
C:\KIK2-LabView\Customer Name\Base Part Number1\Program1.exe.......
C:\KIK2-LabView\Customer Name\Base Part Number2\Program2.exe.......
C:\KIK2-LabView\Customer Name\Base Part Number3\Program3.exe.......
C:\KIK2-LabView\Customer Name\Base Part Number4\Program4.exe.......
C:\KIK2-LabView\Customer Name\Base Part Number5\Program5.exe.......
The support files will also be put in the corresponding directories. The common files were supposed to go in the KIK2-LabView directory instead of copies in every installation directory.
Is there something I have to do with the registry? In 6.1 it was all automatic.
I hope there are simple answers to my problems, but I have yet to find them out. I have been able to find very little info on Application Builder, and nothing that is comprehensive.
Thanks!

Thank for the reply, Andy
I have scoured the Help files and this forum which helped me to create the build and installer, but they didn't address any of the problems that I described in my post. I tried to make sure that I exhausted numerous resources before posting and requesting help.
I appreciate the response, but you didn't quite get to my most important problem - that when I try to install a program from the created installer, it overwrites my previously installed program. Actually I have found the answer in a different thread. --->  http://forums.ni.com/ni/board/message?board.id=140&message.id=16146. My problem is that I cut and pasted all of my project files and made the appropriate changes specific to each new project. If you don't create brand new builds and installers in these projects, you will create duplicate registry keys, even though all of the names, numbers, files, etc. were changed to be completely unique. I opened the .lvproj file in notepad and found several registry keys to be the same; here is an example:
<Property Name="UpgradeCode" Type="Str">{831013BF-9112-45AA-BF13-A13F08098841}</Property>
All of the projects that I created by cut and paste (and edit) method had this same exact key (as well as other keys) which was causing the previous install to be deleted/overwritten or gave me the message that a higher version already existed.  Again, this happened even though all of the project data was completely unique after it was edited, including the project filename (of course). Finally, I completely rebuilt my projects from scratch starting with "New Project" and voila, they now all install properly. Obviously, none shared any of the same registry keys.
I don't know if this is something that was overlooked, but it is so much easier to cut, paste and edit projects when they are very similar.   Unfortunately I have found out the hard way that new build and install spec's must be created. Is there a change that can be made to the Project File in LabView so that when certain information changes (like the executable file name) that new registry keys will be generated? It is obvious that you don't want someone to accidentally install a lower version of the project over a newer one, but it would have prevented my work time loss (several days) and will prevent time loss for others in the future as well. Could you at least consider allowing the developer to generate new keys like was available in LabView 6.1?
Also concerning the location of files, I previously had done all of what you said and can locate the build files where I want. However, in the Installer (Source Files Tab), when I create the folders in [Windows Volume], all of the files from the build spec are put into the SAME directory, regardless of where they were located in the build spec. If I try to delete one file, all will be removed. I can't place individual files where I want them to go in the installer (if they are a part of the build). Example: In the installer, I created the subfolders KIK2-LabView\Customer\UUT Base Part Number on the [Windows Volume] directory and set the UUT Base Part Number as default. I want most of the files to go into the default directory, but a few of the dependent dll's should go into the KIK2-LabView folder as they are common to many other programs/projects. In short, I don't need or desire 50 copies of these dlls on my ATE. I was able to locate the installer files anywhere in LabView Pro 6.1, but so far I can't figure out if this is possible in 8.2. It would appear that it is not.
Thanks,
John W.

Make the data for a registry key point to the installation folder of my app.

I have an application that creates files with a unique file extension (.myextension). These files should be associated with a particular icon so that the icon is shown when they are viewed in Windows Explorer, etc. I know how to do this when I create an installer by adding several registry keys and values under the [HKEY_CLASSES_ROOT] key as shown below.
                   key                                                name              type                                   data
[HKEY_CLASSES_ROOT]
     .myextension                                         (Default)          REG_SZ               Myextension.file.type.record
     Myextension.file.type.record              (Default)          REG_SZ               Text description of file type
               DefaultIcon                                  (Default)          REG_SZ               path to the icon file.
The key for the file extension record (.myextension) has a default value where the data points to the key for the file type record (Myextension.file.type.record). The data for the default value of the Myextension.file.type.record key is just a description for the file type. There is also a subkey called DefaultIcon. The data for it's default value is the path to the file containing the icon that is to associated with the file type. If the file contains more than one icon, it may be necessary to modify the data (path) to indicate which icon to use.
So, this is all good if path to the file containing the icon is known. I added an icon file to the build when I built my application and it will be installed in a known location within the directory where my application is installed. The location is [InstallDirectory]data\myicon.ico, where [InstallDirectory] is the directory where my application is installed. The installation process, including the addition of registry keys is handled by an installer that I have created. The problem arises when the user choses to install to a location other than the default directory specified in the installer. I can't know before hand where that will be. How can I specify the path in the DefaultIcon key so that it points to the correct location after installation? Is there some symbol that I can use for the installation directory so that the path will be set correctly at installation time?

Hi cbfsystems,
If correctly understand what you are trying to do, check this out. This shows you how to add a user-specified install directory to a registry entry in the installer build spec.
Cheers,
Brian A.
National Instruments
Applications Engineer

Build installer error, help

Hi all,
There's a problem need your help.
I have a LV8.5 PDS. And I create a exe, when I want to create a installer, I cannot found any information is "additional installer". When I try to build it, error reports as below.
error information:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_PreBuild.vi >> CDK_Validate_DistParts.vi >> CDK_DistParts_GetInstalledProducts.vi >> NI_MDF.lvlib:MDFProdInfoList_Open.vi
Before I reinstall my notebook, it worked.
Thanks ahead.

From the forum
The build specification for your installer may have been corrupted. Try the following to correct this:
Open up your project in the Project Explorer window and expand the Build Specifications tree.
Right-click all of the applications (executables) build specifications that are included in your installer and select Build to force each one to rebuild.
If all the executables build successfully, next right-click your installer's build specification and select Properties to change its configuration.
In the Category pane on the left, navigate to the Source Files category.
Find your executable (.exe) files on the right side and click it to select it. Press the Delete key or click the red X at the bottom of the window to remove the executable and its associated files from the build.
Re-add the executable and its files to the same folder by selecting the executable in the Project View pane and the proper folder in the Destination View pane (on Windows systems, this is typically ProgramFilesFolder\[your product name]), and clicking the blue arrow button in the middle of the window.
Repeat steps 5 and 6 for any other executables you have in your installer, as well as for any other files which show up in the ProgramFilesFolder path.
Your installer should now build successfully. If that does not work, try making a new installer build specification which has all of the same settings as the build specification which does not work. If the new installer builds properly, you can keep it and delete the old, corrupted specification.

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

Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\120 registry key.

Dear Expert,
I setup SharePoint for 3 tiers, WFE, APP + DB Server.
I installed SQL 2014 reporting service Add-in on APP Server and already enable sql reporting service in DB Server. DB Server can do report server.
I follow the step : https://msdn.microsoft.com/en-us/library/jj219068(v=sql.120).aspx but I stuck in no.2, I cannot start the services, in picture below.
I checked the SSRS provision is disabled not online
Please help.

Hi MasterBird,
According to your description, when you register and start the Reporting Services SharePoint Service, the error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\120 registry key is thrown out.
As this
article say, if you use three-computer deployment, the first computer hosts an instance of a SharePoint product. The Reporting Services Add-in is installed on this computer. The second computer hosts SQL Server Reporting Services and the third computer
hosts an instance of the Database Engine.
Regarding the error message, it could cause by the Reporting Services – SharePoint feature and Reporting Services Add-in for SharePoint Products haven’t been installed. Please refer to articles:
SSRS SharePoint 2013 Create Service Application error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key Error
Installing SSRS 2012 in SharePoint Mode on SP2010
If issue persists, please check the error detailed information in ULS logs, and check Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log to see if any error occurred during set up. For more information, please refer to this article:
Troubleshoot a Reporting Services Installation.
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

Project "Installer Build Product version" vs exe version

Hi,
Can someone help me understand why the "Installer Build" in a project has a "product version", which later shows up in the Windows add/remove programs?
I must be missing something because to me it seems very strange that what they call "product version" in the installer is not automatically linked to the compiled exe version that the installer is built for?
Now I have to try and remember to manually keep these two versions synchronized, and the build 'product version' doesn't even have the same number of fields as the exe version information?!
It's strange when my program splash screen shows "V1.2.0.8" (read by the app by inspecting its own exe) but in the windows add/remove programs, it could say something totally different, such as 1.0.6...
Why is it like this?? How do other people use/handle these various version numbers? -is there a way for my app exe to find what the installed "product version" is?
---Confused...
-QFang
QFang
CLD LabVIEW 7.1 to 2013

QFang wrote:
I suppose it helps explain.. Perhaps I just need to think differently about how to name our installers.. Divorce the installer name from the (main) application name, then the difference in version numbers wouldn't be confusing.
Ideally the NI builder would be flexible enough that you could have a "Company Name" as the "installer name" and you could add/remove/maintain the whole company's product list with that same installer, similar to the NI installer.. sounds like a lot of work though.
Thanks for replying!
It does sound like a ton of work! I have to belive it is feasable with TKs like VIPM and Deploy on the market. (A few others I am less familliar with come to mind as well) Niether is exactly what you seem to want but demo that the tech is there!
Jeff

LV2010 SP1 Installer Build Issue- Cannot find the file it need on requesyed disk

I am migrating a project from LV8.6.1 to 2010SP1 and had issues building the installer that I was finally able to overcome, but something is amiss with the process.
Brand new development PC, running XP SP3, fresh install of LV2010SP Dev Suite and also installed VDM2010 SP1 (even though the project does not use any vision modules).
-          Copied 8.6.1 project to the PC, did a mass compile of it and built the exe from scratch without issues.
-          Now it’s time to build the installer from scratch. Additional Installers were:
LV2010 RTE, MAX 4.7, NI-DAQmx Full App Devel Support 9.2.3, and NI-VISA 5.03.
-          Get the message that it will need some disks to build it which I have on hand:
Dev Suite DVD#2, Drivers DVD, and VDM DVD (huh, why VDM?)
-          The installer build progresses through the first two disks fine but will not find the files it needs on the VDM DVD (it is looking for “NI System Components”).
-          Installer build bails out with a message box and no installer is created (1st attachment). The installer logs are also attached.
-          Try the build process gain, same result.
-          Copied the VDM DVD to my hard drive and point it to that folder to get the files, same result.
-          Try again saying I don’t have the disks on hand. It lists some alternate disks to use but to get all the files it still wants the VDM DVD to complete it. Not much use, the build still fails.
-          Try one last time again selecting that I don’t have the disks on hand. I now notice that the folder the VDM was copied to on the hard drive is an option to select. Select that one and lo and behold the installer is built successfully.
So I guess it boils down to:
            - Why does it need the VDM DVD when there are no components of vision used?
            - Why can’t the installer find the files it needs on the VDM DVD or a copy of the DVD on the hard drive?
            - Why will it only work if I choose that I do not have the disks and point it to a copy of the DVD that resides on the hard drive?
-AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
Attachments:
MessageDuringVDMCopyForInstaller2010.JPG ‏127 KB
TowersSPCv225Installer_build.log ‏3126 KB
TowersSPCv225Installer_edit.log ‏915 KB

Che:
It gave no specific indication of what it was looking for, the only message that came up was in the screenshot jpg I originally posted.
The only other vague clue I had was it needed NI System Component from the VDM DVD.
Does not make sense that it required the VDM DVD since there were no vision components in the project. I presume it would have taken VISA off of the Dev Suite DVD's.
I can't replicate the problem since I had the build cache the system components required for the project. I'd rather not start deleting folders at this point since I have a viable installer at this time (after many hours of troublshooting expended).
Thanks
-AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Project Build Installer Properties Slow to load, (Maximum vi size)

I have a LabVIEW Project with 450Mbytes of source code, and drivers. The Project was originality in LabVIEW 2009. I upgraded to LabVIEW 2011.
Now the Project Build > Installer Properties Menu is about 10x slower than was in LV 2009.
I've done a mass compile, resolved all error messages in the Project, yet 2011 is still 10x slower than 2009.
The 2011 Project will build an functional exe, and a functional installer given enough time (like 15 minutes). During that time the computer is locked up, no other applications are functional.
The Computer is XP, dual Core, 2.5GHz, 4Gbytes Ram, 4Gbyte Page File.
The NI Support Desk is saying (quote) >>>> seem that the requirements for LabVIEW 2011 are different than the requirements for LabVIEW 2009 <<<<<
Suggestions ???

Does the procedure take 30 minutes or 15 minutes (first post)? Also, what is it about the installer build spec that requires further modification after you modify your exe build spec? If the exe is included in the installer, the installer build will automatically re-preview the included exe to get an updated list of files to include next time the installer is built. So unless you need to modify something about the installer spec and not the included source files, no edits would normally be required after changing your exe (or other included source files).
Keep in mind, the previewing of the exe will take about as long as it takes to build the exe -- it's computing a list of the files that would be built without actually creating the files. A data point of interest is how much longer it takes your exe to build, comparing 2009 to 2011. Does your exe take 10 times longer to build in 2011? Longer exe build times mean longer preview operations in Installer Builder.
Another thing to check is which distributions you're including on the Additional Installers page. Are more distributions being included in the 2011 build? Did the distributions change significantly in size since 2009?

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!

App Builder Installer Build Registry Keys no longer created in Vista.

Similar Messages

Maybe you are looking for