Today, on a Win2K Server server, when installing the machine's Oracle9i database via the ASP, the error is found, and the database cannot be connected at all. Its error describes the following: Microsoft OLE DB Provider for ODBC Drivers Error '80004005' [Microsoft] [ODBC Driver Manager] Driver SQLAllochandle on SQL_HANDE_ENV Failed or Microsoft Ole DB Provider for ODBC Drivers Error '80004005' Due to System Error 5 ( Oracle in jxt_user, resulting in the way the specified driver connection cannot be loaded by ODBC, the driver includes Oracle ODBC Driver and Microsoft ODBC Driver for Oracle. The connection string is as follows: (1) Connectionstring = "dsn = txltns; uid = user; pwd = password" (2) Connectionstring = "driver = {Oracle in txl_user}; uid = user; pwd = password; dbq = txltns; dba = W; "The result is not working properly. After the examination, the% ORACLE_HOME% setting is correct, and it is included in the path. In Google Search for Simplified Chinese Information, I found an information statement as follows: "This is actually due to the error generated on the NTFS partition of the 2000 in 2000. Mainly IIS's permissions, can't find the error of Oracle9i." He also gives a bunch of English abstracts, the answer is:% Oracle_home% This directory is installed, it is set up permission, the default is the administrator group, the System group and a group called "Authenticated User" Permissions.
He also said that you should be like this: --------------------------------------- V. Click ON "Authenticated Users" Item in the "name" list (on Windows XP the "name" list is called "group or user names"). Vi. Uncheck the "read and execute" Box in the "permissions" list Windows XP the "Permissions" list is called "Permissions for Authenticated Users"). This box will be under the "Allow" column. vii. Check the "Read and Execute" box. This is the box you just unchecked. --- -------------------------------------- feel this English saying is a bit blamed, why should Cancel the "reading and execution" permission from the Authenticated User Group, isn't it not enough? Continue to check the relevant information in Oracle Technology Network, discover this information: ----------------------------------- ------ The Microsoft Odbc Driver for Oracle Is Known Not to Work Correctly on a 9.2 Oracle Client. You NEED TO Use You're Using The 9.2 Client. --------- ---------------------------------- This seems that this error occurred, and it is independent of Oracle installation configuration. It is successful because previously tested using Java through JDBC. So download the latest MDAC2.8, after installation, restart your computer, then test the original ASP program, and find that it has been successfully connected to the Oracle database. The "permission" problem that others said, it seems that it is not used here. Ha ha. Attached to: MDAC2.8 Download address: http://www.microsoft.com/downloads/details.aspx? DisplayLANG = zh-cn & familyid = 6c050FE3-C795-4B7D-B037-185D0506396 after: 2005/03/02 Today On another Win2000 Server, you can connect the remote Oracle database, so you only need to install Oracle's client in the system. At first, I chose "runtime" installed in Oracle Client 9.2.0.1.0, not "managed client" nor "custom."
After installation, then configure ODBC, why is there only one Microsoft ODBC for Oracle driver in ODBC, and does not expect Oracle special ODBC drivers. Since I have installed MDAC_type2.8, I first use Microsoft's ODBC for Oracle to generate a DSN. When I test ASP and remote Oracle, I found out that this error was found.
It seems that Microsoft's ODBC for Oracle driver is not working properly if the MDAC_Type2.8 is upgraded.
Later, in the list of Oracle9i "Custom" installation components, add "Oracle Windows Interfaces 9.2.0.1.0", after installation, Oracle in orahome92 This driver appears in the ODBC's driver list. Use Oracle in orahome92 to add a data source, follow the ASP program, and finally connect the remote Oracle database.
