and the link to "EventID 1645 from source Active Directory" for information about this event.
In one case, this Event ID appeared when an attempt to transfer a FSMO role (the PDC role) by running NTDSUTIL on another domain controller failed. This was fixed by using DCPROMO to demote/promote the domain controller.
for two hotfixes applicable to Microsoft Windows 2000.
As per Microsoft: "The servicePrincipalName attribute is a multiple-valued, non-linked attribute. In some Dcpromo.exe update situations, the replication SPN may be lost because of a conflict with another write process on this attribute". See ME308111
for more details.
If this error is being reported for Active Directory replication between two domain controllers of different domains which have a parent/child or tree root trust relationship, this error may be due to an absent critical object that represents the trust relationship between the two domains. This object is known as a "trustedDomain" object (TDO) and is found in the System container in the Active Directory Users and computers tool. This type of object directly relates to the trust relationships displayed in the Active Directory Domains and Trusts administrative tool. If this object is not present in the Active Directory, cross-domain authentication will not be able to succeed contributing to the errors described above.
You may receive this error if you have multiple Service Principal Name (SPN) records for an individual domain controller in DNS under xyz.com/_msdcs. For instance:
I have domain controllers A, B, and C in domain XYZ.COM. In my scenario, I added and removed domain controller C three times. In DNS I ended up with three different SPN records under xyz.com/_msdcs for Domain Controller C. This then confused DC A when it tried to replicate to DC C.
SOLUTION: Delete all the records for DC C. Restart NETLOGON service on DC C so it will reregister DNS records.