Troubleshooting 80004005 and other error messages

Troubleshooting 80004005 and other error messages
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Data Access Components versions 1.5, 2.0, 2.1, 2.5
Active Server Pages
Microsoft Visual InterDev, version 1.0
--------------------------------------------------------------------------------
Profile
This article details some common reasons why Microsoft data Access Components (MDAC) received 0x800040005 errors, including ActiveX data Objects, OLE DB, and Remote Data Services (RDS).
Also, this article discusses some other error messages, including 80040E21, 80040e14, and 80040e10.
More information
The 80004005 error message can be summed up as: "For some reason, I can't access your data."
This article gives a list of the various 80004005 error messages, which lists the most common causes of these error messages and their troubleshooting steps.
Although this article assumes that you are using ActiveX Data Objects (ADO) in the Active Server page (ASP) page (. asp), these causes and many troubleshooting steps apply to any other environment that accesses data through ODBC.
Error message list
In this section we describe the text of various error messages and the cause of the error.
Error message
Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 ' [microsoft][odbc Microsoft Access Driver] the Microsoft Jet The database engine cannot open the file ' (unknown) '. It is already opened exclusively by another user, or your need to view its data.
Reason
This error occurs, usually because the account (usually IUSR) used by Internet information Server (IIS) does not have the correct Windows NT permissions to access the File-based database or the folder containing the files.
Please check the permissions settings for these files and folders.
Verify that you can create and/or delete any temporary files.
Temporary files are generally created in the same folder as the database, but can also be created in other folders, such as/winnt.
You can use the Windows NT file Monitor to check the cause of failed access to the file.
The Windows NT file Monitor can be obtained from the following Web sites: http://www.sysinternals.com.
If you are using the network path (UNC or image Drive) of the database, check the permissions on the share, files, and folders.
Verify that the file and data source name (DSN) are not marked as exclusive.