Asp error message Summary

SubmittedIcebergOn 2004, November 24, AM.ASP

1. error message Microsoft ole db Provider for ODBC Drivers error "80004005" [Microsoft] [ODBC Microsoft Access 97 Driver] The Microsoft Jet database Engine cannot open the file "(unknown)". It is already opened exclusively By another user, or you need permission to view its data. Cause: This error occurs when IIS uses an anonymous account (usually IUSR) and the account is in the NT directory of the database. You do not have the correct permission. (This is why Win95 and PWS are okay, because win95 has no directory permission) Check the file and directory permissions. Make sure that you have the permission to create and delete temporary files in the directory. These temporary files are actually files created in the same directory of the database, but note that these files may It may also be created in another directory, such as/Winnt. What directory is accessed when an NT file monitoring program fails to monitor the file. 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 ing address, check the permissions of shared files and directories, Check whether the data source file (DSN) is marked as in use by other programs, These other programs are generally Visual InterDev, which closes any project in InterDev that is connecting to the database. This error may also occur when a UNC path (generic naming Protocol) is used in the DSN. Test the local path because an error may occur if you use UNC for the local database. This may also happen if the server wants to Access a table in Access, but the table is connected to a network server. 2. error message: Microsoft ole db Provider for ODBC Drivers error "80004005" [Microsoft] [ODBC Microsoft Access 97 Driver] Couldn "t use" (unknown) "; file Already in use. Cause: The database is locked when multiple users use 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. Cause: The most likely cause is that ConnectString is a Session variable initialized in global. asa, but global. asa But not working properly. The solution is to check whether the assignment is correct: (Add the following code to your asp) <% = "" Auth_user "is" & request. servervariables ("auth_user") %> <P> <% = "" Auth_type "is" & request. servervariables ("auth_type") %> <P> <% = "Connection string is" & session ("your_connectionstring") %> <P> Another reason is that you add extra spaces to your ConnectString, such DSN = MyDSN; Database = Pubs; Try to change it to the following: DSN = MyDSN; Database = Pubs; If global. asa is not working, check whether the file is in the root directory of the application or the root directory of the virtual directory. The possible cause of the error is that the DSN name is not found, which can be solved by the id = 36767 method provided by me. Finally, check whether the latest driver is installed, that is, 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 occur in the software installation (or reverse installation) sequence on your computer. This error occurs if the ODBC version is inconsistent. The 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 open Registry key "DriverId". Cause: 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 Monitoring Program (NTRegMon) in NT to view the failed reading information. The program finds it here: 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 contains a license relationship that is independent of machines, This may also happen on the same machine. When you set a UNC path for a link, the other link is a local path. The cause of the error is: After a user logs on using an anonymous IIS account, the user has the right to log on to the local machine, but for a machine with a UNC path, In addition, this machine does not think that the account you are currently logged on anonymously is also valid on it. In this way, it does not allow you to access the resources above it, resulting in errors. Two solutions: 1. In IIS tools, change the IIS Anonymous account to another domain-based account. (That is, do not use anonymous logon) 2. Or create an account on the machine on which you want to access resources and use the same password as the current anonymous account. 7. error message Microsoft ole db Provider for ODBC Drivers error "80004005" Microsoft] [ODBC Microsoft SQL Driver] Logon Failed () Cause: This error is generated by SQL Server. If it does not accept or cannot recognize this Logon account, or does not log on as an administrator, It may also be caused by the absence of an SQL shadow account in NT. Use the system administrator account (SA) to log on. Generally, the password should be blank. Note that you must use the CoonectString instead of the DSN File. Because the user name and password are not saved in DSN. Check whether NT maps an account to SQL. 8. error message Microsoft ole db Provider for ODBC Drivers error "80004005" [Microsoft] [odbc SQL Server Driver]