How to control ownership of ldb file?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Siegfried Heintze - 22 Oct 2005 20:48 GMT

What happens when the administrator account opens up my Access database and
creates an ldb file? Who owns the ldb file? Administrator I suspect!

Then what happens when the web server comes in under IUSR_MACHINENAME and
tries to open the same access database? If it succeeds in opening the mdb
file, could it fail to open the ldb file?

I think this is my problem! How do I fix it? I have the administrator
account (actually this should be something other than the adminimistrator
account for security reasons) has created the ldb file, I need to make that
ldb file accessible by the ISR_MACHINENAME account. How do I do that?

Thats it! I finally solved my problem! I just granted "everyone" full
control over the ldb file and my ASP.NET page works! Hurray -- I've been
struggling with this for weeks! But this is not a good solution because that
ldb file gets recreated everytime a perl program exits and starts again
(which happens many times everyday).

So my perl programs are running under the administrator account and creating
a temporary ldb file that the IUSR_MACHINENAME could not access.

So,
(1) Why did it not work when I granted ISR_MACHINENAME full control?
(2) What do I need to do so MS Access creates ldb files that the web server
can access?
(3) Exactly what kind of access to the ldb does the IIS Web need in order to
INSERT and UPDATE and DELETE and SELECT?

Thanks,
Siegfried

Reply to this Message

david@epsomdotcomdotau - 22 Oct 2005 23:49 GMT

Don't worry about the /owner/. The ldb file inherits
permeations for new files in the place where it is created.

Also, you CAN remove delete permission from the ldb file
if you are having real problems with permeations. You
won't be able to get exclusive locks on the database
file if you can't delete the ldb file, so this "solution" is
a more work - you have to recreate the appropriate
permeations after deleting the file for administrative tasks.

(david)

> What happens when the administrator account opens up my Access database and
> creates an ldb file? Who owns the ldb file? Administrator I suspect!
[quoted text clipped - 26 lines]
> Thanks,
> Siegfried

Reply to this Message

Siegfried Heintze - 23 Oct 2005 01:07 GMT

David,

> Don't worry about the /owner/. The ldb file inherits
> permeations for new files in the place where it is created.

IF this is true, they why am I experiencing different behaviour depending on
whether the IUSR_MACHINENAME account opens up MSAccess first, or
Administrator opens it up first?

> Also, you CAN remove delete permission from the ldb file
> if you are having real problems with permeations.

How would I do that? the ldb file comes and goes -- rapidly if there is a
lot of different perl programs/web pages running.

>You
> won't be able to get exclusive locks on the database
[quoted text clipped - 40 lines]
> > Thanks,
> > Siegfried

Reply to this Message

david epsom dot com dot au - 24 Oct 2005 00:21 GMT

> whether the IUSR_MACHINENAME account opens up MSAccess first, or
> Administrator opens it up first?

If you want it to work correctly based on New File
permissions, you have to set up the New File permissions
correctly.

Don't worry about the things you can't change (ownership).
Concentrate on the things you can change: permissions.

(david)

> David,
>
[quoted text clipped - 61 lines]
>> > Thanks,
>> > Siegfried

Reply to this Message

Siegfried Heintze - 24 Oct 2005 19:15 GMT

Thanks, David.
What do you mean by new file permissions?
Do you mean changing the permissions on the directory so the new files will
be created similarly?

Thanks,
Siegfried

> > whether the IUSR_MACHINENAME account opens up MSAccess first, or
> > Administrator opens it up first?
[quoted text clipped - 73 lines]
> >> > Thanks,
> >> > Siegfried

Reply to this Message

david epsom dot com dot au - 24 Oct 2005 23:17 GMT

> Do you mean changing the permissions on the directory so the new

Yes. There will typically be permissions for
'CREATER-OWNERS', Administrators, Power Users, current user
etc. You may want to add 'users', or perhaps IUSR_MACHINENAME
to the list, and then add the correct permissions to the
user or group that the user is in.

(david)

> Thanks, David.
> What do you mean by new file permissions?
[quoted text clipped - 93 lines]
>> >> > Thanks,
>> >> > Siegfried

Reply to this Message