Issue with ASP/IIS and remaining Access 2K lockfile .ldb

[Tom Kaminski [MVP]]

"Immanuel" <wetteraar@hotmail.com> wrote in message
news:2791C693-262A-4CBC-A382-5462D169167E@microsoft.com...

> Dear all,
>
> as you all know, IIS manages application protection (in/out-of process),

which in turn manages connection pooling. A way to empty the pool, is by
unloading the application protection.

>
> I have several ASP applications on a Win 2K server (IIS 5 web server) with

Access 2K back-end DB. Apparently, connections are not closed properly in
code (e.g. cn.Close set cn = nothing) because .ldb lockfiles remain.

>

I'm not sure that's true - I would suggest following-up in asp.general and
asp.db ...

--
Tom Kaminski IIS MVP
[url]http://www.iistoolshed.com/[/url] - tools, scripts, and utilities for running IIS
[url]http://mvp.support.microsoft.com/[/url]
[url]http://www.microsoft.com/windowsserver2003/community/centers/iis/[/url]

[Bob Barrows]

Tom Kaminski [MVP] wrote:

> "Immanuel" <wetteraar@hotmail.com> wrote in message
> news:2791C693-262A-4CBC-A382-5462D169167E@microsoft.com...

>> Dear all,
>>
>> as you all know, IIS manages application protection (in/out-of
>> process),

> which in turn manages connection pooling. A way to empty the pool, is
> by unloading the application protection.

>>
>> I have several ASP applications on a Win 2K server (IIS 5 web
>> server) with

> Access 2K back-end DB. Apparently, connections are not closed
> properly in code (e.g. cn.Close set cn = nothing) because .ldb
> lockfiles remain.

>>

>
> I'm not sure that's true - I would suggest following-up in
> asp.general and asp.db ...

If ldb files are remaining, it is usually because the last user in the
database does not have the authority to delete them. If the application is
running in its own process, then the user is the IWAM account, not the IUSR
account, so you need to be sure that the IWAM account has Change permissions
for the folder containing the database file, in addition to the IUSR
account. If using Integrated authentication, then the users need to have
those Change permissions.

FWIW, I would not be too concerned about emptying the pool: ADO does a good
job of managing that on its own.


Bob Barrows
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[Tom Kaminski [MVP]]

"Immanuel" <anonymous@discussions.microsoft.com> wrote in message
news:1FE4C4FE-5323-4322-A212-24C530A592BF@microsoft.com...

> Maybe I could re-phrase my problem like this:
>
> I need to be able to delete all open ldb files (thus unlock the Access 2K

DB's used by the ASP applications) with a VB 6 batch program, without having
to lookup all these ldb files.

>
> I'm hoping there is a way to get programmatically to the connection pool

managed by IIS and emptying this pool would delete all open ldb files, but
this is a hunch.

>
> If this could be realised, I think I'll make the code public, because I've

seen many others in the forums asking for a way to get rid of ldb files ;-)

>
> Thank you for your feedback all

You've been given good advice - and no one so far in here thinks it's
necessary.

You're saying you can't find the newsgroups
microsoft.public.inetserver.asp.general and
microsoft.public.inetserver.asp.db?
[url]http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.inetserver.asp.ge neral&lang=en&cr=US[/url]
[url]http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.inetserver.asp.db &lang=en&cr=US[/url]

Go to those groups and get some "expert" advice from users who do this
everyday and show it to the person asking you to delete the ldb files, maybe
they can learn something too ...

--
Tom Kaminski IIS MVP
[url]http://www.iistoolshed.com/[/url] - tools, scripts, and utilities for running IIS
[url]http://mvp.support.microsoft.com/[/url]
[url]http://www.microsoft.com/windowsserver2003/community/centers/iis/[/url]

[Immanuel]

Tom

the links you provided worked, thanks! I'll have a look in these forums too

I appreciate the advice, but you know how people can be stubborn about an idea heh

Maybe they'll change their mind afterall...

[Bob Barrows [MVP]]

Bob Barrows wrote:

> FWIW, I would not be too concerned about emptying the pool: ADO does
> a good job of managing that on its own.
>

I should add that it is not a good idea to delete the ldb files if a user is
currently connected to the database.

Instead of concentrating on searching for and deleting ldb files, you should
be concentrating on making sure all database users have sufficient authority
to delete them when they are the last users exiting the database.

If you are having so many issues with Access ldb files, perhaps it is time
to consider that you have exceeded Access' capabilities and move on to a
server-based database such as SQL Server (the MSDE version of SQL Server
comes with Access)

Bottom line: I do not know of any way to gain access to the ODBC connection
pool or the OLEDB session pool.

HTH,
Bob Barrows
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.