Re: Problems with MS Access data source

From: Jeff Cochran (jcochran.nospam_at_naplesgov.com)
Date: 07/15/03 

Date: Tue, 15 Jul 2003 14:10:02 GMT

On Tue, 15 Jul 2003 02:25:50 +0400, "Dmitry Korolyov"
<d__k@nospamformorons.mail.ru> wrote:

>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.

Same on both systems or correct for Server 2003?

>System DSNs are configured exactly in the same manner on both systems. This
>can be easily verified as well.

Okay, so you're using ODBC then instead of OLEDB. Does your ODBC work
if you use a client such as Access to attach to the database?

>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 it works for everything but that SELECT statement?
Post the SELECT statement. And do a Response.Write of the SQL
statement to see what's actually getting sent.

>In other words, I would not suggest looking into general IIS troubleshooting
>part - because it does work fine on IIS 5.0.

Again, IIS6 is *not* IIS5. I have an oil filter that worked fine on
my Pinto, but doesn't seem to work on my Mazda. Troubleshoot the
current setup, not the old one.

>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.

I'm getting to feel sorry I ever tried to help here. Is your
application a .NET app, straight ASP or something else? Have you
tried a very basic connection, then the SELECT statement? Have you
tried an OLEDB connection instead of the ODBC?

The error you posted is almost always a permissions error. With
Access, it could be an exclusive lock, such as having Access or VS.NET
open on the server, it could be file permissions, it could be Temp
file creation, it could be the ODBC key in the registry, it could be
Access security or it could be the specific code you use. Make sure
you're configuring permissions according to the account the app is
running under, which may or may not be the logged in user.

Jeff

Jeff

Relevant Pages

  • Re: [VW 7.3.1] ODBCConnection
    ... I played around with a few combinations on the connection string and ... with a trusted SQL Server connection. ... there are differences for database connects. ... > any database specific odbc drivers. ...
    (comp.lang.smalltalk)
  • Re: Ada DB bindings and APQ
    ... >>I didn't like the use of handles for database objects. ... > will ensure that the connection will not go away until at least one query ... > things which can be made with a connection. ... That is different to ODBC. ...
    (comp.lang.ada)
  • Re: Mailmerge using a secure database
    ... Database does not have a long path name. ... When I tried re-opening my mail merge documents I get an error message ... Do you need or want specifically to connect with ODBC? ... likely to run into problems where Word truncates the connection string ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Linking Access f/e to Access b/e via ODBC
    ... > Is it possible then to create an ODBC connection to use the ISAM driver ... If I understand your question correctly, the ISAM driver for Jet _is_ what ... you're getting when you create the DSN for an Access database file. ... the ODBC Data Source Administrator can create the DSN to the Access ...
    (microsoft.public.access.externaldata)
  • Re: Data Source Lost When Merge From Access to Word
    ... DDE was the default connection method and ODBC was the alternative as far as Access/Jet sources were concerned. ... In Word 2003, OLE DB is the default, but unfortunately when you have selected your database, Word does not display the Access tables that are linked to ODBC data sources. ... create one query in your Access database for each linked table you want to use, with SELECT * FROM, and use that as the data source. ...
    (microsoft.public.word.mailmerge.fields)