Installation problem with nvioref.dll

[Maciej_Antonik]

Hi Todd

So please do the following:

- rename all existing files to a different names (like .old)

- try installing the application again

- see if it works

- search again for nvioref.dll and see where the file has been installed on your HDD.

Those are troubleshooting steps needed to figure out a workaround for this problem

[toddho]

I renamed all of the NVIOREF.DLL files on the target PC and then uninstalled my program.  I then reinstalled my program.  The re-instillation went really fast.  I then restarted my program and it could not find NVIOREF.DLL.  I then searched for the file and could not find it.  It looks as if it was not loaded  when the program was installed.

Thanks

Todd

[mgoldman]

I have been having the same problem.  I seemed to have solved it by adding a copy of NVIORef.dll to my project and then having the installer manually deploy it.  I found that using the Source Files tab to put the file either in the same directory as the executable or in the [SystemFolder] directory works.  Since this problem seems to be related to a conflict between different installations of NI products, I think that I will stick with the executable directory.

If that does not work for you, you can always try a carpet-bombing approach.  Put the file in all of the directories in the Source Files tab, see if one of them works, and then narrow it down.

[Maciej_Antonik]

Hi Todd

Pls see if the solution adviced works for you. 

When you see the error saying that your program can't find the file, doesn't it say where should it be?

[toddho]

I went ahead and specifically included the file in the build and that fixed the problem for me.  Odd that this is not automatic.  Thanks for all of your help.

Thanks

Todd

[gdvorak]

Just to add my two cents...

I was having a similar issue. The NVIORef.dll file error kept popping up when I tried to run a deployed application with hypertrend graphs in it. I had a 2009 DSC Runtime license installed on the PC but my program was built in Labview 2010 on a seperate computer.

I know a pervious person mentioned that it could be a version issue and in my case it was. Verify that the DSC licence on the PC matches the version of Labview the application was built in.

[carrasquel]

Greetings, I had this same problem this same week, but didn't found any useful, but I found out that the DSC Module only works in the LabVIEW development enviroment, If you want to execute a builded application in another computer without LabVIEW, you have to buy from National Instruments a DSC Run-Time System.

http://sine.ni.com/nips/cds/view/p/lang/es/nid/210561

[EZ-TechStop]

This thread is two years old, but to confirm this issue still exists with the LabVIEW 2017 SP1 application builder.  When I build the installer and include dependencies including the LabVIEW Run-Time Engine and the DSC Run-Time Engine, it does not include the NVIORef.dll that is required to complete the installation of the application.  

I may end up needing to build my own installer to automate this since the NI installer is unable to determine and package the necessary dependencies.  

[fboteroh]

Same issue within LabVIEW 2018...

[EZ-TechStop]

I reached NI and they confirmed that you have to activate a run-time license for the deployment machine.  I installed the LVRT and DSC run-time after purchasing a license, which also install MAX.  All worked after that.  There is no 30 day trial and no way to test a deployment without first buying a license.  Good luck.