Thanks.
For the objects where the error message is Type of value exists: aRecord, I would try to remove the corresponding reject file and to re-sync the reject from the S4 side to the UCS side. This can be achieved with the following two commands:
/usr/share/univention-s4-connector/remove_s4_rejected.py <object's S4 DN>
/usr/share/univention-s4-connector/resync_object_from_s4.py <object's S4 DN>
For example:
/usr/share/univention-s4-connector/remove_s4_rejected.py DC=HAN-VCKT01L,DC=mycompany.log,CN=MicrosoftDNS,DC=DomainDnsZones,DC=mycompany,DC=log
/usr/share/univention-s4-connector/resync_object_from_s4.py DC=HAN-VCKT01L,DC=mycompany.log,CN=MicrosoftDNS,DC=DomainDnsZones,DC=mycompany,DC=log
According to the log file, this applies to the following objects: DC=HAN-TONGHOP01, DC=HAN-VCKT01L and DC=HAN-SALES02L.
I suggest these steps because the entry on the UCS side seems to be correct already — no need to add another IP. So what I’m basically telling the system with these two commands is “ignore that change, and just make sure that the UCS side looks like the S4 side”.
Read more about handling S4 connector rejects in this support database article.
The log file excerpt you’ve shown doesn’t contain anything for the first reject, though, CN=cnmb.tonghop. Can you get me log entries and error messages for that one, too? Thanks.
Kind regards,
mosu