Bug #4268 ODBC crashes on Win2k3
Submitted: 24 Jun 2004 1:50 Modified: 30 May 2013 11:48
Reporter: Keith Farmer Email Updates:
Status: Closed Impact on me:
Category:Connector / ODBC Severity:S2 (Serious)
Version:MySQL ODBC 3.51 Driver OS:Microsoft Windows (Windows Server 2003)
Assigned to: CPU Architecture:Any

[24 Jun 2004 1:50] Keith Farmer
At seemingly random intervals -- generally several times per day -- the MyODBC driver faults, bringing down the ASP.NET worker process.  I've turned on logging, and nothing has yet shown up.

Unless this is resolved, I'll have to recommend moving the project to MSDE (the ByteFX driver's problems make it unsuitable).

The following is from the Application Event Log.  A collegue suspects it to be a bad pointer deallocation attempt?

The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below. 
Component Prog ID: 0[ODBC][Env 67914e8]
Method Name: IDispenserDriver::CreateResource
Process Name: w3wp.exe
Exception: C0000005
Address: 0x77F470FE
Call Stack: 
ntdll!RtlFreeHeap + 0xa19
myodbc3!_DllMainCRTStartup + 0x3af
myodbc3!_DllMainCRTStartup + 0x2a6

How to repeat:
No pattern noticed.
[4 Jul 2004 2:34] Miguel Solorzano
Can you provide a test case ? The information that you had provided
isn't enough for to repeat the behavior reported.

[14 Feb 2005 22:54] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[30 May 2013 11:48] Bogdan Degtyariov
I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.