Now I am getting this error after about 2hours of continuous connections (about 20 per
second) ~ 9000 connections. Less crippling, but still too often.

Hopefully I can restart the worker process if this happens, in the short term. However in
the long term, this app needs to run non-stop. with little down time (months, year(s)). If
you have any info, or can reproduce, it would be appreciated

Nick

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 22512a0]
Method Name: IDispenserDriver::CreateResource
Process Name: w3wp.exe
Exception: C0000005
Address: 0x0447EBFB
Call Stack:
dbodbc! + 0xfebfb
odbc32!SQLRowCount + 0xcd2
odbc32!SQLRowCount + 0xe1d
odbc32!SQLConnectA + 0x1006
comsvcs!DispManGetContext + 0xa3d

Nick,

<< Now I am getting this error after about 2hours of continuous connections
(about 20 per second) ~ 9000 connections. Less crippling, but still too
often.

Hopefully I can restart the worker process if this happens, in the short
term. However in the long term, this app needs to run non-stop. with little
down time (months, year(s)). If you have any info, or can reproduce, it
would be appreciated >>

So, the same operations occur for 2 hours, and then the ODBC driver AVs in
an SQLRowCount call ?  If that's the case, then it sounds external to me.
The SQLRowCount call is very simple, and the only way it would AV is if the
internal state of the ODBC driver was messed up due to a connection being
re-used across thread boundaries.  You aren't using connection pooling or
anything like that, correct ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Apologies for dropping this thread for so long. I have had other issues to look at. This
is now heading back up the priority list.

Any tips on how to ascertain this would be appreciated, however I have followed the
following DB article: http://support.microsoft.com/kb/189410/EN-US/ and the  CPTIMEOUT
keyvalue is not set. leading me to believe that connection pooling is not enabled.

Nick.

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

Nick,

<< Now I am getting this error after about 2hours of continuous connections
(about 20 per second) ~ 9000 connections. Less crippling, but still too
often.

Hopefully I can restart the worker process if this happens, in the short
term. However in the long term, this app needs to run non-stop. with little
down time (months, year(s)). If you have any info, or can reproduce, it
would be appreciated >>

So, the same operations occur for 2 hours, and then the ODBC driver AVs in
an SQLRowCount call ?  If that's the case, then it sounds external to me.
The SQLRowCount call is very simple, and the only way it would AV is if the
internal state of the ODBC driver was messed up due to a connection being
re-used across thread boundaries.  You aren't using connection pooling or
anything like that, correct ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Nick,

<< Any tips on how to ascertain this would be appreciated, however I have
followed the following DB article:
http://support.microsoft.com/kb/189410/EN-US/ and the  CPTIMEOUTkeyvalue is
not set. leading me to believe that connection pooling is not enabled. >>

Correct.

The only thing I can recommend at this time is for you to try and isolate
what portion of the code is causing the issue.  I don't know what your
application looks like or anything, so if you could send me a sample it
would help me at least get a feel for what you're trying to do.

--
Tim Young
Elevate Software
www.elevatesoft.com

OK,

I'll write up a simple test case & see if I can get it crashing...

Thanks for you reply.

Nick

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

Nick,

<< Any tips on how to ascertain this would be appreciated, however I have
followed the following DB article:
http://support.microsoft.com/kb/189410/EN-US/ and the  CPTIMEOUTkeyvalue is
not set. leading me to believe that connection pooling is not enabled. >>

Correct.

The only thing I can recommend at this time is for you to try and isolate
what portion of the code is causing the issue.  I don't know what your
application looks like or anything, so if you could send me a sample it
would help me at least get a feel for what you're trying to do.

--
Tim Young
Elevate Software
www.elevatesoft.com