Re: Most amazing problem

Anders -
One of the first things I checked was permissions since it is such a common
problem; I have made IUSR_XXX admin and enabled all web services too no
avail; I have canceled my upgrade to 2003 as I still do not consider it
ready for production deployment; fortunately I did this experiment on a test
/ development server so no production systems were impacted. I do find it
amazing that such a typical query fails and there seems to be no documented
fix. Do you need to enable any Web Service Extensions for ADO? I really have
exhausted my resources; it is so weird, it only fails on certain queries -
yes, it kind of smells like a permissions issue, but I have literally made
my IUSR account admin on the whole disk. Going to give up on this one - MS
that just cost you 6 copies of 2003 server.
BigFish



"Anders Eriksson" <andis59@xxxxxxxxx> wrote in message
news:50ze97g4dtly.dlg@xxxxxxxxxxxxxxxxxxxxxxxxxx
> On Wed, 7 Sep 2005 11:58:46 -0400, BigFish wrote:
>
>> Anders -
>> What newsgroup was this posted to ? I am using msado15.dll v2.82.1830.0
>> which is SP2 I believe. I have run CompChecker and all seems OK.
>>
> It wasn't real newsgroup, it was a forum. here the link:
> http://dbforums.com/t882013.html
>
> I found another thing you might check. In this newsgroup:
> http://www.issociate.de/board/post/142950/error_updating_access_database_using_where_on_number_column.html
>
> They have a similar problem and it has to do with the folder rights for
> IUSR_MACHINENAME in the folders program files/common files/ado and
> windows/system32
>
> <quote>
> "From some Google bait I found on a hardly related error, I decided to
> check perms on program files/common files/ado and windows/system32 -------
> and -------- sure enough, giving IUSR_MACHINENAME read and execute
> permissions on those folders fixed the problem. Is this a known problem
> with any recent update to win2k3?"
>
> <answer>
> This is a feature of Jet databases. In order to use a database
> concurrently with other users, all users of the database must have
> read/write permissions for the folder containing the database. The reason
> for this is that the first user to open the database needs to create a
> locking control file, databasename.ldb. Subsequent users must be able to
> edit this file. And the last user to close the database must be able to
> delete this file. Watch the folder containing your database as it is used.
> You should be able to see the creation and deletion of the ldb file as the
> database is used.
> Bob Barrows
> --
> Microsoft MVP -- ASP/ASP.NET
> </answer>
>
> </quote>
>
> Best Wishes!
> // Anders
> --
> English isn't my first, or second, language.
> So anything rude or strange are due to the translation


.

Relevant Pages

  • Re: Have database mismatch, can I move NTDS.dit and Exchange to new identical server?
    ... Check the physical location of the Winnt\NTDS\ folder. ... Check the permissions on the \Winnt\NTDS folder. ... as it may not be the database that is the ... MCSA + Exchange ...
    (microsoft.public.win2000.active_directory)
  • Re: Help - locked out of database
    ... IT checked all the permissions and everything seems to be ok. ... "Joan Wild" wrote: ... I have poured a year into this database - is there someway to recover this? ... You need, at minimum, modify permission on the folder. ...
    (microsoft.public.access.security)
  • Re: Shared v. Exclusive Access
    ... The folder wherein the frontend resides grants Full permissions to the ... When I open the database, however, I don't get the message boxes. ...
    (microsoft.public.access.security)
  • Re: error updating access database using where on number column
    ... The solution was not to set permissions for the folder, ... Again, pardon my crankiness, this is my third monday this week and it's only ... In order to use a database concurrently ...
    (microsoft.public.inetserver.asp.db)
  • Re: Display of Message "You do not have eclusive access toa databa
    ... > in the foder that has the database. ... >> permissions on the folder, then have one of them open the folder in ... >> permissions on the folder. ... >> Ian Shaw wrote: ...
    (microsoft.public.access.security)