There are several causes for this error message:
- The account that Microsoft Internet Information Server (IIS) is
using (which is usually IUSR) does not have the correct Windows NT
permissions for a file-based database or for the folder that contains
- The file and the data source name are marked as Exclusive.
- Another process or user has the Access database open.
error may be caused by a delegation issue. Check the authentication
method (Basic versus NTLM), if any. If the connection string uses the
Universal Naming Convention (UNC), try to use Basic authentication or an
absolute path such as C:\Mydata\Data.mdb. This problem can occur even
if the UNC points to a resource that is local to the IIS computer.
error may also occur when you access a local Microsoft Access database
that is linked to a table where the table is in an Access database on a
The following items correspond to the previous list of causes:
- Check the permissions on the file and the folder. Make sure that
you have the ability to create and/or destroy any temporary files.
Temporary files are usually created in the same folder as the database,
but the file may also be created in other folders such as the WINNT
For additional information about how to identify which folder does not
have the correct permissions and how to configure temporary files, click
the following article number to view the article in the Microsoft
If you use a network path to the database (UNC or mapped drive), check the permissions on the share, the file, and the folder.
Microsoft Access 97 database connectivity fails in Active Server Pages
- Verify that the file and the data source name (DSN) are not marked as Exclusive.
"other user" may be Microsoft Visual InterDev. Close any Visual
InterDev projects that contain a data connection to the database.
- Simplify. Use a System DSN that uses a local drive letter. If necessary, move the database to the local drive to test.
- Follow the instructions in the following article to work around this problem:
FIX: ASP fails to access network files under IIS 4.0 and IIS 5.0