LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

DAQmx broken even after full re-install

I’m having a nightmare problem with DAQmx libraries having somehow become corrupt in my LabVIEW installation on my laptop. It's LV8.5 and I'm on Windows XP SP2.

The problem is that they can’t find the nilvaiu.dll. I get the error: "nilvaiu.dll a dynamic link library (DLL) initialization routine failed." I have checked and the dll is most definitely there in both C:\WINDOWS\System32 and C:\i386.

Having googled around, I found the problem mentioned in a few places and have followed the recommendation to do a clean re-install which I have done. I followed the instructions that had been sent from NI tech support using MSIBlast, cleaned out everything including the repository entries and then reinstalling from scratch. But the problem is still there!

I have tried to mass compile the DAQmx libraries and get a sequence of "Bad VI" errors (log attached).

In desperation I have also tried copying both the nilvaiu.dll and the DAQmx folder from vi.lib from a working installation on another machine but to no avail.

Also, when I start up my laptop, I get the error “nidevmon application failed to initialize properly”. This also should have been dealt with by the reinstall but hasn’t so I suspect these two problems are related.

It’s worth pointing out that my laptop is a new machine which I recently migrated from my old laptop which was on it’s last legs. The migration tool I used successfully migrated all software except for device drivers so I suspect there’s something which DAQmx or nilvaiu.lld depends on which is not installed properly but since it doesn’t give me any helpful errors or any indication as to what it’s dependant on I have no hope of tracking this down.

I have also tried doind a "repair" from the "add and remove applications" angle but also to no avail.
 
Any clues would be most welcome as I'm at the end of my teather with this.
0 Kudos
Message 1 of 7
(3,611 Views)

This is really a long-shot but have you checked with any security conflicts on your machine?  Are there issues with firewall or permissions?  I am just recently running Vista and have had some odd issues.  For instance, I cannot write to a file or create a file in "C:\" without some sort of irritating security message.  You could try to run LabVIEW.exe as an administrator to see if that helps.  Navigate to your LV directory (something like "C:\Program Files\National Instruments\LabVIEW 8.5"), right-click the exe, select properties and then check the "Run this program as an administrator" box.

Another parting thought is a possible conflict with any virus scanning software.  You might want to track those things down, turn them off, and then test your problem again.  This could just be Mircosoft's way of subtly saying "All your base are belong to us!".

-cb

0 Kudos
Message 2 of 7
(3,600 Views)
Hi cb,
 
I had a look but I can't see a "Run this program as administrator" box on the properties dialog. Is this a Vista-specific feature? I'm running on XP.
 
I should have mentioned that I've already tried disabling my anti virus (Kaspersky 7) and the windows firewall but it still fails in exactly the same way 😞
 
Thanks for the thoughts though... any more suggestions would be very very welcome.
 
 
 
0 Kudos
Message 3 of 7
(3,582 Views)

Sorry, the Run As deal is a Vista thing.  I misunderstood your post.  Hmmm, can't think of any other stuff.  Sounds like corruption of sorts.  Have you virus scanned your system to see if there is some horrid foul infection?

Good luck! -cb

0 Kudos
Message 4 of 7
(3,578 Views)

Actually I haven't done a full virus scan since the problem arose although I did do one straight after I migrated the laptop and it does scan continuously (aledgedly). That said, it's worth a go so I'll kick a full scan off over night, just in case.

 

0 Kudos
Message 5 of 7
(3,572 Views)
I am having a very similar issue.  I am trying to bring up a top level VI already built on a another machine.  However,  all the DAQmx VIs such as DAQmx Write are broken and the error "Code could not be generated because an external component or driver is missing" is thrown.  There is a call to an exposed method in nilvaiu.dll which I think is the issue.  I copied nilvaiu.dll from another machine which doesn't have a top level VI that is broken.  However, I noticed that the nilvaiu.dll version on the working machine is 1.6.0.49153.  However, I my machine it is 1.7.0.49153 which I think was for the reinstall of NIDAQmx version 8.5.  I am running Labview 8.5.  What version of nilvaiu.dll should I have with my current NIDAQmx?  Should I upgrade to the latest and greatest?
0 Kudos
Message 6 of 7
(3,545 Views)
I have since learned that I need minimum NI-DAQmx version 8.6 for use with Labview 8.5.  That was the whol issue.
Message 7 of 7
(3,528 Views)