No Unique Proposal for Objects When You Use Server-Based Join with the Active Directory Management Agent (269173)
The information in this article applies to:
- Microsoft Metadirectory Services 2.2
This article was previously published under Q269173 NOTE: The QFE patch associated with this article has been superceded by Q285852.EXE. However, the description of this article remains valid. In order to access the fix referred to in this article, please refer to Q285852.EXE
285852 Replacement QFE for MMS 2.2
SYMPTOMS
When you try to join the Active Directory Management Agent connector space object to metaverse objects by using the Join tool, the following error message is generated in the Operator's log file:
No unique proposal for object DN
When you run the Join tool with a higher logging level, it resolves attributes as empty even though they have values in Hologram view.
The join is successful, however, if you run the management agent and project the objects into the metaverse. For example, the join succeeds if you select the Attempt to join check box in the management agent configuration settings when you bring the objects into the connector space.
Account Joiner enables the administrator to choose four actions: Create, Join, Hold, and Exclude. When the Create button is clicked, Account Joiner should take the connector space object you have selected and create a metaverse entry for that object. However, when doing this, the object creation fails and the log reports:
FAILED TO CONSTRUCT[19049] error
CAUSE
This behavior occurs only when you run the server-based join on preexisting, disconnected objects. The problem is caused by the management agent's inability to extract the required attribute values from its parsing template. Typically, the parsing template is used as the attribute value source during the join operation. However, in the Active Directory management agent, the parsing template is unavailable and the values must be retrieved elsewhere.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next version of Microsoft Metadirectory Services that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
-----------------------------------------------------
08-25-2000 21:35 1124 1,375,232 Importt.exe
08-25-2000 21:35 1124 1,503,744 Replica.exe
08-25-2000 21:35 1124 1,911,808 Viaserver.exe
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 10/7/2005 |
|---|
| Keywords: | kbbug kbenv kberrmsg kbfix kbQFE KB269173 |
|---|
|