ASP page hangs on opening connection object to mdb database

[Mendel Nemanov]

I have a number of websites running against several Access
databases.

Every once in a while (under relatively heavy load, but
rarely more than 1 asp request per second) asp pages would
stop responding when it gets to opening a recordset
connection.

I am returning a connection object from this function:
Function conn()
if isEmpty(myConn) then
set myConn = Server.CreateObject
("ADODB.Connection")

myConn.open "Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=" & server.mappath("data\database.mdb")
End if
set conn = myConn
End Function

There is no error message, the page just does not produce
any output. if I turn off buffering I get the content up
to the opening connection and that's it.

Pages which do not reference the database continue to
function.

Server is Windows Server 2003 and IIS6 has an option to
recycle the application pool (I have my websites divided
into several application pools) when I recycle the pages
begin functioning immediately. 90 seconds after a recycle,
the even log shows that the application pool with Process
id of xxx exceeded time limits during shutdown. The fact
that the pages begin function immediately even though it
takes another 90 seconds for the old application pool to
close suggests that this is some in memory problem with
ADO/MDAC/OLEDB.JET and not a lock on the actual mdb.

These websites ran previously on a Windows NT4 server for
3 years and I never had this problem. the problem only
showed up after transfering to a new (not an upgrade)
clean install of server 2003

Thank you
Mendel Nemanov
Spotlight Design

[Mendel Nemanov]

I've found references to KB Article 838306 which discuss
this problem, but I can't find the actual KB article. does
anyone have a copy of it. (did microsoft pull the article?)

Mendel

>-----Original Message-----
>I have a number of websites running against several

Access

>databases.
>
>Every once in a while (under relatively heavy load, but
>rarely more than 1 asp request per second) asp pages

would

>stop responding when it gets to opening a recordset
>connection.
>
>I am returning a connection object from this function:
>Function conn()
> if isEmpty(myConn) then
> set myConn = Server.CreateObject
>("ADODB.Connection")
>
> myConn.open "Provider=Microsoft.Jet.OLEDB.4.0;Data
>Source=" & server.mappath("data\database.mdb")
> End if
> set conn = myConn
>End Function
>
>There is no error message, the page just does not produce
>any output. if I turn off buffering I get the content up
>to the opening connection and that's it.
>
>Pages which do not reference the database continue to
>function.
>
>Server is Windows Server 2003 and IIS6 has an option to
>recycle the application pool (I have my websites divided
>into several application pools) when I recycle the pages
>begin functioning immediately. 90 seconds after a

recycle,

>the even log shows that the application pool with Process
>id of xxx exceeded time limits during shutdown. The fact
>that the pages begin function immediately even though it
>takes another 90 seconds for the old application pool to
>close suggests that this is some in memory problem with
>ADO/MDAC/OLEDB.JET and not a lock on the actual mdb.
>
>These websites ran previously on a Windows NT4 server for
>3 years and I never had this problem. the problem only
>showed up after transfering to a new (not an upgrade)
>clean install of server 2003
>
>Thank you
>Mendel Nemanov
>Spotlight Design
>.
>