gdrtx Absent Member.
Absent Member.
377 views

eDir-to-eDir Driver Matching Issue


I have two eDirectory systems connected with eDir-to-eDir drivers. I am
trying to synch objects from Tree A to Tree B. All of the schema for
these objects is the same in both trees so no schema mapping or anything
is needed. In the Subscriber in Tree A I am creating a destination DN
(because if I don't it throws an error) and in the Publisher for Tree B
I have my placement logic. The issue is that even though I do not have
a matching policy for this class the driver in Tree B always reports
back with "A match found" and then results in an an error
"ERR_ILLEGAL_DS_NAME". How can a match be found when there is no match
policy being executed?

I have added a matching policy but it did the same thing (returned the
"A match found" message when I know no match exists). I'm stumped.

Thanks in advance.


--
gdrtx
------------------------------------------------------------------------
gdrtx's Profile: http://forums.novell.com/member.php?userid=114908
View this thread: http://forums.novell.com/showthread.php?t=453910

Labels (1)
0 Likes
2 Replies
Knowledge Partner
Knowledge Partner

Re: eDir-to-eDir Driver Matching Issue

On 3/26/2012 1:16 PM, gdrtx wrote:
>
> I have two eDirectory systems connected with eDir-to-eDir drivers. I am
> trying to synch objects from Tree A to Tree B. All of the schema for
> these objects is the same in both trees so no schema mapping or anything
> is needed. In the Subscriber in Tree A I am creating a destination DN


This is the root cause. You should not need to do this.

> (because if I don't it throws an error) and in the Publisher for Tree B
> I have my placement logic. The issue is that even though I do not have
> a matching policy for this class the driver in Tree B always reports
> back with "A match found" and then results in an an error
> "ERR_ILLEGAL_DS_NAME". How can a match be found when there is no match
> policy being executed?


Dest-dn is there, so it tries to use that value, and it is complaining
that the matching object exists, but has not converted from a <add> to a
<modify> yet.

> I have added a matching policy but it did the same thing (returned the
> "A match found" message when I know no match exists). I'm stumped.


Match won't work, as find matching object skips any event where dest-dn
is present.

0 Likes
gdrtx Absent Member.
Absent Member.

Re: eDir-to-eDir Driver Matching Issue


Thanks Geoff. As always you are absolutely correct. I was getting an
error about not generating a DN so I added a policy to do that which
lead to this error. After doing a bit more looking based on your input
I realized I had the wrong class selected in my placement policy so all
this time it was just a simple oversight on my end. Thanks again.


--
gdrtx
------------------------------------------------------------------------
gdrtx's Profile: http://forums.novell.com/member.php?userid=114908
View this thread: http://forums.novell.com/showthread.php?t=453910

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.