Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Unexpected error occurred while trying to start the server. The port may be already in use.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
Why are some errors “unexpected”?
This event may occur when w32tm command is used while the w32time (Windows Time) service is running. As they are trying to use the same port, a conflict is reported. In order to be able to use w32tm command, stop first the Windows Time service. See ME247321 for more details.
See the link to "Symmetricom Document KB2002.101" for a solution to this problem.
Christophe Lubrano di Ciccone
I had this event after a successfull DCpromo process. I stop and restart the "window time" service using dos command. I run w32tm -v to check the status. This return W32Time: 0xC0000031 reported to System Log in Event Viewer as the event 11 source w32time. I apply ME307937 ("Configuring the Time Service to Log When the Time Is Changed") in order to log all the evnt including the successfull one. I stop and restart the "window time" service using dos command. I obtain the event 61 source w32time following by event 0 source w32time. To my opnion this may have refreshed the entries used by the DC in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services \W32Time\Parameters for the time synchronization.
|Private comment: Subscribers only. See example of private comment|
|Links: ME247321, Symmetricom Document KB2002.101|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated