MySQL Bugs: #6011: myODBC driver crash

Bug #6011	myODBC driver crash
Submitted:	11 Oct 2004 8:17	Modified:	11 Oct 2004 12:05
Reporter:	Tom Sommer	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	3.51.9	OS:	Microsoft Windows (Windows 2003, Web Edition)
Assigned to:		CPU Architecture:	Any

Description:
The myODBC driver on our hosting servers have begun to crash terribly every 4 hours or so, each with this log entry the event log:

Component Prog ID: 0[ODBC][Env 2505538]
Method Name: IDispenserDriver::CreateResource
Process Name: w3wp.exe
Exception: C0000005
Address: 0x77F470FE
Call Stack: 
ntdll!RtlFreeHeap + 0xa19
myodbc3!_DllMainCRTStartup + 0x30d

Webpages using the driver will report: "Catastrophic failure"

How to repeat:
Unknown

Suggested fix:
Our current fix is to simply restart the Internet Information Service, however the driver will crash again a few hours later

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Can't tell anything by the output from the event log?

Could this be caused by the driver being added as both "mysql" and "MySQL ODBC 3.51 Driver" in the ODBC administrator's the "Drivers" tab?
The two instances appear exactly the same in all other fields, except the "name" field

Can you tell me the MS Driver Manager Version?

Is it to be gotten possible a Driver-Manager trace, 
only part with fails?

It is very important, if you can tell us how to repeat this BUG!

How is the situation if the driver will crash ?
They are to many open Connections/Statements (handles)?

Of course I cannot provide a way of reproducing, this is a shared hosting server - I have no way of knowing under which cercumstanses the problem occurs, all I can see in my event log is these two entries showing up when the driver crashes:

-----------------------------------------
Event Type:	Error
Event Source:	Application Error
Event Category:	(100)
Event ID:	1000
Date:		17-10-2004
Time:		18:25:32
User:		N/A
Computer:	NT1
Description:
Faulting application w3wp.exe, version 6.0.3790.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x000117de.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 77 33 77   ure  w3w
0018: 70 2e 65 78 65 20 36 2e   p.exe 6.
0020: 30 2e 33 37 39 30 2e 30   0.3790.0
0028: 20 69 6e 20 6e 74 64 6c    in ntdl
0030: 6c 2e 64 6c 6c 20 35 2e   l.dll 5.
0038: 32 2e 33 37 39 30 2e 30   2.3790.0
0040: 20 61 74 20 6f 66 66 73    at offs
0048: 65 74 20 30 30 30 31 31   et 00011
0050: 37 64 65                  7de     

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

-----------------------------------------
Event Type:	Error
Event Source:	COM+
Event Category:	Unknown
Event ID:	4786
Date:		17-10-2004
Time:		18:25:32
User:		N/A
Computer:	NT1
Description:
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 4f74848]
Method Name: IDispenserDriver::CreateResource
Process Name: w3wp.exe
Exception: C0000005
Address: 0x77F517DE
Call Stack: 
ntdll!RtlReAllocateHeap + 0x2123
ntdll!RtlAllocateHeap + 0x344
myodbc3!_DllMainCRTStartup + 0x346

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------

i've had the same exact problem happen- has anyone found a cause and/or fix here?

here are the event log details:

====================================================================== 
Event Type: Error 
Event Source: Application Error 
Event Category: (100) 
Event ID: 1000 
Date: 10/30/2004 
Time: 11:50:05 PM 
User: N/A 
Computer: WIN 
Description: 
Faulting application w3wp.exe, version 6.0.3790.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x000070fe. 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. 
Data: 
0000: 41 70 70 6c 69 63 61 74 Applicat 
0008: 69 6f 6e 20 46 61 69 6c ion Fail 
0010: 75 72 65 20 20 77 33 77 ure w3w 
0018: 70 2e 65 78 65 20 36 2e p.exe 6. 
0020: 30 2e 33 37 39 30 2e 30 0.3790.0 
0028: 20 69 6e 20 6e 74 64 6c in ntdl 
0030: 6c 2e 64 6c 6c 20 35 2e l.dll 5. 
0038: 32 2e 33 37 39 30 2e 30 2.3790.0 
0040: 20 61 74 20 6f 66 66 73 at offs 
0048: 65 74 20 30 30 30 30 37 et 00007 
0050: 30 66 65 0fe 

======================================================================== 

and also this: 

========================================================================= 
Event Type: Error 
Event Source: COM+ 
Event Category: Unknown 
Event ID: 4786 
Date: 10/30/2004 
Time: 11:50:05 PM 
User: N/A 
Computer: WIN 
Description: 
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: 1[ODBC][Env c6d3068] 
Method Name: IDispenserDriver::CreateResource 
Process Name: w3wp.exe 
Exception: C0000005 
Address: 0x77F470FE 
Call Stack: 
ntdll!RtlFreeHeap + 0xa19 
myodbc3! + 0x1e837 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. 
======================================================================

We are experiencing this problem also.  We can't really give any extra info than what's being provided.  This error will occur randomly.  Sometimes it takes 3-4 days.  Sometimes just 1 day.  But it seems like it's happening to enough people that somebody should be working with people to figure out this problem.  The error from windows says to contact the manufacturer and we're told you need more info.  But if we knew the exact cause we'd tell you.  It sounds like a resource leak based on everything we've seen.

Hi,

We have a similar problem. We are using a newer version 3.51.10.
Any progress?

Our setup:
Windows 2003 server
MyOdbc 3.51.10
Server 4.1.10a-nt-log

Here is the dump:

Event Type:	Information
Event Source:	Application Error
Event Category:	(100)
Event ID:	1004
Date:		4/6/2005
Time:		6:24:18 PM
User:		N/A
Description:
Reporting queued error: faulting application w3wp.exe, version 6.0.3790.0, faulting module myodbc3.dll, version 3.51.10.0, fault address 0x000164ab.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 77 33 77   ure  w3w
0018: 70 2e 65 78 65 20 36 2e   p.exe 6.
0020: 30 2e 33 37 39 30 2e 30   0.3790.0
0028: 20 69 6e 20 6d 79 6f 64    in myod
0030: 62 63 33 2e 64 6c 6c 20   bc3.dll 
0038: 33 2e 35 31 2e 31 30 2e   3.51.10.
0040: 30 20 61 74 20 6f 66 66   0 at off
0048: 73 65 74 20 30 30 30 31   set 0001
0050: 36 34 61 62               64ab    

Thanks,
Pete Fleming

We, too, are having the same problem. Does anyone have an idea on this??

[June 07, 2005]  This exact problem began for me across multiple shared hosting servers immediately after Windows 2003 SP1 was installed.  Note that IIS is running in 'Worker Process Application Mode', MyODBC 3.51, and this problem does not happen on my servers with the ntdll.dll prior to the SP1 update to 2003 server.

The function the worker process intermittantly crashes on is 'ntdll!RtlAllocateHeap'.  Here is a stack trace of that crash.

 # ChildEBP RetAddr  
00 00d3fed0 77bbcfdb ntdll!RtlAllocateHeap+0x358
01 00d3fee4 77bba995 msvcrt!_heap_alloc+0x26
02 00d3fef8 64710275 msvcrt!operator new+0x24
03 00d3ff14 647103d0 IISUTIL!IPM_MESSAGE_IMP::CreateMessage+0x1c
04 00d3ff3c 5a361cf3 IISUTIL!IPM_MESSAGE_PIPE::WriteMessage+0x5e
05 00d3ff5c 5a3024de w3dt!WP_IPM::HandlePing+0x59
06 00d3ff8c 5a3026bc W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x73
07 00d3ffa0 5a301db9 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x24
08 00d3ffb8 77e66063 W3TP!THREAD_MANAGER::ThreadManagerThread+0x39
09 00d3ffec 00000000 kernel32!BaseThreadStart+0x34

Any help on this would be greatly appreciated, as I would like to use 2003 SP1.

We have a similar problem in an Veritas Cluster enviroment, also with Win2003SP1. 

The error could be an access violation, actualy independent of the aplication.exe.

For those of you with an easier access to a single server; Could you try to add a  HOTFIX from Microsoft? And, return your status?

http://support.microsoft.com/?kbid=890744

I have similar problem with myODBC 3.51.11-2 and MySQL 4.0.26 (or 5.0.13) with Windows Server 2003 SP1.

I have two servers, one with mysql server and other with web pages using asp.

I has changed all my hosts to access my mysql server by direct IP (192.168.1.50 for example, or 127.0.0.1 for localhost) and the problem has solved.

After change my odbc don't more crashing.

I've pinpointed an error with the exact same results by passing a System.Null by Parameter for a char(X) field.  The first time gives you a memory access error - the second time it kills the MyODBC driver and you must restart IIS.