Microsoft Jet Database Engine 0x80004005 Error – Solved!

  • Written By  

  • Updated on May 28th, 2020

80004005 is a Jet Database Engine error which occurs in MS Access. The error does not allow the user to access the data file. The error is not a result of a corrupted database but, is a combination of several inconsistency issues. The most common reason for occurring error ‘80004005’ is aiming to use a shared folder of Virtual box. The recurrent error interrupts the progress of a database file. So, Let’s take a look at how Microsoft Jet Database Engine 0x80004005 Error looks like:

 looks like:

 You may receive a message like “Provider error ‘80004005’”


“Unspecified error”


“Database Connection (OLEDB) Exception. Unspecified error”

Causes Of Microsoft JET Database Engine 0x80004005 Error :

  • MIIS (Microsoft Internet Information Server) account, comprises incorrect Windows NT permission. This malfunction prevents the user from accessing the database file/folder.
  • The name and file of data sources are noticeably Exclusive.
  • And MS Access database files are being accessed by multiple users and programs.
  • The error ‘80004005’ sometimes occurs due to delegation defaults. One must always examine the authentication method before accessing the MS Access database. The naming convention field is used to fix a permanent path with the help of a connection string.
  • Sometimes, the error occurs due to the local database accessing the database linked to the global server.

How to fix Microsoft Jet Database Engine 0x80004005 Error?

Have a look over the multiple run-time error 80004005 messages a user can receive while working on the database file.  Let’s take look what a particular message means and how to resolve them.

Message 1: The search key was not found in any record, Microsoft JET Database Engine 0x80004005 Error.

If users notice an unusual error that states the Access database has been corrupted. To solve this error, one might need to fix the database file. Follow the below-mentioned steps to repair the database file, if the database lies on the outlying server. 

  • In Microsoft Access, open the corrupted database and go to the Tools menu. Next, choose Database Utilities, and then hit the Compact and Repair Database.
  • After fixing the server via file transfer protocol, reload the database to the server.
Message 2: General error unable to open registry key, “Temporary (volatile) Jet DSN for process 0x6cc Thread 0x78c DBC 0x144cfc4 Jet”. Microsoft OLE DB Provider for ODBC Drivers.
  • However, there is no such reason for the occurring of the above error but, it can sometimes occur due to incorrect path details. 
  • To repair the error, examine whether the given path details are correct or not.
Message3: [Microsoft][ODBC Microsoft Access 97 Driver]. The Jet database engine cannot open the file. You need permission to view this data or it is already opened by another user. Microsoft OLE DB provider for ODBC Drivers error “80004005”
  • Due to accessing the local Access database table which is linked to an Access database table on the internet server. 
  • Both file and data sources are distinguished Exclusive.
  • Delegation issue can be the reason this occurring message so, always choose a certified method (if available). Try using the casual validated method, if naming convention is used for path like- C:\Mydata\
Message 4: Object or Database is Read-only. Microsoft OLE DB Provider for ODBC Drivers error “80004005”.
  • The error usually occurs, when an update is initiated in the database or file insertion is in progress. This indicates that the user doesn’t have the authorization to edit the MS Access database.
  • Re-assure that the database id uploaded to the Database folder is placed at the same directory level as WWW.
Message 5: It may not be a database that your application recognizes, Microsoft JET Database Engine error “8000405”. The file may be corrupt or cannot Open Database.

This error message usually occurs in a basic server situation. It often occurs due to many clients using the network server at once. Let’s take a look at the solution to solve the error.

  • Convert your database file to a SQL database file.
  • If your database is not updated yet, update it to Acess 2000 version and then re-upload your database file. 
Message 6: Microsoft JET Database Engine error “80004005”, Table “tblTable” is exclusively locked by users on Machine “My Machine”.
  • This error enables the user to view the database table or the table is already open in the Design view in your MS Access. 
  • Exit Access database and reopen it.

If the portable approach does not give you the appropriate results than choosing a  third party utility instead is the relevant option. One such solution is the MS Access Database Recovery. The utility claims to restore BLOB data, offers dual modes of recovery, compatible with all versions of Windows OS, highly supports MS access 2013, 2016, 2019, and earlier versions promise to repair database contents like tables, reports, queries, index, and forms efficiently.


We conclude that resolving Error 80004005 is a difficult task overall. But, everything that seems difficult it doesn’t mean impossible. The Above mentioned solutions are appropriate enough to solve a recurrent Microsoft Jet Database Engine 0x80004005 Error.

About The Author:

Pallavi is a content writer in the field of data recovery and email migration. She has a passion for creating engaging and thought-provoking content. With several years of experience in the field, she has developed a deep understanding of various writing styles and formats,

Related Post

© Copyrights 2017-2023 Database File Recovery. All Rights Reserved.