Hello all,

I recently updated to the latest SAPDB ODBC driver 7.04.03.  I am running
Windows 2000 Server SP3.  ASP.net 1.0 and ODBC.net 1.0, with latest SP2
service packs.  With the older driver we had a crash about every 24 hours on
both our sites.  With the new 7.4 driver, we are having the crash every 8
hours!  This is on multiple servers, all installed from scratch (not cloned
installs).

 === error recorded by ASP.NET ===
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][E:\Program Files\SAPDB\ODBC74\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: 0x0FE933FC
Call Stack: 
sqlod32 + 0x533FC
sqlod32 + 0x54EB1
sqlod32 + 0x3DE56
sqlod32!Ordinal997 + 0xD1B1
sqlod32!SQLConnectW + 0x287
sqlod32!SQLDriverConnectW + 0x385
odbc32!SQLDriverConnectW + 0x285
odbc32!SQLGetConnectOption + 0xE42
COMSVCS!DispManGetContext(unsigned long *,unsigned long *) + 0xB27
COMSVCS!DispManGetContext(unsigned long *,unsigned long *) + 0x163F
odbc32 + 0x2D1A8
  == end of error ===

This is a production problem for us.

Last round of this problem, Thomas Koetter @ SAP sent me a debug version of
sqlod32.dll to better track down the problem.  However, the debug driver
required that you answer a GUI dialog prompt.  The GUI prompt can not be
answered in ASP.NET process context  (SYSTEM).  I have asked repeatedly to
have a fix for this issue (debug driver without prompt).  After two months
of asking I finally gave up.  I am now asking again, as the crash is still
present in the latest release of the 7.4 driver.

The problem appears to be related to socket / network transport to a remote
SAPDB server.  Turning off connection pooling makes the problem worse.

Note to anyone using Win32:  Every time you install a new ODBC driver on
Win32, make sure you check the Connection Pooling setting.  We had
connection pooling enabled on 7.3 driver, but the 7.4 driver is "new" and
the default is off.  In other words, settings are not inherited when you
upgrade from 7.3 to 7.4 on the ODBC driver.

  Stephen Gutknecht
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to