Common 80004005 errors and their solutions
In the process of writing a web application, we often have to deal with the database, such as database Access, SQL Server, etc. we often use. When connecting these databases, the system tends to give us some "80004005" errors, these five hundred erroneous information is very headache. In order to facilitate netizens to solve such problems, this article will introduce and answer this kind of problem.
[Error Message] Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft] [ODBC Microsoft Access 97 Driver] The Microsoft Jet databaseengine can not open the file '(unknown)'. It is already opened exclusivelyby another user, or you need Permission to View ITS Data. [Cause] This error occurs when IIS uses an anonymous account (usually IUSR), which is not correct in the directory where the database is located in NT.
[Solution] 1. Check the permissions for files and directories. Ensure that Evryone can have new and delete temporary files in this directory. 2. Check if the data source file (DSN) is used by other programs, these programs are generally Visual InterDev, closing any items that are open and database connections in InterDev. 3. Check if a table in Access is already connected on a web server at this time. [Error Information] Microsoft OLE DB Provider for ODBC Drivers Error '80004005' [Microsoft] [ODBC Microsoft Access 97 Driver] Couldn't Use '(unknown)'; FileAlReady in Use. [Cause] To connect Access database, it is being Use the database to be locked, resulting in unacceptable.
[Error Message] Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft] [ODBC Driver Manager] Data source name not found and no defaultdriver specified. [Reasons] ConnectString possible reason is initialized in the global.asa Application connection String, and this global.asa file is not working properly.
[Solution]
Check if the assignment is correct, add the following code in the ASP: <% = "'auth_user' is" & request.servervariables ("auth_user")%>
<% = "'auth_type' is" & request.servervariables ("Auth_Type")%>
<% = "Connection String is" & session ("Your_Connectionstring")%>
There is another reason to add spaces in ConnectString, such as DSN = MyDSN; Database = Pubs Try to change to the following: DSN = MyDSN; Database = PUBS; if Global.asa has not been run, check if the file is in the root of the program, or the root directory of the virtual directory. There is also a possibility that the cause is that the DSN name is not found, which can be solved by Idle Id = 36767. Finally, check whether the latest driver is installed, whether it is the latest MDAC version. [Error] Microsoft Ole DB Provider for ODBC Drivers Error '80004005' [Microsoft] [ODBC Driver Manager] Data Source Name NOT ?? [Cause] This error may appear on your computer installation (or reverse installation) The order is in the order. If the version of the ODBC is inconsistent, it will happen. [Solution]
The way is to install the latest version of MDAC.
[Error Information] Microsoft Ole DB Provider for ODBC Drivers Error '80004005' [Microsoft] [ODBC Access 97 ODBC Driver Driver] General Error Unable to OpenRegistry Key 'DriverId'. [Cause] This error occurs in reading the value from the registry when. Check the permissions of the registry using regedit32.exe.
[Error Information] Microsoft Ole DB Provider for ODBC Drivers Error '80004005' [Microsoft] [ODBC SQL Server Driver] [DBNMPNTW] ConnectionOpen (CREATEFILE ()). One of the reasons: When a database is included in a database This may also occur on the same machine when the license is on the machine, and the next relationship is a local path. Cause 2: When the user uses the IIS anonymous account to log in, he is right for local machines, but for a machine of a UNC path, this machine will not think that your current anonymous login account is in it. That is also legal. This does not allow you to access the resources above, causing errors. [Solution] 1. In the IIS tool, change the IIS anonymous account into another domain-based account. (I.e., not using anonymous login) 2, or create one of the same accounts as the current anonymous account on the machine you want to access resources, using the same password.
[Error Information] Microsoft Ole DB Provider for ODBC Drivers Error '80004005' Microsoft] [ODBCMICROSoft SQL Driver] Logon Failed () [Cause] This error is generated by SQL Server, when it is not accepted or can not know this login account When you use an administrator to log in, it may be caused by no SQL image in NT. [Workaround] Log in with the System Administrator Account (SA), the general password should be empty. Note that CoonectString must be used without using the DSN file. Because the username and password are not saved in the DSN. Check if the NT is mapped to 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 valid user of a trusted SQL Server connection [reason ] This error is generated by SQL Server, when it is not accepted or can not know this login account, or if you do not log in as an administrator, it may be caused by no SQL image in NT. [Solution]
In the Enterprise Manager of SQL Server, select Server / SQL Server / Configure [ASCII133] / Security Options / Standard. If it is running in IIS4, deselect the Password Synchronization option for the item.
[Error Information] Microsoft Ole DB Provider for ODBC Drivers Error '80004005' [Microsoft] [ODBC Microsoft Access 97 Driver] COULDN '' LOCK FILE. [Cause] Perhaps the lock file (.LDB) that does not have the correct permissions to generate an Access database (.ldb) This file is the same directory at the same directory by default. Access the permissions of the database shared directory for anonymous accounts. Sometimes because the file is due to sharing, it is intended to use only read-only permissions.
[Solution] Set Conn = Server.CreateObject ( "ADODB.Connection") Conn.Mode = adModeShareDenyWrite '8 [error] Microsoft OLE DB Provider for ODBC Drivers error' 80004005 '[Microsoft] [ODBC Microsoft Access 97 Driver]' (unknown) 'isn't a validpath. make sure what the path name is spelled to the server on which the file resides. [Cause] path illegal. It is most likely that when Global.asa and Coonecntstring are used to be used on another machine. [Error Information] Microsoft OLE DB Provider for ODBC Drivers Error '80004005' [Microsoft] [ODBC SQL Server Driver] [SQL Server] The Query and The Views INIT EXCEED The Limit of 16 Tables. [Cause] There is a restriction on the query.
[Error Information] Microsoft OLE DB Provider for ODBC Drivers Error '80004005' [Microsoft] [ODBC SQL Server Driver] [DBMSSOCN] General Network Error. CheckYour Network Document [Cause] The machine with SQL Server is renamed, but the database name ( DSN) also used the original machine name. [Solution]
Reset DSN.
