LabVIEW: An exception occurred within the external code called by a Call Library Node. This might have corrupted LabVIEW's memory. Save any work to a new location and restart LabVIEW. VI "..." was stopped at node "..." of subVI "..."

[DuneMedical]

Hi

Help please...

I get the message:

"LabVIEW: An exception occurred within the external code called by a Call Library Node. This might have corrupted LabVIEW's memory. Save any work to a new location and restart LabVIEW. VI "..." was stopped at node "..." of subVI "...""

The Call Library Node calls a dll I wrote in C 

This message pops up only when running as an executable, as VI it never happens

Also - when running the executable without closing the window (after approving the error message) it runs without any problems

Any advice?

Version:

LV 7.1

Thanks

Roy Sasi

[DuneMedical]

More details to my previous post:

My target is a windows XP OS

My code calls a dll - when I run it as a VI the dll is called and works without a problem only when I compile the code and run it as an executable I saw the error

When I run the executable the error almost always appears - when I press OK (to confirm error popup window), my application window is still open, and run my application again - the error never appears

Thanks

Roy Sasi

[smercurio_fc]

---

DuneMedical wrote:

Any advice?

---

Yes. Stop trying to stuff the entire body of your message in the subject thread.

I don't know how you can expect us to help. You've told us nothing about what your DLL does, or how you're calling it, or how it interface to LabVIEW, or whether it's dependent on other DLLs, or whether it tries to access certain resource that have to be initialized, or anything else. You haven't even shown us any code. You've told us: "It doesn't work in the executable". Now, if I came to you with that exact problem statement how would you help?

[mikeporter]

Especially in earlier versions of LV these sorts of errors were common if the call wasn't made just right or the parameters were set up incorrectly.

1. Where did you get the DLL from? Was it written internally or did it come from another vendor?
2. Try building a DLL call into a very small, simple application. Do you see the same issue?
3. Are there multiple calls to the same DLL in your code? If so, is there problems with all of them?
4. Can you track it down to a specific function that you are trying to access that is causing the problem?
5. Is there any indication of a memory leak?

Finally any additional information you can provide would helpful.

Mike...