Microsoft KB Archive/280771

= The Join Is Unsuccessful When Connector Space Entry Is Assumed to Be a Non-Person Object =

Article ID: 280771

Article Last Modified on 1/25/2006

-

APPLIES TO


 * Microsoft Metadirectory Services 2.1
 * Microsoft Metadirectory Services 2.2 Service Pack 1

-



This article was previously published under Q280771



SYMPTOMS
The following messages may be reported in the log file when your system is running at a log level 4 or higher:

Criterion [$cd.employeenumber] is [PMV0971]

No unique proposal for

employeenumber=PMV0971,ma=TestJoin3,DsaName=CurtCorp,ou=Server

Applications,dc=CurtCorp,dc=COM]

The preceding log message indicates that the join (the establishment of a link between a metaverse object and a specific connector space object) has not been successful.

-or-

Criterion [$cd.employeenumber] is [PMV0971]

+Proposal[0]: [uid=Smith.John,ou=People,dc=CurtCorp,dc=COM]

>> append $cs.zcConnectedDirectoryId =

[uid=PMV0971,ma=TestJoin3,DsaName=CurtCorp,ou=Server

Applications,dc=CurtCorp,dc=COM]

The preceding log message indicates that the join has been successful.



CAUSE
This behavior may occur because Microsoft Metadirectory Services has hard-coded logic that can join the &quot;cn=...&quot; or &quot;uid=...&quot; connector space entries to &quot;person&quot; objects in the metaverse. This process prevents the join of connector space entries to &quot;non-person&quot; objects in the metaverse.



RESOLUTION
To resolve this behavior, you must use only &quot;CN&quot; or &quot;UID&quot; as the distinguishing attribute in the Distinguished Name (DN) when you set up the connector space DN in the construction template.



MORE INFORMATION
The preceding logic exists to prevent a connector space person from being joined to a metaverse object that is either a &quot;list&quot; or &quot;ou&quot; type, even if the join search criteria evaluates a single match. However, you cannot examine the connector space object class value to identify a connector space person.

In general, connector space objects contain only a single object class, either the ZcAliasThing or ZcExcludedAliasThing object. Instead, you must examine the connector space DN and isolate the distinguishing attribute.

As previously mentioned, Microsoft Metadirectory Services contains hard-coded logic which defines the &quot;cn&quot; and &quot;uid&quot; distinguishing attributes as a person. For this reason, objects that have a distinguishing attribute other than &quot;cn&quot; or &quot;uid&quot; are ignored by the join.

Additional query words: Zoomit Via MA zscript genlogs

Keywords: kberrmsg kbprb KB280771

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.