Scrambled destination view in installer build specifications LV8.5

I don't think this build specifications bug has been mentioned yet. I am using LV8.5 Pro under Win XP.
When configuring a new installer build specs, under Source Files, I select my application item in the Project View and click on the arrow button to add it to the Destination View. The latter then faithfully reproduces the application files hierarchy, for example:
Application Directory
    Manuals Directory
       Manual.pdf
    Application.exe
    Application.ini
    Startup.exe
    Startup.ini
However, after I close and reopen the installer properties, the Destination View hierarchy appears scrambled, for example:
Application Directory
    Manuals Directory
       Startup.ini
    Application.exe
    Application.ini
    Manual.pdf
Supporting files get moved around the directory tree, some disapper, and others actually appear in duplicate. The outcome is exactly the same every time I repeat this process, but there is no apparent pattern to it.
Now, when I actually build the installer and later use it, the application gets installed properly, with correct files hierarchy. What doesn't work are the shortcuts. For instance, in the above example, if I create a shortcut to Manual.pdf, it will actually point to Startup.exe. And if I need a shortcut to Startup.exe, I cannot create it because the target is not part of the Destination View.
Thoughts?

Dear Zador,
Bug number 4CM921LJ titled "Shortcuts Added in Installers Are Not Created Properly" is a LabVIEW 8.5 Known Issue. More information on the bug can be found in Knowledge Base 4EGEL6HY: Wrong or Incorrectly Disabled File Names Displayed in LabVIEW
8.5 Installer Builder. If you need an alternative to the workaround presented in the Knowledge
Base, you can create separate folders for each file you need to have a
shortcut created for instead of putting them all in one.
This issue has been fixed in LabVIEW 8.5.1. Please post back bug 4CM921LJ does not describe your problem.

Similar Messages

Build specification of installer hides already spec. destination

I have an installer build specification with the following problem with the "source files" dialog:
I select the exe build spec to be installed into a certain dest. dir (e.g. under program files). After doing so i close the dialog with ok. The next time i open the dialog this information seems to be gone, in the dest. view no folder has subfolders or other files below it. But if i repeat my steps from the first time, trying to install the exe into the same dir under program files, i get this error message:"The following files already exist in the destination directory:...". But i can't see them!
Any ideas?
This is Labview 2009 on Vista.
Holger

Perhaps they were written (somehow) as hidden files.
This way, if you browse to that location, you will not see them.
But if you try to save something with the same name, the computer will know the files are there.
Cory K

Build specification Destination Does Not Preserve Hierarchy

I have a destination configured in my build specification (application) so that I can include required LabVIEW and non-LabVIEW files in my builds. This destination is configured as a directory with "Preserve disk hierarchy" checked. Under "Source File Settings", I have one of the folders in my project configured to use the aforementioned destination.
There are two issues that occur when I build my application. The first is that it ignores empty folders entirely. The second is that I have one folder that contains files (this folder is a child of the folder that is listed in the build spec) and when I build, it completely ignores the child hierarchical step. I.e. It omits the child folder completely and put's the child folder's contents in the parent/top-most folder. E.g.:
Source:
source/ParentFolder/ChildFolder/file1.ext
source/ParentFolder/ChildFolder/file2.ext
Build Result:
builds/ParentFolder/file1.ext
builds/ParentFolder/file2.ext
If I put a dummy file (or another child folder with a dummy file) in "ParentFolder", it will then actually preserve the hierarchy of the files (empty folders are still ignored though). Note that the ParentFolder is "Always Included" under the build spec's "Source Files".
I need to be able to preserve the hierarchy without having to use a dummy file (this would be extremely confusing and could get deleted easily by future developers) or having to remove this hierarchical step in the folder structure (this code was inherited).
I'm using LabVIEW 2013 SP1.

Actually this has been discussed before -- a lot. The builder will not create an empty directory, and it only counts files as contents.
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

How can I configure a Build Specification to install for current user only

Is there any way I can configure an installer build specification to install my application to the current user's folder? This does not seem possible at first glance due to the limited "destinations" available.
Ideally I'd want the application to be placed in "C:\Users\[USERNAME]\AppData", or some equivilent where it'd be protected from being run by other users without administrative access.
Has anyone been able to do this? Thanks!
CLA, CCVID, Certified Instructor

There is a destination called [Personal] that goes to the user's MyDocuments folder. Whether program files should be mixed with a documents folder could be debated.
I see the [Public App Data] choice, but I don't see a [User App Data] option.
Another possibility would be to allow it to go to Public App Data, but after the installation, run a VI that then moves the program folder to the User's Application Data directory. However, that probably means updating shortcuts as well. And I don't know whether that VI would essentially step on itself in trying to do that move.
Maybe another choice would be to allow it to install to the program file directory, but use CACLS to prevent users from accessing that directory except for explicit permissions to the one or more users you want to allow to execute it. An advantage is it would allow one user to install a program for another user to use. The disadvantage is the person doing the installing would almost certainly have to be an administrator.
A disadvantage of the method you desire is that a user has to be the person logged in and install it for themselves (assuming that group policies allow non-admin users to install their own programs). Another disadvantage is if you want to have more than one permitted user, it would need to be installed multiple times, one for each.
Perhaps you could install security at the front end of your applicaiton. Anyone can run it, but the application determines if the currently logged in user is permitted to run it when comparing against some sort of encrypted file that lists valid users. If the user is permitted, the program moves onto normal operation. If not on the list, the program tells them so and never advances onto normal operation.
Perhaps someone else can determine if there is a path tagged within the installer builder that goes to the User App Data that I am missing.

Missing Build Specifications in LV8 Full Development package

After installing LV8 Full Development Version, the only Build Specification option available is "Source Distribution". The options "Application", "Installer", "Shared Library" and "Zip File" are missing. The correct serial number appears on the About screen so I assume I activated the package correctly.
How do I make those other build options available?

Buy the application builder - or upgrade to the professional version...
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

How do I include a dll in a build specification and/or installer?

I have a custom "wrapper" dll built with VC++ that I need to include in a LabVIEW Build Specification and/or LabVIEW Installer. It needs to be installed in the C:\Windows\System32 folder.

Good morning!
You can set your support files to install
in a separate directory than your executable. In the build
specifications for your EXE, select the Destinations category and change
the path for the Support Directory to C\WINDOWS\System32 as shown
below.
Then go the Source File Settings category and set your dll to install in the Support Directory, as shown below.
Let me know if this works!
Take care!
Tanya V
National Instruments
LabVIEW Platform Product Support Engineer

Build specification freezes when trying to view "Shared Variable Deployment" screen

Labview 2009 f3
For some strange reason, any applications that include shared variable libraries will no longer build into executables.
I was able to build these applications without issue a week ago. However, when I went to make an updated build today, the build failed and I had to force Labview to close. When I view the build specification properties, I can navigate through all the option screens except the "Shared Variable Deployment" screen. As soon as I click on that option, the interface freezes up and I have to force Labview to close.
This problem does not occur for applications that do not include shared variable libraries.
I tried removing the shared variable libraries from the applications that were failing, but that did not correct the issue.

I never did find a proper fix to this issue.
One day I attempted to build the application again, but this time I got distracted doing something else. When I finally checked the build status a few minutes later I expected it to still be frozen, but to my surprise I found that the application did successfully build. To this day, that particular application still looks like it is going to lock up, but about about 8 minutes later it finally takes off and builds like nothing was wrong...like every other shared variable application I have created. So I guess my only suggestion is to let the application sit for a while and see what happens.

Labview 2009 SP1 Installer build help needed

Hello,
First time posting here. I have a rather large project that I recently converted from Labview 7.0 to 9.0. I am able to build an executable and it starts up Ok but I don't know for sure if it works. Since I couldn't build an installer, I copied the folder containing the .exe onto the targeted machine and installed Labview Run-time Engine 2009 SP1. The executable then complains that it needs the full development version to work. I am not too worry about this part at the moment, but if you have any pointers, please go ahead and post them.
Ok, I have gone through a lot of posts on building and installer but it seems the one post that has something similar to what I experienced didn't get an answer. Here's the Build Errors from the pop-up dialog:
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_SetOtherProperties.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
*** Error: An internal tool or library returned an error. (Error code -21)
*** End Error Report
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
The build log file has slightly more info:
    [LOG ON] Mon May 31 20:55:07 2010
<<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
<<<MDFConfig_SetDistributionLanguage>>> Language id: 9
<<<MDFConfig_SetBuildDir>>> Build directory: C:\HardwareTest\XXX\Release\Installers\Lab Test Suite 4.2.9 Installer - XXX
<<<MDFConfig_SetBuildMode>>> Build mode: 1
    [NMDK BEGIN] Mon May 31 20:55:07 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] Mon May 31 20:55:07 2010
    [MDF END] Mon May 31 20:55:07 2010
     Closing MDF.
I realize that I should post my project file but I can't do that until tomorrow. From those 2 errors, can you tell me what the installer builder is looking for? I have gone through all my dependencies and they look Ok at the moment.
Thanks for you time.

Hi Celeb,
I had to help out on another project and finally only getting back to looking at this issue yesterday. As you suggested, I went ahead and created a new project and created new build specifications (exe and installer). I was able to properly build both items but won't be able to check out the executable til later this week.
I noticed one thing about the project that Labview produced after converting the old *.bld file to a project file.  With the converted project, Labview adds unexpected installer destination folders into WindowsFolder in the Installer/Source Files/Destination View. I thought I deleted them before but they seem to make it back (kinda hazy about this at this point).  My actual installer folder should only go into the WindowsVolume folder. Anyway, on the new build spec, since I don't manually add the installer folder into the WindowsFolder, nothing get populated there and the installer is able to build properly. This might have been the cause of my inability to build an installer with the converted project/build specs.
I hope NI could add in more details into the build error messages. As it is, it's really difficult to know why a build failed because there's no details in those messages.
Thanks again,
T.

Creating Builds Programmatically LV8.0.1

Salut.
From LV8.0.1 help :
QUOTE
Creating Builds Programmatically
You can use the BuildTargetBuildSpecification VI located in the vi.lib\AppBuilder directory to build source distributions programmatically from build specifications. If you have the Application Builder installed, you can use the VI to build stand-alone applications, shared libraries, Windows installers, and zip files programmatically. The VI is not available on the Functions palette.
Note The LabVIEW Professional Development System includes the Application Builder. If you use the LabVIEW Base Package or Full Development System, you can purchase the Application Builder separately by visiting the National Instruments Web site.
The BuildTargetBuildSpecification VI creates a build from a build specification that you specify in the Name of build specification input. If you do not specify a build specification, the VI creates builds from all build specifications in the specified LabVIEW project. You must specify the path and filename of the project to use in the Path to project input.
If you want the VI to create a build from a build specification located in a target that is not My Computer, specify a target in the Name of target input.
After you run the VI, you can view the path to the completed build files in the Generated files output.
END QUOTE
1-
QUOTE After you run the VI, you can view the path to the completed build files in the Generated files output.END QUOTE
Does someone know how to also get the created installer files? (i only get the exe output files)
2- How can i start the build status feedback window when using the BuildTargetBuildSpecification.vi?

Hi jacemdom,
I hope you're doing well. I have tested building an Installer specification on my end, and I am seeing the same results. The correctly passes in the appropriate build specification reference, but no files are actually generated as you have noticed. I am currently looking for more documentation for you on the BuildTargetBuildSpecification as it is a relatively new feature. Regarding the status window with this VI, it looks like that feature is currently unsupported. I will verify this an update you with what I find. Have a great day!
Thaison V
Applications Engineer
National Instruments

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.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Installer Build Requestion DAQmx 8.6

I am attemping to build an installer for an exe. The exe build was successful but when I try to build the installer it asks for "DAQmx 8.6, Disk 1" I have inserted the disk without any luck, the error doesn't state the specific file it is looking for. The installer builds successfully if I don't include DAQmx as an additional installer. I have also tried mass complie, creating a new project, fresh builds (exe and installer), and even repairing LabVIEW. I am using LV 8.5.1 and have DAQmx 8.7 on my machine. Is there anyway to tell the installer to use DAQmx 8.7 rather than 8.6?

Hi martym,
Have you seen this article?
Why Do I Get A "Missing Distribution" Error When Trying to Build an Installer from LabVIEW 8.0?
http://digital.ni.com/public.nsf/allkb/C3666BA408F81E59862570D20056E692?OpenDocument
My guess is that, when you include DAQmx 8.7, there is some shared component that hasn't been updated from DAQmx 8.6. Inserting the original 8.6 install disc should fix this, but it may be that you have had a different version of 8.6 (such as 8.6.0f6) on your system than on your disc (you can check the full version number in Measurement & Automation Explorer under the software tab).
I would recommend installing the latest version of DAQmx (8.7.1)
http://joule.ni.com/nidu/cds/view/p/id/965/lang/en
to see if that updates the component and fixes the problem. If not, please create a log when you try to build the installer and post it here by:
   1. Navigate to the C:\Program Files\National Instruments\LabVIEW 8.X directory.
   2. Open up the LabVIEW.ini file and copy the "CDK.EnableLog=true" text to the bottom of the file. Enabling this feature will cause a detailed debug log to be written to your temp directory.
   3. Save the changes and close the ini file.
   4. Attempt to build your installer
The debug log should be located in the %temp% directory of your computer (%...% means a computer variable). To determine where this temp directory is located, follow the steps below:
   1. Select Start » Run, type in "cmd" and then press OK.
   2. Type "set" in the command prompt. This will return all of your computer's variable names.
   3. Look for TEMP in the list of variable names. You should see something like "TEMP=C:\DOCUME~1\user\LOCALS~1\Temp".
   4. 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".
Eric V
National Instruments
Applications Engineer
Certified LabVIEW Associate Developer
"I'm a Ramblin' Wreck from Georgia Tech and a helluva (NI Applications) Engineer!"

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

Instrument Control Build Specifications

Dear Sir:
      I am trying to build a working *.exe instrument control program. This is a simple program which only queries my test instrument with a *IDN? command.
      The program fails to call my instrument driver and the program also runs on boot up when (running under normal conditions) it should wait for me to input the GPIB address of my test instrument.
      Let's begin with the failure of Labview to communicate with the instrument driver.   This is some background information.
       When I run the program as simple *.VI in the Labview environment, the program runs perfectly.    No issues.
       When I use Agilent Connection Expert or MAX to communicate to the test instrument, communication is established and there are no issues - I receive a reply, connectivity is established.
        After I build the *.VI into a *.EXE program, this is where the program's issues arise.
       The *.EXE program fails to initialize correctly and fails to establish connectivity with my test instrument.
        Here are some issues that I have noticed about the program running in *.EXE mode
1) The program runs on "boot up" when you click on the *.EXE program.   In *.VI mode, the program does not run on boot but waits for the user to input the GPIB address of the test instrument - program run is designed to be enabled by the user.
      I do not believe this is the source of the problem but only an incidental consequence of the problem.   If I stop the program and input the GPIB address, I receive a message about not being able to communicate to the driver.
2) Once the *.EXE program runs, there is a condition whereby the operating system cannot close the program and WINDOWS itself cannot shut down itself unless I manually close all the programs associated with the *.EXE program in the WINDOWS operating environment.
3) If the labview program and *.EXE program are closed but the operating system is still running, Agilent Connection Expert and MAX can no longer communicate with the test instrument.   They no longer see the test instrument.
It is obvious that the *.EXE program is making a change which is causing the operating system to "hang" on shutdown and is also preventing the other programs from operating as they should.
I believe the source of my problem may be how I programmed my build specifications.     In reply, can you please tell me what are the minimum requirements for the build specification so that my test instrument can reply to a simple *IDN? query?   What files are normally required for a successful build?
Other information as to the source of my issues are welcome as well.
Thank you.
Solved!
Go to Solution.

Thanks for you advice.
I think this problem is a lot easier than you might think.   I just started using Labview and the *.VI is super simple. I am away from my development computer right now so I can't post it.
The information I need to know right now are the typical files that are needed to be added in the build.
I found this quote that I found on a webpage to be interesting, (although I am not building an installer):
" Do I need to include NI-488.2 2.7.3 module if I use only basic GPIB Write.vi and GPIB Read.vis in my project?
Yes, if you are making an installer ..."
This is a link to the webpage:
http://forums.ni.com/t5/LabVIEW/Uninstalling-LabVIEW-after-an-application-EXE-build/td-p/1553310
My program involves only simple reads and writes using NI-488.2 calls to a test instrument.   A simple list of files specified with filename extensions to get me started would be appreciated.

Labview project build specification

I created a LabVIEW8 project. WIthin it I have a few folders that organize my code. I'm trying to create a Build Specification (found at the bottom of the project view). I created a new Build Spec and began populating it. I can add information to all fields, except the Source Files category. When in the Source Files category I'm able to specify the Dynamic VIs and Support VIs in the bottom box by selecting Full OI - Top Level VI.vi. However, when I try to select any single file (Launcher.vi in this case) as the Startup VI, all my VI files become grayed out. I can't select any of them. I tried placing my launcher file in a new folder (apart from the majority of my code). It allows me to move the folder into the Startup VIs area, but when I say 'OK' or 'Build' at the bottom, it comes back telling me that it can't continue because I haven't selected a Startup VI. Any ideas?

Have you tried saving the project and trying again. I tried to create one on the fly and it wouldn't allow me to select it as a top level VI until I saved the project and the VIs in the project. Give that a try and let us know how it goes.
Tyler H.
National Instruments

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.

Scrambled destination view in installer build specifications LV8.5

Similar Messages

Maybe you are looking for