Error | resolution | data | database
The following is the virtual machine maintenance, often encountered in some ASP programs in the database call errors, are collected and sorted as follows:
Unable to open registry key (8007000e)
Microsoft OLE DB Provider for ODBC Drivers error ' 8007000e '
[Microsoft] [ODBC Microsoft Access Driver] Common error cannot open registry key ' temporary
(volatile) Jet DSN for process 0x11b4 Thread 0x1a4c DBC 0x9d34354 jet '.
1. When you open the database incorrectly, the standard Access database calls are written:
"Driver={microsoft Access Driver (*.mdb)};d bq=" & Server.MapPath ("DB. MDB ")
2. Uploading database files.
――――――――――――――――――――――――――――――――――――
General network error. Please check your network documentation (80004005)
Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 ' [Microsoft][odbc SQL Server DRIVER][TCP/IP Sockets] General network error. Please check your network documentation.
1. Incorrect database connection writing, possibly database name, server name error.
2. Database server reboot.
――――――――――――――――――――――――――――――――――――
cannot use '; file is already in use (80004005)
Microsoft JET Database Engine error ' 80004005 '
Cannot use '; file is already in use.
1. Files may be occupied: Upload, compress, pack.
2. There may be nested inclusion in the program code, repeating the contained database call file.
――――――――――――――――――――――――――――――――――――
cannot be updated. Database or object must use an updatable query for read/operate (80004005)
Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 '
[Microsoft] The [ODBC Microsoft Access Driver] operation must use an updatable query.
Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 ' [Microsoft][odbc Microsoft Access Driver] cannot be updated. The database or object is read-only.
1. database file permissions are not sufficient.
2. The amount of space occupied by the file reaches the disk limit.
There are several main reasons for the error when you are prompted to "operation must use an updatable query": This error occurs when your program attempts to perform an update database or other similar operation. This is because ADO is not able to write a database because of several reasons below.
1. The most common reason is that the anonymous user account (Iusr_machine) does not have write access to the database file. To resolve this problem, adjust the properties of the database file in the organizer so that anonymous users have the correct permissions. When you use an Access database, you will not only write permissions to the file, but also write permissions to the directory, because Jet needs to create a. ldb file in that directory.
2. The second reason is that the database is not open with the correct mode. You should open it using the following method.
SQL = "UPDATE products Set UnitPrice = 2;"
Set Conn = Server.CreateObject ("ADODB. Connection ")
Conn.mode = 3 ' 3 = adModeReadWrite
Conn.Open "MyDSN"
Conn.execute (SQL)
Conn.close
Note that the default mode is set 0 (adModeUnknown), which is allowed to be updated.
3. It is also possible to select the Read-only option for this DSN in the ODBC Administrator.
4. You are updating fields in two tables at the same time, and this error message appears, and the solution is to update the respective fields in both tables separately.
5. When you use a query that is loaded from a lower version (such as access2.0,access7.0) into a high version (ACCESS 2000), the error occurs when you execute the query.
――――――――――――――――――――――――――――――――――――
data source name not found and no default driver specified (80004005)
Microsoft OLE DB Provider for ODBC Drivers error ' 80004005 '
[Microsoft] [ODBC Driver Manager] did not find a data source name and no default driver specified
1. Using the ODBC Connection database, the ODBC database is not configured on the server, and the standard invocation method for OLE DB is used instead:
"Driver={sql Server};D atabase=dbname; Server=srv; Uid=user; PWD=PD "can be solved.