ms access freezes iis

[sam]

once in a while, we get an access db that has a .ldb file
that can not be deleted. This either creates or is the
result of iis not being able to serve anymore asp pages.
Only solution is to restart either server or iis. any idea
what would cause this? win2k3, iis 6, pached, access 2000.

[Aaron Bertrand [MVP]]

Make sure you always close your recordsets and set them to nothing, and
close your connection objects and set them to nothing. Grab all of your
files that use ADODB.Connection and make sure that all objects created using
set are also set = nothing.

--
Aaron Bertrand
SQL Server MVP
[url]http://www.aspfaq.com/[/url]




"sam" <sshilo@hotmail.com> wrote in message
news:13d8b01c3c2c9$38658c20$a601280a@phx.gbl...

> once in a while, we get an access db that has a .ldb file
> that can not be deleted. This either creates or is the
> result of iis not being able to serve anymore asp pages.
> Only solution is to restart either server or iis. any idea
> what would cause this? win2k3, iis 6, pached, access 2000.

[sam]

Thanks Aaron, (I will make sure to do that).
Another bit of info. This happens randomly, so it can
happen twice within an hour, or twice a week. It the cause
was connections not being closed, wouldn't it take a while
for the limit to be reached before crashing again?

>-----Original Message-----
>Make sure you always close your recordsets and set them

to nothing, and

>close your connection objects and set them to nothing.

Grab all of your

>files that use ADODB.Connection and make sure that all

objects created using

>set are also set = nothing.
>
>--
>Aaron Bertrand
>SQL Server MVP
>[url]http://www.aspfaq.com/[/url]
>
>
>
>
>"sam" <sshilo@hotmail.com> wrote in message
>news:13d8b01c3c2c9$38658c20$a601280a@phx.gbl...

>> once in a while, we get an access db that has a .ldb

file

>> that can not be deleted. This either creates or is the
>> result of iis not being able to serve anymore asp pages.
>> Only solution is to restart either server or iis. any

idea

>> what would cause this? win2k3, iis 6, pached, access

2000.

>
>
>.
>

[Meelis Lilbok]

Maybe too many connections?
Move to SQL Server or MSDE ;o)


Mex



"sam" <sshilo@hotmail.com> wrote in message
news:13daf01c3c2cf$8ec32b80$a601280a@phx.gbl...

> Thanks Aaron, (I will make sure to do that).
> Another bit of info. This happens randomly, so it can
> happen twice within an hour, or twice a week. It the cause
> was connections not being closed, wouldn't it take a while
> for the limit to be reached before crashing again?
>
>
>

> >-----Original Message-----
> >Make sure you always close your recordsets and set them

> to nothing, and

> >close your connection objects and set them to nothing.

> Grab all of your

> >files that use ADODB.Connection and make sure that all

> objects created using

> >set are also set = nothing.
> >
> >--
> >Aaron Bertrand
> >SQL Server MVP
> >[url]http://www.aspfaq.com/[/url]
> >
> >
> >
> >
> >"sam" <sshilo@hotmail.com> wrote in message
> >news:13d8b01c3c2c9$38658c20$a601280a@phx.gbl...

> >> once in a while, we get an access db that has a .ldb

> file

> >> that can not be deleted. This either creates or is the
> >> result of iis not being able to serve anymore asp pages.
> >> Only solution is to restart either server or iis. any

> idea

> >> what would cause this? win2k3, iis 6, pached, access

> 2000.

> >
> >
> >.
> >

[Aaron Bertrand [MVP]]

> Another bit of info. This happens randomly, so it can

> happen twice within an hour, or twice a week. It the cause
> was connections not being closed, wouldn't it take a while
> for the limit to be reached before crashing again?

It could be as simple as two users "colliding" rather than a progressive
buildup...

Anyway, you know more about your app than I do... but this is certainly a
known issue with Access.

--
Aaron Bertrand
SQL Server MVP
[url]http://www.aspfaq.com/[/url]

[sam]

"but this is certainly a known issue with Access."

would moving to sql server solve the problem? or is making
sure all connections, recordsets, etc. are closed enough?

>-----Original Message-----

>> Another bit of info. This happens randomly, so it can
>> happen twice within an hour, or twice a week. It the

cause

>> was connections not being closed, wouldn't it take a

while

>> for the limit to be reached before crashing again?

>
>It could be as simple as two users "colliding" rather

than a progressive

>buildup...
>
>Anyway, you know more about your app than I do... but

this is certainly a

>known issue with Access.
>
>--
>Aaron Bertrand
>SQL Server MVP
>[url]http://www.aspfaq.com/[/url]
>
>
>.
>

[Aaron Bertrand [MVP]]

Moving to SQL Server will solve (or at least reduce) this issue. You will
also get many other benefits, such as performance, security, scalability,
etc.

[url]http://www.aspfaq.com/2195[/url]
[url]http://www.aspfaq.com/2214[/url]

If you have the ability to move, all the power to you. (Many people are
stuck with Access, without the money for SQL Server or the ability to
install the free MSDE on their server.)

However, regardless of which RDBMS you use, ALWAYS close your objects and
set them to nothing. This shouldn't be something you consider only because
it may be causing a problem; it is purely good programming practice.

[url]http://www.aspfaq.com/2435[/url]

--
Aaron Bertrand
SQL Server MVP
[url]http://www.aspfaq.com/[/url]




"sam" <sshilo@hotmail.com> wrote in message
news:030301c3c2d3$4e633b80$a501280a@phx.gbl...

> "but this is certainly a known issue with Access."
>
> would moving to sql server solve the problem? or is making
> sure all connections, recordsets, etc. are closed enough?
>
>
>

> >-----Original Message-----

> >> Another bit of info. This happens randomly, so it can
> >> happen twice within an hour, or twice a week. It the

> cause

> >> was connections not being closed, wouldn't it take a

> while

> >> for the limit to be reached before crashing again?

> >
> >It could be as simple as two users "colliding" rather

> than a progressive

> >buildup...
> >
> >Anyway, you know more about your app than I do... but

> this is certainly a

> >known issue with Access.
> >
> >--
> >Aaron Bertrand
> >SQL Server MVP
> >[url]http://www.aspfaq.com/[/url]
> >
> >
> >.
> >

[sam]

Since we have taken over the project, it is taking some
time cleaning up old code. We will do so and and then go
to SQL. One other question, is there a reason why this
problem would happen so much more with win2k3/iis6 than
win2k/iis5?

>-----Original Message-----
>Moving to SQL Server will solve (or at least reduce) this

issue. You will

>also get many other benefits, such as performance,

security, scalability,

>etc.
>
>[url]http://www.aspfaq.com/2195[/url]
>[url]http://www.aspfaq.com/2214[/url]
>
>If you have the ability to move, all the power to you.

(Many people are

>stuck with Access, without the money for SQL Server or

the ability to

>install the free MSDE on their server.)
>
>However, regardless of which RDBMS you use, ALWAYS close

your objects and

>set them to nothing. This shouldn't be something you

consider only because

>it may be causing a problem; it is purely good

programming practice.

>
>[url]http://www.aspfaq.com/2435[/url]
>
>--
>Aaron Bertrand
>SQL Server MVP
>[url]http://www.aspfaq.com/[/url]
>
>
>
>
>"sam" <sshilo@hotmail.com> wrote in message
>news:030301c3c2d3$4e633b80$a501280a@phx.gbl...

>> "but this is certainly a known issue with Access."
>>
>> would moving to sql server solve the problem? or is

making

>> sure all connections, recordsets, etc. are closed

enough?

>>
>>
>>

>> >-----Original Message-----
>> >> Another bit of info. This happens randomly, so it can
>> >> happen twice within an hour, or twice a week. It the

>> cause

>> >> was connections not being closed, wouldn't it take a

>> while

>> >> for the limit to be reached before crashing again?
>> >
>> >It could be as simple as two users "colliding" rather

>> than a progressive

>> >buildup...
>> >
>> >Anyway, you know more about your app than I do... but

>> this is certainly a

>> >known issue with Access.
>> >
>> >--
>> >Aaron Bertrand
>> >SQL Server MVP
>> >[url]http://www.aspfaq.com/[/url]
>> >
>> >
>> >.
>> >

>
>
>.
>

[Jimmy e]

I have the same problems, there is an bug in iis6 on win2003 with the
jet pack sp8!

Try to read the following urls:

[url]http://www.developersdex.com/asp/message.asp?p=592&r=3625064[/url]

[url]http://www.matrixreseller.com/forum/archive/index.php/t-6117[/url]


Jimmy


*** Sent via Developersdex [url]http://www.developersdex.com[/url] ***
Don't just participate in USENET...get rewarded for it!