LDAP Queries That Use the ADSI NOT Character (!) in a Filter Work Incorrectly (265502)

The information in this article applies to:

Microsoft Site Server 3.0
Microsoft Site Server 3.0 Commerce Edition

This article was previously published under Q265502

SYMPTOMS

A SQL Server-based LDAP query that uses the Active Directory Service Interfaces (ADSI) logical NOT character (!) in a filter to test if an attribute is present returns the opposite results.

The following sample query demonstrates this behavior:

<BR/>
"<LDAP://server:port/o=Org/ou=Members
<ldap://server:port/o=Org/ou=Members>>;(!(mail=*));ADsPath, cn, mail;subtree"

In this example, the results that are returned contain only the entries in the members container that did contain a mail address, which is the opposite of what should be returned. Only the items in the members container that did not have the mail attribute set should be returned in this case.

RESOLUTION

To resolve this problem, obtain the latest service pack for Site Server version 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

STATUS

Microsoft has confirmed that this is a problem in Site Server 3.0. This problem was first corrected in Site Server 3.0 Service Pack 4.

MORE INFORMATION

For additional information about related LDAP fixes, click the article numbers below to view the articles in the Microsoft Knowledge Base:

258670 ADSI Filters May Return the Incorrect Results When Text Is Inside a Filter Match

265500 LDAP Queries That Contain the Single-Quotation Character (') Fail

252178 LDAP Search Not Present Filter Does Not Work with Membership

247953 Error Message: The Object You Tried to Create Already Exists in the Directory

231732 Updating Member Properties Using ADSI May Cause Corruption

Modification Type:	Minor	Last Reviewed:	7/15/2004
Keywords:	kbbug kbfix kbQFE kbSiteServ300sp4fix KB265502