Installer build spec loses spec for exe to run after

I don't know why, but now & then the build spec for my application installer loses the setting in the Advanced tab to run a certain .exe after installing. The .exe to run after installing is created by a build spec in the same project (from LV source). Besides rebuilding that .exe (without changing the .exe's build spec, name, or location, just minor source code mods), nothing has changed in the project, but the installer's Advanced setting will suddenly be gone. What the heck?!
My project & source files are too large to attach.

Hi Meg,
I noticed this forum post and figured I would chime in here as well.
We have been working on this issue and are hoping to isolate the exact steps that cause the sporadic loss of the postbuild EXE setting. An initial suspicion was the EXE being moved or rebuilt to a different location. That being said, if anyone has run into this issue in the past and has any insight it would be appreciated, as this problem has not been consistently reproduced.
Thanks,
Matt
Product Owner - NI Community
National Instruments

Similar Messages

SERVIC~1.EXE Stays Running After PC Suite Exits

It's great that automatic start-up is now optional in PCS version 6.80.20, and that you can 'Exit' from the sys tray icon. But when I use Exit, it always leaves SERVIC~1.EXE running. Does this matter and is it a bug? (XP2 fully patched; Nokia 6021; Bluetooth).

In most cases and by default, the frmweb process will die approximately 15 minutes after receiving its last heartbeat from the client. This assumes the runtime is not in a hung or spinning state. My recommendation is the following:
1. Set networkRetries to 5 (in formsweb.cfg)
2. Set FORMS_TIMEOUT to 10 (in default.env)
3. Set HEARTBEAT to 5 (in formsweb.cfg)
Finally, be sure you are using a newer, certified JRE. For example 1.6.0_31.

Fix for Photoshop not running after install

Hi all,
I recently purchased Photoshop CC and tried to install it on my home built computer that has an SSD for the OS and an HDD for my installed programs. When I went to run Photoshop after I installed it, it gave me an error message saying that it could not find a good version of Adobe Application Manager, saying it was damaged or broken. After numerous attempts to fix the problem, an Adobe technical support team member named Arul copied the Adobe folder C:\Program Files (x86)\Common Files to my HDD E:\Program Files (x86)\Common Files. Following this Photoshop and Lightroom booted up without a hitch.
Hope this helps anyone with the same issue!@

Or at least a restart.  menu/About This Mac - what OS shows?

Freezes when redirected on web & firefox32.exe still running after closing app

When a link leads to a "redirect" page, Mozilla freezes.
Dell laptop w/ Win7 Home Premium
No crash reports exist although "Submit crash reports" is checked...
Thanks for any help.
Ed

Hai Erik,
That was execellent work done. But
I have not been able to use javaw properly.Can You Help me?
See,I have used javaw class name.Then Put all paths and command lines into a batch file.Then I ran the batch. Now If I click that batch file it runs. But How can we use javaw as like is done in the demo folder of jdk1.2.2. They have got jfc folder in which all jar files are double clickable and are executed directly. Now how Can I do that?
Thank you very much.
Pulin
[email protected]

Using firefox 7.0.1 in Win XP (SP3), firefox.exe still runs after I exit and I have to end this process in task manager in order to get Firefox to run again. Fix?

I tried exiting Firefox using the File|exit menu item or just killing the window and (of course) re-booting the computer to see if that fixes the problem. Is this perhaps an incompatibility between the latest version of Firefox and Windows XP? (I do not have a problem like this on my Win 7 Professional (SP1) machine.)

take a look:
https://support.mozilla.com/en-US/questions/882621
thank you

SQL Server 2008 R2 Installation Media Root Directory location for XP SP3?

Where is the SQL Server 2008 R2 Installation Media director? This question asks during a 'new installation or add features to an existing installation'. The installation media root directory is not indicated under 'options'. I trying side-by-side
installation next to SQL Server 2008 Express Edition.
It appears that C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2 (where 1033_ENU_LP, Resources, and x86 dirs are installed) is the installation media root directory, but is is not a valid folder.
Also tried copying the 1033_ENU_LP, Resources, and x86 dirs from the C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2 into a directory that I created in c:\2008R2installationDir, and then running setup.exe, but still do not have
an installation media root dir specified under options.

There is no DVD; SQLServer2008R2SP2-KB2630458-x86-ENU.exe was downloaded. This problem occurs when setup.exe is run, after running *ENU.exe to download the files. Specifying the directory where the
SQLServer2008R2SP2-KB2630458-x86-ENU.exe doesn't help.
>>It doesn't seem like any instances have been installed, yet. Nothing shows up under Administrative Toos | Services. Under Start | Microsoft SQL Server 2008 R2 , there are two choices: Configuration Tools and Documentation&Tutorials.
Hello,
What seems to me that you have downloaded SP2 for SQL server 2008 R2(SQLServer2008R2SP2-KB2630458-x86-ENU.exe ).And as you say you dont find any thing under SQL 2008 r2.So i guess that is why SP2 installation is not moving
ahead.Can you download SQL server 208 R2 setup again and install database engine and ither fetures with client tools.And then you can move ahead with SP2 installation
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

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

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

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

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

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.

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.

I am not able to install adobe flash builder plugin 4.7 for myEclipse blue edition 2014

I am not able to install adobe flash builder plugin 4.7 for myeclipse blue edition 2014. Both are 64 bit and I have successfully installed adobe flash builder 4.7 and myEclipse blue edition 2014. Now the problem is not able to install the Adobe Flash Builder 4.7 Plug-in Utility.exe, while installing it asked for drop-ins folder after selecting that, it is saying the selected folder not contained Eclipse instance.

You don't have service pack 3 most likely. Refer to the tech specs:
http://www.adobe.com/products/flash-builder/tech-specs.html
Mylenium

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

Make the installer for my executable run the DAqcarddriver and runtime engine installer automatically

*Hi
I would like to know how to make the installer for my executable run the DAqcarddriver and runtime engine installer automatically
I would like to include run time engine and the drivers of my daqcard(AI16XE50),( and maybe Ni daq or anything else needed?) in order to make my application portable for other computers on OS win98 and winXP .
How can I do that
thank you in advance
Olivier

Olivier,
What version of LabVIEW are you using to build your application? On a remote computer you should only need the drivers you are using and the Run-Time Engine. You can attach installers to LabVIEW 8 installers, but for previous versions you will have to add it by opening the installer configuration page, configuring your installer and then configure the Advanced properties. This will allow you to attach a EXE to the installer which you can run. Also depending on the version of LabVIEW will affect the OS version that you will be able to install the RTE on. LabVIEW 7.0 is the last version that can be installed on Windows 98.
Please let me know if you have any further questions and please include the version of LabVIEW you are using. Thanks!
Andy F.
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 spec loses spec for exe to run after

Similar Messages

Maybe you are looking for