Installer build issue LV2010

Hello All,
After installing DAQmx 9.8 with my LV2010 installation I can no longer build an installer, I can however build an executable.  I removed LV2010 but not everything unfortunatly and reinstalled LV2010 with original device drivers distrubution DVD on my PXI-1042Q with a PXI-8106 Win7 64bit controller and still get the identical "Build Errors" message:
I loaded the _edit.log file and searched for "Edit code -30" and there is not and error in the log as per instructions from this link:
http://digital.ni.com/public.nsf/websearch/8E5E6C58C625B88A8625786A005B21E0?OpenDocument
Any ideas?  PLEASE SEE ERROR LOG BELOW
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> AB_UI_FRAMEWORK.vi >> AB_UI_Frmwk_Installer.lvclass:Build.vi >> Installer.lvclass:Build_from_Wizard.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> NI_MDF.lvlib:MDFConfig_SetDistributionLanguage.vi
Loading product deployment information
*** Error: Improper function call or command line argument. (Error code -30)
*** Error Details:
Error in MDF API function: _MDFConfig_SetDistributionLanguage
The MDF does not have support for distribution language LANGID 9.
*** End Error Report

It sounds like you re-installed LabVIEW 2010 after DAQmx was installed on your computer. This can cause errors.
You may want to make sure you install DAQmx drivers after your LabVIEW 2010. (Re-install DAQmx)
Mark P.
Applications Engineer
National Instruments
www.ni.com/support

Similar Messages

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

  • Labview 2012 Installer builder issues with Windows 7 64 bit

    I have a clients project application program I am working on and am having a lot of trouble getting installed applications to work on Windows 7 properly. The Labview Installer sets the default installation directory to "c:\Program Files\" on Windows Xp and on Windows 7 64bit this defaults to "C:\Program Files (x86). When I install the application on Windows 7 and run it, because Windows 7 64 bit unreasonably protects this directory and every folder under it, if you try to write file to any subdirectory under it (like a reports directory), windows 7 will not let the file write to the directory and the file(s) disappear and you get permission errors. This has been difficult to address. Even logging in as administrator, I have difficulty changing the folder permissions. In addition, when I am in the file write process, if the default directory is coded to come up in the file Open/Save dialog, will not properly
    go to and display these protected directories. So thinking that OK, I'll just chage the install directory to something direct to the C: drive and not the Program Files (x86) directory, so I have better control of the folder permissions. Now the Installer build gives errors. It built, but the install fails. Looks like National did not test this for Windows 7 very well. I have run into just about every issue possible with Windows 7 and Labview. Clearly Labview was not very well tested with Windows 7 6 bit. I do not have the Internet toolkit added to the application, only the VISA 5.2 driver. Anyone else having application issues with Labview and Windows 7 and have ideas how to work around this?? 
    Attachments:
    BuildErrors.txt ‏11 KB

    It's no NI's fault and has nothing to do with 64 Bit either. It is something MS changed starting with Vista, namely tightening security of the whole system to a similar level as was usual on more professional OSes like Unix 20 years earlier. A user has not rights anymore to write into the location where applications are installed. This is for one reason to protect installed applications from being modified by malicious code.
    Instead every application should write its runtime data in one of the user writable loacations such as the user's Documents directory for data files, or in the user's or the machine's configuration directory for configuration settings. For single installations you could always set the directory which your application got installed into to be user writable by changing the rights of that directory afterwards but for applications that get installed on normal user computers this is a VERY hacky and discouraged move. Same about installing your application into the root of your system drive. I think it was an oversight by MS to not protect that directory too from user modifications, but was most likely unavoidable to allow DOS application installations to still work.
    LabVIEW has functions to retrieve a whole bunch of those preconfigured and user writeable locations and you really should change your application to make use of those locations, instead of trying to write into the installation directory or installing the application into the root location of the system drive, if you want to be compatible with Windows Vista/7/8.
    Windows 7 also requires for a number of actions such as installing programs or drivers so called elevated rights. This means that even if you are logged in as administrator you have to explicitedly provide the admin password again to be able to perform the action. This can be done by starting the program as administrator, when this is available in the right click pop-up menu, and is also sometimes done automatically for applications that Windows determines to need those rights such as setup programs for installations.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Installer build error LV2010

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

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

  • Installer Build Error using LV Runtime Engine 2010

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

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

  • 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.

  • 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

    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.

  • LabVIEW 8.6.1 Installation Builder Crashes Windows 7

    Hello, my very helpful friends.  I have what I think to be a rather complicated issue and for which I've run out of ideas.  Recently, I had to go through the dreaded enterprise wide Windows 7 upgrade.  Upon completing that slog, I reinstalled LabVIEW 8.6.1 onto my machine by going to the distributions folder and installing each piece one at a time.  After completing this process, I opened a pre-existing project (stored on a separate server) which had some pending changes in a couple VIs which needed to be incorporated into the executable and installation builds.  The executable build worked without a hitch, but when I attempt to build the installation, I get most of the way through the build, but then it crashes Windows 7 via the blue screen once it gets to this point in the build:
    This is at the part where the progress bar stops proceeding for a minute or so.  I've tried deleting the installation and executable builds from the pre-existing project and recreating them, but that didn't work.  I've also tried completely reconstructing the project from scratch to no benefit either.  I've been able to succesffuly build both executables and installers in other projects since upgrading to Windows 7 so it seems particular to what's going on in this project.  The only other bit of information I can think of which might be useful is that every now and then, building the installer only crashes LabVIEW and not full Windows 7.
    Any ideas or suggestions are appreciated.  Thanks in advance!
    Andrew

    I never tried using this, but one of the options you could consider...
    http://windows.microsoft.com/en-us/windows7/install-and-use-windows-xp-mode-in-windows-7
    TailOfGon
    Certified LabVIEW Architect 2013

  • 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

  • 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

  • I am having an installation failure issue with my itunes 11 software.  File is corrupted and i don't know what to do.  I've un-install and re-installed the software three times and continue to get the same error message.  It states that "This copy of ITun

    I am having an installation failure issue with my itunes 11 software.  File is corrupted and i don't know what to do.  I've un-install and re-installed the software three times and continue to get the same error message.  It states that "This copy of ITunes is corrupted or is not installed correctly.  Please reinstall Itunes"
    iMac, iOS 6

    HI,
    If your old version of iTunes is still working - then I sugest you stick with that.
    iTunes 11 is a lousy update - It will not retain your playlists, you can't find and delete duplicates... and a whole arry of oyher issues. (have a look around this forum to see how many issues IT11 gives people)
    Just a friendly advise and warning :-)

  • AW: [Acrobat Installation & Update Issues] AW: [Acrobat Installation & Update Issues] Update von Acrobat 8.0 auf 8.3

    hello
    I say again that I have acquired the Acrobat 8.0 version honestly. I ordered this version even if a handler is Germany. This handler was registered on the website at Adobe as a handler. If you do not believe me, I'm looking for stuff from my archive. But this time I would like to have then paid by you. Again, it is known that the version 8 Without the update 8.3, constantly has errors. I used to simply confirmed the update button. Today there is no longer this site. You are obliged to provide me with the update. Or give me a free replacement to the next higher version. Please give me a link to a zip file that contains a setup file.
    Best Regards
    Werner
    Hallo
    Ich sage nochmals, dass ich die Acrobat 8.0 Version ehrlich erworben habe. Ich habe diese Version auch bei einem Handler ist Deutschland bestellt. Dieser Handler war auch auf der Webseite bei Adobe als Handler registriert. Wenn Sie mir nicht glauben, werde ich die Sachen aus meinem Archiv suchen. Diese Zeit möchte ich aber dann von Ihnen bezahlt haben. Nochmals, es ist bekannt, das die Version 8. Ohne das Update 8.3, ständig Fehler hat. Ich habe früher einfach das Update Button bestätigt. Heute gibt es diese Seite nicht mehr. Sie sind dazu verpflichtet, mir das Update zu liefern. Oder liefern Sie mir kostenlosen Ersatz auf die nächste Höhere Version. Bitte, Sie mir einen Link mit einer Zip-Datei, die eine Setup Datei beinhaltet.
    Best Regards
    Werner
    Mobil:   +41 (0) 79 559 83 21
    Skype:<skype:werner6331?call> Werner Göbel<skype:werner6331?call> (werner6331)
    Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Der Inhalt dieser E-Mail ist ausschließlich für den bezeichneten Adressaten bestimmt. Bitte beachten Sie in diesem Fall, dass jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser E-Mail UNZULÄSSIG ist. Wenn Sie nicht der richtige Adressat bzw. sein Vertreter sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Vielen Dank. Der Versender übernimmt keine Haftung für die Richtigkeit oder Vollständigkeit der Meldung. Eventuell entstandene Schäden die aus den Inhalten dieser Meldung resultieren werden vom Versender nicht übernommen.
    This e-mail may contain confidential and/or privileged information. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error), any form of disclosure, reproduction, distribution or any action taken or refrained from in reliance on it, is strictly PROHIBITED and may be unlawful. If you have received this transmission in error, please inform the sender immediately by e-mail at the above address and destroy this e-mail. Thank you.
    The sender does not accept liability for any errors or omissions in the contents of this message, which may arise as a result of e-mail transmission.
    Von: Rave
    Gesendet: Donnerstag, 28. August 2014 22:50
    An: Werner Göbel
    Betreff:  AW:  Update von Acrobat 8.0 auf 8.3
    AW:  Update von Acrobat 8.0 auf 8.3
    created by Rave<https://forums.adobe.com/people/Rave> in Acrobat Installation & Update Issues - View the full discussion<https://forums.adobe.com/message/6682731#6682731>
    < This thread has been answered a duplicate of Update von Acrobat 8.0 auf 8.3<https://forums.adobe.com/thread/1558776> >
    Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at https://forums.adobe.com/message/6682731#6682731
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
    To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Acrobat Installation & Update Issues by email<mailto:discussions-community-acrobat-installation_and_update_installation@adobe-v7.hosted.jivesoft ware.com> or at Adobe Community<https://forums.adobe.com/choose-container.jspa?contentType=1&containerType=14&container=47 14>
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

    Warum Sie antworten nicht auf meine Frage??
    Wie muss ich Instaliren??
    Beste Grüße
    Werner Göbel
    Mobil:     +41 (0) 79 559 83 21
    Skype:<skype:werner6331?call>  Werner Göbel<skype:werner6331?call> (werner6331)
    IGH Holding AG
    Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Der Inhalt dieser E-Mail ist ausschließlich für den bezeichneten Adressaten bestimmt. Bitte beachten Sie in diesem Fall, dass jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser E-Mail UNZULÄSSIG ist. Wenn Sie nicht der richtige Adressat bzw. sein Vertreter sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Vielen Dank. Der Versender übernimmt keine Haftung für die Richtigkeit oder Vollständigkeit der Meldung. Eventuell entstandene Schäden die aus den Inhalten dieser Meldung resultieren werden vom Versender nicht übernommen.
    This e-mail may contain confidential and/or privileged information. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient (or have received this e-mail in error), any form of disclosure, reproduction, distribution or any action taken or refrained from in reliance on it, is strictly PROHIBITED and may be unlawful. If you have received this transmission in error, please inform the sender immediately by e-mail at the above address and destroy this e-mail. Thank you.
    The sender does not accept liability for any errors or omissions in the contents of this message, which may arise as a result of e-mail transmission.
    Von: Bill@VT
    Gesendet: Sonntag, 31. August 2014 22:09
    An: Werner Göbel
    Betreff:  AW:  AW:  Update von Acrobat 8.0 auf 8.3
    AW:  AW:  Update von Acrobat 8.0 auf 8.3
    created by Bill@VT<https://forums.adobe.com/people/Bill%40VT> in Acrobat Installation & Update Issues - View the full discussion<https://forums.adobe.com/message/6689459#6689459>

  • Labview 8.5 installer build *.exe wrong date code

    In Labview 8.5 application installer build *.exe has a date code of 7/17/2007 even though it was built today.  It will not update even after deleting it.  Is this a known bug?  SS

    Hi SS,
    The Date Modified property of setup.exe shows the date the MetaInstaller was built.  This was true in earlier versions of LabVIEW as well.  It was reported to R&D (# 3T87DAP4) but was determined to be expected behavior.  The actual date and time the installer was built can be determined by looking at the properties of \bin\dp\install.msi.  Feedback is always appreciated, so please feel free to create a product suggestion if you think this should be changed. 
    Jennifer R.
    National Instruments
    Applications Engineer

  • Installer build: When run, error: Windows can't open this file xyz.vi

    Hello all, I've taken my vi. I"ve created it as an executable. I've taken that...and made an Installer project... This is with LV 2011, and installing to Win7. The installer seems to work fine...but when I try to run the application from the start menu, I get a windows error, saying it doesn't know what to do with my file xyz.vi...that it needs to know what application to open it with....? Any ideas what to do here? The installer seems to install the NI runtime engine just fine...? Would this be due to, on the Installer builder...setting the vi to be read-only and hidden? When I'd done this a previous time, I believe it all worked then... Suggestions? Thank you, cayenne
    Attachments:
    screen_shot_windows_error.jpg ‏35 KB

    Please disregard...I found the problem after going through the older working one....
    Late nights and working two jobs...you start to overlook things.
    FOr the dependency, I'd put the vi instead of the exe of the vi.....that did the trick.
    Thanks all,
    cayenne

Maybe you are looking for

  • Integration of SAP e-Recruiting 6.0 in Enterprise Portal 7

    Hi, I'm trying to integrate e-Recruiting functionalities into our Portal. The current situation: SAP e-Recruiting 6.0 is set up (integrated on ECC 6.0), and works fine when using the BSP-front-end. De ESS/MSS Business Packages are installed on the po

  • Error copying data from Goods Receipt PO to A/P Invoice

    Hi all, this seems like it should be a simple process. We get an error doing the following: - Open a blank A/P Invoice - Select the Vendor - Copy from Goods Receipt PO - Choose the items - Draw Document Wizard 'finish' The process aborts, and the sys

  • Insert Query in workbook

    Hi Can anyone of you please give me some information or any links explaning step by step procedure on: 1. How to copy a query 2. How to insert query in Workbook Many Thanks

  • Burn Error AFTER running ONYX

    Last week I had a problem when I tried to burn a DVD. I am in iDVD 4.0.1. I keep getting the message: "The Recording Device reported the error #8: No Additional Sense Information. (0X00, 0X00). I ran that ONYX program and I was able to burn my DVD. I

  • CLIENT_OLE2 - Attempting to insert additional rows into a table in MS Word

    I cannot find the commands to perform the above. I have looked at the Microsoft site but it only gives the VB equivalent and I cannot work out the syntax for CLIENT_OLE2 commands. Does anyone know where I can find a list of Word.Application commands