LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Input file missing required key: [Distribution] GUID.

Hi,

 

I freshly converted a .bld (LV7.1) file to .lvproj (LV11) through Tools > Convert Build Script. It ran well.

 

Opening the .lvproj, I then successfully build the .exe but failed on the Installer :

 

Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:


CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi


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
 
**************
*** Error: An internal tool or library returned an error. (Error code -21)
Error Messages
Input file missing required key: [Distribution] GUID.

**************
*** Error Details:
Error in MDF API function: _MDFBuildDist_Build
Error List
.\InputParser.cpp(5420): InstallerError 105
Input file missing required key: [Distribution] GUID.
<No Debug Message>


*** End Error Report
**************
 
Done building deployment

 

Any idea ?

 

Many thanks

0 Kudos
Message 1 of 3
(2,422 Views)

Not too sure... Is your installer supposed to create any keys in the registry?

Anyway, open your installer's build specification and check all the sections, I would suggest to bring specific attention to the following sections :

- "Source Files", because here, all the "extra files you want you installer to place in specific format have to be included/referenced in the project (.lvproj)

- "Registry", that's only if the installer is supposed to create keys in the registry

- "Additional installers", make sure you only tick the boyes corresponding to drivers/module that are required for you application and also make sure that when building, the installer you used to install those drivers/modules on your computer are still available.

 

Hope this helps


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 2 of 3
(2,417 Views)

Problem solved !

 

Just need to duplicate my installer --> Copy of MyInstaller

 

Then delete MyInstaller

 

Then rename  Copy of MyInstaller to MyInstaller

 

Now it builds !

 

Thanks

0 Kudos
Message 3 of 3
(2,403 Views)