• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 116031, created on Apr 30, 2013, last review on May 10, 2014

  • Applies to:
  • Operations Automation


Lync Server Logging Tool is not available in the Lync 2013 anymore, so to get detailed logs of Lync services one may use the Centralized Logging Service.


The Lync 2013 Centralized Logging Service is represented by the 'C:\Program Files\Common Files\Microsoft Lync Server 2013\ClsAgent\ClsController.exe' binary on Lync server.

Usage: ClsController.exe (COMMAND) [(OPTIONS)] [(SCOPE)]
Available commands:
start : Starts trace session for given scenario.
stop  : Stops trace session for given scenario.
flush : Flush logs and make them available for searching immediately.
search: Search logs. Results are returned in a text file.

Use the Get-CsClsScenario PowerShell cmdlet to get list of possible scenarios.

See examples below.

Start logging of the IMAndPresence scenario: ClsController.exe -start -scenario IMAndPresence -pools fepool01.hosting.local
Stop logging of the IMAndPresence scenario on all Lync servers: ClsController.exe -stop -scenario IMAndPresence
Flush logs: ClsController.exe -flush -pools fepool01.hosting.local
Search logs of the SipStack component and save results in the c:\SipStackLog.txt file: ClsController.exe -search -pools fepool01.hosting.local -components SipStack > c:\SipStackLog.txt
So, the typical scenario of using Centralized Logging Service to get logs of the problem with a particular scenario is as follows:
1. ClsController.exe -start -scenario <scenario>
2. Perform steps to reproduce issue
3. ClsController.exe -stop -scenario <scenario>
4. ClsController.exe -flush
5. ClsController.exe -search > c:\Log.txt

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF