ADSI 2.0, 2.5, and MDAC 2.1 Compatibility Issues

This article was previously published under Q216709
This article has been archived. It is offered "as is" and will no longer be updated.
Site Server Membership Samples and Commerce Server Sample Sites use ActiveDirectory Service Interfaces (ADSI) 2.0. There are several knowncompatibility issues with ADSI 2.0 and MDAC 2.1 that occur in the SiteServer Membership Samples and Commerce Server Sample Sites.

Issue #1: When you conduct dynamic queries from the MembershipSample Site, an OLE DB error occurs.

When you conduct dynamic queries to the LDAP directory through ADSI, thefollowing error occurs:
Microsoft OLE DB Service Components error 80040e21
The following ADSI connection fails:
Set MyConnection = Server.CreateObject("ADODB.Connection")    MyConnection.Provider = "ADsDSOObject"    My Connection.Open "ADs Provider", "", ""				
Issue #2: ADSI 2.5 installation causes failure during CommerceServer installation.

The following error occurs during the configuration of the Trey Researchsample site:
Cannot Set Attribute Description
Issue #3: SAWIZARD Fails to configure the directory afterinstalling ADSI 2.5. The following error occurs:
SAWIZARD: The New Membership Server Wizard cannot create or configure DSaccounts for the selected services
Issue #1: This error corresponds to a condition where the data typeof the parameter being passed to the stored procedure does not match thedata type that the stored procedure is expecting. This occurs because ADSI2.0 and MDAC 2.1 are not compatible.
Issue #2: This error occurs when ADSI 2.5 has been installed priorto Site Server 3.0. Site Server 3.0 installs ADSI 2.0 and overwrites ADSI2.5. Although no error messages occur during the Site Server 3.0installation, subsequent Commerce Server installations will fail when thesample sites are being configured for the LDAP directory.

Issue #3: This error is caused by ADSI 2.5 and Site Server 3.0compatibility issues that are not resolved with Site Server 3.0 SP2. Thefollowing conditions will produce this error:
  • Attempting to create more than one instance on the same computerthat all point to the same LDAP directory.
  • Creating an instance on computer A that points to an existingdirectory, and then deleting the instance on computer A and attempting tore-create the same instance, pointing to the same directory asbefore.
In these scenarios, the New Membership Server wizard will fail because thegroups to be created for the selected services already exist in thedirectory.
To resolve this problem, obtain the latest service pack for Site Server 3.0. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
219292 How to Obtain the Latest Site Server 3.0 Service Pack
For All Issues: MDAC 2.1 is delivered with SQL Server 6.5 SP5 as aseparate install, and in SQL Server 7.0 as a mandatory install. As aresult of the LDAP component using ADSI 2.0, if you want to install MDAC2.1 on your SQL Server 7.0 or SQL Server 6.5 SP5 computer, you must runSQL Server on a separate computer than the LDAP service, or install ADSI2.5.

Issue #3:
  1. If you create more than one instance pointing to the samedirectory on the computer, stop all instances.
  2. In MDM, go to the property page of the group(s). If AUO/Broker isto be created, the group is "GRPBRKR" appended with the computer name. IfDirect Mail instance is to be created, the group is "GRPDM" appended withthe computer name.
  3. Click the Members tab on the properties. If there is more thanone member to the group, write down all of the members on a piece ofpaper.
  4. Delete the group(s) in MDM.
  5. Re-run the New Membership Server wizard.
  6. When the instance is created, go back into MDM and bring upproperty page for the same group(s). Add all the members that used tobelong to the group back into the group.
Note: If the computer only has ONE instance pointing to thatdirectory, you can simply delete the group from MDM and re-run theInstance Creation wizard WITHOUT writing down the group membershipinformation.
This problem was first corrected in Site Server 3.0 Service Pack 3.
80040e21 -2147749409

Article ID: 216709 - Last Review: 10/26/2013 14:22:00 - Revision: 4.0

Microsoft Site Server 3.0 Commerce Edition

  • kbnosurvey kbarchive kbqfe kbhotfixserver kbbug kbfix kbsiteserv300sp3fix KB216709