LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to locate NiRioSrv.dll for use in standalone application.

I have a stand-alone application that works properly on the computer on which it was developed.  When I copy it to a computer that doesn't have LabView, I get the error "..cannot find NiRioSrv.dll".  My first instinct is to simply find NiRioSrv.dll on the original machine and copy it over to the target machine, but I cannot locate the file.  It is listed as being in C:// in the .lvproj that generated the application, but does not show up at that location.

 Is there an option in build specifications to include this file, or can someone help me locate it?
0 Kudos
Message 1 of 13
(4,960 Views)
It would appear that I need a whole host of ni*.dll files on the target computer.
0 Kudos
Message 2 of 13
(4,956 Views)
...because the LabView Runtime Engine needs to be installed.  Problem (hopefully) solved
0 Kudos
Message 3 of 13
(4,951 Views)
Installing the latest (and appropriate) version of LabView Runtime Engine does not solve the missing NiRioSrv.dll problem.  I tried copying the .dll, which I found in the System32 folder of the original computer, to the System32 folder of the target computer.  I then unsuccessfully attempted to register the .dll, as per http://forums.ni.com/ni/board/message?board.id=170&message.id=243871&requireLogin=False.

LabView Runtime Engine is supposed to fully facilitate running labview applications on machines without any other LabView software, but it does not appear to be handling communication with our cRIO.
0 Kudos
Message 4 of 13
(4,940 Views)
Hi,
 
Can you please tell me what operating system you are running? These dll files seem to be a reuqirement for embedded operating systems.
 
Ipshita C.
National Instruments
Applications Engineer
Message 5 of 13
(4,918 Views)
Obxetec,
 
You most likely need the NI-RIO driver installed on your system as well.  From your desctription, it sounds like your attempting to remotely call the cRIO device from a windows machine rather than opening a reference to the FPGA from the RT controller.  If this is true, you would be required to have the NI-RIO driver installed on any systems your planning to deploy the software too.
 
Basset Hound
0 Kudos
Message 6 of 13
(4,903 Views)
The OS was vista
0 Kudos
Message 7 of 13
(4,897 Views)
Basset Hound - that was the solution, installing NI-RIO did the trick.
0 Kudos
Message 8 of 13
(4,896 Views)

Having essentially the same problem.  Additional Installers I've included in the build are NI LabVIEW Run-Time Engine 2009 SP1, NI Measurement & Automation Explorer 4.6.1, and NI-VISA 4.5 for LabVIEW Real-TIme and LabLwindos/CVI Realtime.

 

I can checkbox NI-RIO 3.4.0 which is described as "NI-RIO Driver  This feature includes the National Instruments RIO drivers for Windows.  This software is required to use RIO devices such as the 78xxR and CompactRIO devices."  But I have two versions of LabVIEW on my machine (8.6 and 2009 SP1), and the installer appears to be asking for the 8.6 disks in order to get these files-- in other words, I think they're the wrong version.  So in the new version 2009 SP1, where is NiRioSrv.dll?

0 Kudos
Message 9 of 13
(4,240 Views)

Hi Chatwin,

 

If you select RIO 3.4.0, it will should install the right files.  It's probably looking for a specific component that was originally installed on the 8.6 disks.  If this component wasn't modified by the 2009 install, then it will look for what originally installed it, which is 8.6.  You probably can insert the 9.0.1 disks and it will work (they're usually smart enough to figure that out).

 

You can also manually install RIO 3.4.0 on the other computer, but including an installer is probably easier.

Jared S.
Applications Engineering
National Instruments
0 Kudos
Message 10 of 13
(4,207 Views)