W32tm Command Generates Error Messages When Run on a Windows 2000 Domain Controller

View products that this article applies to.

This article was previously published under Q247321

SYMPTOMS

The W32tm command is used to test and maintain time synchronization between workstations and servers in an enterprise. If you use the command on a Windows 2000 domain controller, you may receive an error message in the output of the command if you are using the -v switch for verbose output and\or the following error message may be logged in the System Event log:

Back to the top

Error Message at Command Prompt

==============================
(previous lines removed)
W32Time: Server: Binding to 1 NIC.
W32Time: bind failed: 0x80072740
W32Time: 0xC0000031 reported to System Log in Event Viewer
W32Time: BEGIN:FinishCleanup
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1384
W32Time: BEGIN:UnInitializeDC
W32Time: Ptrs 0 - 0
W32Time: END:Line 725
W32Time: Time service stopped.
W32Time: END:Line 383

Back to the top

Error Message in the Event Log

==============================
Event Type: Error
Event Source: w32time
Event Category: None
Event ID: 49
Date: xx/xx/2000
Time: 10:49:44 AM
User: N/A
Computer: machinename
Description:
An unexpected error occurred while trying to start the server.
The port may already be in use.
Data:
0000: 00 00 00 00 ....

Back to the top

The W32tm Command Generates the Following Error Message

RPC to server -v returned 0x6ba

Back to the top

CAUSE

This problem can occur on a domain controller (DC) when the default port (123) is already in use by the Time service that is running on the DC before the command is executed. The W32tm command tries to start the Time service before execution, but it does work if the service is already started.

Back to the top