
Checking the Errors radio button causes only error messages to be recorded to the log file.

If you want log files written to a different direction, click the Browse button and select or create the folder in which log files are written.īy clicking the appropriate tracing Level radio button, the user can filter the kinds of messages that will be recorded in the log file. Lync Server 2010 Logging Tool writes log files to this directory. When UCMA 3.0 Core SDK is installed it creates a Tracing folder under the %WinDir% directory. You can start a trace for one or more of the listed components. The default choices are Collaboration, S4, SpeechComponent, and SpeechVxmlComponent.

Before starting a trace, the user should do the following: Launching OCSLogger.exe opens the window shown in the following figure. When you install the Microsoft Unified Communications Managed API (UCMA) 3.0 Core SDK, the Lync Server 2010 Logging Tool (OCSLogger.exe) is located in the SDK\Core\Tracing folder in the UCMA 3.0 Core SDK installation directory. By viewing the contents of the protocol stack during or after the execution of your code, you can familiarize yourself with the topology of UCMA 3.0. An important part of the process of developing a Microsoft Unified Communications Managed API (UCMA) 3.0 application is the ability to trace the protocol stack.
