NIOREF DLL problem

[craige]

I've been experiencing the following problem on and off: Upon building an executable this error is shown in a popup dialog.

Error copying files.
Source: C:\Program Files\National Instruments\LabVIEW 8.2\resource\NVIORef.dll
Destination: C:\Company\Source\builds\RTacquire\NVIORef.dll

Librarian Path Location.vi

My original solution was to rename this file so LabVIEW couldn't find it then redirect it to C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\8.2\NVIORef.dll. This has worked for the past 20+ builds but now the problemed has resurfaced and no amount of renaming, redirecting, or even copying this dll from another coworkers computer will allow me to complete an EXE build.

My application utilized DSC Module and shared variables over a network.

Why is LabView fighting with itself?

frustrated,

Craig

[Chris_Cilino]

Hey Craig,

LabVIEW sometimes can seem to have a multiple personality disorder so I certainly appreciate your frustration. There are two I'd suggest. First, can you manually copy this dll in general? Second are you enabling enhanced DSC support in the App builder? Try toggling this option when building the executable (it is on the advanced page).

Chris C

[craige]

Yes, I can manually copy the DLL. (in fact labView moves the DLL into my build directory. It is immediately after this that it throws this error)

I would add DSC support but this is only an EXE. But you're correct, my installer Build Specification that I have already made has DSC support checked. All I need now is this EXE to build so I can put it into it.

Dillon Mahmoudi (AE) had talk to a friend of mine about this issue briefly but I was not part of the converstation. They were the ones who discovered redirecting the file to solve this issue in the first place.

Craig 

[Doug M]

Craig, three things to try here:

1) Check the Enable Enhanced DSC Run-Time Support checkbox in the Advanced category of the executable Build Specs dialog like Chris mentioned:



2)  Try building a simple project to see if it also gives this error.  If not, perhaps add some of the DSC related features your main project uses, such as shared variable deployment, etc. and see if this will build.

3) If you continue experiencing this, try repairing your DSC and/or LabVIEW installation.

Finally if none of this works, you can FTP us your project and we can see if we can reproduce the problem here.

Message Edited by Doug M on 01-29-2007 11:54 AM

[craige]

Thanks for you suggestions. My problem fixed itself. (i hate when that happens) I've since tried to replicate the error but do not have the exact system setup as my customer. I had a few layers of shared variables using RT-FIFO, Data Binding, and then evetually logging into a Citadel Database. Any mixture of these could have caused the error when deployed.

I made sure to undeploy all variables related to my application then the build seemed to work just fine. If I stumble across the exact cause of this I'll make sure to document it here.

Craig