Error -17004 - Unable to find dll

[Gary_H]

Hi,

I found solving "-17004 - Unable to find dll" errors up until now, straight forward.

I have created a sequence which contains a CVI Action step, which calls function (1)  within
dll (1) created using Labwindows/CVI.

Function (1) then goes on to call function (2) which is defined in dll (2).

The Action step will not execute because dll (2) cannot be found, i.e. error -17004.

In the past, I'm sure errors like this were resolved by configuring the Teststand search directories so

any directory containing a dll, was listed to be searched and all dlls' were found.

But this is not working for me.

If dll (2) is placed in the same directory as dll (1) there is no problem.

Have I misunderstood the use of Search Directories ?

thanks in advance

Gary.

[j_dodek]

Hi Gary,

I took some screen shots from example AccessingArrays (DLL, but CVI looks similar)
In the module tab you will allways see the linked path to dll. (if there is one)

I assume you have to add your dll to search list. Or make it absolute.

hope this helps

Juergen

Message Edited by j_dodek on 02-28-2008 08:40 AM

[AllenP]

The TestStand search directories will only work within TestStand.  Any dependent dlls must be found using CVI's rules for finding DLLs, which include the directory of the DLL, the working directory (I believe), and any system directories that it searches.

Allen P.
NI

[Gary_H]

Thank you for the replies.

It appears I was expecting too much from the Search Directories feature in Teststand.

I now remember that in the past I modified the System's Path Environment Variable
to include sub-directories containing dependencies, i.e. DLLs not directly
called by Teststand.

thanks,

Gary.

[j_dodek]

Hi Gary,

I assume that i missunderstood your question. So thank you for good rating !!!

So just one additional hint.

Do know the Tool "Dependency Walker"?   You can download it at http://dependencywalker.com/ . With it you can look "inside" your dll
and see from where you are loading all your internal dlls.

Hope this helps 

Greetings

Juergen