In the process of writing web applications, we often have to deal with databases, such as database access and SQL server that we often use. When connecting to these databases, the system will often give us something like this"
80004005"Errors, these various error messages are another headache. To help users solve such problems, this article will detail and answer these questions.
[Error message]
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 directory of the database in NT
You do not have the correct permission.
[Solution]
1. Check the file and directory permissions to ensure that evryone has the permission to create and delete temporary files in the directory.
2. Check whether the data source file (DSN) is marked in use by other programs. These programs are generally Visual InterDev, closing any project that is enabling connection to the database in InterDev.
3. check whether a table in access 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]
To connect to the Access database, the database is being used and locked, resulting in access failure.
[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 possible cause is that connectstring is the application connection string initialized in global. Asa, but the global. Asa file does not work properly.
[Solution]
Check whether the assignment is correct. Add the following code to 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 a space is added to connectstring, for example
DSN = mydsn; database = pubs;
Try to change it to the following:
DSN = mydsn; database = pubs;
If global. ASA is not running, 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.
[Solution]
The method 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 a value is read from the registry. Use regedit32.exe to check Registry Permissions.
[Error message]
Microsoft ole db provider for ODBC drivers error '000000'
[Microsoft] [odbc SQL Server Driver] [dbnmpntw] connectionopen (createfile ()).
[Cause]
One of the reasons: When a database contains a license relationship on a separate machine, this may also happen on the same machine. When a UNC path is set for a link, the other link is a local path.
Cause 2: 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.
[Solution]
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 the resource 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.
[Solution]
Log On with the system administrator account (SA). 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]
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.
[Solution]
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.
[Solution]
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]
Queries are restricted.
[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]
The machine with SQL Server is renamed, but the database name (DSN) uses the original machine name.
[Solution]
Reset the DSN.