topic Re: Error after stopping executable in LabVIEW

Error after stopping executable

becktho — Tue, 26 Apr 2005 14:29:09 GMT

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

Re: Error after stopping executable

Zac Fisher - NGC — Tue, 26 Apr 2005 14:54:08 GMT

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.

Re: Error after stopping executable

becktho — Tue, 26 Apr 2005 20:18:29 GMT

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

Re: Error after stopping executable

Philip_Courtois — Thu, 28 Apr 2005 07:17:41 GMT

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!

Re: Error after stopping executable

becktho — Thu, 28 Apr 2005 07:42:32 GMT

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

Re: Error after stopping executable

Philip_Courtois — Fri, 29 Apr 2005 17:16:49 GMT

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.

Re: Error after stopping executable

rolfk — Sun, 01 May 2005 18:47:23 GMT

@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

Re: Error after stopping executable

becktho — Mon, 02 May 2005 05:59:36 GMT

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

Re: Error after stopping executable

becktho — Mon, 02 May 2005 13:59:16 GMT

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

Re: Error after stopping executable

Philip_Courtois — Tue, 03 May 2005 07:08:13 GMT

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.

Re: Error after stopping executable

becktho — Tue, 03 May 2005 07:47:04 GMT

Hi Philip

Ok, I replaced my dll-call with your vi, built an exe, run it and the error still appears.

Don't forget the point that it works correctly and without error, if I start it in development mode. The error just comes up after stopping / exiting an executable.

Did you try my vi as exe too?

Thomas

Re: Error after stopping executable

tst — Tue, 03 May 2005 09:17:46 GMT

@Philip C. wrote:
Your VI seems to be fine except for the "uType" which is supposed to be I32 and not U32.

Really?
According to the MSDN this is a UINT.
Is there something I'm missing?

Re: Error after stopping executable

becktho — Tue, 03 May 2005 09:24:17 GMT

I agree with tst - that's why I set a U32.

But maybe that's one more MS-puzzle, which mankind will never be able to solve... 😉

Re: Error after stopping executable

Philip_Courtois — Wed, 04 May 2005 06:11:10 GMT

Hi Thomas and 'tst',

Ooops, you are right that the 'uType' should be U32 and not I32. The confusion comes from the MessageBox.vi that uses I32 to avoid a coercion dot, since the "MessageBox Type" Listbox can only be a I32. Sorry!

Apart from this, I figured out what the issue was. Originally I was able to reproduce the error with your executable. I noticed that the "user32.dll" was being copied to the "data" folder when building your VI into an executable. Since your VI was supposed to point at the DLL in the "C:\WINDOWS\SYSTEM32\" folder, I deleted the DLL in the "data" folder. From that point onwards, I didn't receive the error anymore.

I tried building the "MessageBox.vi" into an executable and noticed that a "data" folder wasn't created, hence no copy of the user32.dll. After some investigation, it turns out that the reason that the DLL is not copied, is because the DLL is not being specified by path in the Call Library Function Node - only the name "user32.dll" appears where it in your VI specified "C:\WINDOWS\SYSTEM32\user32.dll". Specifying the complete path will result in the DLL being added to the "data" directory when the VI gets build to an executable. Refer to this other thread about the same issue.

Therefore, to make a long store short, you have two options to fix your VI/executable:

Workaround: After creating the executable, delete the user32.dll from the "data" directory. Your executable will now spend some time searching for the DLL every time you launch the executable. Fix this by adding the "C:\WINDOWS\SYSTEM32\" folder to "Tools >> Options... >> Paths >> VI Search Path" of the executable. This will result in an added line in the *.ini file.

Fix: Use only the name of the DLL in the Call Library Function Node by deleting the path (see info in the above link). This will result in no copy of the DLL being created when building the application.

Thomas, I hope this solves your issue on your system too. Please let me know if you have any questions, thanks.

Re: Error after stopping executable

becktho — Wed, 04 May 2005 08:10:07 GMT

Hi Philip

It was a long hard fight but in the end I could manage to remove the path.

Now it works.

Thanks a lot for your help.

Thomas

Re: Error after stopping executable

Athanassios — Thu, 14 Dec 2006 15:46:53 GMT

Hi @ all,

I have the same problem!

But the error doe's not appear after stopping the executable!

It is shown however if I insert a combi box on the front panel and want to change the characteristics.

I don't know what to do and I can't work without using a combi box!

Thanks,

Atha