Lync Server hosting provider ProxyFqdn value causes push notifications to fail

Use the information listed below to make sure that the value being used for the Lync Online hosting provider ProxyFqdn is correct.

Note Use the following link to download and install the OCS logger utility for Lync Server 2013 to take SipStack logging from specific Lync Server 2013 Edge servers

Microsoft Lync Server 2013 Debugging Tools

Use the following steps to launch the Lync Server Logging Tool from the Windows Server console:

Using Windows Server 2012

  1. For Lync Server 2013 press the Windows function key and choose the Search option
  2. Type in Explore.exe and click on the Search icon
  3. Use Windows Explorer to browse to <local drive:>\Program Files\Microsoft Lync Server 2013\Debugging Tools, use the Windows Explorer details pane to locate OcsLogger.exe and double click on it
  4. For Lync Server 2010 press the Windows function key to access the Start page
  5. Click on the Lync Server Logging Tool tile
Using Windows Server 2008 or Windows Server 2008 R2

  1. Click on Start, All Programs, Microsoft Lync Server and then choose Lync Server Logging Tool
Use the following steps to continue with taking the SipStack logging:
  1. Select SipStack logging component from the Logging Options selection
  2. Check the All Levels, and then check All Flags
  3. Click on the Start Logging button
  4. Launch the Lync Server Management Shell from the Windows Server console
  5. Test federation with the Push notification Clearing House using Lync Server Test-CsFederatedPartner PowerShell cmdlet as per the example:

    Test-CsFederatedPartner –TargetFqdn –Domain

  6. Wait for the Test-CsFederatedPartner Lync Server PowerShell cmdlet to complete
  7. Click on the Lync Server Logging Tool's Stop Logging button
  8. Click on the Lync Server Logging Tool's View log Files button to open the SipStack log in a text format
  9.  Research the SipStack logs from the Lync Server Edge server and locate the following diagnostic information:


The ProxyFqdn value for the hosting provider has been configured with an incorrect value 
Use the steps listed below to resolve this issue:

  1. Launch the Lync Server Management Shell from the Windows Server console
  2. Use the Remove-CsHostingProvider Lync Server PowerShell cmdlet to remove the unwanted hosting provider information as per the example:

    Remove-CsHostingProvider -Identity ""

  3. Use the New-CsHostingProvider Lync Server PowerShell cmdlet to add the correct hosting provider information as per the example:

    New-CsHostingProvider –Identity "LyncOnline" –Enabled $True –ProxyFqdn "" –VerificationLevel UseSourceVerification

  4. Use the Invoke-CsManagementStoreReplication Lync Server PowerShell cmdlet to initiate Central Management Store (CMS) replication to all replica stores in the Lync Server enterprise as per the example:


    Note There could be a two to three minute delay as changes are processed by the Master Replicator

More information
For detailed information on the Lync Server PowerShell cmdlet described in this article, review the Microsoft TechNet links listed below:





Note Lync Server 2013 supports the use of the Centralized Logging Service. For detailed information on how to configure the Centralized Logging Service for Instant Messaging (IM) and Presence.

Using the Centralized Logging Service

Lync Mobility Push notification flow

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Article ID: 2743783 - Last Review: 07/07/2013 19:58:00 - Revision: 2.1

Microsoft Lync Server 2010 Standard Edition, Microsoft Lync Server 2010 Enterprise Edition, Microsoft Lync Server 2013

  • kbsurveynew KB2743783