IIS failure when Access DB linked to outside tables

  • Thread starter Thread starter chris
  • Start date Start date
C

chris

I have an ASP application that relies on an Access database with linked
tables. The application works fine on the internet (the site functions
properly). In the testing environment I need to have the table links
set to emulate the website, or change the links prior to posting a copy
of the database to the site. I'd prefer to test it with the proper
linking.

Linked tables are stored in mapped drive (H:). This drive is local to
the testing machine, however when I run the application, using URL
http:/localhost/app, queries fail with a message that the path is
invalid. This doesn't make any sense. I'm assuming that there's some MS
security that's causing the problems, but I've been unable to figure
what it's controlled by.

I really don't have the $250 to call MS and ask them (and I wouldn't
bet on they're having a good answer, I've been down this road
before)....

TIA...
 
On 3 Mar 2005 15:42:00 -0800, (e-mail address removed) wrote:

¤ I have an ASP application that relies on an Access database with linked
¤ tables. The application works fine on the internet (the site functions
¤ properly). In the testing environment I need to have the table links
¤ set to emulate the website, or change the links prior to posting a copy
¤ of the database to the site. I'd prefer to test it with the proper
¤ linking.
¤
¤ Linked tables are stored in mapped drive (H:). This drive is local to
¤ the testing machine, however when I run the application, using URL
¤ http:/localhost/app, queries fail with a message that the path is
¤ invalid. This doesn't make any sense. I'm assuming that there's some MS
¤ security that's causing the problems, but I've been unable to figure
¤ what it's controlled by.
¤
¤ I really don't have the $250 to call MS and ask them (and I wouldn't
¤ bet on they're having a good answer, I've been down this road
¤ before)....

The process under which the web application is executing doesn't know anything about drive letters
mapped to other resources. Is there anyway you can use logical drive letters for your linked tables
instead?

The other option might be to link your tables with a UNC path to the database.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Thanks for the comment.

I'm not sure what you mean. I'm interpreting this as IIS can't deal
with mappings that aren't physical. When you say logical drive, you
mean use the drive manager to create a logical drive that matches my
drive mapping requirement in the database linked table manager?

One thing I don't understand is why IIS even cares what resources my
database accesses.

PS: I think if I could UNC I wouldn't be in this mess in the first
place.
 
¤ Thanks for the comment.
¤
¤ I'm not sure what you mean. I'm interpreting this as IIS can't deal
¤ with mappings that aren't physical. When you say logical drive, you
¤ mean use the drive manager to create a logical drive that matches my
¤ drive mapping requirement in the database linked table manager?
¤

IIS doesn't know anything about drive mappings that are not defined by the OS. So, if you create a
logical drive when you log in, that drive mapping is essentially created under your identity. The
IIS web application runs under a different identity and is not aware of this drive mapping.

¤ One thing I don't understand is why IIS even cares what resources my
¤ database accesses.
¤

Because the database is opened by an IIS process running under an identity that is different than
the identity under which the drive mappings were created and therefore does not have access to those
drive mapped resources.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
Back
Top