What does this CRASH reflects??

[Parny]

HI,

I've been coming across the following crash incident very oftenly(many times in a day). Can some one pls point any understandable meaning in it for me?? The following is just one of the top lines from the very fresh crash report which is also here enclosed as a simple text file.

c:\builds\penguin\labview\branches\Jupiter\dev\source\typedesc\TypeManagerObjects.cpp(321) : DWarn: You should not be calling TMBeginTransaction in the middle of an UndoRedo prop types!
$Id: //labview/branches/Jupiter/dev/source/typedesc/TypeManagerObjects.cpp#36 $

[mikeporter]

What are the circumstances around the occurance of these crashes?

What OS?
What version of LV?
What are you doing?
What is LV doing?

Mike...

[Parny]

Mike, thanks for showing interest.

What OS?
windows NT

What version of LV?

8.5

What are you doing? , What is LV doing?

Performing DAQ operation and storing them in access database. Here I very oftenly get error  about "opencommand object" which I am also thinking to be the culprit. please refer to my following old post regarding to it.

http://forums.ni.com/ni/board/message?board.id=170&message.id=279954#M279954

This error(opencommand objest) occurs randomly.

Message Edited by Parny on 11-09-2007 12:49 AM

[mikeporter]

How are you connecting to Access? What are you trying to do?

Mike...

[AnalogKid2DigitalMan]

Just a side note:

According to the release notes, LabVIEW 8.5 does not support Windows NT.

[Parny]

My apologies,

The OS is "Microsoft Windows XP Professional Service Pack 2 (5.01.2600)""

Also enclosing here, with MAX configuaration report.

[Parny]

Got some feedback from the NI support, sharing the info here.

-------------------------------------------------

Thank you for your queries. I've looked at your log file and noticed that

this is a DWarn message. DWarns are not fatal so LV will generally keep

running - does LabVIEW crash when running the VI? Or do you get this error

dialog on startup?

If LabVIEW doesn't crash and the VI behaves as expected we can disable the

specific DWarn so that you won't get this messages again. Please let me

know if you would like to know how to do this. Otherwise we can start

troubleshooting the cause of the error.

For starters, the error log file indicates that the error occurred while in

'dau_stand3_U.vi'. Can you reproduce the error with this VI? Is the error

intermittently appears?

DWarn is a warning that occurred during the last time you were using

LabVIEW. By default LabVIEW does not show a dialog at the time of the

warning since it is not critical to execution. However, it is hard to

identify the cause of the DWarn without knowing when it occurred. By adding

the following line to your LabVIEW.ini file you will see a dialog

immediately when the error occurs, which will help you (and NI) identify

the cause.

DWarnDialog = TRUE

It will show a dialog and halt execution of your program when the DWarn

error occurs. Please let me know how you go with these tests.

Kind regards,

Linda Kurniawan

National Instruments

Applications Engineering

www.ni.com/support

-------------------------------------------------