Resolving Ms Access Error 80004005 “the Microsoft Jet Database Engine Cannot Open The File”

By Author: Tech nova
Total Articles: 54
Comment this article

Microsoft OLE DB Provider for ODBC Drivers error '80004005' The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.
Causes for Access error ‘80004005'
Following are the causes for this error message:
The account that MS Internet Information Server (IIS) is using is not having the correct Windows NT permissions for a file-based database or for the folder that contains the file.
The file and the data source name marked as Exclusive.
Another process or user has the Access database open.
There is a delegation issue. Check the authentication provided, 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.
You are accessing a local MS Access database that is linked to a table where the table is in an Access database on a network server.
Resolutions for eradicating Access error ‘80004005'
...
... Check the permissions on the file & the folder and 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 folder.
Make sure that the file and the data source name (DSN) are not marked as Exclusive.
The other user may be MS Visual InterDev. Close any Visual InterDev projects that contain a data connection to the database.
Use a System DSN that uses a local drive letter. If necessary, move the database to the local drive to test.
If above steps are performed then error '80004005' The Microsoft Jet database engine cannot open the file '(unknown)' gets resolved in most of the cases, without damaging the database.
If somehow, the Access database gets corrupt while resolving this issue, then it is advised to compact Access database and restore the data within. Kernel for Access recovers every bit of data from corrupt MDB database and also compact Access database, increasing the database space.

Please visit for more information: http://www.compactaccessdatabase.com