Text Logs are kept in the %SystemRoot%\System32\ folder. There are two main log files collected when the service is running:
1. domtimem.log
   This is the currently active service text log file.
   If log archiving is enabled (see below), additional archived log files will be created using a domtimem.YYYYMMDD.log naming scheme (i.e. domtimem.20090928.log).

2. domtimem.startup.log
   A detailed text log of the service startup process. Only data from the latest startup is included.

To view these logs, click the button, which launches the Domain Time Log Viewer.

Log Level
This drop-down chooses what type of entries to include in the log. You can increase or decrease the amount of information logged as needed.

The available levels are (in increasing amount of detail):

• Disabled
  This switch will only disable the domtimem.log file. The other system log, domtimem.startup.log cannot be disabled.

• Errors
  Only messages marked as Errors will be logged

• Warnings
  Logs will include Errors and Warnings

• Information
  Includes Errors, Warnings, and Information messages.

• Trace
  Includes all of the above, plus detailed Trace information .

• Debug
  Includes all available information provided by the service.

  CAUTION:
  

  ---

  Debug logging will generate a great deal of data, so be sure to only enable it when you need the additional information, and don't forget to turn it off when finished troubleshooting.

  ---

Max size
This sets how large the log file is allowed to grow (in kilobytes).

Once the maximum size is reached, the oldest events will be scrolled off to make room for new events. Enter 0 (zero) if you don't want to limit the log size.

It's a good idea to set a log size that will allow you to keep enough history to help you determine the timeframe and scope of any issues you may encounter.

Log Roll
Domain Time can automatically archive the text log on a daily, weekly, or monthly schedule.

When the log is archived, all existing log events in the domtimem.log file will be written to an archive file named domtimem.YYYYMMDD.log (i.e. domtimem.20090928.log) and the current log file will then be cleared to accept new data.

You can choose how many archived log files to keep on the machine. When the indicated limit is reached, the oldest log file will be deleted.

This section specifies whether Monitor's service activity will be echoed to the Windows Event logs.

Note: Some levels of logging can create a significant amount of data. The Windows Event logs can be difficult to read, or the Event Log process may even have problems recording all the data when large amounts of log activity are generated.
 
You should consider using only the Error level when using the Event Logs unless you generate a very small amount of logging data overall. In general, Text logging is a better choice for keeping more detail.

The Log Level drop-down chooses what type of entries to include in the Event logs. You can increase or decrease the amount of information logged as needed.

The available levels are (in increasing amount of detail):
• Disabled
  Monitor will not log events to the Windows Event Logs.

• Errors
  Only messages marked as Errors will be logged

• Warnings
  Logs will include Errors and Warnings

• Information
  Includes Errors, Warnings, and information on the activity of the time service, such as time sources contacted, amount of clock correction, etc.

• Trace
  Includes all of the above, plus detailed information on time setting and time sample analysis.

• Debug
  Includes all available information provided by the service.

Warning:


---

The amount of data generated by Debug logging can easily overwhelm the Event Log system. Use the Text log for debugging instead.

---

Click the button to launch the Windows Event Viewer.

 Back to the Alerts page