03-16-2009 01:32 PM
Solved! Go to Solution.
03-16-2009 06:44 PM
It appears there was a report of this issue back in late 2007, but it was never reproduced. From the looks of it, somehow, a prerelease version of the LabVIEW 8.2.1 runtime engine may have found its way on to your system. Please search your registry (values and keys) under HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer for the code {B5171839-26E3-48D9-9FD6-AF7F39055146}. Under that same key, you should find a version number. It ought to be 8.2.379.0, but I'm guessing in your case it is 8.2.378.1.
What we want to do is remove the bad version of the LabVIEW 8.2.1 runtime engine from your system, then install the typical, released build in its place. The latter can be downloaded and installed from this location. As for getting rid of the bad version, you should first try to remove it via Add/Remove Programs. The other customer to report this issue did not see the LabVIEW 8.2.1 runtime engine in Add/Remove Programs, but was able to get their registry back in a consistent state by running the Windows Installer CleanUp Utility. I have not used this utility before, so I cannot necessarily make any endorsements.
Please let me know what you find, and if you have success reinstalling the LV 8.2.1 RTE.
Mert A.
National Instruments
03-17-2009 10:33 AM
Mert, I used the Windows Cleanup utility to remove the old LabVIEW RTE and installed the version downloaded from the NI website. I was then able to build and install my application.
I did not find a reference to version 8.2.378.1 in the registry. 8.2.379.0 was listed as the minimum version. I only searched for the first instance of {B5171839-26E3-48D9-9FD6-AF7F39055146}, however, so perhaps I missed something else. I also tried a build with the 8.2.1 RTE deselected (since I wasn't sure why I needed it for a CVI program), but this build failed with an internal error.
Thanks for the assistance.
03-17-2009 10:52 AM
After more investigation, I found that the 8.2.378.1 build came from a Circuit Design Suite distribution. If you were able to successfully install the 8.2.1 RTE from the web, I would expect you should not have any further problems related to this issue. If you do run into anything, do let us know. Sorry for the trouble.
Mert A.
National Instruments
10-08-2010 07:26 AM
Hi,
I am facing a similar issue. I tried the solution presented above and it didn't work - I had not performed a registry-cleanup though.
I then just uninstalled and reinstalled LV and voila, I could create working installers again. However after about 2 weeks (and after having created about 10 working installers of my project) I am confronted with the error message below again. The changes I had performed on my LV-installation meanwhile were:
1. To install NI-Visa 5.0.2., and I had not even done that when the error showed up for the first time (before the LV-reinstall).
2. To install NI-DAQmx 9.1, both times
The error did however not happen immediately after these updates. I did create at least one working installer with these installed.
If I perform the builds of the same project on another pc in the office the installer is valid – so I guess it can't be project that is causing this. That pc has NI-DAQmx 9.0.2 and NI-Visa 4.6.1 installed.
I now fear that this could come up every now and then, consuming a lot of time to fix each time.
.\Distribution.cpp(2106): IInstallerError 11004
Entwicklerfehler.
Distribution enhält ungültige Abhängigkeiten:
1. Product
NI-VISA GPIB-VXI (Legacy) Passport 5.0.2
({FAD4596A-05CA-4303-BABA-C507D93145A3}) depends on
product with upgrade code {8627993A-3F66-483C-A562-0D3BA3F267B1},
version [5.00.32768,), language in {}
which is
not in the distribution.
2. Product NI System Configuration
1.1.2 ({D0409C8F-7F01-41A0-B7B2-1031D766CE53}) depends on
product with upgrade code {8368F4A0-C37A-4787-BB7B-754FD92719A7},
version [4.70.49152,), language in {}
which is
not in the distribution.
3. Product NI System Configuration
1.1.2 for Windows 64-bit ({C0F23A48-E0CF-4A14-B3FF-E70D1E936DBF})
depends on
product with upgrade code
{8368F4A0-C37A-4787-BB7B-754FD92719A7},
version
[4.70.49152,), language in {}
which is not in
the distribution.
4. Product CAROBA 1.03c
({30A4A784-0567-40C1-BA7E-A2F5D50E2980}) depends on
product with upgrade code {8627993A-3F66-483C-A562-0D3BA3F267B1},
version [5.02.49154,), language in {}
which is
not in the distribution.
Distribution korrigieren und
erneut versuchen.
<No Debug Message>
10-08-2010 07:34 AM
Update:
After saving the projekt on the second pc I get the following error on the first one when trying to build, not later when trying to install. So nown I can't even produce invalid installers on my machine 😞
The message is in part german - but I think the essential parts are recognizeable.
The lines under ***WARNING*** translate to:
Product 'xxx' depends on a product which couldn't be found on this System. ID of missing Product: {yyy}
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
Informationen zur Distribution laden
Informationen zur Distribution laden
*** WARNING ***
Produkt 'NI Measurement & Automation Explorer 4.7' ist abhängig von einem Produkt, das auf dem System nicht gefunden werden kann. ID des fehlenden Produkts: {A1DD654C-E897-4C46-8077-12873C75D79D}
Produkt 'NI Measurement & Automation Explorer 4.7' ist abhängig von einem Produkt, das auf dem System nicht gefunden werden kann. ID des fehlenden Produkts: {11D580A9-CAA9-4FAE-ACCE-008751A7AE9F}
Dateien zum Installer hinzufügen
Hinzufügen von Dateien abgeschlossen
Erstellen der Distribution vorbereiten
Produkte von Distributionen kopieren
Software 'NI-DAQmx 9.1' von C:\National Instruments Downloads\NI-DAQmx\9.1\NIDAQ910-1\ nach \\Hal9000\TMP\CAROBA_TMP\TESTBUILD BOB - Löschen wenn fertig\ kopieren
Software 'NI-VISA 5.0.2' von C:\National Instruments Downloads\NI-VISA\5.0.2\ nach \\Hal9000\TMP\CAROBA_TMP\TESTBUILD BOB - Löschen wenn fertig\ kopieren
Distribution erstellen
Setup-Dateien kopieren
Informationen zur zusammengeführten Datenbank festlegen
Produktinformationen festlegen
Informationen zum Entwicklerteil festlegen
Letzten Build starten
Prüfen...
Kopiere Dateien...
Aktualisiere Dateien...
Gemeinsame Datenbank erstellen...
Installationsdateien erstellen...
**************
*** Fehler: Ein internes Werkzeug oder eine Bibliothek hat einen Fehler zurückgegeben. (Fehlercode -21)
Fehlermeldungen
ERROR: [rpcSetupLVRT.msi] has the same product code {52C3DD72-17E5-4E0D-83A8-FB42FCE3A8EF} as another part's product code. Make sure that the same part is not referenced in multiple PDFs.
**************
*** Fehlerdetails:
Error in MDF API function: _MDFBuildDist_Build
Error List
.\UberBuilder.cpp(1268): IInstallerError 108
ERROR: [rpcSetupLVRT.msi] has the same product code {52C3DD72-17E5-4E0D-83A8-FB42FCE3A8EF} as another part's product code. Make sure that the same part is not referenced in multiple PDFs.
<No Debug Message>
*** Ende des Fehlerprotokolls
**************
Erstellen der Distribution abgeschlossen
10-11-2010 03:57 AM
I have a similar problem, too!
I've builded the Installer (with LV2009 SP1) on a desktop wich has the following LabVIEW's installed:
- LabVIEW7.1
- LabVIEW 2009 SP1
- LabVIEW 2010
Building of the installer was sucessfull, the application is OK, too.
But while trying to install the package a dialogue appears with this message:
##############
.\Distribution.cpp(2106): IInstallerError 11004
Developer Error. Distribution contains invalid dependencies:
1. Product NI LabVIEW Run-Time Engine 2009 SP1 ({0AAB121C-8EA7-49F5-B37C-DF117FB46771}) depends on
product with upgrade code {5CE8DDCA-6BEE-4DA9-BD67-ABA516A727AF},
version [9.0.319.0,), language in {}
which is not in the distribution.
2. Product NI Logos 5.2.0 ({01CF3725-EE33-4308-BBF9-90BF6AC43814}) depends on
product with upgrade code {177ED463-0E03-4F4A-A725-5F5DF2C78E47},
version [5.2.21.0,), language in {}
which is not in the distribution.
3. Product NI Logos 5.2.0 ({01CF3725-EE33-4308-BBF9-90BF6AC43814}) depends on
product with upgrade code {FDA3F8BB-BAA9-45D7-8DC7-22E1F5C76315},
version [9.0.201,), language in {}
which is not in the distribution.
4. Product NI Logos64 5.2.0 ({F7B62B13-5E47-4511-B317-4F9FBA627BA6}) depends on
product with upgrade code {FDA3F8BB-BAA9-45D7-8DC7-22E1F5C76315},
version [9.0.201,), language in {}
which is not in the distribution.
5. Product NI System Web Server Base 1.0 ({2254CBFE-56BB-47BD-9958-5103AA58C5F7}) depends on
product with upgrade code {FB99B180-68F3-4D20-A3B7-CABFEDAB7F59},
version [10.0.234.0,), language in {}
which is not in the distribution.
Correct the distribution and try again.
<No Debug Message>
#########
This was very bad last week because I was out of Office trying to install it on a customer PC on site wich was not possible.
I've installed this package several times before without problems. I did some modifications in the program and had to build again, and now I can't install the project.
Any helps?!
11-18-2010 04:15 AM
I have the same problem after installing LV 2010 on my development machine. On the PC were LV 6.1, LV 7.1.1, LV 8.2, LV 8.5.1 and now LV 2010 installed. After compiling an existing project I run into the same trouble. (see attachment) ???
11-18-2010 05:14 AM
Hi,
the solution was really simple:
In the existing project I just had to recreate the "Installer" under "Build specification". After that everything worked fine.
Dublicating a project causes this effect too:
I dublicated a project (Project 1) for another, similar application (Project 2). Changed the code etc. and VI's were working OK. I renamed the project of cause,
but I used the "Installer" under "Build specification" from Project 1 for Project 2 (I did nor recreate it, just renamed it).
So, the output was installable, but with this effect:
- Installing Project 1 --> OK
- Open executeable from Project 1 -- OK
- Installing Project 2 --> OK
- Open executeable from Project 2 --> OK
- Now open again executeable from Project 1 --> NOT OK, because it is quitly uninstalled while installing Project 2...!
With LabVIEW Version <= 7.1 it was possible to create a registration-tag with the application builder, somehow in versions > 7.1 this is done in a black-box by NI...