Overnight I finally got the crash to happen on my main development system.
This system is Windows XP Professional Service Pack 1 + all latest patches. All the other systems were Windows 2000 Server. Component Prog ID: 0[ODBC][F:\Program Files\SAPDB\ODBC73\sqlod32.dll] Method Name: IDispenserDriver::CreateResource Process Name: aspnet_wp.exe Exception: C0000005 Address: 0x043FB9CF Call Stack: sqlod32! + 0x4B9CF sqlod32! + 0x855F0 ! + 0x45574550d This was again stress testing my full web application in a endless loop. Once this crash happened, all types of calls to SAPDB are reporting socket problems. Still looking like some resource leak... Stephen -----Original Message----- From: Stephen Gutknecht (SAPDB) [mailto:[EMAIL PROTECTED]] Sent: Friday, October 04, 2002 1:54 AM To: '[EMAIL PROTECTED]' Subject: Win32 ODBC driver 7.0.3.28 crash in sqlod32.dll Is anyone able to help me track down where in the driver code this crash is being encountered? I'm using the latest ODBC driver on Windows 2000 SP3. Running ASP.NET application. I get this crash about every 24 hours on both of our production servers. Both of my production servers produce the following error from COM+ which is what ASP.NET is using to interface with the ODBC driver: ==== START server 1 and server 2 error ======= 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][E:\Program Files\SAPDB\ODBC73\sqlod32.dll] Method Name: IDispenserDriver::CreateResource Process Name: aspnet_wp.exe The serious nature of this error has caused the process to terminate. Exception: C0000005 Address: 0x0F0FB9CF Call Stack: sqlod32 + 0x4B9CF sqlod32 + 0x855F0 + 0xCD6D31F4 ==== END server 1 and server 2 error ======= I've finally been able to reproduce a crash by using a web simulator on one of my test machines. For some odd reason, I get a different version of the error message: ==== START test machine error ===== 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][E:\Program Files\SAPDB\ODBC73\sqlod32.dll] Method Name: IDispenserDriver::ResetResource Process Name: aspnet_wp.exe The serious nature of this error has caused the process to terminate. Exception: C0000005 Address: 0x1F7D34C5 Call Stack: odbc32!CursorLibTransact + 0x40AF odbc32!SQLGetConnectOption + 0x964 COMSVCS!DispManGetContext(unsigned long *,unsigned long *) + 0xDDD COMSVCS!DispManGetContext(unsigned long *,unsigned long *) + 0x2633 ==== END test machine error ==== >From the looks of it, I'm running into TWO different crashes? This 2nd crash, on my test machine, seems to happen in a regular pattern. I run a web simulator that goes through my web site and executes 1 SQL UPDATE and about 15 SQL SELECT statements. It does this in a loop 1000 times, and the crash happens about 5 times in that loop. Sure seems like a leak of some sort in the driver... As the crash happens about every 4 minutes while the loop is running. Thomas Koetter: On my test system I replaced the SQLOD32.DLL with the larger debug version you provided, but the crash response message did not change. Is there any way we can track these offset references back to where in the driver code the problem is having problems? Stephen Gutknecht Renton, Washington USA _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
