Microsoft Office Tutorials and References
In Depth Information
Unified Logging Service (ULS)
This section explains the primary logging system used by MOSS and explores the various configurable
properties. It also describes the data that is provided through ULS and how you can leverage this
information to assist with administering your Excel Services enterprise deployment.
The ULS is an API used by the MOSS applications, including Excel Services. The ULS interface allows the
applications to send notifications to the event and trace logs, feed data to performance counters, and use
the error reporting system that collects information related to hardware and software problems.
ULS is enabled and functional out-of-the-box. In fact, the MOSS setup process does not prompt you to
make any decisions related to monitoring. Default settings are in place to ensure proper operation of
ULS upon completion of your farm’s setup. Immediately after setup, ULS trace logs, event log entries,
and performance objects are available for your use.
ULS Trace Logs
The ULS trace logs are primarily intended to be used by Product Support after you report a problem and
share the logs with them. A number of tools have been developed within Microsoft to assist with
searching, filtering, and reading the ULS trace logs, but unfortunately they have not made their way into
publicrelease channels. However, the logs are tab-delimited text files that you can read with your favorite text
editor. You can use Excel’s filtering functionality to work with large trace logs.
Each server in the farm has its own ULS trace logs that contain only trace entries specific to the
events for the MOSS applications running on that server. By default, the trace logs are written to the
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS directory on
each of the servers in your farm. When you navigate to the logs folder, you can readily identify the
ULS trace log files by the naming convention associated with them, as follows:
ULS trace log file name mask — ServerName-YYYMMDD-HHMM.log, where
ServerName is the computer name for this server.
YYYMMDD is the date the log was created.
HHMM is the time the log was created, in 24-hour format.
ULS trace log file name — TheExcelServer-20060711-1124.log, for example.
The volume of trace events present in the log is mostly a factor of the chosen logging level and the
activity level associated with the server. A new sequential trace log is created every 30 minutes from the time
when the Windows SharePoint Services Tracing service is started (see Figure 7-22). The service is
automatic, so it is always running and requires no manual administration.
With events being written to the trace logs around the clock, the ULS trace log directory becomes
crowded if left unchecked and requires some disk management. A total of 96 ULS trace logs are allowed