Microsoft KB Archive/838400

= Several messages are logged in the Domain Server event log when you upgrade a Windows NT 4.0-based server that is operating as a domain controller to a Windows 2000 Server-based server =

Article ID: 838400

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server

-





SYMPTOMS
When you upgrade a Microsoft Windows NT 4.0-based server that is operating as a domain controller to a Microsoft Windows 2000 Server-based server, the following messages are logged in the Domain Server event log after you restart the server: Event ID: 1645

Source: NTDS Replication.

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 \\. .com. The SPN being used is GC/. .com/ .com@ .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.

Event ID: 1224

Source: NTDS Replication.

Description:

An attempt to automatically update information on this Computer object and this Server object failed with error 87.

The attempt will be made again in 22 minutes. DSID 32b0281.

Event ID: 1126

Source: NTDS General.

Description:

Unable to establish connection with global catalog.

Event ID: 1655

Source: NTDS Replication.

Description: The attempt to communicate with global catalog \\. .com failed with the following status:

Logon Failure: The target account name is incorrect.

The operation in progress might be unable to continue. The directory service will use the locator to try to find an available global catalog server for the next operation that requires one.

The record data is the status code.

Status code is 0x574:ERROR_WRONG_TARGET_NAME

If you run the Domain Controller Diagnostic tool (Dcdiag.exe) on the domain controller, you receive the following error message:

Starting test: MachineAccount

Failed with 87: The parameter is incorrect.

Can not test for HOST SPN

Failed with 87: The parameter is incorrect.

Can not test for HOST SPN


 * Missing SPN :LDAP/ . .com/ .com


 * Missing SPN :LDAP/ . .com


 * Missing SPN :LDAP/


 * Missing SPN :(null)


 * Missing SPN :LDAP/d20fdbba-4320-4746-a063-830da0ffd027._msdcs.numeric_NetBIOS_name.com


 * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/d20fdbba-4320-4746-a063-830da0ffd027/numeric_NetBIOS_name.com


 * Missing SPN :HOST/ . .com/ .com


 * Missing SPN :HOST/ . .com


 * Missing SPN :HOST/


 * Missing SPN :(null)


 * Missing SPN :GC/ . .com/ .com

.........................  failed test MachineAccount

If you run the Network Diagnostics Tool (Netdiag.exe) on the domain controller, you receive the following error message:

Kerberos test. . . . . . . . . . . : Failed

Cached Tickets:

Server: krbtgt/ .COM

End Time: 1/20/2004 0:03:23

Renew Time: 1/19/2004 17:03:23

[FATAL] Kerberos does not have a ticket for $.

...

Registered Service Principal Names:

E3514235-4B06-11D1-AB04-00C04FC2DCD2/d20fdbba-4320-4746-a063-830da0ffd027/ .com

NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/. .com

DNS/. .com

[WARNING] The default SPN registration for 'HOST/. .com' is missing on DC '. .com'.

[WARNING] The default SPN registration for 'HOST/ ' is missing on DC '. .com'.

Cannot test LDAP to ' ' since it isn't running the DS. [Test skipped.]

[FATAL] The default SPNs are not properly registered on any DCs.



CAUSE
This problem occurs when the following conditions are both true:
 * The Microsoft Windows NT 4.0 network basic input/output system (NetBIOS) name consists completely of numeric characters.
 * The replication service principal names (SPNs) are not declared when the Active Directory Installation Wizard (Dcpromo.exe) updates the domain controllers to Windows 2000 Server.



Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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:

http://support.microsoft.com/contactus/?ws=support

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.

Prerequisites
No prerequisites are required.

Restart requirement
You must restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File Information
The 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 --  22-Mar-2004  23:12  5.0.2195.6825      57,616  Ntdsapi.dll



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

