1. Error message (I don't have to translate into Chinese, huh, huh, everyone understand) Microsoft Ole DB Provider for ODBC Drivers Error '80004005' [Microsoft] [ODBC Microsoft Access 97 Driver] The Microsoft Jet DatabaseEngine Cannot Open THE FILE ' (unknown) '.. IT IS Already Opened Exclusivelyby Another User, or You NEED Permission to View ITS Data: This error occurs when IIS uses an anonymous account (usually IUSR), the account is in the directory where the database is in the database in NT. There is no correct permission. (This is why there is no problem under Win95 and PWS, because Win95 has no directory permission to check the file and directory. OK you can create and delete temporary files in this directory. Permission. These temporary files are actually files that the database is built in the same directory, but it should be noted that these files may also be built in other directories, such as / WinNT.
What directory is accessible when using NT's file monitor monitoring file fails. This NT file monitor can download http://www.sysinternals.com in this place.
If you use a network address for the database, such as a map address, you have to check the permissions of shared files and directories.
Also check if the data source file (DSN) is in use by other program flags, which are typically Visual InterDev, close to the projects in any InterDev, and a database connection.
This error may also happen: If a UNC path is used in the DSN (that is, the universal naming protocol), you can use the local path to test because if you use UNCs to the local database. It is also possible to happen, if the server wants to access a table in Access, and this table is coupled to a web server.
2. Error message: Microsoft OLE DB Provider for ODBC Drivers Error '80004005' [Microsoft] [ODBC Microsoft Access 97 Driver] COULDN '' '(unknown)'; FileAlReady IN Use. Cause: The database is locked when used.
3. error message: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft] [ODBC Driver Manager] Data source name not found and no defaultdriver specified Cause: The most likely cause is a ConnectString is initialized in the global.asa The session variable, but Global.asa did not work properly. The solution is to check if the value is correct: (add the following code) <% = "'auth_user' is" & request.servervariables ("auth_user")%>
<% = "'auth_type 'is "& required.servervariables (" auth_type ")%>
<% =" connection string is "& session (" Your_connectionstring ")%>
There is another reason to join in your ConnectString Excess space, such as DSN = MyDSN; Database = PUBS; try to change to the following: DSN = MyDSN; Database = PUBS; if it is Global.asa has not yet worked, check if the file is in the root directory of the program, Or in 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.
4. Error message Microsoft Ole DB Provider for ODBC Drivers Error '80004005' [Microsoft] [ODBC Driver Manager] Data Source Name Not ?? Cause: This error may be available on your computer installation (or reverse installation) In the order of order. If the version of the ODBC is inconsistent, it will happen. Solution is to install the latest version of MDAC
5. Error message: 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 love from the registry Time to the value. Use regedit32.exe to check the permissions of your registry. You can also read the failed information using the Registry Monitor (NTREGMON) in NT. This program is found 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 ()). Cause: Two 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 other relationship is the local path when you give a relationship. The error reason is that when the user uses the IIS anonymous account to log in, he is right, but for the machine for 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. Two solutions: 1. In the IIS tool, change the IIS anonymous account into another domain-based account. (I.e., no anonymous login) 2. Or, on the machine you want to access resources, create a sum of the same account as the current anonymous account, using the same password.
7. Error message 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 It is time to log in or if you don't use the administrator, or it may be caused by no SQL image account in NT.
Using System Administrator Account (SA), the general password should be empty. Note that you must use CoonectString without using the DSN file. Because the username and password are not saved in the DSN. Check if the NT is mapped to SQL.
8. The 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 reasons: The reason is the same. Try this method: In the Enterprise Manager of SQL Server, select Server / SQL Server / Configure [ASCII133] / Security Options / Standard. If you are running in IIS4, deselect the PASSWORD SYNCHRONIZATION option for the project.
9. 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) of the ACCESS database is generated without the correct permissions. This file is the same directory with your database. 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. Try using the following code. Set conn = server.createObject ("adoDb.connection") conn.mode = admodesharedenywrite '8
10. The error message Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft] [ODBC Microsoft Access 97 Driver] '(unknown)' is not a validpath. Make sure that the path name is spelled correctly and that you areconnected to Reason: The path illegally. It is most likely that when Global.asa and Coonecntstring are used to be used on another machine. 11. 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.
Reason: The query is too complicated, and the query is restricted.
12. Error message: Microsoft OLE DB Provider for ODBC Drivers Error '80004005' [Microsoft] [ODBC SQL Server Driver] [DBMSSOCN] General Network Error. CheckYour Network Document Cause: When there is a machine to be renamed with SQL Server. But DSN also uses the original machine name.
