ASP Learning: Error 80004005 Information processing methods

1. Error message (Error message I do not have to translate into Chinese, hehe, everyone understanding)
Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 '
[Microsoft] [ODBC Microsoft Access Driver] The Microsoft Jet database
Engine cannot open the file ' (unknown) '. It is already opened exclusively
By another user, or your need permission to view its data.

Reason:

This error occurs when IIS uses an anonymous account (usually IUSR). The account does not have the correct permissions in the NT for the directory in which the database resides. (This is why there is no problem with Win95 and PWS, because Win95 does not have directory permissions at all) check file and directory permissions. Make sure you have permission to create and delete temporary files in this directory.

These temporary files are actually files built in the same directory as the database, but note that it is possible that these files
It may also be built in a different directory, such as/winnt.

What directory is accessed when a file monitor using NT has failed to monitor the file.
This NT File Monitor can download http://www.sysinternals.comin this place.

If you use a network address for a database, such as a mapping address, check the permissions for shared files and directories.

Also check to see if the data source file (DSN) is being used by another program flag.
These other programs are typically Visual InterDev, which closes any project that is open and database connected in a InterDev.

This error can also occur if a UNC path (the Universal Naming convention) is used in DSN, instead, use a local path for testing because it can be an error if the UNC is used against the local database.

This can also happen if the server wants to access a table in Access, but the table is joined to a network server.

2. Error message:

Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 '
[Microsoft] [ODBC Microsoft Access Driver] Couldn ' t use ' (unknown) '; File
Already in use.

Reason:

The database is locked when multiple people are using it.

3. Error message:

Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 '
[Microsoft] [ODBC Driver Manager] Data source name not found and no default
Driver specified.

Reason:

The most probable cause is that ConnectString is a session variable initialized in Global.asa, but Global.asa
But not working properly. The solution is to check that the assignment is correct: (Add the following code to your ASP)

Another reason is that you add extra spaces to your connectstring, such as

DSN = MyDSN; Database = Pubs;
Try changing it to the following:
Dsn=mydsn;database=pubs;

If Global.asa is not yet working, check to see if the file is in the root directory of the application, or in the root directory of the virtual directory.

It is also possible that the error occurred because the DSN name was not found, which can be solved by the id=36767 method I provided.
Finally, check to see if the latest driver is installed, whether it is the latest version of MDAC.

4. Error message

Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 '
[Microsoft] [ODBC Driver Manager] Data source name not??

Reason:

This error may occur in the order of the Software installation (or reverse installation) on your computer.
This error can occur if the version of ODBC is inconsistent.
The workaround is to install the latest version of MDAC

5. Error message:

Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 '
[Microsoft] [ODBC Access driver ODBC Driver] General error Unable to open
Registry key ' DriverID '.

Reason:

This error occurs when love reads a value from the registry. Use Regedit32.exe to check your registry permissions.
You can also use the Registry Monitor (NTRegMon) in NT to read the failure information. The program is here to find: http://www.sysinternals.com

6. 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 separate license relationship on the machine,
This can also happen on the same machine, when you set a UNC path to a relationship, and the other relationship is a local path.
The reason for the error is:

When a user logs on with an IIS anonymous account, he is entitled to the local machine, but for a UNC-path machine, the other machine does not assume that your current anonymous login account is also legal on the computer. This will not allow you to access resources above it, resulting in errors.

Two solutions:

1. In the IIS tool, change the IIS anonymous account into another domain-based account. (that is, do not use anonymous logins)
2. Or on the machine where you want to access the resource, create an account that is the same as the current anonymous account, using the same password.

7. Error message

Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 ' Microsoft][odbc
Microsoft SQL Driver] Logon Failed ()

Reason:

This error is generated by SQL Server, when it is not accepted or is not able to recognize the login account, or is not logged in as an administrator, or it may be caused by a SQL mapping account in NT.

Log on using the System Administrator account (SA), the general password should be empty. Note that you must use coonectstring instead of using the DSN file.

The user name and password are not saved in the DSN.
Check to see if NT has mapped the account number for SQL.

8. 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 valid user of a trusted SQL Server connection.

Reason:

Reasons above.
Z
Try this: In SQL Server's Enterprise Manager, select Server/sql server/configure[ascii
133]/security Options/standard.
If you are running in IIS4, deselect the Password Synchronization option for the item.

9. Error message

Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 '
[Microsoft] [ODBC Microsoft Access Driver] Couldn ' t lock file.

Reason:

Maybe you don't have the right permissions. To generate a lock file (. ldb) for an Access database
By default, the file is the same directory as your database.
Give anonymous accounts full access to the database share directory.

Sometimes it is because the file is shared with the intent to use read-only permission restrictions. Try using the following code.
Set Conn = Server.CreateObject ("ADODB. Connection ")
Conn.mode = adModeShareDenyWrite ' 8

10. Error message

Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 '
[Microsoft] [ODBC Microsoft Access Driver] ' (unknown) ' isn ' t a valid
Path. Make sure this the path name is spelled correctly and so you are
Connected to the server on which the file resides.

Reason:

The path is illegal. Most likely occurs when Global.asa and coonecntstring are used on another machine.

11. 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.

Reason:

The query is too complex to have restrictions on the query.

12. 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. However, DSN also used the original machine name.