Again, was there any solution to this problem? I am having the same issue deploying a library programmatically within an executable. I do not have LabVIEW installed on the target computer, but I have installed the DSC Module Run-Time on that computer.
What version of LV DSC Runtime are you using? Are there IO-Servers included in the library? Are you binding to another device? If so which kind of binding are you using?
I am using LV DSC 8.5. There are no I/O servers and I am not binding to anything. I am trying to log data to a Citadel database from a real-time executable through shared variables. Any ideas?
Ok. You have said that you are not binding to anything. But how do you establish it when using a real-time executable in connection with citadel logging? Isn't the windows computer connecting via "Bind to Source" to the RT computer? Maybe you can attach your project.
My personal solution to the problem was installing the full Labview
development system on the target machine too. After technical support
failed helping me, National Instruments (Italy) gave me permission to
do it without paying another license
I solved the problem. It turns out the LV DSC Run Time wasn't installed, even though I thought it was. I had to get the RTS from NI and install it on the target computer, and now the error is gone.
