The information in the article applies to:
Microsoft Data Access Components versions 1.5, 2.0, 2.1, 2.5
Active Server Pages
Microsoft Visual InterDev, version 1.0
----------------------------------------------------------------------------
Summary
This article describes in detail some common reasons why Microsoft Data Access Component (MDAC) receives 0x800040005 errors. MDAC includes ActiveX data objects, OLE DB and Remote Data Services (RDS). At the same time, this article also discusses some other error messages, including 80040e21, 80040e14 and 80040e10.
More information
80004005 The error message can be summarized as: "For some reason, I cannot access your data." This article provides a list of various 80004005 error messages, which list the most common causes of these error messages and their troubleshooting steps. Although this article assumes that you are using ActiveX Data Objects (ADO) in the Active Server Page (ASP) page (.asp), these causes and many troubleshooting steps are also applicable to any other environment where data is accessed through ODBC.
Error message list
In this section we introduce the text of various error messages and the causes of the error.
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.
reason
This error usually occurs because the account (usually IUSR) used by Internet Information Server (IIS) does not have the correct Windows NT permissions, so it cannot access the file-based database or folder containing files. Please check the permission settings for these files and folders. Confirm that you are able to create and/or delete any temporary files. temporary
Files are generally created in the same folder as the database, but they can also be created in other folders, such as /Winnt. You can use the Windows NT File Monitor to check the reasons for the failure to access the file. Windows NT file monitors can be obtained from the following Web sites:
。
If you are using the network path (UNC or image drive) of the database, check the permissions on the shares, files, and folders. Confirm that the file and data source name (DSN) is not marked as exclusive. Use a system DSN that uses local drive letters. If necessary, move the database to the local drive and test it. The other user in the error message may be Visual InterDev. Please close any Visual InterDev project that contains data connections to the database.
The error can also be caused by a delegation problem. Check for any authentication methods that may exist ("basic" rather than NTLM). If the connection string uses the Uniform Naming Convention (UNC), try using "Basic Authentication" or an absolute path, such as C:\Mydata\. Even if the resource pointed to by UNC is located on the local IIS computer, the above error may occur.
This error may also occur when accessing a Microsoft Access database linked to a table if the table is in the Access database on the network server. In this case, see the following Microsoft Knowledge Base article for a feasible solution:
Q189408 PRB: ASP cannot access network files under IIS 4.0
Error message Microsoft OLE DB Provider for ODBC Drivers Error '80004005' [Microsoft][ODBC Microsoft Microsoft Access 97 Driver] Couldn't use '(unknown)'; file already in use.
reason
The database cannot be locked correctly for multiple users. For details, please refer to the following Microsoft Knowledge Base article:
Q174943 PRB： 80004005“Couldn't Use '(unknown)'；File Already in Use”
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.
reason
The most common reason is that the session variables initialized in the connection string are not fired. You can check whether the variable is initialized correctly by adding the following code to the .asp page:
Another common reason is that there are too many spaces in the connection string used.
DSN = MyDSN; Database = Pubs;
Try using the following syntax instead:
DSN=MyDSN;Database=Pubs;
If the file is not fired, please check and confirm that it is under the application root of IIS 4.0 (if you are running IIS 3.0, it should be under the virtual root, and the Execute check box is already selected). In addition, when Windows NT permissions restrict access to folders, an error in programming may also prevent the file from being fired. For more information, please refer to Microsoft Knowledge Base
article:
Q173742 "BUG: When restricting Web access, it is not executed" The DSN name cannot be found.
Please check and confirm that the DSN of the "User" type is not used.
If you are using a file DSN or a system DSN, try changing the connection string to DSN=MySystemDSN or DBQ=MyFileDSN accordingly. Simplify!
Check and confirm that the latest drivers are installed. If you are not sure about this, please download the latest MDAC (Microsoft Data Access Component) from the following Web site:
/data/
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC
Driver Manager] Data source name not ??
reason
This problem seems to be related to the order in which software is installed or uninstalled on your computer. This error may occur if the ODBC kernel files are not synchronized (they must be the same version).
Please download the latest version of MDAC (Microsoft Data Access Component) from the following Web site to upgrade all ODBC core drivers:
/data/
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'.
reason
This error is caused by reading a numeric value from the registry. Please use Registry Editor () to check the permissions set on the registry key. You can also use Windows NT Registry Monitor (NTRegMon) to check for registry reading failures. NTRegMon can be from
The following Web site downloads:
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver][dbnmpntw] ConnectionOpen (CreateFile()).
reason
There are two reasons for this error. They are all related to permissions, or the database is not on the same computer as the Web server, or the database is being referenced through the UNC path (\\Server\Share). Even if the database is on the same computer as the Web server, the UNC path makes the Web server think that the database seems to be on another computer on the network.
If the .asp page is being accessed by anonymous users, the following will happen:
IIS will use (default) Windows NT account:
USR_。
Because the account is the local account of the Web server, other computers on the network have no way to know the account. When IIS (running in a secure environment for an IUSR account) attempts to access any resources on the remote computer, the remote computer will verify the account it is using. Since the IUSR account is a local account, it is unknown to remote computers, so access is denied.
When anonymous access raises this problem, there are two solutions:
In the "Internet Service Manager" tool, change the anonymous login account from the default local account to a valid domain-based account from the Web property. In the User Name field, enter the domain account to use, the format is domain\userid. In this way, the remote computer can use the domain controller to verify the security credentials passed to it by IIS.
-or-
Account copied on a remote computer containing the resources you want to access
IUSR_. If the account is created on a remote computer, containing the exact same name and password, Windows NT takes it
They are considered equivalent accounts.
-or-
If the .asp page only allows authenticated access, please refer to the following content:
If the page does not allow anonymous access, IIS will attempt to verify the identity of the user who made the request and use their security credentials to control all their activities, such as the activity that accesses the database. The following explains the two main reasons for failure in this situation.
By default, IIS is configured to use Windows NT Challenge/Response as its authentication method.
Due to the limitations of the Windows NT 4.0 (and earlier) security model, users who have passed the Windows NT Challenge/Response authentication cannot access resources on the remote computer. This is usually
It is called a delegation problem. To verify whether this is the case, in the "Internet Service Manager" tool, select the Basic (Precision Text) check box from the Web properties, and then clear Windows NT Challenge/Response. If this step solves the problem, it is obvious that this is a delegation problem.
-or-
If the problem persists, it may be that the user account used does not have the correct SQL Windows NT computer permissions. You might as well try using an account that explicitly has access to the SQL computer.
For more information on delegation, how IIS can protect web sites through authentication, and related issues, please refer to the article "IIS Authentication and
Security for Internet Developers”，
It is located at the following Web site:
/workshop/s...re/
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' Microsoft][ODBC Microsoft SQL Driver] Logon Failed()
reason
This error is generated by the SQL server when the SQL server does not accept or recognize the submitted login account and/or password (when using standard security), or if no Windows NT accounts are mapped to the SQL account (when using integrated security).
If you are using standard security, it means that the SQL account name and password are incorrect. Please try using the system administrator account and password (UID="SA", password is empty). These must be defined in the connection string because DSN does not store username and password.
If you are using integrated security, check the Windows NT account on the call page to find out the target account it maps.
SQL Don't allow underscores in SQL Account names. If someone manually maps the Windows NT account IUSR_machinename to a SQL account with the same name, it will fail. Please map all accounts containing underscores to account names that do not contain underscores in SQL.
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.
reason
Integrated security is turned on in SQL Enterprise Manager, and the Windows NT account used is not mapped to the SQL account.
Please try to switch SQL to standard security (in Enterprise Manager, select Server/SQL Server/Configure/Security Options/Standard.
If you are running under IIS 4.0, deselect password synchronization for the project.
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBCMicrosoft Access 97 Driver]Couldn't lock file.
reason
This error may be caused by not having the correct permissions to create a locked file (.ldb) for the Microsoft Access database. By default, the locked file is created in the same folder as the Microsoft Access.mdb file.
Please try to give users accessing the database (usually IUSR_machinename) full control permissions to share/folders.
Sometimes, shared folder permissions are set to read-only. You can also try to change the connection mode, and you can use the following sample code:
Set Conn = ("")
= adModeShareDenyWrite '8
'From
'---- ConnectModeEnum values ----
'Const adModeUnknown = 0
'Const adModeRead = 1
'Const adModeWrite = 2
'Const adModeReadWrite = 3
'Const adModeShareDenyRead = 4
'Const adModeShareDenyWrite = 8
'Const adModeShareExclusive = &Hc
'Const adModeShareDenyNone = &H10
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access 97 Driver] '(unknown)' isn't a valid path. Make sure that the path name is spel
led correctly and that you are connected to the server on which the file resides.
reason
The path read by the web server is an invalid path. This error is most likely to occur when a file is being used and the connection string is created on another computer outside the web server. If the path is an image drive letter, it may only be valid for the client computers that created the connection string.
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver][SQL Server] The query and the views in it exceed the limit of 16 tables.
reason
Query is too complicated. There are too many restrictions in the query.
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server
DRIVER][DBNMPNTW] CONNECTIONWRITE (GETOVERLAPPEDRESULT()).
reason
When the "Allow anonymous users" environment is closed, WINDOWS NT must close the pipeline connected to SQL SERVER after the first request is completed. This is because the first connection to SQL SERVER is established in the IIS anonymous user account. Then, IIS either chooses to simulate a browser client on the same thread, or attempts to access connections on other threads running in the simulated user environment. In either case, WINDOWS NT will detect if anyone attempts to use a network named pipe handle that has been opened in other user environments and close the pipe according to security rules. In SQL SE
According to RVER Network Monitor, this is a request issued by WINDOWS NT to close the named pipe, which causes a WEB browser error.
Error message
MICROSOFT OLE DB PROVIDER FOR ODBC DRIVERS ERROR '80004005' [MICROSOFT][ODBCSQL SERVER DRIVER][DBMSSOCN] GENERAL NETWORK ERROR. CHECK YOUR NETWORK DOCUMENT
reason
This error may occur when the SQL server is renamed. Since the computer name cannot be found, the DSN that references the old name will fail.
Error message
MICROSOFT OLE DB PROVIDER FOR ODBC DRIVERS ERROR '80040E21' ERRORS OCCURRED
reason
This error may be caused by attempting to insert too much data into a field, exceeding the allowable value. For example, a MICROSOFT ACCESS field format is set to accept only 25 characters, and attempt to insert 26 characters.
Error message
MICROSOFT OLE DB PROVIDER FOR ODBC DRIVERS ERROR '80040E14' [MICROSOFT][ODBC MICROSOFT ACCESS 97 DRIVER]
SYNTAX ERROR IN INSERT INTO STATEMENT.
reason
A column name may be a reserved word, such as DATE. Please change the column name to a non-reserved word, such as SALEDATE.
Error message
MICROSOFT OLE DB PROVIDER FOR ODBC DRIVERS ERROR '80040E10' [MICROSOFT][ODBC MICROSOFT ACCESS 97 DRIVER]
TOO FEW PARAMETERS. EXPECTED 1.
reason
The column name used in the query syntax does not exist. Often, this is just a typo. Please check the column names in the query string by checking the column names in the query string. If you are using MICROSOFT ACCESS, make sure you are using the actual column name, not the column's "display" name.
refer to
To enable the remote workstation working method of VISUAL INTERDEV, please follow the following MICROSOFT KNOWLEDGE BASE article to establish a system DSN:
Q178215 HOWTO: Configure VID for authentication WEB project
Q174943 PRB： 80004005“COULDN'T USE '(UNKNOWN)'；FILE ALREADY IN USE”
Q173742 BUG: Restricted WEB access, not executed
Q172864 ASP page cannot access sessions and application objects
Q156526 General error when connecting ACCESS data source =51
Q175671 PRB: SQL80004005 CONNECTIONOPEN (CREATEFILE()) error during access
Q149425 IDC: Error in execution of query, not defined as a valid user
Q167452 PRB: 'NOT A VALID PATH' error when using ACCESS data source
Q125767 PRB: Query after executing SQL query is too complicated error
Q166659 PRB: Access to SQL database failed on the second attempt
Q166029 PRB: When using ACCESS, unidentified files cannot be opened.
Q178215 HOWTO: Configure VID for authentication WEB project
Microsoft Data Access Components versions 1.5, 2.0, 2.1, 2.5
Active Server Pages
Microsoft Visual InterDev, version 1.0
----------------------------------------------------------------------------
Summary
This article describes in detail some common reasons why Microsoft Data Access Component (MDAC) receives 0x800040005 errors. MDAC includes ActiveX data objects, OLE DB and Remote Data Services (RDS). At the same time, this article also discusses some other error messages, including 80040e21, 80040e14 and 80040e10.
More information
80004005 The error message can be summarized as: "For some reason, I cannot access your data." This article provides a list of various 80004005 error messages, which list the most common causes of these error messages and their troubleshooting steps. Although this article assumes that you are using ActiveX Data Objects (ADO) in the Active Server Page (ASP) page (.asp), these causes and many troubleshooting steps are also applicable to any other environment where data is accessed through ODBC.
Error message list
In this section we introduce the text of various error messages and the causes of the error.
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.
reason
This error usually occurs because the account (usually IUSR) used by Internet Information Server (IIS) does not have the correct Windows NT permissions, so it cannot access the file-based database or folder containing files. Please check the permission settings for these files and folders. Confirm that you are able to create and/or delete any temporary files. temporary
Files are generally created in the same folder as the database, but they can also be created in other folders, such as /Winnt. You can use the Windows NT File Monitor to check the reasons for the failure to access the file. Windows NT file monitors can be obtained from the following Web sites:
。
If you are using the network path (UNC or image drive) of the database, check the permissions on the shares, files, and folders. Confirm that the file and data source name (DSN) is not marked as exclusive. Use a system DSN that uses local drive letters. If necessary, move the database to the local drive and test it. The other user in the error message may be Visual InterDev. Please close any Visual InterDev project that contains data connections to the database.
The error can also be caused by a delegation problem. Check for any authentication methods that may exist ("basic" rather than NTLM). If the connection string uses the Uniform Naming Convention (UNC), try using "Basic Authentication" or an absolute path, such as C:\Mydata\. Even if the resource pointed to by UNC is located on the local IIS computer, the above error may occur.
This error may also occur when accessing a Microsoft Access database linked to a table if the table is in the Access database on the network server. In this case, see the following Microsoft Knowledge Base article for a feasible solution:
Q189408 PRB: ASP cannot access network files under IIS 4.0
Error message Microsoft OLE DB Provider for ODBC Drivers Error '80004005' [Microsoft][ODBC Microsoft Microsoft Access 97 Driver] Couldn't use '(unknown)'; file already in use.
reason
The database cannot be locked correctly for multiple users. For details, please refer to the following Microsoft Knowledge Base article:
Q174943 PRB： 80004005“Couldn't Use '(unknown)'；File Already in Use”
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.
reason
The most common reason is that the session variables initialized in the connection string are not fired. You can check whether the variable is initialized correctly by adding the following code to the .asp page:
Another common reason is that there are too many spaces in the connection string used.
DSN = MyDSN; Database = Pubs;
Try using the following syntax instead:
DSN=MyDSN;Database=Pubs;
If the file is not fired, please check and confirm that it is under the application root of IIS 4.0 (if you are running IIS 3.0, it should be under the virtual root, and the Execute check box is already selected). In addition, when Windows NT permissions restrict access to folders, an error in programming may also prevent the file from being fired. For more information, please refer to Microsoft Knowledge Base
article:
Q173742 "BUG: When restricting Web access, it is not executed" The DSN name cannot be found.
Please check and confirm that the DSN of the "User" type is not used.
If you are using a file DSN or a system DSN, try changing the connection string to DSN=MySystemDSN or DBQ=MyFileDSN accordingly. Simplify!
Check and confirm that the latest drivers are installed. If you are not sure about this, please download the latest MDAC (Microsoft Data Access Component) from the following Web site:
/data/
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC
Driver Manager] Data source name not ??
reason
This problem seems to be related to the order in which software is installed or uninstalled on your computer. This error may occur if the ODBC kernel files are not synchronized (they must be the same version).
Please download the latest version of MDAC (Microsoft Data Access Component) from the following Web site to upgrade all ODBC core drivers:
/data/
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'.
reason
This error is caused by reading a numeric value from the registry. Please use Registry Editor () to check the permissions set on the registry key. You can also use Windows NT Registry Monitor (NTRegMon) to check for registry reading failures. NTRegMon can be from
The following Web site downloads:
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver][dbnmpntw] ConnectionOpen (CreateFile()).
reason
There are two reasons for this error. They are all related to permissions, or the database is not on the same computer as the Web server, or the database is being referenced through the UNC path (\\Server\Share). Even if the database is on the same computer as the Web server, the UNC path makes the Web server think that the database seems to be on another computer on the network.
If the .asp page is being accessed by anonymous users, the following will happen:
IIS will use (default) Windows NT account:
USR_。
Because the account is the local account of the Web server, other computers on the network have no way to know the account. When IIS (running in a secure environment for an IUSR account) attempts to access any resources on the remote computer, the remote computer will verify the account it is using. Since the IUSR account is a local account, it is unknown to remote computers, so access is denied.
When anonymous access raises this problem, there are two solutions:
In the "Internet Service Manager" tool, change the anonymous login account from the default local account to a valid domain-based account from the Web property. In the User Name field, enter the domain account to use, the format is domain\userid. In this way, the remote computer can use the domain controller to verify the security credentials passed to it by IIS.
-or-
Account copied on a remote computer containing the resources you want to access
IUSR_. If the account is created on a remote computer, containing the exact same name and password, Windows NT takes it
They are considered equivalent accounts.
-or-
If the .asp page only allows authenticated access, please refer to the following content:
If the page does not allow anonymous access, IIS will attempt to verify the identity of the user who made the request and use their security credentials to control all their activities, such as the activity that accesses the database. The following explains the two main reasons for failure in this situation.
By default, IIS is configured to use Windows NT Challenge/Response as its authentication method.
Due to the limitations of the Windows NT 4.0 (and earlier) security model, users who have passed the Windows NT Challenge/Response authentication cannot access resources on the remote computer. This is usually
It is called a delegation problem. To verify whether this is the case, in the "Internet Service Manager" tool, select the Basic (Precision Text) check box from the Web properties, and then clear Windows NT Challenge/Response. If this step solves the problem, it is obvious that this is a delegation problem.
-or-
If the problem persists, it may be that the user account used does not have the correct SQL Windows NT computer permissions. You might as well try using an account that explicitly has access to the SQL computer.
For more information on delegation, how IIS can protect web sites through authentication, and related issues, please refer to the article "IIS Authentication and
Security for Internet Developers”，
It is located at the following Web site:
/workshop/s...re/
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' Microsoft][ODBC Microsoft SQL Driver] Logon Failed()
reason
This error is generated by the SQL server when the SQL server does not accept or recognize the submitted login account and/or password (when using standard security), or if no Windows NT accounts are mapped to the SQL account (when using integrated security).
If you are using standard security, it means that the SQL account name and password are incorrect. Please try using the system administrator account and password (UID="SA", password is empty). These must be defined in the connection string because DSN does not store username and password.
If you are using integrated security, check the Windows NT account on the call page to find out the target account it maps.
SQL Don't allow underscores in SQL Account names. If someone manually maps the Windows NT account IUSR_machinename to a SQL account with the same name, it will fail. Please map all accounts containing underscores to account names that do not contain underscores in SQL.
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.
reason
Integrated security is turned on in SQL Enterprise Manager, and the Windows NT account used is not mapped to the SQL account.
Please try to switch SQL to standard security (in Enterprise Manager, select Server/SQL Server/Configure/Security Options/Standard.
If you are running under IIS 4.0, deselect password synchronization for the project.
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBCMicrosoft Access 97 Driver]Couldn't lock file.
reason
This error may be caused by not having the correct permissions to create a locked file (.ldb) for the Microsoft Access database. By default, the locked file is created in the same folder as the Microsoft Access.mdb file.
Please try to give users accessing the database (usually IUSR_machinename) full control permissions to share/folders.
Sometimes, shared folder permissions are set to read-only. You can also try to change the connection mode, and you can use the following sample code:
Set Conn = ("")
= adModeShareDenyWrite '8
'From
'---- ConnectModeEnum values ----
'Const adModeUnknown = 0
'Const adModeRead = 1
'Const adModeWrite = 2
'Const adModeReadWrite = 3
'Const adModeShareDenyRead = 4
'Const adModeShareDenyWrite = 8
'Const adModeShareExclusive = &Hc
'Const adModeShareDenyNone = &H10
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access 97 Driver] '(unknown)' isn't a valid path. Make sure that the path name is spel
led correctly and that you are connected to the server on which the file resides.
reason
The path read by the web server is an invalid path. This error is most likely to occur when a file is being used and the connection string is created on another computer outside the web server. If the path is an image drive letter, it may only be valid for the client computers that created the connection string.
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver][SQL Server] The query and the views in it exceed the limit of 16 tables.
reason
Query is too complicated. There are too many restrictions in the query.
Error message
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server
DRIVER][DBNMPNTW] CONNECTIONWRITE (GETOVERLAPPEDRESULT()).
reason
When the "Allow anonymous users" environment is closed, WINDOWS NT must close the pipeline connected to SQL SERVER after the first request is completed. This is because the first connection to SQL SERVER is established in the IIS anonymous user account. Then, IIS either chooses to simulate a browser client on the same thread, or attempts to access connections on other threads running in the simulated user environment. In either case, WINDOWS NT will detect if anyone attempts to use a network named pipe handle that has been opened in other user environments and close the pipe according to security rules. In SQL SE
According to RVER Network Monitor, this is a request issued by WINDOWS NT to close the named pipe, which causes a WEB browser error.
Error message
MICROSOFT OLE DB PROVIDER FOR ODBC DRIVERS ERROR '80004005' [MICROSOFT][ODBCSQL SERVER DRIVER][DBMSSOCN] GENERAL NETWORK ERROR. CHECK YOUR NETWORK DOCUMENT
reason
This error may occur when the SQL server is renamed. Since the computer name cannot be found, the DSN that references the old name will fail.
Error message
MICROSOFT OLE DB PROVIDER FOR ODBC DRIVERS ERROR '80040E21' ERRORS OCCURRED
reason
This error may be caused by attempting to insert too much data into a field, exceeding the allowable value. For example, a MICROSOFT ACCESS field format is set to accept only 25 characters, and attempt to insert 26 characters.
Error message
MICROSOFT OLE DB PROVIDER FOR ODBC DRIVERS ERROR '80040E14' [MICROSOFT][ODBC MICROSOFT ACCESS 97 DRIVER]
SYNTAX ERROR IN INSERT INTO STATEMENT.
reason
A column name may be a reserved word, such as DATE. Please change the column name to a non-reserved word, such as SALEDATE.
Error message
MICROSOFT OLE DB PROVIDER FOR ODBC DRIVERS ERROR '80040E10' [MICROSOFT][ODBC MICROSOFT ACCESS 97 DRIVER]
TOO FEW PARAMETERS. EXPECTED 1.
reason
The column name used in the query syntax does not exist. Often, this is just a typo. Please check the column names in the query string by checking the column names in the query string. If you are using MICROSOFT ACCESS, make sure you are using the actual column name, not the column's "display" name.
refer to
To enable the remote workstation working method of VISUAL INTERDEV, please follow the following MICROSOFT KNOWLEDGE BASE article to establish a system DSN:
Q178215 HOWTO: Configure VID for authentication WEB project
Q174943 PRB： 80004005“COULDN'T USE '(UNKNOWN)'；FILE ALREADY IN USE”
Q173742 BUG: Restricted WEB access, not executed
Q172864 ASP page cannot access sessions and application objects
Q156526 General error when connecting ACCESS data source =51
Q175671 PRB: SQL80004005 CONNECTIONOPEN (CREATEFILE()) error during access
Q149425 IDC: Error in execution of query, not defined as a valid user
Q167452 PRB: 'NOT A VALID PATH' error when using ACCESS data source
Q125767 PRB: Query after executing SQL query is too complicated error
Q166659 PRB: Access to SQL database failed on the second attempt
Q166029 PRB: When using ACCESS, unidentified files cannot be opened.
Q178215 HOWTO: Configure VID for authentication WEB project