Microsoft recommend that this can happen if there is a specific stored procedure causing this problem, try adding these lines to the beginning of the proc, running it once, and then commenting out or removing the NO_BROWSETABLE line:

SET NO_BROWSETABLE OFF
SET NOCOUNT ON

If you are querying system tables, use a forward-only cursor (to be safest, avoid ADODB.Recordset altogether and update us if this resolves the problem or not.

Troubleshooting ’80004005′ Error Message in Microsoft Access Database

Error Message 1:
Cannot update. Database or object is read-only.Microsoft OLE DB Provider for ODBC Drivers error ‘80004005’.[Microsoft][ODBC Microsoft Access Driver] Cannot update. Database or object is read-only.
 
Solution:
The error usually happens when you try to insert data into or update data in an Access database. It means that you don’t have sufficient permissions to write to the database.
 
Please make sure that you have uploaded your database to the /db folder which locate at the same directory level as www or wwwroot.
 
Error Message 2:
Operation must use an updateable query.Microsoft OLE DB Provider for ODBC Drivers error ’80004005′ .[Microsoft][ODBC Microsoft Access Driver] Operation must use an updateable query.
 
Solution:
This error usually happens when you try to insert data into or update data in an Access database. It means that you don’t have sufficient permissions to write to the database.
 
Please make sure you have uploaded your database to the /db folder which located at the same directory level as www or wwwroot.
 
Error Message 3:
General error Unable to open registry key.Microsoft OLE DB Provider for ODBC Drivers (0×80004005).[Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key ‘Temporary (volatile) Jet DSN for process 0x6cc Thread 0x78c DBC 0x144cfc4 Jet’.
 
Solution:
This error can happen for a number of reasons the main reason being if the path to the database is incorrect.

You need to check that the path to the database is correct (You must use the physical path on the server to the database and not a virtual path).
 
Error Message 4:
Could not find file.Microsoft JET Database Engine (0×80004005).Could not find file ‘C:\Inetpub\wwwroot\databaseName.mdb’.
 
Solution:
This error is more or less what it says, the database file can not be found. This usually occurs if the path to the database is incorrect. By default all shared hosting client does not have access to the C:\Inetpub\*.

You need to check that the path to the database is correct (You must use the physical path on the server to the database and not a virtual path).
 
Error Message 5:
Table ‘tblTable’ is exclusively locked by user ‘Admin’ on machine ‘MyMachine’.Microsoft JET Database Engine error ’80004005′.Table ‘tblTable’ is exclusively locked by user ‘Admin’ on machine ‘MyMachine’.
 
Solution:
This error means that you are either unable to open the table or that you already have the table open in ‘Design View’ in Microsoft Access.

Close Access and try again.
 
Error Message 6:
The search key was not found in any record.Microsoft JET Database Engine (0×80004005).The search key was not found in any record.
 
Solution:
This error often means that the database has become corrupted.

To correct the error the database needs to be repaired. If the database is on a remote server download the database and follow the instructions below to repair the database.

Open the database in Microsoft Access, click on the ‘Tools’ menu and select ‘Database Utilities -> Compact and Repair Database’.
 
Once the database has been repaired, reupload it to the server using FTP.
 
Error Message 7:
Microsoft JET Database Engine error ’80004005′. Cannot Open Database. It may not be a database that your application recognizes, or the file may be corrupt.
 
Solution:
Permissions need reset -or- (and most likely!) MS Access on server is receiving too many hits. In a shared server environment, this is the likely cause. Access databases have a limit of 20 users accessing them at once.You have several options in resolving this error :
 
1. Convert to a SQL database.
 
2. We are using the latest MDAC on the Windows server.If your database is in MS Access 97 version, please upgrade it to Access 2000 or later and reupload your database.
 
Error Message 8:
Microsoft OLE DB Provider for ODBC Drivers error ’80004005′.[Microsoft][ODBC Microsoft Access 97 Driver] 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.
 
Solution:
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.
• The file and the data source name are marked as Exclusive.
• Another process or user has the Access database open.
• The 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.
• This 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 network server.

Connection Strings (MSSQL 2000, MSSQL 2005, MSSQL 2008, MySQL4, MySQL5, MS Access Database)

MSSQL2000
Set conn = Server.CreateObject(“ADODB.Connection”)
conn.Open “Provider=SQLOLEDB; Data Source =mssql.dnsracks.com,1533; Initial Catalog = Yourdatabase; User Id = USER; Password=PASSWORD; Network Library=dbmssocn;”
If conn.errors.count = 0 Then
Response.Write “Connected OK”

MSSQL2005
Set conn = Server.CreateObject(“ADODB.Connection”)
conn.Open “Provider=SQLOLEDB; Data Source =74.86.116.10; Initial Catalog = Yourdatabase; User Id = USER; Password=PASSWORD; Network Library=dbmssocn;”
If conn.errors.count = 0 Then
Response.Write “Connected OK”

MSSQL 2008
Data Source=72.18.135.197,1433;Network Library=DBMSSOCN;Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword;

MySQL4
<%
dim CN
set Cn = Server.CreateObject(“ADODB.connection”)
CN.Open “DSN=dsn_name; Server=localhost;database=database_name; Uid=user_id; Pwd=password;”
%>

MySQL5
<%
dim CN
set Cn = Server.CreateObject(“ADODB.connection”)
CN.Open “DSN=dsn_name; Server=localhost:3307;database=database_name; Uid=user_id; Pwd=password;”
%>

MS Access

DSN-Less

<%
set conn=Server.CreateObject(“ADODB.Connection”)
conn.Provider=”Microsoft.Jet.OLEDB.4.0″
conn.Open “c:/webdata/northwind.mdb”
%>
Connected !!

DSN

1) You must first create the DSN in Helm under your domain.
2) Then use the following connection string – with your own DSN
name of course :

<%
Set connectionToDatabase=Server.CreateObject(“ADODB.Connection”)
connectionToDatabase.ConnectionTimeout=60
connectionToDatabase.Open”DSN=DSN_Name”
%>
Connected !!

To Know more about Connection Strings open the following link
http://www.connectionstrings.com/

Error: [Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key ‘Temporary (volatile) Jet DSN for process”

If the above error you are facing in your website when connecting to access database just because access database requires additional permission to run from server. In this situation just open a ticket to support@wipl.in to resolve this issue.