Active Directory replication may not be completed correctly with one or more partners on a domain controller or on a global catalog server that is running Windows 2000 (305591)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional
This article was previously published under Q305591 SYMPTOMSOn a domain controller or on a global catalog server that is running Microsoft Windows 2000, Active Directory directory service replication may not be completed correctly with one or more partners, and the following event may appear in the event log:
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1645
Date: 10/08/2001
Time: 18:52:03
User: Everyone
Computer: Computer_Name
Description:
The Directory Service received a failure while trying to perform an authenticated RPC call to another Domain Controller. The failure is that the desired Service Principal Name (SPN) is not registered on the target server. The server being contacted is domain_name.com. The SPN being used is GC/ Global_Catelog.com/ domain.com.
Please verify that the names of the target server and domain are correct. Please also verify that the SPN is registered on the computer account object for the target server on the KDC servicing the request. If the target server has been recently promoted, it will be necessary for knowledge of this computer's identity to replicate to the KDC before this computer can be authenticated.
If you use the Repadmin.exe utility, you may receive the following error message:
Logon Failure: The target account name is incorrect.
CAUSE
This issue may occur when a replicated naming context is deleted while at least one domain controller that is hosting that domain is available. When this situation occurs, the NCname attribute for the Crossref object of the domain that is affected points to the naming context object (NChead). However, the naming context object has already been deleted. This condition prevents replication.RESOLUTIONService pack information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Hotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesNo prerequisites are required. Restart requirementYou must restart your computer after you apply this hotfix. Hotfix replacement informationThis hotfix does not replace any previous hotfixes. File informationThe English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name
--------------------------------------------------------
13-Aug-2001 17:53 5.0.2195.4126 159,504 Ntdsutil.exe
To work around this problem, use Ntdsutil.exe to perform a semantic analysis on the Active Directory database of the domain controller or of the global catalog server that is reporting the event. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 10/6/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbDirServices kbfix kbQFE kbWin2000PreSP3Fix kbWin2000sp3fix KB305591 |
---|
|