From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

APPCRASH StackHash_0a9e

Hi together,

I'm struggling since hours with crashing of my LabView Application on a W7 32bit maschine.
We use this application since years on WXP and since weeks on W7 maschines - without problems.

The executable is compiled on a W7 64 bit maschine (english lang.).
The problem occurs very often on a W7 32bit maschine (german lang.).
The problem seems to be triggerable by opening the windows explorer. But over night the crash comes without doing anything.

LabView Version is 2012 .0.1.f5 SP1  32bit

Does anybody has an idea?

Many Thanks, Thomas.




Here the crash logs:

Problemsignatur:
  Problemereignisname:    APPCRASH
  Anwendungsname:    UploadResults.exe
  Anwendungsversion:    1.0.0.0
  Anwendungszeitstempel:    50d22f24
  Fehlermodulname:    StackHash_0a9e
  Fehlermodulversion:    0.0.0.0
  Fehlermodulzeitstempel:    00000000
  Ausnahmecode:    c0000005
  Ausnahmeoffset:    05d68650
  Betriebsystemversion:    6.1.7601.2.1.0.256.48
  Gebietsschema-ID:    1031
  Zusatzinformation 1:    0a9e
  Zusatzinformation 2:    0a9e372d3b4ad19135b953a78882e789
  Zusatzinformation 3:    0a9e
  Zusatzinformation 4:    0a9e372d3b4ad19135b953a78882e789

Lesen Sie unsere Datenschutzbestimmungen online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407

Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
  C:\Windows\system32\de-DE\erofflps.txt

 
 
 
  Problemsignatur:
  Problemereignisname:    APPCRASH
  Anwendungsname:    UploadResults.exe
  Anwendungsversion:    1.0.0.0
  Anwendungszeitstempel:    50d22f24
  Fehlermodulname:    sqlod32.dll_unloaded
  Fehlermodulversion:    0.0.0.0
  Fehlermodulzeitstempel:    403e0864
  Ausnahmecode:    c0000005
  Ausnahmeoffset:    06768650
  Betriebsystemversion:    6.1.7601.2.1.0.256.48
  Gebietsschema-ID:    1031
  Zusatzinformation 1:    0a9e
  Zusatzinformation 2:    0a9e372d3b4ad19135b953a78882e789
  Zusatzinformation 3:    0a9e
  Zusatzinformation 4:    0a9e372d3b4ad19135b953a78882e789

Lesen Sie unsere Datenschutzbestimmungen online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407

Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
  C:\Windows\system32\de-DE\erofflps.txt

0 Kudos
Message 1 of 8
(9,503 Views)

Hello Thomas! 

 

Would you mind attaching the actually crash log .txt file? 

 

0 Kudos
Message 2 of 8
(9,472 Views)

Hi Nik,

 

attached the log files.

 

Thanks for help, Thomas.

 

 

0 Kudos
Message 3 of 8
(9,460 Views)

Thomas,

 

Can you try running your executable on other Windows 7 machines and see if the executable crashes on these computers as well? 

 

0 Kudos
Message 4 of 8
(9,432 Views)

Hi Nik,

 

same on other W7 machines.

 

Thx. Thomas.

0 Kudos
Message 5 of 8
(9,415 Views)

I found the part in the program which seems to be the reason but ....

 

The suspicious program part is a simple select statement on a SAPDB database server.

Open DB, select, fetch, free, close DB.

 

If I delete this program part, the app does NOT crash.

If I enable it and make perform the select statement on a local MS Access database, the app does NOT crash.

Then I created a new exe only with the suspicious program part and a select on the SAB DB. And? The app does NOT crash.

 

Sorry, but I'm totally lost.

 

Does anybody has an idea?

0 Kudos
Message 6 of 8
(9,401 Views)
Try to see if there is an updated driver for the db. It should be an ole type. Also, the db should be opened once at the beginning and closed when the program ends.
Message 7 of 8
(9,382 Views)

Hi,

 

 

the problem is solved.

Long time ago I was triggered by our DB administrator to close the server DB immediately after SQL statement,

and open it again if any other SQL action is necessary. But that seems to be the reason for the crash.

 

So, the server SAP DB will be opened after app start and closed when the app closes.

 

 

Many thanks for this tipp, Thomas.

0 Kudos
Message 8 of 8
(9,325 Views)