failed to load nicvidu.dll

[LelandDurrette]

I have LabWindows/CVI version 8.5.0 (279) installed.  I'm running the Sample "Simple_DIO_Example" in debug and getting an error on the call to function "NIDAQmx_NewPhysChanDOLineCtrl()".  If I step through the program I get a popup saying "The procedure entry point __CVI_Resource_Acquire could not be located in the dynamic link library cvirte.dll", but if I just run the program without stepping through it, I get a popup saying "Failed to load nicvidu.dll.  Check your installation."

I found several posts referencing the "...procedure entry point..." message which indicates a different version of the cvirte, and to remove multiple copies and/or repair the installation.  I have only one copy, and it is the same version as the software (there are two other references on my computer, but these are in an Acronis backup file).  Further, the posts seem to have in common that the error occurs on a different machine from the development environment, whereas mine is within the development environment.  I tried the repair route, but no change.

I haven't seen any related posts to the second message.

 I'm using Windows XP SP3, LabWindows/CVI 8.5.0 (279), and NI-DAQmx version 9.0.2 (recently updated from 8.0.1).

Thanks in advance,

Leland

[JÞB]

Did you install "Device Drivers?"  Send a snapshot of MAX Software" like the attached;

[LelandDurrette]

Thanks, Jeff.  Here's the screenshot.

-Leland

[JÞB]

Leland

the dll should be at C:\WINDOWS\system32 on your machine.   You may need to repair the LabWindows/CVI installation.

[AndrewMc · Accepted solution]

Hey Leland,

It appears that what you are running into might be a bug.  A corrective action request has been filed (CAR #:196232).  It appears that a dependency was added for DAQmx IO controls in CVI such that runtime engine 9.0 or newer is required.

The workaround here should be rather simple: Upgrade to CVI Runtime Engine 9.0 or newer: http://joule.ni.com/nidu/cds/view/p/id/1285/lang/en

Sorry for any inconvenience, and thank you for bringing this to our attention.

Please let me know if you have any follow-up questions. If you would like to follow up on the status of this request at a later time, feel free to reply to this post then.

[LelandDurrette]

Thanks, Andy; I'll give it a try as soon as I can.  A quick question, though I think I know the answer already:  Once I put this RTE on the development system, will it be the version included in any installation sets that I create, or will I need to do something else to get this RTE version on application machines?

Thanks again,

Leland

[AndrewMc]

No problem.

The currently installed CVI runtime should be the version packaged with your CVI distribution.  That is, your deployed systems would be updated with the latest CVI runtime if your distribution packages it.

As well, I wanted to mention another possible workaround.  While we have not fully investigated all of the possible symptoms of having the older runtime engine installed with DAQmx 9.0.2, it seems that the issues are limited in scope to the use of IO controls.  That is, if you use a string control in your user interface rather than a DAQmx IO control, the application should work fine.

Again, sorry for any inconvenience, and let me know if you have any follow-up questions.

[LelandDurrette]

I just tried the updated RTE and it seems to be working just fine.  Thanks for the information.  So, if I had kept v8 of NI-DAQmx, I wouldn't have had this issue, it sounds like.  No matter; as long as everything works.

[AndrewMc]

Yes; this is a DAQmx 9.0 issue.  This will be fixed in a later version of NI-DAQmx.

That being said, now that you have DAQmx 9.0, some of the nice features that you have are:

NI-DAQmx Logging (you can just called DAQmxConfigureLogging and all of your data will be logged to disk).

X-Series family support

NI-Spy support (a debugging tool)