DIAdem Application Error (mfc71u.dll)

[MicheleS]

Hi, I'm working with an application in DIAdem who analize some data that LABview acquire and save the result in one file ("BRAKE_#.TDM") every test.
I've got some error saving this files:
23   19:15:34 Error:
     Error while executing "DATASAVE("Brake_1231")" command
     Error type: ACCESS VIOLATION
     Error address: 00009E81
     Module name:kernel32.dll
24   19:15:34 Error:
     Error in <Rumore.VBS> (Line: 234, Column: 5):
     Error while executing "DATASAVE("Brake_1231")" command
     Error type: ACCESS VIOLATION
     Error address: 00009E81
     Module name:kernel32.dll
25   19:16:08 Error:
     Error while executing "" command
     Error type: ACCESS VIOLATION
     Error address: 000631BA
     Module name:gfsdesk.DLL

Sometimes also DIAdem crash and in the EventViewer there are this errors (the PC where run the program is in spanish):
Aplicación con errores: diadem.exe, versión: 10.0.0.2658, módulo con error:
mfc71u.dll, versión 7.10.3077.0, dirección de error 0x00023fee.
or
Aplicación con errores: diadem.exe, versión: 10.0.0.2541, módulo con error:
mfc71u.dll, versión 7.10.3077.0, dirección de error 0x00023fee.

Someone can help me ?

Thanks

[Brad_Turpin]

Hi MicheleS,

I don't know what's causing those errors with the DataSave() command, and I've asked R&D to comment on them.  However, the DataSave() command creates a *.DAT file, the old DIAdem standard file format.  If you want to create a "BRAKE_#.TDM" file after running your DIAdem analysis, then you need to instead use the DataFileSave() command.

Let us know if that also gives you errors,
Brad Turpin
DIAdem Product Support Engineer
National Instruments

[MicheleS]

Hi Brad, sorry but I've done a mistake: the files Brake_# are .DAT; I use another file Result.TDM where I put one line, with some elaborated data,  each Brake I analize. Sometimes DIAdem can't save also this file.

Thanks

[Brad_Turpin]

 MicheleS,

R&D has no idea what this is or why it is happening.  We need to figure out how to reproduce this error on an NI computer in order to make any progress here.  Anything you can send over-- data files, VBScripts, etc. which would help us reproduce this effect would be very helpful.

Regards,
Brad Turpin
DIAdem Product Support Engineer
National Instruments

[giuna]

Hi Brad, what about this CAR 3UC2FENK? Do you think that it can help us to resolve the problem? THANKS Giuseppe

[Twigeater]

Hello MicheleS! Hello Brad!

In the past I ran several times into the same strange error messages. The DATASAVE AV was never the reason, but it was always the symptom for a corrupt memory content. In my case it was caused by extension DLLs (GPI) I used (and developed).

I recommend to find the reason for the 'mfc71u.dll' AV.

Matthias

[Brad_Turpin]

Hi All,

I looked up Giuseppe's CAR, and a similar error occurs when the following GPI-DLL has been added to DIAdem: "GFSSPID8.DLL".  In this case the GPI-DLL needed a Borland DLL that was sometimes not registered on the computer.  Have you added this DLL?  Have you added any other GPI-DLLs to your DIAdem?

Does anyone know what this DLL does?  Is it a DAC-driver?

Brad Turpin
DIAdem Product Support Engineer
National Instruments

[MicheleS]

Hi, thanks at all for your answers!!!

Brad, I'm working on a Script that can be run "lonely"; I'll send you.

Sorry but what's CAR ???

I've look at the GPI extension: there are only the standard GPI loaded.

Have a good week end

[Brad_Turpin]

Hi Michele,

A "CAR" is a Corrective Action Request, otherwise known as a bug report.  We have an internal database at NI for tracking reported bugs and the solutions implemented to fix them.  What's a "lonely" script?

Brad Turpin
DIAdem Product Support Engineer
National Instruments

[MicheleS]

Hi Brad and Giuna,
could you give me your mail address and I send you the script. Sorry but I prefer don't insert my program in the forum.
Thanks