Compatibility issues with ADSI 2.0, 2.5, and MDAC 2.1

Compatibility issues with ADSI 2.0, 2.5, and MDAC 2.1 (transferred from m$)
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Site Server version 3.0
Microsoft Site Server version 3.0, Commerce Edition
--------------------------------------------------------------------------------
Symptoms
Site Server Membership Samples and Commerce server Sample Sites use Active Directory Service interfaces (ADSI) 2.0.
There are several known compatibility issues with ADSI 2.0 and MDAC 2.1 that occur in the Site Server Membership Samples and Commerce server Sample Sites.
Problem #1: An OLE DB error occurred when you implemented a dynamic query in membership Sample Site.
When you implement a dynamic query to an LDAP directory through ADSI, the following error occurs:
Microsoft OLE DB Service components error 80040E21
The following ADSI connections failed:
Set myconnection = Server.CreateObject ("ADODB. Connection ") Myconnection.provider =" Adsdsoobject "My Connection.Open" ADs Provider "," "," "
Problem #2: ADSI 2.5 Installation causes a failure during the Commerce Server installation process.
The following error occurred during the configuration of the Trey Study sample site:
Cannot Set Attribute Description
Problem #3: After you install ADSI 2.5, Sawizard cannot configure the directory.
The following error occurred:
Sawizard:the NEW Membership Server Wizard cannot create or configure DS accounts for the selected services
Reason
Problem #1: This error occurs when the parameter data type passed to the stored procedure does not match the data type expected by the stored procedure.
This error occurs because ADSI 2.0 and MDAC 2.1 are incompatible.
Problem #2: This error occurs when ADSI 2.5 is installed before Site Server 3.0 is installed.
Site Server 3.0 installs ADSI 2.0 and overrides ADSI 2.5.
Although error messages do not appear during Site Server 3.0 setup, subsequent Commerce Server Setup fails when the sample site is configured by an LDAP directory.
Problem #3: This problem is caused by an incompatibility between ADSI 2.5 and Site Server 3.0 and Site Server 3.0 SP2.
This error can occur in the following situations:
An attempt was made to create multiple instances on the same computer that points to the same LDAP directory.