Troubleshooting guide for 80004005 errors in Active Server Pages and Microsoft Data Access Components (306518)

MORE INFORMATION

List of Error Messages

The 80004005 error message indicates that your data cannot be accessed. This error can be paraphrased as "I could not access your data for some reason." This section lists the text and cause of the most common error messages. For other related articles that may help to determine the cause of the error, see the "References" section. Although this article attempts to provide as much information as possible, some areas may have been missed.

Error Message

Cause

The account that is being used to access the ASP page does not have permissions to access the .mdb file.

Note In this case, you may receive the following error message instead depending on the IIS configuration:

Error Message

Cause

There are several causes for this message. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

Error Message

Cause

The database cannot be locked correctly for multiple users. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Error Message

Cause

This error is one of the more common error messages and has multiple resolutions. For more information, click the following article number to view the article in the Microsoft Knowledge Base: Make sure that the most current drivers are installed. You can download the latest version of MDAC from the following Microsoft Web site:

Error Message

Cause

This error can occur because of a problem with the order in which the software is installed and uninstalled on the computer. You may receive this error if the ODBC core files become unsynchronized (they should all be the same version).

To update all of the core ODBC drivers, install the latest version of MDAC from the following Microsoft Web site:

Error Message

Cause

This error occurs when you read a value from the registry. Use Registry Editor (Regedt32.exe) to check the permissions on the registry key. You can also use the Windows NT Registry Monitor (NTRegMon) to check for registry read failures. You can download NTRegMon from the following Sysinternals Web site:

Error Message

Causes

There are two causes for this error, both of which are permission-related. This error can occur when a database resides on a different computer than the Web server, or when you use a Universal Naming Convention (UNC) path (\\Server\Share) to reference a database. Even if the database is on the same computer as the Web server, the Web server assumes that the database resides on a different computer on the network when you use UNC paths.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: For more information about delegation, how Microsoft Internet Information Server (IIS) uses authentication to secure a Web site, and problems such as this, refer to the following Microsoft Web site:

Error Message

Cause

SQL Server generates this error if it does not accept or recognize the logon account and/or password that is submitted (if you are using Standard security) or if there is no Windows NT account to SQL account mapping (if you are using Integrated security).

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Error Message

Cause

This error can occur because Integrated security is turned on in the SQL Enterprise Manager, and the Windows NT account that is being used is not mapped to a SQL account. To resolve this problem, use one of the following methods:

• Configure SQL Server to use Standard security. In SQL Enterprise Manager, right-click the Server, and then click SQL Server. Click the Security Options tab in the SQL Server Property dialog box. Click to select SQL Server and Windows under Authentication, and then click OK.
• If you are running under IIS 4.0, clear the Password Synchronization check box for that project.

Error Message

Causes

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Error Message

Cause

The path that the Web server is reading is not a valid path. Often, this occurs when the Global.asa file is being used, and the connection string is created on a computer other than the Web server. If the path is a mapped drive letter, it is probably only valid for the client computer that created the connection string.

Error Message

Cause

This error occurs because the query is too complex. There are several limitations on a query.

Error Message

Cause

When you turn off the allow Anonymous User context, Windows NT closes the pipe to SQL Server after the first request is complete. This is because the first connection to SQL Server is made under the IIS Anonymous User account. IIS then either impersonates the browser client on that same thread or tries to access the connection on a different thread that is running in the impersonated user context. In either case, Windows NT detects the attempt to use a network-named pipe handle that was opened in a different user context and forces the pipe to close, according to its security rules. When you view the connections on the SQL Server with a network monitor, Windows NT issues a name pipe close request, which causes the error in the Web browser.

Error Message

Cause

This error can occur when you rename a SQL server computer. Domain Name Systems (DSNs) that reference the old name fail when the computer name cannot be located.

Error Message

Cause

This error can occur when you try to insert more data into a field than is allowed (for example, if you insert 26 characters into a Microsoft Access field that is formatted to accept only 25 characters).

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Error Message

Cause

There are multiple causes for this message; see the "References" section for articles that pertain to this message.

Error Message

Cause

This error occurs because a column name may be a reserved word, such as "DATE." Change the column name to a non-reserved name, such as "SaleDate."

Error Message

Cause

This error occurs because the column name that you used in the query syntax does not exist. Often this error is just a typographical error. Check the column names in a database against your query string. If you are using Microsoft Access, make sure that the actual column name is used and not a column's "display" name.