Could not Send Internal Error Information

[pockey]

The error is shown below:

http://forums.lavag.org/index.php?act=attach&type=post&id=5255

Does that mean I should change the location? But how? And why the current location did not work?

Thanks！

[Michael Aivaliotis]

I know you're not meaning to be funny but this is freakin' hilarious. And your comment "Does that mean I should change the location?" is the best punchline! :laugh:

[pockey]

Thank you, Michael_Aivaliotis,

Can you tell me why the path "C:\Documents and Settings\Workstation 2\My Documents\LabVIEW Data\lvfailurelog" doesn't work?

[Aristos Queue]

QUOTE(pockey @ Mar 22 2007, 02:39 AM)

Can you tell me why the path "C:\Documents and Settings\Workstation 2\My Documents\LabVIEW Data\lvfailurelog" doesn't work?

My only guess would be that maybe you don't have permission to write to that directory. Is it read only or something? Other than that, I have no idea.

Having said that... check if the log file actually got written out (in spite of what the error message says). If so, go ahead and post the log file here. Maybe we can puzzle out what happened.

[pockey]

Oh, Aristos Queue

You're right!

The "LabVIEW Data" folder is "Read-Only"!

However, the property of the folder will change back to "Read-Only" right after I clear the option.

I'm the administrator of this computer...

And ther're Log files in the folder!! :headbang:

The latest one with information shown below:

####

#Date: Thu, Mar 22, 2007 10:09:44 AM

#OSName: Windows NT

#OSVers: 5.1

#AppName: LabVIEW

#Version: 8.2

#AppKind: FDS

#AppModDate: 07/27/2006 05:08 GMT

.\manager\ThEvent.cpp(116) : DWarn: DestroyPlatformEvent failed

$Id: //labview/branches/Europa/dev/source/manager/ThEvent.cpp#4 $

0x004C6D73 - LabVIEW <unknown> + 0

0x00EF060D - LabVIEW <unknown> + 0

0x00EF077B - LabVIEW <unknown> + 0

0x00EE79FD - LabVIEW <unknown> + 0

0x00CE4192 - LabVIEW <unknown> + 0

0x00CE5922 - LabVIEW <unknown> + 0

0x00CE5BE3 - LabVIEW <unknown> + 0

0x00583D68 - LabVIEW <unknown> + 0

0x00F934C4 - LabVIEW <unknown> + 0

0x00FA71CF - LabVIEW <unknown> + 0

0x005F7912 - LabVIEW <unknown> + 0

0x0055FE62 - LabVIEW <unknown> + 0

0x00C47531 - LabVIEW <unknown> + 0

0x00C497C6 - LabVIEW <unknown> + 0

0x004CCB39 - LabVIEW <unknown> + 0

It's too difficult for me to understand.

[Aristos Queue]

QUOTE(pockey @ Mar 22 2007, 03:50 AM)

.\manager\ThEvent.cpp(116) : DWarn: DestroyPlatformEvent failed

Looks like something tried to shutdown as part of LV exiting last time, and LV didn't uninitialize correctly.

I wouldn't worry about it unless it becomes common.

I'll report the problem about the read-only directory. We ought to handle that better.

[pockey]

Thank you, Aristos Queue

It's not very often to get the error. Sometimes my computer was shut down abnormally. Then when I turn on my pc and open LabVIEW, the error will be shown.

[James N]

QUOTE(pockey @ Mar 22 2007, 10:27 PM)

Thank you, Aristos Queue

It's not very often to get the error. Sometimes my computer was shut down abnormally. Then when I turn on my pc and open LabVIEW, the error will be shown.

I think this relates.

Something I overheard one time but didn't get the full details of.. If LabVIEW crashes, it leaves temporary files in your temp directory which are sometimes left if an odd condition. The next time LabVIEW tries to reuse these temp files, errors ensue. So it's a good idea to delete temporary files in this directory.. which files specifically is part of the "details" I missed.

I've done about zero research on my own.... but what does anyone know about this?

-James