LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"Error loading ..\vi.lib\Daq\lvdaq.dll ... initialization routine failed" -> suggested fixes failed as well

Hi,

I have a similar problem as reported here in the forum before.
But the suggested fixes I have found have not helped me so far.

Problem:

I have a Labview code using the NI-PCI6036E card to steer/monitor some parameters, i.e. it is
using NI-DAQ code (system: WinXP, Labview 7.1, NI-DAQ version is 7.2).
The code was developed on a sister-system (same hardware and software setup) by a standard user.
There it runs without problems.

When the code was copied to this system I get the following error message when running as a standard user:
Error loading "C:\Program Files\National Instruments\LabVIEW7.1\vi.lib\Daq\lvdaq.dll".
A dynamic link library (DLL) initialization routine failed.
... multiple times - I suppose as often as there are (indirect) references to this routine in my code.

The routine exists at this location and has the same permission setting as on the sister-system.

When logged in as administrator the code runs without problems (on either of the two systems).

This looks like the signature reported here earlier, but the following attempts to fix the problem didn't work in my case...

1) log in as administrator, run the code, log in as standard user, finding the access/enable problems fixed
2) deinstall NI-DAQ, reinstall NI-DAQ, do the fix 1)
3) deinstall Labview and all other NI software, reinstall again everything from CDROM

... sure, there must be a difference in the installation between the two systems, but I have no idea where...

... are there any further suggestions to this problem?

Any help is much appreciated. I'm out of my wits here...

Cheers.
0 Kudos
Message 1 of 3
(3,288 Views)
Hey,

I ran into this very problem on a test machine I put together; I installed all the programs on two systems exactly, but one of them ran into this type of problem where it worked perfect on one but not another.

I don't know why, but adding "write" permissions to the "C:\Program Files\National Instruments\" directory does the trick. You don't have to give any other directories write permissions, and this root directory only contains subdirectories. However, if I give "write" permissions in addition to the "read, execute, list" permissions everything magically works. I have not figured out why this works, there aren't any files being written to this directory, but I accidentally stumbled across it when I was also playing with another NI software product. Go figure. 🙂

Good Luck!
-Danny
Message 2 of 3
(3,276 Views)
Hi Danny,

Thank you very much for the hint!
Enabling the write permission to "C:\Program Files\National Instruments" for standard users solved the problem for me, too.

Cheers, Stephan
0 Kudos
Message 3 of 3
(3,267 Views)