ADSI 2.0, 2.5, and MDAC 2.1 Compatibility Issues

Article translations Article translations
Article ID: 216709 - View products that this article applies to.
This article was previously published under Q216709
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

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.

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

When you conduct dynamic queries to the LDAP directory through ADSI, the following 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 Commerce Server installation.

The following error occurs during the configuration of the Trey Research sample site:
Cannot Set Attribute Description
Issue #3: SAWIZARD Fails to configure the directory after installing ADSI 2.5. The following error occurs:
SAWIZARD: The New Membership Server Wizard cannot create or configure DS accounts for the selected services

Cause

Issue #1: This error corresponds to a condition where the data type of the parameter being passed to the stored procedure does not match the data type that the stored procedure is expecting. This occurs because ADSI 2.0 and MDAC 2.1 are not compatible.
Issue #2: This error occurs when ADSI 2.5 has been installed prior to Site Server 3.0. Site Server 3.0 installs ADSI 2.0 and overwrites ADSI 2.5. Although no error messages occur during the Site Server 3.0 installation, subsequent Commerce Server installations will fail when the sample sites are being configured for the LDAP directory.

Issue #3: This error is caused by ADSI 2.5 and Site Server 3.0 compatibility issues that are not resolved with Site Server 3.0 SP2. The following conditions will produce this error:
  • Attempting to create more than one instance on the same computer that all point to the same LDAP directory.
  • Creating an instance on computer A that points to an existing directory, and then deleting the instance on computer A and attempting to re-create the same instance, pointing to the same directory as before.
In these scenarios, the New Membership Server wizard will fail because the groups to be created for the selected services already exist in the directory.

Resolution

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 the Microsoft Knowledge Base:
219292 How to Obtain the Latest Site Server 3.0 Service Pack

Workaround

For All Issues: MDAC 2.1 is delivered with SQL Server 6.5 SP5 as a separate install, and in SQL Server 7.0 as a mandatory install. As a result of the LDAP component using ADSI 2.0, if you want to install MDAC 2.1 on your SQL Server 7.0 or SQL Server 6.5 SP5 computer, you must run SQL Server on a separate computer than the LDAP service, or install ADSI 2.5.

Issue #3:
  1. If you create more than one instance pointing to the same directory on the computer, stop all instances.
  2. In MDM, go to the property page of the group(s). If AUO/Broker is to be created, the group is "GRPBRKR" appended with the computer name. If Direct Mail instance is to be created, the group is "GRPDM" appended with the computer name.
  3. Click the Members tab on the properties. If there is more than one member to the group, write down all of the members on a piece of paper.
  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 up property page for the same group(s). Add all the members that used to belong to the group back into the group.
Note: If the computer only has ONE instance pointing to that directory, you can simply delete the group from MDM and re-run the Instance Creation wizard WITHOUT writing down the group membership information.

Status

This problem was first corrected in Site Server 3.0 Service Pack 3.

Properties

Article ID: 216709 - Last Review: October 26, 2013 - Revision: 4.0
Applies to
  • Microsoft Site Server 3.0 Commerce Edition
Keywords: 
kbnosurvey kbarchive kbqfe kbhotfixserver kbbug kbfix kbsiteserv300sp3fix KB216709

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com