Re: Problems with MS Access data source

From: Dmitry Korolyov (d__k_at_nospamformorons.mail.ru)
Date: 07/15/03


Date: Tue, 15 Jul 2003 02:25:50 +0400


Yes, I did check everything. File system permissions both for the website
itself and the database (mdb file) are very easy to check and veryfy that
they are the same on both systems.
System DSNs are configured exactly in the same manner on both systems. This
can be easily verified as well.
Talking about "Locked down" state of IIS, I see no problem here. Both web
servers are configured to user intergated windows authentication and do not
allow anynomous connections. There may be other differences, but I do not
see how they would affect ODBC connectivity. Web app does not use ISAPI
filters or anything. Since my original post we narrowed it down to
performing a single select statement, and the problem still exist.
In other words, I would not suggest looking into general IIS troubleshooting
part - because it does work fine on IIS 5.0. And the reference says nothing
about how "locked down" configuration of IIS 6.0 may affect database
connectivity - it simply knows nothing about IIS 6.0 existense.

--
Dmitry Korolyov
d__k@nospamformorons.mail.ru
To e-mail me, remove "nospamformorons"
from the address.
"Jeff Cochran" <jcochran.nospam@naplesgov.com> wrote in message
news:3f1a0eb6.1844826229@msnews.microsoft.com...
> Dmitry, did you look at the reference supplied?  Have you checked
> permissions, did you check the LDB lock file, have you configured
> authorization correctly?  Remember that just because it worked in
> IIS5, on a W2K system, has no bearing on whether you've correctly
> applied permissions on an IIS6 system, which is Server 2003 and comes
> with permissions locked down.
>
> 80004005 errors are almost always permission related.
>
> Though at your request I'm also perfectly willing to 'never mind'.
>
> Jeff
>
> On Mon, 14 Jul 2003 17:58:53 +0400, "Dmitry Korolyov"
> <d__k@nospamformorons.mail.ru> wrote:
>
> >But you didn't try to answer the original question too. Well nevermind
then.
> >  "Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> wrote in message
news:beua7n$9j411@kcweb01.netnews.att.com...
> >  I'm not a mind reader, you didn't say what investigation you did.
> >
> >
> >  "Dmitry Korolyov" <d__k@nospamformorons.mail.ru> wrote in message
news:OSNekagSDHA.1724@TK2MSFTNGP10.phx.gbl...
> >    Tom, this is very helpful indeed, but don't you think that I've
posted the original message without investigating the problem first? Note
also that exactly the same configuration (NTFS permissions, system data
source configuration, authentication settings on IIS) works just fine on IIS
5.0. Access database is located physically on the same server in both cases.
Yes, I do agree that "something" is locking up the file, however I suspect
that this "something" is IIS itself or one of its working processes. Note
the behavior: when you first time open the page, it works, whe you open it
from another computer on in different browser window (i.e. in another IIS
session), it fails with the error message quoted in the first posting.
> >      "Tom Kaminski [MVP]" <tomk (A@T) mvps (D.O.T) org> wrote in message
news:beu7hv$9j410@kcweb01.netnews.att.com...
> >      http://www.aspfaq.com/show.asp?id=2009
> >
> >      --
> >      Tom Kaminski IIS MVP
> >      http://www.iistoolshed.com/ - tools, scripts, and utilities for
running IIS
> >      http://mvp.support.microsoft.com/
> >      http://www.microsoft.com/windowsserver2003/community/centers/iis/
> >
> >        "Dmitry Korolyov" <d__k@nospamformorons.mail.ru> wrote in message
news:eOVGCrfSDHA.3088@TK2MSFTNGP10.phx.gbl...
> >        An ms access database is set up as a system data source and used
in asp application. When second user tries to open asp page which connects
to the database and fetches data, the following error is raised:
> >
> >        Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> >
> >        [Microsoft][ODBC Microsoft Access Driver] Could not use
'(unknown)'; file already in use.
> >
> >
> >        Server is IIS 6.0, error occurs both in worker process and IIS
5.0 isolation mode. The same configuration works fine with no errors on IIS
5.0 server.
> >
> >        --
> >        Dmitry Korolyov,
> >        d__k@nosmapformorons.mail.ru
> >        To e-mail me, remove "nospamformorons".
>


Relevant Pages

  • RE: IIS6 database link
    ... To write to the database you need to ensure the following, ... The IIS Website is a 'Application' under IIS Manager (the folder with ... ensure that the account used to browse, ... must have modify permissions on the DB. ...
    (microsoft.public.frontpage.programming)
  • security settings.
    ... I'm using IIS 6.0 ... >database with an asp web form, ... >permissions and IIS permissions correctly so I can avoid ...
    (microsoft.public.inetserver.iis.security)
  • configuring IIS security
    ... decided to compact and repair the access2000 database. ... SO via IIS window, i looked at the permissions on the ... sure you have local access" but no one says exactly what ...
    (microsoft.public.inetserver.iis.security)
  • security settings.
    ... I'm using IIS 6.0 ... database with an asp web form, ... Microsoft JET Database Engine error '80040e09' ... permissions on the file I see that the read only checkbox ...
    (microsoft.public.inetserver.iis.security)
  • re:Disaster Recovery
    ... - restore Sharepoint Services SQL backups (configuration and content ... I am keeping the same DB name in a diferent server. ... - create an application pool using the IIS backup file from product ... - on the configuration database page I am choosing CANCEL but is not ...
    (microsoft.public.sharepoint.portalserver)