This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

LabVIEW Searching for a DLL or EXE Used in the Call Library Function Node

Updated Oct 6, 2018

Reported In

Software

LabVIEW Base
LabVIEW Professional
LabVIEW Full

Issue Details

When I entered the name of a DLL in the Call Library Function Node configuration window, I did not specify the path to the DLL in the Library name or path field. I just entered the name of the DLL. Where will LabVIEW look for the DLL? Also, if I included the correct path but later moved the DLL, where will LabVIEW search?

Solution

LabVIEW is searching for a DLL in certain order:

LabVIEW will first look in the location that you specified in Library name or path field in configuration window (to open the configuration window, right-click on the Call Library Function Node and select Configure).
After that it will use the VI Search Path. The VI Search Path can be set in: Tools » Options in the category of Paths, then you need to choose the VI Search Path from the drop down list.

Additional Information

This search order is different from the search order that is used by an executable built using the Application Builder (see My Stand-Alone Executable Cannot Find My DLL, Even Though I Have Specified the Path for the DLL).
In addition to the explanation of calling DLL, you can also call the LabVIEW.exe by inputting LabVIEW in the Library name or path box. As shown in the following image. Refer to [External] LoadLibrary function explanation for detailed reason.

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums

Search the NI Community for a solution

Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.

Open a service request

Learn about software subscriptions and services

Learn about hardware service programs