Lync network monitor parsers

The Lync - Options dialog box, click General . Under Logging , check the box Turn on logging in Lync and check the box Turn on Windows Event logging for Lync check boxes. Click OK . Restart Lync, and then try to reproduce the issue. Collect the full contents of %userprofile%\tracing\ directory. Description : The Microsoft Lync Server 2010 Logging Tool facilitates troubleshooting by capturing and logging tracing information from the product while the product is running. Logging Tool with the Lync Server administrative tools and can be used to troubleshoot issues on any Lync Server role. Lync Server 2010 Logging Tool generates log files on a per-server basis, so it must be actively running and tracing on each computer for which you want to generate a log. Figure 1. Lync Server 2010 Logging Tool Unless otherwise noted you should use the following when gathering traces: Level: All Flags: Check All Type: New File Maximum Size: 100 MB Components: AsMCU, DataMCU, SipStack Simultaneous Network Monitor Trace from the Lync Front-end servers and the Lync client Go to Start menu -> Programs -> Network Analysis Tools and right click on Network Monitor and hit “Run as Admin” If you don’t find it here, check the following Start -> Programs - >Administrative Tools - > Network Analysis Tools Click on capture menu and click on network Click on local computer and select the Local area connection Network Cards Select Capture menu and select start Once you reproduce the problem, stop the NETMON by selecting Capture and Stop. Save the file by selecting file menu save as option Download the Microsoft Network Monitor 3.4 from the Download Center. Update Resource Center for Lync 2010 Application Sharing in Lync External User Access from the Lync Server 2010 Resource Kit and see page 41 for a section on Conferencing . Figure 2. Application- sharing conference join flow Lync Server 2010 Documentation Library DrRez blog NextHop blog Lync Server and Communications Server resources Fan us on Facebook Follow us on Twitter Send us e-mail Keywords : Desktop Sharing; Application Sharing

Registration—Install Registration and Run-Time Registration—is important. For more information, see Register Contextual Conversation Packages in Lync 2010 in the Lync 2010 SDK documentation.Understand which Registry entries are required and which are optional. For more information, see Register Contextual Conversation Packages in Lync 2010.Use localhost for the InternalURL registry entry.Microsoft Internet Information Service (IIS) Manager is used in the deployment of the applications discussed in this series of articles.DebuggingConsider the following tools for debugging scenarios that involve a Microsoft Unified Communications Managed API (UCMA) 3.0 application and a Microsoft Lync 2010 application.Snooper.exe: This protocol analysis tool can help you analyze Session Initiation Protocol (SIP) and Centralized Conferencing Control Protocol (C3P) protocol logs, including those generated by OCSLogger.exe. It is available at the Microsoft Download Center.Microsoft Network Monitor 3.4: Like Snooper, Network Monitor is a protocol analyzer. You can capture, view, and analyze network traffic with this tool. It is available at the Microsoft Download Center.A Lync 2010 desktop application that is used to obtain the Conversation object: In dealing with scenarios such as the one described in this series of articles, it can be useful to create a separate application to use the ConversationManager class to loop through the collection of currently active conversations. Typically the Conversation object that you want is the only one active object. Examining the Properties property on the Conversation instance will often help resolve issues.Logging and SIP Message FlowFor a UCMA 3.0 application, the Microsoft Lync Server 2010 Logging Tool can be used to capture logging

(See Data Collection Checklist below for full details). Simultaneous Network Monitor Trace from the Lync Front-end servers and the Lync client Lync Logging from Edge server (SIPSTACK & S4) with Remote Connectivity Analyzer . RTCBPA (Best Practices Analyzer) Summary Both internal and external Lync clients are unable to share Desktop or Applications with internal conference participants– Error: Screen sharing cannot connect to the server now . Environment Lync Server 2010 Internal client to internal client External to external or internal (any) Recommended Steps This error is commonly reported when the Application Sharing Server (ASMCU) service is not running on the Lync Server Front End pool. If the ASMCU service is not installed on the Lync Front End it is likely because the components have not been enabled within the Lync Topology. Verify Application Sharing service is enabled in topology builder. If not, enable it and publish the topology. Rerun component setup on FE pool using the Lync Deployment Wizard. Verify Application Sharing and Web Conferencing Services are actively running on FE pool. If not, try to start them. Check Lync Application Event logs if start fails. Verify whether the user has the appropriate conferencing policy applied and that the policy applied has EnableAppDesktopSharing = TRUE. Get-CsConferencingPolicy Additionally: The January 2011 Lync Server updates addressed an issue that could result in this error being reported. See A Lync 2010 user cannot share his desktop or share an application during a Lync online meeting that contains an OCS 2007 R2 user and a Lync 2010 user ( for details. Recommended Diagnostics Client side logging for the Presenter attempting to start Application Sharing (See Data Collection Checklist below for steps). Lync Logging Tool logs for the same repro (See Data Collection Checklist for steps) Lync Event logs from the FE Pool. Complete an Escalation Template : Premier Support for Lync Partners Escalation Template . Use Lync client logging to collect the uccp and etl logs. Lync Client-side logging is a valuable troubleshooting tool. To enabled logging: In the upper right corner of the Lync main window, under Tools click Options (gear icon). In