sporatic error against SQL Server

Hi,

We have a client running our application against SQL Server 2000 (on same
box as web-server). After a few hours they start getting sporatic error
messages:

Microsoft OLE DB Provider for ODBC Drivers Error Code: -2147467259
Description: [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on
SQL_HANDLE_DBC failed SQLState: IM005 SQLState: IM005

Rebooting the server clears it up for a while.

We have numerous other clients running similar configurations with no
problems. I have had them verify that they are using TCP/IP and not Named
Pipes. The only thing I can find on Google is a reference to connection
pooling problems or running out of resources (I don't have the specs on
their server yet).

Can anyone point me toward some more information.

--
--Mark Schupp
Head of Development
Integrity eLearning
www.ielearning.com

Re: sporatic error against SQL Server

You are almost certainly leaking resources. One way to investigate, after
the app has been running for awhile, execute sp_who2 on the SQL server, to
get a feel for the number of un-closed connections. If the number of
connections grows progressively until SQL crashes, then you are not calling
cn.Close for each time you are calling cn.Open. (Just setting a connection
object to Nothing does not close it, and any time you do that to an open
connection, for which no other references are kept, you effectively leak a
connection.)

One other thing, you may want to try the SQL Server OLE DB provider
(SQLOLEDB) rather than using the OLE DB provider for ODBC, it tends to be
more capable and more robust.


-Mark




"Mark Schupp" wrote in message
news:upPrXLQJFHA.2728@TK2MSFTNGP09.phx.gbl...
> Hi,
>
> We have a client running our application against SQL Server 2000 (on same
> box as web-server). After a few hours they start getting sporatic error
> messages:
>
> Microsoft OLE DB Provider for ODBC Drivers Error Code: -2147467259
> Description: [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on
> SQL_HANDLE_DBC failed SQLState: IM005 SQLState: IM005
>
> Rebooting the server clears it up for a while.
>
> We have numerous other clients running similar configurations with no
> problems. I have had them verify that they are using TCP/IP and not Named
> Pipes. The only thing I can find on Google is a reference to connection
> pooling problems or running out of resources (I don't have the specs on
> their server yet).
>
> Can anyone point me toward some more information.
>
> --
> --Mark Schupp
> Head of Development
> Integrity eLearning
> www.ielearning.com
>
>