NI Ethernet device enumerator 64-bit install error

[terry92054]

I get the following error when trying to run my installer on a Win7 64bit computer.

The computer has no net work connection.

These are the components being installed (according to the installer at install time.)

Adding or Changing

• BW-LPD-DAQ4000 Files
• NI MAX Configuration Support
• NI-DAQmx 9.9
• LabVIEW C Interface
• NI Measurement & Automation Explorer 5.6
• NI System Configuration 5.6.0

I've tried recreating the installer but continue to get this error.

The installer is created on a 64bit Win7 machine running LV2010 32bit

In the installer properties, I've select the follow additional installers for the application.

NI LabVIEW Run-Time Engine 2010

   Math Kernel Libraries

   NI LabVIEW 2010 Real-Time NBFifo

   NI TDM Streaming 2.5

   NI VC2008MSMs

NI Measurement & Automation Explorer 5.6

NI-DAQmx MAX Configuration Support 9.9

The application seems to run OK, even after getting a final message saying that the install failed; fix the problem and try again.

Any suggestions on how to get rid of this error would be appreciated.

[natasftw]

Try making a simple VI that doesn't require the DAQmx drivers. Build an executable and installer from that.  See if the error exists then.  It'll help narrow down what is flagging the error

[terry92054]

Thank you for the suggestion and assistance.

I created a simple _Hello World_ VI and installer.

I uninstalled everything NI from the target computer, rebooted, and installed the simple project.

I encountered no errors during installation - rebooted.

Ran the simple project w/o any errors.

The only thing now listed under the NI uninstaller is the NI System Components.

Thanks and Happy New Year!

t

[terry92054]

Update -

- Modified the simple project VI to add DAQmx Create Task.vi

I then added just the drivers to the installer (additional installers) and I did not get the enumerator error during the install.

All that is being reported by the installer to install is just the drivers. No configuration or MAX items listed.

- When I added the just configuration support to the installer build (additional installers)

This is what's being reported that is going to get installed.

NI MAX Configuratoin Support

NI Measurement & Automation Explorer 5.6

NI System Configuratoin 5.6.0

And now I get the device enumerator error again.

(I see that the Ethernet device enumerator is in the registry numerous times even after the uninstall.)

- Tried adding only MAX ...

This is what's being reported that is going to get installed.

NI MAX Configuratoin Support

NI Measurement & Automation Explorer 5.6

NI System Configuratoin 5.6.0

NI-DAQmx 9.9

LabView C Interface

And still get the device enumerator error.

Progress is at 67% but there's no indication as to which component is being installed.

Wondering if there's a way to remove all NI entries from the registry in case one of the old entries is causing this error.

[terry92054]

Another update -

After uninstalling everything NI from the target computer, I searched for any registry entries called NI Ethernet device enumerator and found three. I saved each of these off as .reg files and then deleted the entries from the registry.

Still getting the device enumerator error during the installation.

Happy New Year

[ADrexelDragon]

I am receiving the same error. Did you find a solution?

[terry92054]

No, I have not found a solution yet. I will be installing on different HW later today. I am hoping this error is computer specific and I don't get this on a different computer. If I do get this elsewhere, it becomes a much bigger deal as I can't ship updates to customers and just tell them to ignore the error

[Sam_Sharp]

Have you looked in the windows event logs or if there is an NI installation log somewhere that might give you some more information about what happened during the installation?

[ADrexelDragon]

I ended up deleting some registry values associated with NI that were still around after a completed uninstallation of LabVIEW. I then reinstalled Windows 8.1.

It works now. 

[terry92054 · Accepted solution]

I too gave up on getting an answer for this one and restaged the computer.

t