Error 80004005 Information processing method
1. Error message (Error message, I don't have to translate into Chinese, huh, everyone understands) Microsoft Ole DB Provider for odbc drivers error '' '80004005' [Microsoft] [ODBC Microsoft Access 97 Driver] The Microsoft Jet DatabaseEngine Cannot Open THE File '' '' '. IT IS Already Opened Exclusivelyby Another User, or You Need Permissions To View ITS Data: This error occurs when IIS uses an anonymous account (usually IUSR), the account is in NT. The directory where the database is located does not have correct permissions. (This is why there is no problem under Win95 and PWS, because Win95 does not have directory permissions to check the permissions of the file and directory. Make sure you can create new and Delete the permissions of a temporary file. 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. Using the NT file monitoring file to fail, it is access to the end What is a directory. 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, and check it out. Data Source File (DSN) is being used by other program flags, which are typically Visual InterDev, close to any INTERDEV's positive open and database connections. 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' '' '' '; FileAlReady IN Use. Cause: Multi-person use The database is locked. 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 in global.asa The SESSION variables initiated in the initialization, but Global.asa did not work properly.
The solution is to check whether the assignment is correct: (add the following code) <% = "'Auth_User' '' IS" & Request.ServerVariables ("Auth_user")%>
<% = " '' Auth_Type '' '' & Request.ServerVariables ("Auth_Type")%>
<% = "Connection String IS" & session ("Your_ConnectionsTRING")%>
There is another reason is you in yours. Energent spaces are added to, for example, 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 using the program In the root directory, 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 information 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 software installation (or The order of installation) is installed. If the version of the ODBC is inconsistent, it will happen. The solution is to install the latest version of MDAC5 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 '' reasons: This error occurs when love reading a value from the registry. 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.com6. 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 licensing relationships on the machine, this may also happen on the same machine, and when you set a UNC path, and another relationship is local path. 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] [ODBCMICROFT SQL Driver] Logon Failed () Cause: This error is generated by SQL Server, when it is not accepted or can not know this login At the time of the account, or if you do not log in as an administrator, it may be caused by no SQL image 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. Cause: 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 message Microsoft Ole DB Provider for ODBC Drivers Error '' 80004005 '[Microsoft] [ODBC Microsoft Access 97 Driver] COULDN'' '' '' '' '' '' '' '' LDB) This file is the same directory with your database at the 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. Try using the following code. Set Conn = Server.CreateObject ( "ADODB.Connection") Conn.Mode = adModeShareDenyWrite '' 810. Error message Microsoft OLE DB Provider for ODBC Drivers error '' 80004005 '' [Microsoft] [ODBC Microsoft Access 97 Driver] '' ( Reason: Path illegal path. It is most likely that when Global.asa and Coonecntstring are used to be used on another machine.
