This article was previously published under Q166029
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 7.0 running on Microsoft Windows Server 2008. IIS 7.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
When using Active Server Pages (ASP) to query an Access database, you mayencounter the following error message.
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Microsoft Access 97 Driver] The Microsoft Jet databaseengine cannot open the file '(unknown)'. It is already openedexclusively by another user, or you need permission to view its data.
/scripts/somefile.asp, line x
This Error message can be caused by any of the following conditions:
The Access .mdb file is located on another computer than the IIS Server.
IIS Server is configured to use NT Challenge / Response whenaccessing secured script files.
The Access .mdb file is located on another computer than the computer running IIS.
IIS is configured to use the IUSR_computername account for anonymous access.
The script file being accessed is not secured and permits anonymous access.
The IUSR_computername is a local account and the same account/password does not exist on the remote computer
The Access .mdb file is located on the same computer as the Web server.
The datasource uses a UNC path to point to the .mdb file (for example, DSN=\\servername\share).
NT Challenge/Response is used to authenticate the user.
The Access .mdb file is linked to a table where the table linked to is in an Access database on a network server. In this situation, please refer to the following article in the Knowledge Base for a workaround:
189408 PRB: ASP Fails to Access Network Files Under IIS 4.0
This behavior is by design.
When using NT Challenge / Response with IIS, the users credentials arecreated at the browser. The credentials are then sent to IIS. IIS cannotforward those credentials on to another server.
The connection is attempted, but there is no username specified whenconnecting to the remote machine, so the connection fails.
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
174811 Authentication and Security White Paper for Internet Developers
253580 HOWTO: Connect to a Remote Access Database from Active Server Pages