Microsoft KB Archive/252178: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 12: | Line 12: | ||
<div id="TitleRow"> | <div id="TitleRow"> | ||
= <span id="KB252178"></span>LDAP Search | = <span id="KB252178"></span>LDAP Search "Not Present" Filter Does Not Work with Site Server Membership Directory = | ||
Line 44: | Line 44: | ||
== SYMPTOMS == | == SYMPTOMS == | ||
The LDAP | The LDAP "Presence" operator allows LDAP search operations to select entries containing a specified attribute. For instance, the LDAP filter "(mail=*)" can be used to retrieve all members with a mail attribute defined. However, applying the "Not" bolean operator to this "Presence Filter" does not work when you use a SQL Server based Site Server Membership Directory database. The filter "!(mail=*)" returns all entries with the mail attribute PRESENT instead of showing all objects with the mail attribute NOT PRESENT. | ||
</div> | </div> |
Latest revision as of 13:52, 21 July 2020
Article ID: 252178
Article Last Modified on 9/23/2005
APPLIES TO
- Microsoft Site Server 3.0 Standard Edition
This article was previously published under Q252178
SYMPTOMS
The LDAP "Presence" operator allows LDAP search operations to select entries containing a specified attribute. For instance, the LDAP filter "(mail=*)" can be used to retrieve all members with a mail attribute defined. However, applying the "Not" bolean operator to this "Presence Filter" does not work when you use a SQL Server based Site Server Membership Directory database. The filter "!(mail=*)" returns all entries with the mail attribute PRESENT instead of showing all objects with the mail attribute NOT PRESENT.
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.
Keywords: kbbug kbfix kbqfe kbsiteserv300sp4fix kbhotfixserver KB252178