Lync Server 2013 Logging Tool displays a main dialog and four dialogs available through the Advanced Options menu item.
Lync Server 2013 Logging Tool user interface The S4.etl file in this directory will contain error, warning, and protocol messages. By default, these files are written to the %WINDIR%\Tracing directory. You can have a trace running for each of the two trace provider components. To start a protocol trace you must be a member of the Administrators group on the computer running the protocol trace. Each radio button below the Errors button causes more messages to be recorded to the log file. 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 2013 Logging Tool writes log files to this directory. When UCMA 4.0 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.
Lync server download install#
When you install the UCMA 4.0 SDK, the Lync Server 2013 Logging Tool (OCSLogger.exe) is located in the SDK\Core\Tracing folder in the UCMA 4.0 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 4.0.
An important part of the process of developing a UCMA 4.0 application is the ability to trace the protocol stack.
0 kommentar(er)
