Can't build classic installer

[Konan__]

Hello,

I have LV2020 Professional. With application builder I created a exe, now I need to create an installer.

When I click "build installer", I get the attached screen, where Labview asks for missing packages/modules (which I dont use by the way).

Now I dont have the media, because I installed the product via VLM, using packages.

How can I solve this?

I downloaded the Labview 2020 SP1 media iso, and have it on letter drive, but it seems it doesnt have "OLD" installer modules, it has the new package technology.

I dont want to use package installer, I need to create an old installer.

Pls help

thanks

[JÞB]

That sort of looks like you are simply missing an EULA update.  I am guessing that any one of those preselected media is enough.  I'd try installing the missing LabVIEW 2020 RTE f1 patch first and see if that resolves it.

[Konan__]

No, it's not EULA update.

Why Labview is messed UP??

I have all updated, I can't create an installer!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[JÞB]

You need the media to install the installer needed by your installer. Just having the update installed doesn't install the EULA (or whatever's) installer.

Clear as mud right?

[billko]

Usually the installer is pretty good at identifying which packages you actually need.  Chances are, the installer sees parts of a package that you didn't even know you were using.

At any rate, you can choose not to add those packages to your installer, but then you will have to make sure they are installed on the target.

[JÞB]

---

@billko wrote:

Usually the installer is pretty good at identifying which packages you actually need.  Chances are, the installer sees parts of a package that you didn't even know you were using.

At any rate, you can choose not to add those packages to your installer, but then you will have to make sure they are installed on the target.

---

The installer won't build unless it has all the component installers.  ESPECIALLY an EULA installer.  NI really does need to include those little legal notices.

[WesW · Accepted solution]

When you install a product via NI Package Manager (regardless if it's from VLM or not), it also caches a copy of the files necessary for the classic\legacy installer builder to use as the source MSIs. That it's prompting for all of those low-level components means that installer cache is possibly missing or damaged. A potential way to fix this is to run repair by:

• From the Start Menu, launching NI Package Manager.
• Going to the install tab, and click the products that are included in your deployment, such as LabVIEW or any driver.
• Let the repair run - it might take a while.
• Now try building your deployment again.

[Konan__]

I UNINSTALLED ALL (labview and every NI driver) and cleared all, rebooted.

REINSTALLED Only Labview 2020 SP1 and activated on our VLM server. 

It was downloaded OFFLINE installer from the NI website (1.86 GB iso, that has a NI package manager technology installer)

I created a blank project, with main.vi with just a numeric indicator. 

I created an EXE.

I created an installer for this EXE.

And I get this:

HOW ??? WHY???? 

Pls help, this NEVER occured when I had ACTUAL media, this is NI PACKAGE technology FAULT.

This is UNACCEPTABLE unclear, it's LOW QUALITY from NI, guess why it's going down the drain

[Konan__]

---

@WesW  ha scritto:

When you install a product via NI Package Manager (regardless if it's from VLM or not), it also caches a copy of the files necessary for the classic\legacy installer builder to use as the source MSIs. That it's prompting for all of those low-level components means that installer cache is possibly missing or damaged. A potential way to fix this is to run repair by:

• From the Start Menu, launching NI Package Manager.
• Going to the install tab, and click the products that are included in your deployment, such as LabVIEW or any driver.
• Let the repair run - it might take a while.
• Now try building your deployment again.

---

Done repair on ALL packages (select all -> repair).

it works.

Still dont understand why a full clear uninstall-install cycle didnt work.

Kudoed and reported as solution.

thanks