Executable run-time error: "Failed to process adress of Labview Program. Occurences will not work."

[Kari]

When I run my VI it works fine. However, when I create it into an executable and try to run the exe, it gives me an error, "Failed to process adress of Labview Program. Occurences will not work." Why?

[Robert M]

Hello Kari,

I�m not exactly sure why you are getting this error. What version of LabVIEW are you using? Could you post your code so I can try in on my machine? A screenshot of the error would also be helpful.

If none of these suggestions help, or if I�m not correctly understanding your issue, please reply with comments or answers to the discussion above and any additional information that may help, and I�ll be happy to look further into it.

Have a nice day!

Robert M
Applications Engineer
National Instruments

[Kari]

I am using Labview 7.0. I have attached a screen shot and the code. thanks for checking it out and let me know if you need any more info.

[Kari]

After some more investigation it looks like this error occurs when there are Call Library Nodes that are calling a DLL in the vi. the vi I attached doesn't have any Call Library nodes but, it uses VI server to dynamically call a different vi that does have a Call Library node. Does this help in understanding what the problem might be? Do I need to do something different in building my exe when I have Call Library Nodes calling a DLL? The dll is in a data folder in the same directory as the exe but, it still doesn't work??

[Kari]

Here are a copy of the dll and a copy of a simple vi with just a call library node...

[Robert M]

Kari,

Am I correct in assuming that the dll in question was compiled using Visual Studio .NET? I was able to reproduce your error on a machine with the Visual Studio .NET Environment installed, but received multiple errors on one that did not.

It looks like your error is being originiated from the dll itself and not from the LabVIEW Run-time Engine. What function are you calling in the dll and what is it doing? Did you write the dll yourself?

The dll is probably having a harder time tracing the call chain back to LabVIEW when it is running inside the executable, as opposed to in the development environment. That�s why you don�t get the error when running the VI.

Have a nice day!

Robert M
Applications Engineer
National In
struments