error 2711 on installing apllication

[WilMM]

when installing an application on a new PC there is an error code 2711. NIFeature.1.601EB45057EO.MDF100 and the installation failes.

On building the installer to this application there are no errror messages.

Using Labview 2023 W3 964bit) 23.3f0

How to resolve this error?

[wiebe@CARYA]

---

@WilMM wrote:

Using Labview 2023 W3 964bit) 23.3f0

---

964 bit installers are not supported yet 😁. But seriously...

Something's wrong with "YOKOGAWA":...

We don't have any way of knowing what that is. My guess is a 3rd  party installer? Or the main exe?

If it's a 3rd party installer, try to install it by itself and see where it fails.

What happens if you continue? What expected functionality is missing?

[WilMM]

the main executable is named  YOKOGAWA.

If I continu the executable in not installed.

[wiebe@CARYA]

Is the target a clean system?

2711 seems to mean 'feature not available'... This could be because something is corrupt on the system (not clean) or not available (very clean).

Are there additional installers in the build? 3rd party installers?

I would either start with a new installer\project and see when it stops working when adding stuff (code and packages) or remove stuff until it starts working. Or both.

[WesW]

To see what's going on, pass a "/log" command-line argument to the install.exe, like this:
install.exe /log "%temp%\mylog.txt"

Start at the bottom of the log, and work up. If it's not an obvious problem, post the log here.

Regards,

- Wes

[WilMM]

I made a log-file while trying a new installation over the the existing installation that went wrong. Now almost immediatly the installation was stopped and the same error 2711 appeare..

I find the error in the log, but I don't now what to do.

[wiebe@CARYA]

That's not very descriptive...

If I had to guess: could your executable (the LabVIEW exe) already been installed on the system?

It's definitely a complaint about something already being installed with a later version.

I'd expect a clearer message if this was the case....

If at all possible, clear the system of anything NI. Or, test on a clean system or VM to see if it has the same problem.

[WilMM · Accepted solution]

Using the installer on an empty system does the job. The erro no longer occurs