LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

x86 installer

Hi all I receive this when trying to build an installer containing the labview runtime (or any other built-in installer). I have Win 7 64 bit, LV 2009 SP1 (copied dvd's to hdd, and installed from there). I create a project with a blank VI, build an exe, then build an installer with the LV runtime, and I get this: I've tried clearing the cache files, uninstall all of NI, reinstall all of NI - just cannot figure it out. I definitely have .Net framework 2, so I just don't know. Can anyone help, or point me in a new direction to look? CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi Loading product deployment information ************** *** Error: Internal error. (Error code -40) There was a problem getting information about the source distribution for product 'NI .NET Framework 2.0 Language Pack x86 Installer' *** End Error Report ************** *** WARNING *** Skipping deployment information for an unidentified product because error code -40 occurred while loading file: C:\Program Files (x86)\National Instruments\Shared\MDF\Manifests\NI .NET Framework 2.0 Language Pack x86 Installer {F8ECD2D6-659C-49EB-8454-5F8F7B526FCF}.xml Loading product deployment information ************** *** Error: Internal error. (Error code -40) There was a problem getting information about the source distribution for product 'NI .NET Framework 2.0 Language Pack x86 Installer' *** End Error Report ************** *** WARNING *** Skipping deployment information for an unidentified product because error code -40 occurred while loading file: C:\Program Files (x86)\National Instruments\Shared\MDF\Manifests\NI .NET Framework 2.0 Language Pack x86 Installer {F8ECD2D6-659C-49EB-8454-5F8F7B526FCF}.xml ************** *** Error: Internal error. (Error code -40) There was a problem getting information about the source distribution for product 'NI .NET Framework 2.0 Language Pack x86 Installer' *** End Error Report ************** *** WARNING *** Skipping deployment information for an unidentified product because error code -40 occurred while loading file: C:\Program Files (x86)\National Instruments\Shared\MDF\Manifests\NI .NET Framework 2.0 Language Pack x86 Installer {F8ECD2D6-659C-49EB-8454-5F8F7B526FCF}.xml Adding files to installer 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... Updating files... Creating merged database... ************** *** Error: Windows SDK function returned an error. (Error code -12) *** End Error Report ************** Done building deployment
0 Kudos
Message 1 of 3
(2,969 Views)

longbow:

 

The issue is with the Application Builder looking for certain installer package dependencies. It's possible that the cached information on those external installers is either incorrect or corrupt.

 

You can test this by backing up and deleting the cache folders from the directory that it's looking in (Program Files (x86)\National Instruments\Shared\MDF\Manifests\). If the cache is no longer there, it should request the source installation media, and we can give it that instead. We may also be able to determine if the installation media is potentially at fault.

 

I believe there is a similar issue here that might be of some help.

 

Let me know if that helps!

Caleb Harris

National Instruments | http://www.ni.com/support
0 Kudos
Message 2 of 3
(2,942 Views)
Hi Caleb Found a solution that works. Removing the directory (renaming it to _Deleted) did not work, however it inspired me to read to content of the xml file. I found the name of the actual installer (DotNet20x86langpack.msi) which I located and ran. It asked me to modify / repair or remove - I selected repair and it seems to work now. btw : Uninstalling ALL of NI products, and deleting their directories did not solve the problem, including clearing caches etc. from the links. Thanks Warren
0 Kudos
Message 3 of 3
(2,900 Views)