Ok, then send it to my e-mail which is entered in this post.
Thank you, Tim.


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Tomas,

<< Sorry but no, could you try one more time, please this time send to
tomazaz @ gmail . com >>

GMail won't accept an attachment for your account.

--
Tim Young
Elevate Software
www.elevatesoft.com

Let me know when you will send drivers, thank you.

Tomas

Tomas,

<< Ok, then send it to my e-mail which is entered in this post. >>

I already did, and you said that you never received it, yet we did not
receive a bounce notification here from our mail server.  Is your mail
server stripping out attachments at all ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Ok, can we try this, you upload drivers to your site and send us link to it by e-mail.
I don't know is this possible but also you could add these trial drivers to my elevatesoft control panel,
my username is Tomas Rutkauskas

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Tomas,

<< Ok, then send it to my e-mail which is entered in this post. >>

I already did, and you said that you never received it, yet we did not
receive a bounce notification here from our mail server.  Is your mail
server stripping out attachments at all ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tomas,

<< Ok, can we try this, you upload drivers to your site and send us link to
it by e-mail. I don't know is this possible but also you could add these
trial drivers to my elevatesoft control panel, my username is Tomas
Rutkauskas >>

I'll make them available in the Customers area for your login.  Tell me when
you've got them because I'll need to remove them.

--
Tim Young
Elevate Software
www.elevatesoft.com

I got it, thank you.

We get an Event ID 1000 followed by an Event ID 4786

We're using:
Windows 2003 Server Standard Edition SP2
IIS 6.0
dbsrvr.exe 4.22.0.3
dbodbc.dll 4.22.0.3 (installed as a service)
Connection pooling is off.  CPTimeout not set in the registry.
Delphi 2006 for ASP.NET (v1.1.4322)
.NET ODBCConnection objects
ConnectionString:
ConnectionType=Remote;DRIVER=DBISAM 4 ODBC
Driver;CatalogName=TEST;RemoteIPAddress=127.0.0.1;RemotePort=12005;UID=xxx;PWD=yyy

IIS hangs unpredictably within our application.  Sometimes the user fills out the form 3 times
before IIS hangs.  Other times, it hangs before the 1st form is completed.  Hanging is
always accompanied
by the same Event ID 4786 error pointing to ODBC.  IIS hangs until the ApplicationPool is
recycled.

On the one hand, our web application is a bit wasteful of ODBC connections, using new
sessions as
the user progresses through the form instead of closing old sessions during each postback.  
I counted 15 sessions in srvadmin as I filled out the form.  We will refactor this in the
near future
to either reuse the same ODBCConnection, or ensure that any opened connection is also
closed so
they don't stack up.

However, as inefficient as the present code may be, we have another server where the same
build
does not generate the Event ID errors.  The only difference between the 2 servers that we
notice is
that one is on Win2k3 SP1 (works fine), and the other is on Win2k3 SP2 (event ID errors).

I'm worried that, even though we plan to streamline the code, doing that may not reveal
the true cause of
the event ID 4786 error.  And if letting those ODBC connections stack up is the main cause
of the errors,
that still doesn't explain why the same behavior is permitted on the SP1 server without
triggering the
Event ID errrors.

I'm aware of Microsoft's article http://support.microsoft.com/kb/906092 which recommends
upgrading to
SP2.  In our circumstance, every SP2 server hangs, while our SP1 server does not.

Do you see any clues from what I describe, or from the following EventID error transcript
(1000 followed by 4786)?  

I would be happy to provide more information if that would help.

Best regards,
Chris


Event Type:   Error
Event Source:   Application Error
Event Category:   (100)
Event ID:   1000
Date:      10/23/2007
Time:      10:23:42 AM
User:      N/A
Computer:   IRS
Description:
Faulting application w3wp.exe, version 6.0.3790.3959, faulting module dbodbc.dll, version
4.22.0.3, fault address 0x0000306c.

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 33   0.3790.3
0028: 39 35 39 20 69 6e 20 64   959 in d
0030: 62 6f 64 62 63 2e 64 6c   bodbc.dl
0038: 6c 20 34 2e 32 32 2e 30   l 4.22.0
0040: 2e 33 20 61 74 20 6f 66   .3 at of
0048: 66 73 65 74 20 30 30 30   fset 000
0050: 30 33 30 36 63            0306c   

Event Type:   Error
Event Source:   COM+
Event Category:   Unknown
Event ID:   4786
Date:      10/23/2007
Time:      10:23:42 AM
User:      N/A
Computer:   IRS
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: 7[ODBC][Env 18672298]
Method Name: IDispenserDriver::DestroyResource
Process Name: w3wp.exe
Exception: C0000005
Address: 0x1895306C
Call Stack:
dbodbc! + 0x306c
odbc32!SQLDriverConnectW + 0xa2f
odbc32!SQLDisconnect + 0x434
odbc32!SQLConnectA + 0x17be
comsvcs!DispManGetContext + 0xcb6
comsvcs!DispManGetContext + 0xf73
comsvcs!DispManGetContext + 0x206a
odbc32!SQLConnectA + 0x1fa0
odbc32!SQLConnectA + 0x28d1
odbc32!SQLSetEnvAttr + 0x23b5
+ 0x179e106e
+ 0x19aa6c3b
mscorsvr!GetAssemblyMDImport + 0x1e990
mscorsvr!GetAssemblyMDImport + 0x1ea52
mscorsvr!GetAssemblyMDImport + 0x1e152
mscorsvr!GetAssemblyMDImport + 0x1ed54
mscorsvr!Ordinal78 + 0x1f976
mscorsvr!GetAssemblyMDImport + 0x1ed27
mscorsvr!GetAssemblyMDImport + 0x1e29b
mscorsvr!CoInitializeCor + 0x798b
kernel32!GetModuleHandleA + 0xdf


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

Chris,

<< Do you see any clues from what I describe, or from the following EventID
error transcript (1000 followed by 4786)? >>

I'm not sure what the issue could be, but it sure seems like something wonky
in the COM layer.   The interesting thing is that I didn't know that the
ODBC.NET data provider used COM at all.  I thought that the .NET layer made
direct DLL calls to the driver manager.

I would bet that the DispManGetContext call has something to do with this
issue:

http://www.google.com/search?hl=en&safe=off&rls=com.microsoft%3Aen-us%3AIE-SearchBox&rlz=1I7GGIC&q=DispManGetContext+&btnG=Search

--
Tim Young
Elevate Software
www.elevatesoft.com

I called Microsoft's TechNet Tech Support and they helped me run the Debug
Diagnostic Tool (DebugDiag).  I added a Crash rule for all IIS/COM+
related processes for Exception C0000005 (Access Violation) and created a
Full userdump file.  We then opened the .dmp file with DebugDiag but
without Elevate's debug symbols, it's hard to reveal the function call.

The tech at Microsoft said if I provide Elevate developers with a copy of the
userdump file, they'll be able to match it up with Elevate's debug symbols
and learn which function was being called at the time of the Access Violation.

The .dmp file is rather large (90MB, zipped down to 26 MB), so I'll send a private email
with a link to it.

I'm including some of that crash analysis text below:

I believe at one point I was also getting the same error with v 4.25b5.  If we get to that
point,
I may try to provide similar userdump files with that version.

Thanks
Chris


Report for iis-crash.dmp
Type of Analysis Performed   Crash Analysis
Machine Name   IRS
Operating System   Windows Server 2003 Service Pack 2
Number Of Processors   8
Process ID   3776
Process Image   c:\WINDOWS\system32\inetsrv\w3wp.exe
System Up-Time   7 day(s) 03:24:40
Process Up-Time   00:00:11


Thread 20 - System ID 652
Entry point   mscorsvr!ThreadpoolMgr::intermediateThreadProc
Create time   10/26/2007 1:28:51 PM
Time spent in user mode   0 Days 0:0:1.156
Time spent in kernel mode   0 Days 0:0:0.109






Function     Arg 1     Arg 2     Arg 3   Source
dbodbc+14d023     00000000     00000004     18482ff0    
dbodbc!SQLGetInfo+2c     18b50308     000006d6     0203ee80    
odbc32!CDispenser::CreateResource+298     18482720     00000000     00000000    
comsvcs!CHolder::SafeDispenserDriver::CreateResource+25     1690c01c     18482340    
0203ef6c    
comsvcs!CHolder::AllocResource+328     00000000     18482340     0203ef6c    
odbc32!CDispenser::TryAllocResource+49     18482720     18482340     0203ef6c    
odbc32!CDispenser::GetActiveConnection+31     18482720     18482ff0     02030000    
odbc32!GetActiveConn+7e     184826e0     00000000     0203fb20    
odbc32!SQLDriverConnectW+9df     18482340     00000000     067e9f54    
0x17a00783     067ec2e4     067ecb1c     183d36cc    
0x183d3885     00000001     067ecb7c     00000000    
0x183d3635     067ecb7c     00000000     00000000    




DBODBC+14D023WARNING - DebugDiag was not able to locate debug symbols for dbodbc.dll, so
the information below may be incomplete.



In iis-crash.dmp the assembly instruction at dbodbc+14d023 in
C:\dbisam\odbc\std\ver4\lib\dbodbc\dbodbc.dll from Elevate Software has caused an access
violation exception (0xC0000005) when trying to write to memory location 0x00000000 on
thread 20

Module Information
Image Name: C:\dbisam\odbc\std\ver4\lib\dbodbc\dbodbc.dll   Symbol Type:  Export
Base address: 0x18760000   Time Stamp:  Fri Jun 19 17:22:17 1992  
Checksum: 0x00000000   Comments:   
COM DLL: False   Company Name:  Elevate Software
ISAPIExtension: False   File Description:  DBISAM 4 ODBC Driver
ISAPIFilter: False   File Version:  4.22 Build 3
Managed DLL: False   Internal Name:  DBISAM 4 ODBC Driver
VB DLL: False   Legal Copyright:  Copyright © 2005 Elevate Software, Inc.
Loaded Image Name:  dbodbc.dll   Legal Trademarks:   
Mapped Image Name:     Original filename:  dbodbc.dll
Module name:  dbodbc   Private Build:   
Single Threaded:  False   Product Name:  DBISAM 4 ODBC Driver
Module Size:  1.69 MBytes   Product Version:  4.22
Symbol File Name:  dbodbc.dll   Special Build:  &

Resolved via email - it was an issue with not using Dispose on the ODBC.NET
objects as necessary:

http://www.elevatesoft.com/dbisam4odbc_application_compatibility.htm

under "Microsoft Visual Studio .NET".

--
Tim Young
Elevate Software
www.elevatesoft.com