Thanks for the suggestions Joe
I've looked very carefully at the permissions and have granted [Full
Control] access to both the IUSR and IWAM accounts on the directory
containing the database .MDB file. I've also granted [Full Control] at the
file level as well. Unfortunately I'm still getting the problem of the ODBC
driver reporting that my file is locked by another user or I need
permission to view the data. (Aaaaargh!!!)
Can you tell me what configuration you used to make this work? I'm sure
that I must be missing something really simple but I don't know what! Are
there any other directories which need permissions for this to work? I
have also granted read and write access to the database directory from
within the IIS server manager.
We use NT4 service pack 6a, IIS4, The data base was created in Access '97.
The database file is in a directory off the root level of the web
(d:\inetpub\wwwroot\db\filename.mdb). Annonymous access is granted to the
database directory.
We are really stuck and any suggestions are much appreciated
Bill
==================================================
Message text written by "Joe Moore"
>Bill,
I had a similiar problem, and it was a rights problem. What you'll need to
check are the NTFS permissions on the directory and the MS Access database
file. Specifically, the IUSR_SERVERNAME and, depending on how the IIS
server is configured, the IWAM_SERVERNAME accounts need to be able to add
files to the directory. This is because an .ldb file is created when the
Access file is opened. The .ldb file is basically a locking file so that
Access knows who has what opened. If it can't create an .ldb file, then it
'thinks' the file is opened exclusively by another user.
The IUSR_SERVERNAME (IWAM_SERVERNAME) accounts are used by IIS to access
the filesystem. This is assuming that you have Anonymous Access configured
for IIS.
Of course I'm assuming that you are running IIS.
HTH
Joe Moore
On 05/07/00, ""Mark G. Franz" <[EMAIL PROTECTED]>" wrote:
> The drivers are either loaded with Access or by loading the MDAC 2.1/2.5
> drivers. The error you are encountering is caused by the DSN reading the
> handle and seeing that it is already open by another session connection.
> You MUST close any session handles you open in your code.
>
> Or you don't have the MDAC drivers loaded on your server. Load the
drivers,
> repair your DSN connection and all ~should~ be fine.
>
> But still, you should always close any open handles...
>
> Mark
>
---
You are currently subscribed to perl-win32-users as:
[EMAIL PROTECTED]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
----------------------- Internet Header --------------------------------
Sender: [EMAIL PROTECTED]
Received: from listserv.activestate.com (listserv.activestate.com
[199.60.48.6])
by spdmgaaa.compuserve.com (8.9.3/8.9.3/SUN-1.9) with SMTP id
UAA08067
for <[EMAIL PROTECTED]>; Mon, 8 May 2000 20:13:20 -0400
(EDT)
Message-Id: <[EMAIL PROTECTED]>
Date: Mon, 8 May 2000 17:2:45
Subject: Re: ODBC on WinNT
To: "Perl-Win32-Users Mailing List"
<[EMAIL PROTECTED]>
From: "Joe Moore" <[EMAIL PROTECTED]>
List-Unsubscribe:
<mailto:[EMAIL PROTECTED]>
List-Software: Lyris Server version 3.0
List-Subscribe: <mailto:[EMAIL PROTECTED]>
List-Owner: <mailto:[EMAIL PROTECTED]>
X-List-Host: ActiveState <http://www.ActiveState.com>
Reply-To: "Joe Moore" <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
X-Lyris-Message-Id:
<LYR145489-57880-2000.05.08-17.02.52--billstennett#[EMAIL PROTECTED]
iveState.com>
Precedence: bulk
X-listname: perl-win32-users
X-ListMember: [EMAIL PROTECTED]
<
---
You are currently subscribed to perl-win32-users as: [archive@jab.org]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]