Error message (I do not need to translate the error information into Chinese. Thank you for your understanding)
Microsoft ole db provider for ODBC drivers error '000000'
[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.
Use nt file monitoring Program What directory is accessed when the 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 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.
Error message:
Microsoft ole db provider for ODBC drivers error '000000'
[Microsoft] [ODBC Microsoft Access 97 driver] couldn't use '(unknown)'; File
Already in use.
Cause:
The database is locked when multiple users use it.
Error message:
Microsoft ole db provider for ODBC drivers error '000000'
[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 to your ASP: Code )
<% = "'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.
Error Message
Microsoft ole db provider for ODBC drivers error '000000'
[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.
Error message:
Microsoft ole db provider for ODBC drivers error '000000'
[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
Error message:
Microsoft ole db provider for ODBC drivers error '000000'
[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.
Error Message
Microsoft ole db provider for ODBC drivers error '000000' 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.
Error Message
Microsoft ole db provider for ODBC drivers error '000000'
[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 as above.
Try this method: in Enterprise Manager of SQL Server, Select Server/SQL Server/configure [ASCII
133]/security options/standard.
If it is running In IIS4, deselect the password synchronization option for this project.
Error Message
Microsoft ole db provider for ODBC drivers error '000000'
[Microsoft] [ODBC Microsoft Access 97 driver] Couldn't lock file.
Cause:
Maybe you do not have the correct permission to generate the ACCESS database lock file (. LDB)
By default, the file is in the same directory as your database.
Grant the anonymous account full permission to access the database shared directory.
Sometimes it is because the file is intentionally used for read-only permission sharing. Try the following code.
Set conn = server. Createobject ("ADODB. Connection ")
Conn. mode = admodesharedenywrite '8
Error Message
Microsoft ole db provider for ODBC drivers error '000000'
[Microsoft] [ODBC Microsoft Access 97 driver] '(unknown) 'isn' t a valid
Path. Make sure that the path name is spelled correctly and that you are
Connected to the server on which the file resides.
Cause:
The path is invalid. Most likely, this occurs when global. Asa and coonecntstring are used on another machine.
Error Message
Microsoft ole db provider for ODBC drivers error '000000'
[Microsoft] [odbc SQL Server Driver] [SQL Server] the query and the views in
It exceed the limit of 16 tables.
Cause:
The query is too complex and has restrictions on the query.
Error message:
Microsoft ole db provider for ODBC drivers error '000000'
[Microsoft] [odbc SQL Server Driver] [dbmssocn] General network error. Check
Your network document
Cause:
When the machine with SQL Server is renamed. However, DSN also uses the original machine name.
