If there is an error message prompt, it will be easy to find a problem. This article interprets 80004005 error information in ASP.
error message
Microsoft Jet DataBase Engine Error '80004005' Unexposed error (Provider error)
reason:
Permanent issues, the system cache directory is insufficient permissions
Solution:
Put the system disk such as C:/Winnt/Temp Directory permissions plus Everyone readable permissions
error message
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 Exclusion
by another user, orouned permission to view its data.
reason:
This error occurred when IIS uses anonymous account (usually IUSR), and the account is in the directory where the database is located in NT
There is no correct authority. (This is why there is no problem under Win95 and PWS, because Win95 has no directory permissions at all)
Check the permissions of the file and directory. It is determined that you can have the permissions that can be built and deleted in this directory.
These temporary files are actually files based on the database in the same directory, but it should be noted that these files may
It may also be based on other directory, such as/winnt.
When the NT file monitoring program surveillance file failed, what the directory did it visit?
This NT file surveillance program can download http://www.sysinternals.com.
If you use a network address for the database, such as the mapping address, check the authority of the shared file and directory.
Also check whether the data source file (DSN) is used by other program marks to become in use.
These other programs are generally Visual InterDev to close the items that are connected to database connections in any InterDev.
This error may also happen in this situation: if a UNC path is used in DSN (that is, the general name agreement), please use it
Test the local path because the local database is used to use UNC.
This may also happen in this situation. If the server wants to access a table in Access, this table is connected to a network server.
error message:
Microsoft Ole DB PROVIDER for Odbc Drivers Error '80004005'
[Microsoft] [ODBC Microsoft Access 97 Driver] Couldn't Use '(UNKNOWN)'; File
Already in use.
reason:
The database is locked when multiple people use.
error message:
Microsoft Ole DB PROVIDER for Odbc Drivers Error '80004005'
[Microsoft] [Odbc Driver Manager] Data Source Name Not Found and No DEFAULT
Driver Specify.
reason:
The most likely reason is that ConnectString is a session variable initialized in global.asa, but Global.asa
But there is no normal work. The solution is to check whether the value is correct: (add the following code to your ASP)
<%= 'Auth_user' is & Request.servervariables (Auth_user)%>
<p>
<%= 'Auth_type' is & Request.servervariables (Auth_type)%>%>
<p>
<%= Connection String Is & Session (Your_ConnectionString)%>%>
<p>
Another reason is that you have added excess space to your connectstring, such as
Dsn = mydsn; database = pubs;
Try to change to the following:
Dsn = mydsn; database = pubs;
If Global.asa has not yet worked, check whether the file is in the root directory of the program, or in the root directory of the virtual directory.
It is also possible that the reason for the error is that the DSN name is not found, which can be solved with the method I provided by the ID = 36767.
Finally, check whether the latest driver is installed, whether it is the latest MDAC version.
error message
Microsoft Ole DB PROVIDER for Odbc Drivers Error '80004005'
[Microsoft] [ODBC Driver Manager] Data Source name Not ??
reason:
This error may appear in the order of software installation (or anti -installation) on your computer.
This error occurs if the ODBC version is inconsistent.
The solution is to install the latest version of MDAC
error message:
Microsoft Ole DB PROVIDER for Odbc Drivers Error '80004005'
[Microsoft] [ODBC Access 97 ODBC Driver Driver] General Error Unable to Open
Registry Key 'Driverid'.
reason:
This error occurred when reading the value from the registry. Use Regedit32.exe to check the authority of your registry.
You can also use the registry monitoring program (NTREGMON) in NT to see the failure information. The program is here: http://www.sysinternals.com
error message:
Microsoft Ole DB PROVIDER for Odbc Drivers Error '80004005'
[Microsoft] [Odbc SQL Server Driver] [Dbnmpntw] ConnectionOpen (CreateFile ()).
reason:
Two reasons: When a database contains a license relationship on the machine, respectively,
This may also occur on the same machine. When you set the UNC path for one relationship, the other is the local path.
The reason for the error is:
When the user logs in with an anonymous account of IIS, he is right for the local machine, but for a UNC path machine,
In addition, this machine does not think that your current anonymous login account is also legal on it.
In this way, it does not allow you to access the resources on it, leading to errors.
Two solutions:
1. In IIS tools, change the anonymous account of IIS into another domain -based account. (That is, not using anonymous login)
2. Or create a account that you want to access the resource on that one to access the resource and use the same password as the current anonymous account.
error message:
Microsoft Ole DB PROVIDER for Odbc Drivers Error '80004005' Microsoft] [ODBC
Microsoft SQL DRIVER] logon failed ()
reason:
The error is generated by SQL Server. When it does not accept or cannot know this login account, or log in without using an administrator,
It may also be caused by no SQL transition account in NT.
Log in to use the system administrator account (SA). Generally, the password should be empty. Note that at this time, you must use CoonectString instead of DSN files.
Because the username and password are not saved in DSN.
Check whether the NT has mapped the account to the SQL.
error message:
Microsoft Ole DB PROVIDER for Odbc Drivers Error '80004005'
[Microsoft] [ODBC SQL Server Driver] [SQL Server] Login Failed-User: Reason:
Not defined as a value user of a trusted sql server connection.
reason:
The reason is the same as above.
Try this method: In the Enterprise Manager
133]/Security Options/Standard.
If it is running in IIS4, cancel the Password Synchronization option selected by the project.
error message:
Microsoft Ole DB PROVIDER for Odbc Drivers Error '80004005'
[Microsoft] [Odbc Microsoft Access 97 Driver] Couldn'T Lock File.
reason:
Maybe there is no correct permissions to generate the lock file of the Access database (.LDB)
At the default, the file is the same directory as your database.
Give the anonymous account to access the database sharing directory authority.
Sometimes it is because the file is intentionally used by the read -only authority when sharing. Try using the following code.
Set conn = Server.CreateObject (Adodb.Connection
Conn.mode = admodeShareDenywrite '8
error message:
Microsoft Ole DB PROVIDER for Odbc Drivers Error '80004005'
[Microsoft] [ODBC Microsoft Access 97 Driver] '(UNKNOW)' Isn't A Valid
PATH.
Connected to the server on whether the file resides.
reason:
The path is illegal. It is most likely to occur when Global.asa and CooneCntstring are used on another machine.
error message:
Microsoft Ole DB PROVIDER for Odbc Drivers Error '80004005'
[Microsoft] [Odbc SQL Server Driver] [SQL Server] The Query and the Views in
It exceed the limit of 16 tables.
reason:
The query is too complicated and restricts the query.
error message:
Microsoft Ole DB PROVIDER for Odbc Drivers Error '80004005'
[Microsoft] [ODBC SQL Server Driver] [DBMSSOCN] General Network Error. Check
Your Network Document
reason:
When the machine with SQL Server is renamed. But DSN also used the original machine name.