Error after stopping executable

[becktho]

Hi all

I'm working on a project, which now is almost finished. Unfortunately I discovered the attached error, after stopping the executable.

The error appears on two different machines (both with WinXP).

Could anyone of you figure out what could cause this error? A few weeks ago I had no problems and I can't remember any change which could be linked to OLE.

If you need more information let me know.

Thanks in advance.

Thomas

Message Edited by becktho on 04-26-2005 04:31 PM

[Zac Fisher - NGC]

My German's not what it used to be, but I believe this is the same problem I was having with a project a few months ago, where I was developing the executable on one machine and distributing to lab machines. The programs ran on the other PCs just fine but the error message had to be cleared upon exiting every time. I believe I called it into NI tech support and they told me to make sure my development PC and the distribution PC were using the same version of NI-VISA. When I updated the distribution PC, the problem went away.
If this doesn't fix your problem let me know and I can pour through my notes and verify this was my solution.

[becktho]

Hi

Both PC's use the same version of NI-VISA and the error appears on both machines.
So I think this won't fix my problem.

Do you have another idea?

Thomas

[Philip_Courtois]

Guten Tag, Thomas! Wie geht's?

The German error that you are getting:

Die anweisung in ”0x77f75da0” verweist auf Speicher in ”0x050c2a74”. Der Vorgang "read" konnte nicht auf dem Speicher durchgeführt werden.

is equivalent to the English error:

The instruction at ”0x77f75da0” referenced memory at ”0x050c2a74”. The memory could not be “read”.

For troubleshooting this type of error, refer to the KnowledgeBase with the following name:

LabVIEW Application Error: The instruction at "[address x]" referenced memory at "[address y]". The memory could not be "read".

Good luck!

[becktho]

Hi Philip

The error message is no problem actually, due to the fact that I'm a native german speaker.

The problem is the reason. The windowtitle says "OleAutomation Window"... and I'm not aware of any ole object I use. The error also just appears after exiting labview if I ran the executable. If I test it in development mode there is no problem.

I also have never seen the error while the program was running - just after exiting.

It's really very strange and annoying :(.

Thomas

[Philip_Courtois]

Hi Thomas,

Even though the KnowledgeBase is referring to the LabVIEW.exe object, I still think that it will give you an idea of what to look for.

Let me know if it doesn't help, thanks.

[rolfk]

---

@becktho wrote:
Hi Philip

The error message is no problem actually, due to the fact that I'm a native german speaker.

The problem is the reason. The windowtitle says "OleAutomation Window"... and I'm not aware of any ole object I use. The error also just appears after exiting labview if I ran the executable. If I test it in development mode there is no problem.

I also have never seen the error while the program was running - just after exiting.

It's really very strange and annoying :(.

Thomas

---

Are you by any change using external DLLs or maybe CINs? This type of error is quite often due to a DLL corrupting memory it shouldn't even touch. The reason why this can happen are manyfold. First the DLL might contain a bug. Second the call to the DLL is not entirely correct configured. For instance if you pass an array of 32 elements allocated by LabVIEW to the Call Library Node but the DLL expects to be able to write 33 elements into the array it will scribble over some memory not belonging to the array but instead to some data used by LabVIEW to track its internal states. As long as you execute the program LabVIEW may never need to touch that area or only in rare circumstances but when LabVIEW closes down it wants to properly deallocate anything it has
created and will likely stumble over the memory incorrectly modified by the DLL.

So I would first check for external DLLs or maybe CINs of any kind not coming standard with
LabVIEW. It is almost always the reason for such errors both in my applications and in most others I ever saw.

Rolf Kalbermatter

[becktho]

Hi Philip, Rolf

I almost assumed that it could be a dll-call (I have just one dll used in my project) and it is as you both said.

I made a llb to call the MessageBox-function (I like the icons these messages display) and this cause the problem.

Attached is the actual version. Is there a way to make this work?

Thomas

[becktho]

Hi

I just found this thread. The vi posted there actually makes the same, except the window-handle which is passed to the dll.

I tried this in my version but I still get this error (Ok - maybe one has to live with such errors if one likes MS functions ;)).

Do you know about something similar in LV (not the standard message)? As mentioned in my previous post - I'd like something with the icons.

Thomas

[Philip_Courtois]

Hi Thomas,

Your VI runs fine on my LabVIEW 7.0 and 7.1.1, and I can even close LabVIEW without any errors. Your VI seems to be fine except for the "uType" which is supposed to be I32 and not U32. However, this mistake shouldn't result in the error you are getting.

Please try the attached "Message Box.vi" that comes from the LabVIEW Intermediate II class. It calls the same DLL and has been tested many, many times and proven its stability. Let me know if this also generates the error on your machine, thanks.