Lync 2013 Debugging Connection Issues With Snooper

To diagnose connection problems between Lync Clients and Lync Server, you can use the Lync debugging tools, which you can get from here.

The Debugging Tools uses two programs, OCSLogger, which logs the problems while you try to make connections and Snooper, which is used to view the log files you recorded.

Using Snooper

After you grab and install the Debugging Tools, browse to C:\Program Files\Microsoft Lync Server 2013\Debugging Tools and run OCSLogger.exe

Select the Components that you wish to log:

For most connection problems, S4 and SIPStack will give you enough information to diagnose the issues.

Select the Logging Level:

Set it to All to ensure it will show warnings, errors and information.

Select the Flags:

Put a check by every component to ensure it will pick up all connection errors.

For Global Options, if you have a large environment, change the max size for your log file as it can get quite big.

In the Log File Folder, I change it to somewhere easier to get to than the Tracing directory.

 

Click Start Logging, then try to initiate your client connections until you drop your call or whatever problem you were experiencing. 

 

Click Stop Logging and then, click Analyze Log Files.

 

The Snooper tool will automatically open and you can dig into the trace messages.

 

 

**Note** Snooper opens to the Tracing view (the first tab), which is a list of all the traces. You'll want the second tab (Messages), which lists the messages in groups in the left pane and the actual errors in the right pane.

Comb through the messages and you should be able to see exactly where the client to server connections are failing and what you need to do to fix them!