Lync 2013 Standard Edition Server - Front-End service hangs in "starting" state if a child AD domain is not accessible. RRS feed

  • Question

  • Hello,

    We faced an issue with Lync Front-End service hanging in "starting" state after server reboot due to lost connectivity to one of AD sub-domains. 

    Environment: Lync 2013 Standard edition servers - 1 Front-End and 1 Edge server on Windows Server 2008 R2 Standard edition. A single forest that consists of a root domain and two child domains. Child domains are not CS prepaired and for the moment they are not planned to host any Lync users.

    Issue: Server rebooted for maintenance and Lync FE service hung in "starting" state. Meanwhile we discovered that due to a network issue one of the child domains is not accessible. Once the connection to child domain DCs was restored, Lync Front End service started successfully. 

    Errors logged in the event viewer:

    1. Log Name: Lync Server
      Source: LS User Replicator
      Date: 2/4/2013 7:35:20 AM
      Event ID: 30009
      Task Category: (1009)
      Level: Warning
      Keywords: Classic
      User: N/A
      Computer:  LYNC 2013 FE Server
      Description: Failed to get a connection to a domain controller in domain that User Replicator intended to synchronize. This prevents User Replicator from synchronizing this domain. This failure occurred because DsGetDcName failed to give a valid domain controller to connect to. DsGetDcName failures usually stop occurring after some time. If this error continues to occur, the computer should be rebooted to fix the NetLogon service which calls DsGetDcName. The source of the replication is LocalRegistrarReplication.
    2. Log Name: Lync Server
      Source: LS MCU Infrastructure
      Date: 2/4/2013 10:09:22 AM
      Event ID: 61035 and 61037
      Task Category: (1022)
      Level: Error
      Keywords: Classic
      User: N/A
      Computer: Lync 2013 FE Server
      Description: This process was not able to update its health status

      The Audio-Video Conferencing Server (Web Conferencing Server; Application Sharing Conferencing Server) failed to send health notifications to the MCU factory at 
      Failure occurrences: 4, since 2/4/2013 10:08:22 AM.
      Cause: Either the Front End service is not running, or poor network connectivity.
      Resolution: Verify that the Front End Service is available, and its machine is visible over the network.

    Question: Is it possible to restrict Lync FE server comunications to root domain's DCs only so we could avoid this issue in future. We are not planning to enable the two child domains for Lync in the near future and they are not listed in the addtional supported SIP domains.

    Monday, February 4, 2013 11:13 AM


  • You can use


    -Identity global -AddomainNamingContextList @{Add="dc=contoso,dc=com"}

    To select only your user domains.

    regards Holger Technical Specialist UC

    Monday, February 4, 2013 1:34 PM

All replies

  • You can use


    -Identity global -AddomainNamingContextList @{Add="dc=contoso,dc=com"}

    To select only your user domains.

    regards Holger Technical Specialist UC

    Monday, February 4, 2013 1:34 PM
  • Hi,

    If you add value into AddomainNamingContextList, the User Replicator will only synchronize with the domains specified in the ADDomainNamingContextList.

    In addition, I would like to confirm how many GC in your entire forest.

    Kent Huang
    TechNet Community Support

    Tuesday, February 5, 2013 7:49 AM
  • Thank you for your reply :-)

    I've used the Replace option following

    "to configure the global settings so that only is on the list use this syntax: 

    -ADDomainNamingContextList @{Replace="dc=fabrikam,dc=com"}"

    Tuesday, February 5, 2013 8:41 AM
  • Hi and thank you for your explanation.

    In the ADDomainNamingContextList I've specified the only domain, hosting Lync users,.

    All DCs are GCs.

    Tuesday, February 5, 2013 8:44 AM
  • worked for me like a charm!!!
    Wednesday, July 10, 2013 3:43 AM