Topic Last Modified: 2011-01-24
Computers running Microsoft Lync Server 2010, Group Chat produce troubleshooting log files that report important information that may be helpful in diagnosing problems with your Lync Server 2010, Group Chat deployment. Log files are located in the installation directory, under Logs. If default values are accepted during server installation, the path of these log files is: %ProgramFiles%\Microsoft Lync Server 2010\Group Chat Server\Logs.
Log levels are set in the Microsoft Lync Server 2010, Group Chat Configuration tool. Logging is configured separately for each service:
- Lookup service
- Channel service
- Web service
- Compliance service
The following log levels are available:
- Trace (most verbose) The Trace level is
usually reserved for support team use.
- Debug The Debug level records specific
events that affect system performance and data associated with each
- Info (default) The Info level records
specific events that affect system performance. It records less
data associated with each event than the Debug level does.
- Warn The Warn level records user action
or input that is not valid.
- Error The Error level records all
errors except for operations that fail because of user input or an
action that is not valid.
- Critical The Critical level records
events that are debilitating to the system but not fatal. These
events are included in the Event Viewer Application log as Warning
- Fatal The Fatal level records only very
urgent events that will cause the system to fail and shut down.
They are included in the Event Viewer Application log as Error
- None (least verbose) The None level
does not record any events. A zero-size log file is created if no
log currently exists.
Note: This option is not available in the Group Chat Configuration tool.
All events generated at the selected log level are recorded in the log, and so are all events generated at all levels above the selected log level, toward least verbose. For example, if the log level is set to Info, all events at the Info level and all the events at the Warn, Error, Critical, and Fatal levels are recorded.
The more verbose the level, the more information is recorded. For example, if the log level is set to Info, the log reaches capacity faster than if the log level is set to Warn. A level of Debug or Trace can fill the log file to capacity in a very short time.
A new log is created when the current log reaches a size of 250 MB. After a log reaches capacity, it is archived. Forty logs are kept in the archive at a time. When a new log is archived and there are already 40 archived logs, the oldest archived log is removed. Therefore, no more than 40 logs are archived at a time.
Log levels in the Group Chat Configuration tool take effect immediately. The servers do not have to be restarted.