HA: Error 8418: The replication operation failed because of a schema mismatch between the servers involved

[Sinelnikov Evgeniy]

Hi Stefan,

(I send this email again with gziped attachements)

> -----Original Message-----
> From: samba-technical [mailto:samba-technical-bounces at lists.samba.org]
> On Behalf Of Sinelnikov Evgeniy
> Sent: Monday, February 15, 2016 4:32 PM
> To: samba-technical at lists.samba.org
> Subject: RE: Error 8418: The replication operation failed because of a schema
> mismatch between the servers involved
[...]
>
> > -----Original Message-----
> > From: samba-technical [mailto:samba-technical-bounces at lists.samba.org]
> > On Behalf Of Matthieu Patou
> > Sent: Monday, February 15, 2016 9:57 AM
> > To: Stefan Metzmacher <metze at samba.org>; samba-
> > technical at lists.samba.org
> > Subject: Re: Error 8418: The replication operation failed because of a
> > schema mismatch between the servers involved
> >
> > On 02/13/2016 12:21 AM, Stefan Metzmacher wrote:
> > > Hi Matthieu,
> > >
> > >
> > > Checking the prefixMap attribute is good, but note that this is not
> > > a replicated attribute and the content may not have the same format
> > > on Windows vs. Samba.
> > Yes I agree, still despite a different representation we should insure
> > that we have the same data.
> > > It would be interesting to see the struct drsuapi_DsGetNCChanges
> > > messages in the other direction too, where we replicate from Windows.
> > > We need to compare the drsuapi_DsReplicaOIDMapping_Ctr arrays.
> > Would be much easier if my PIDL patches were accepted at the moment
> > where I was active at doing them :-)
>
> Replication packets from Samba and to Samba are not the same.
> But I tried to get it:
> * https://goo.gl/bpTMKv (Error of replication WindowsDC from SambaDC)
> * https://goo.gl/nVDth9 (Success of replication SambaDC from WindowsDC)
>
> Is it suitable?

I don't really know how previous variant was suitable, but I created a new one
with similar replication of different users created on other side:

* Replication2: to SambaDC from WindowsDC:
 https://goo.gl/8s4th2 (020-test4-dc01-DsGetNCChanges-response.txt)
* Replication2: to WindowsDC from SambaDC (with WERR_DS_DRA_SCHEMA_MISMATCH):
 https://goo.gl/eX0UJD (040-test5-dc02-DsGetNCChanges-response-call_id_18.txt)

So, I hope it would be more useful than the previous. As I see, content of struct
drsuapi_DsReplicaOIDMapping_Ctr are the same. This dumps created using
Wireshark Version 2.1.0 (5d8ca26 from ws-metze-current).

Also next patches were applied:
* da86c6c48f7945fb8df4e200e1d2b0d1fc1de921
* 5e1b9f40fc20b0b55da262c87470abc5e12af1cf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test4-test5-DsGetNCChanges-response.diff.gz
Type: appplication/x-gzip
Size: 38888 bytes
Desc: test4-test5-DsGetNCChanges-response.diff.gz
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20160216/97d8e2c1/test4-test5-DsGetNCChanges-response.diff-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 020-test4-dc01-DsGetNCChanges-response.txt.gz
Type: appplication/x-gzip
Size: 10779 bytes
Desc: 020-test4-dc01-DsGetNCChanges-response.txt.gz
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20160216/97d8e2c1/020-test4-dc01-DsGetNCChanges-response.txt-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 040-test5-dc02-DsGetNCChanges-response-call_id_18.txt.gz
Type: appplication/x-gzip
Size: 34111 bytes
Desc: 040-test5-dc02-DsGetNCChanges-response-call_id_18.txt.gz
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20160216/97d8e2c1/040-test5-dc02-DsGetNCChanges-response-call_id_18.txt-0001.bin>