"A dynamic link library (DLL) initialization routine failed." with NI-DAQ 7.1

[joeljkp]

I have a DAQ application that I've been developing with LabVIEW 6.1 and NI-DAQ 7.0.1. I recently saw that NI-DAQ was updated to 7.1, so I downloaded, uninstalled the old, and installed the new. Now when I try to open my VI, I get a series of errors that say "A dynamic link library (DLL) initialization routine has failed." One of the affected files is Labview 6.1/vi.lib/DAQ/lvdaq.dll, but there are many more.

[Shiner]

Use an application called depends.exe (should have been supplied with the NI install, or go to MS.com and do a search for it. (Its a freebie).

Most likely you have a dependant of the new install missing.

i.e DLL A, needs DLL.B, DLL.C, DLL.D

When you run depends on DLL A, it will tell you which DLL's are present and any that are not.

Obviously, depends cannot detect if 'dynamically' loaded DLL's are missing, only those that are 'statically' linked.

But, I think there is a similar post somewhere in the archives.

Can you post the actuall error code and/or message.

Hope this helps,

Regards

Chris

[Shiner]

Doh... Forget about including the error message. I saw it after I hit send. Sorry.

Chris

[joeljkp]

Do you have any other info about this program? It's not on my computer, and some quick searching of microsoft.com, MSDN, et c. for 'depends.exe', 'depends', 'dependencies', turns up nothing.

Got a link?

Thanks for the help.

[Shiner]

Send me a mail to chris.a.wright@yaps4u.net and I will send it to you if the attachments below get blocked.

Regards

Chris

[Shiner]

It used to have a link at MS somewhere but I couldn't find it either..

http://www.dependencywalker.com/

I would never have guessed that link for years despite its name..

I've also attached the lastest download from that site to save you the time.

Chris

[joeljkp]

Ok, here's a little more info about the problem:

My VI depends on a lot of DAQ VIs. When these VIs get loaded during startup, my error message appears. It appears that all of the offending VIs are DAQ VIs, and they all directly call lvdaq.dll.

Just for fun, I looked at the depends.exe output for lvdaq.dll and the function call in AI Clock Config.vi. The function exists, but that's all I can tell.

depends.exe also says that I have a missing dependency for lvdaq.dll: apphelp.dll

Do you know anything about this, and where it comes from?

[BJD1613]

Most of the problems that you can be encountering could be attributed to the new upgrades in LV 7. Ni just redid some of the nidaq functions to incorporate there new nidaqmx functionality. There is a different palette in LV7 and the linkages to LV might have changed. There are traditional ni daq functions (before 7) available in LV7 but there might have been some improvements or linkages changed. My suggestion would be to call NI about your problem. Or use the previous version. Not a whole lot has changed with the traditional DAQ functions. Unless you are using LV7 and DaqMx you shouldn't see any change. Hope this helps.

[joeljkp]

Ok, I figured out what the problem was. I'm on a Windows 2000 machine with two users: Administrator and me. I development my application as myself, in the Users group. To install NI-DAQ 7.1, I logged in as Administrator, uninstalled the old, rebooted, logged in again as Administrator, installed 7.1, rebooted. I then logged in as myself and tried my VI, getting the above errors.

To test, I logged in again as Administrator and tried running my VI. It ran flawlessly. I then logged out and back in as myself and tried my VI again. This time, I got no error messages.

So it seems that when using NI-DAQ as a non-priveleged user, it must be started once as Administrator before it can be used by a regular user.

This should be considered a bug, or at least a p
oint for further documentation during install.

[Steve Miller]

joeljkp wrote in message news:<5065000000050000001F360100-1066448259000@exchange.ni.com>...
> Do you have any other info about this program? It's not on my
> computer, and some quick searching of microsoft.com, MSDN, et c. for
> 'depends.exe', 'depends', 'dependencies', turns up nothing.
>
> Got a link?

http://www.dependencywalker.com