Application crash by msado15.dll used by database toolkit

[aartjan]

I have a labview built application that runs continuously, doing periodic queries on a sql server database. I use the NI database toolkit for this. Recently I started noticing the application "vanishes". I opened the Windows evenviewer (eventvwr.msc) to find the following two errors:

1.
Application: GD6.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 67B2E409

2.
Faulting application name: GD6.exe, version: 6.3.8.1894, time stamp: 0x5ba06ff4
Faulting module name: msado15.dll, version: 10.0.18362.900, time stamp: 0x6437670b
Exception code: 0xc0000005
Fault offset: 0x0005e409
Faulting process id: 0x257c
Faulting application start time: 0x01d672fb1562e54f
Faulting application path: C:\Program Files (x86)\Gotcha Data\GD6.exe
Faulting module path: C:\Program Files (x86)\Common Files\System\ado\msado15.dll
Report Id: e351597d-a4bf-4d8a-a2e9-5fdbf62208ea
Faulting package full name:
Faulting package-relative application ID:

It has happened a couple of times now. I can deal with normal Labview errors, but I can't deal with errors that simply kill the whole application process. I found nothing on this website mentioning this DLL, although it is evidently a core library being used by the database toolkit.

Any suggestions how I can debug this?

An alternative connection method or other toolkit would also be a possible solution.

I did add a query recently to the application. This query runs many times before any one crash, but I did not experience any crashes before I started using that query.

[Aboughton]

Hi Aart-Jan,

I have taken a look, and the MS ADO15 is a Microsoft component although NI does use the DLL. The exception code which you get is an access violation for that DLL. My suggestion would be to ask on the Microsoft forums, as they are more likely to be able to help you out with this error. 

Searching on the Microsoft forums, you can see troubleshooting steps for the exception code c0000005 causing a crash, and Application Error (0xc0000005) although I am not sure how relevant they are. These posts suggest a corrupted Windows system file(s) may well be causing the issue.

I assume based on the information you have given me that if you can access the Microsoft .dll you will be able to prevent the crash from occurring, and I hope the Microsoft Forums can help you to find a solution. 

Many thanks,  

Alice 

[aartjan]

Alice, thank you for taking the time to look into this. I feel reluctant to venture into MS forums territory. I am a Labview guy after all.

I will try all other options first. One option I explored was to use a REST API instead of these old-fashioned database drivers. Unfortunately, AZURE PAAS SQLserver is completely cloud, but offers no HTTP API to query the database. You have to build it yourself.

I wish I could get rid of drivers altogether and work with web services only. I wonder which relational database ships with a REST interface by default.

[bobi]

Did you manage to resolve your problems? Because I have the same problem. 

Application crash with error in event viewer: 

Faulting module name: msado15.dll, version: 10.0.19041.746, time stamp: 0x3c89c0d2
Exception code: 0xc0000005
Fault offset: 0x000000000007b1d5
Faulting process ID: 0x2d14
Faulting application start time: 0x01d8a33b4464b30b

Best regards Bobi