none
Lync 2013 Front End Service Not Starting ... RRS feed

  • Question

  • yes another thread because all the other forums are not working so looking for individual help, PLEASE

    I did an upgrade from Lync 2010 to Lync 2013 using Migration Steps - Oiboran.  Now I still have Lync 2010 running becuase I restarted the Lync 2013 server and BOOM, NO front-end service.

    So here is what I've tried so far ... 

    Server startup is being delayed because fabric pool manager has not finished initial placement of users.

    Currently waiting for routing group: {ED244653-6A94-5240-B644-249E9C26806C}.
    Number of groups potentially not yet placed: 4.
    Total number of groups: 4.
    Cause: This is normal during cold-start of a Pool and during server startup.
    If you continue to see this message many times, it indicates that insufficient number of Front-Ends are available in the Pool.
    Resolution:
    During a cold-start of a large Pool it can take upto an hour for the placement process to finish as it needs to populate all the Front-End databases with data from the Backup Store. If the Pool is running and the Front-End is just started, this is normal for some time. If this repeats for a long time, ensure that all the Front-Ends configured for this Pool are up and running. If multiple Front-Ends have been recently decommissioned, run Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery to enable the Pool to recover from Quorum Loss and make progress."

    --- The problem is it keeps running saying "Waiting for RtcSrv service at POOL2013 to be Running.  
    Just keeps running and running without starting.

    --- Tried this but again No luck. It won't run. 

    I've tried running these are the Lync 2013 server, Not the Lync 2010 server. Should I be running both these commands on Lync 2010 as well. 

    My setup.
    Lync 2010 is standard and Front End Only

    Lync 2013 is standard and Front End Only

    Any Ideas ?
    I need to migrate users and can't with Lync 2013 being down.

    Thursday, June 26, 2014 12:12 PM

All replies

  • Hi,

    as it suggests, run CsPoolRegistrarState -ResetType QuorumLossRecovery and see if that helps to start the service.


    http://thamaraw.com

    Thursday, June 26, 2014 12:14 PM
  • I ran that only on POOL2013 (not on POOL2010 - lync 2010 server)

    I started with:

    Stop-CsWindowsService  

    then ran:

    CsPoolRegistrarState -ResetType QuorumLossRecovery

    But for the past 3 hours:

    WARNING:  Waiting for RtcSrv service at <pool2013> to be Running.

    Thursday, June 26, 2014 12:18 PM
  • do not stop the service. you have to run the command while the service is on either "running" or "Starting" stage. The command will stop the service and try to start again.


    http://thamaraw.com

    Thursday, June 26, 2014 12:39 PM
  • You mentioned having a Lync Server 2013 Standard Edition. This can only exist on its own in a single-server Lync 2013 pool and optionally paired with another.

    Could you please verify that your Lync topology is correct, published successfully, ensure that the remaining steps in Lync Setup run to completion* and execute the Lync bootstrap (in Deployment Wizard) on the server?

    Note that Reset-CsPoolRegistrarState is a Lync Server 2013 specific PowerShell cmdlet typically employed in a multi-server Lync Server 2013 Enterprise Edition Front-End Pool.

    Thanks / rgds,

    * certificates, DNS, etc.


    TechNet/MSDN Forum Moderator - http://www.leedesmond.com


    Thursday, June 26, 2014 1:31 PM
    Moderator
  • I will give this a try. stand by.

    Thanks

    Thursday, June 26, 2014 1:33 PM
  • It worked before I restarted Lync2013 server (both internally & externally) so DNS, Certs are working correctly. 

    I ran the 

    Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Format-List * | Out-File "c:\computer_filtered.txt"

    and no certificates came up.

    Topology shows:
    Lync Server
    + HQ
      + Lync Server 2010
        + Standard Edition Front End Servers
          + pool2010
       + Lync Server 2013
         + Standard Edition Front End Servers
           + pool2013

    Thursday, June 26, 2014 1:38 PM
  • Thursday, June 26, 2014 2:33 PM
  • Just an heads up, we are 2 1/2 hours in and still stating:

    WARNING: Waiting for RtcSrv service at POOL2013 to be Running. 

    ^^^ this is being run on Administrator: Lync Server Management Shell on Lync 2013 server. I haven't touched the Lync 2010 server.

    please help

    Thursday, June 26, 2014 3:51 PM
  • The new Lync 2013 Front End wouldn't happen to be server 2012? If so please check http://troubleshootinglync.blogspot.co.nz/2014/03/lync-2013-front-end-service-wont-start.html

    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Lync Sorted blog

    Thursday, June 26, 2014 5:17 PM
  • sorry should of explained that.

    lync 2010 & 2013 built on 2008R2 SP1

    Thursday, June 26, 2014 5:18 PM
  • Thanks for the link but if i run the command, No certs came up in the .txt file
    Thursday, June 26, 2014 5:33 PM
  • I have seen this happening on Server 2013 platform which is due to Shennel error. But, in the event viewer of the FE server, System Events, check whether if you see any shennel related errors. and you can try out below registry entry which should take care of the issue if it's related to Shennel

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL

    create a registry key named ClientAuthTrustMode and set value to 2.


    http://thamaraw.com

    Thursday, June 26, 2014 11:38 PM
  • I let the script run overnight (Reset-CsPoolRegistrarState) and came in this morning to

    Friday, June 27, 2014 9:31 AM
  • I've added the registry and restarted.

    No Success.

    Friday, June 27, 2014 9:37 AM
  • Here is my event logs in Lync Server:

    - Warning - Event 32174, LS User Services

    Server startup is being delayed because fabric pool manager has not finished initial placement of users.

    Currently waiting for routing group: {ED244653-6A94-5240-B644-249E9C26806C}.

    Number of groups potentially not yet placed: 4.

    Total number of groups: 4.

    Cause: This is normal during cold-start of a Pool and during server startup.

    If you continue to see this message many times, it indicates that insufficient number of Front-Ends are available in the Pool.

    Resolution:

    During a cold-start of a large Pool it can take upto an hour for the placement process to finish as it needs to populate all the Front-End databases with data from the Backup Store. If the Pool is running and the Front-End is just started, this is normal for some time. If this repeats for a long time, ensure that all the Front-Ends configured for this Pool are up and running. If multiple Front-Ends have been recently decommissioned, run Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery to enable the Pool to recover from Quorum Loss and make progress.

    - Error - Event 61043, LS MCU Infrastructure

    This process was not able to update its health status

    The IM Conferencing Server failed to send health notifications to the MCU factory at

    Storage Service had a failure while refreshing its calculation of DB space used.

    DB Space Used Refresh Error. The FabricConnectionManager is not initialized

    Cause: The Timer task to refresh the DB space used value ran into an exception. This action will be retried and should auto recover.

    Resolution:

    Check event details. If problem persists, notify your organization's support team with the event details.

    - Error - Event 32178, LS User Services

    Failed to sync data for Routing group {72FBDE4A-0497-5C09-9A53-F1D18E586002} from backup store.

    Cause: This may indicate a problem with connectivity to backup database or some unknown product issue.

    Resolution:

    Ensure that connectivity to backup database is proper. If the error persists, please contact product support with server traces.

    Friday, June 27, 2014 9:45 AM
  • I ran the command from lync management power shell:

    start-cswindowsservice -report c:\report.html

    and returns the following:

     RTCSRV     6/27/2014 9:12:20 AM   Failed
                 ServiceStartFailed: Failed to start service within the expected
    timeframe.
      6/27/2014 9:17:24 AM   Error
                
    Error: System error.
     Details
     Type: TimeoutException
      Stack Trace
           at
    Microsoft.Rtc.Management.Deployment.Core.NTService.Start(Boolean
    wait)
      6/27/2014 9:17:24 AM   Error
                 ServiceStartFailed: Service RTCSRV failed to
    start within the expected timeframe.
      6/27/2014 9:17:24 AM    
                 ServiceStartFailedResolution: Wait to see if
    the service eventually starts. Check eventlog for errors. Re-run the cmdlet or
    start the service manually.

    Friday, June 27, 2014 1:18 PM
  • Hi,

    Please also try to run the following command on FE server: setx /m FabricPackageFileName.

    More details:

    http://www.lynced.com.au/2012/11/lync-2013-front-end-service-wont-start.html

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Best Regards,

    Eason Huang


    Eason Huang
    TechNet Community Support

    Sunday, June 29, 2014 12:34 PM
    Moderator
  • Eason;

    ran the cmd and front-end still did not start. Restart server with no success either


    • Edited by Hawks Fly Monday, June 30, 2014 9:49 AM edit previous statement
    Monday, June 30, 2014 9:02 AM
  • Fault bucket , type 0

    Event Name: APPCRASH

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: RTCSrv.exe

    P2: 5.0.8308.556

    P3: 5236eca4

    P4: FabricCommon.dll

    P5: 1.0.960.0

    P6: 50415773

    P7: c0000602

    P8: 0000000000048bd7

    P9:

    P10:

    Attached files:

    These files may be available here:

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_RTCSrv.exe_5aabb26add335a722516bdaec73a25eaa58155_1f0b0879

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 9d66a1f7-0045-11e4-b0e5-005056ad2c42

    Report Status: 0

    Monday, June 30, 2014 11:01 AM
  • Version=1
    EventType=APPCRASH
    EventTime=130485996388209975
    ReportType=2
    Consent=1
    ReportIdentifier=c48017d8-0045-11e4-b0e5-005056ad2c42
    IntegratorReportIdentifier=c48017d7-0045-11e4-b0e5-005056ad2c42
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=RTCSrv.exe
    Sig[1].Name=Application Version
    Sig[1].Value=5.0.8308.556
    Sig[2].Name=Application Timestamp
    Sig[2].Value=5236eca4
    Sig[3].Name=Fault Module Name
    Sig[3].Value=FabricCommon.dll
    Sig[4].Name=Fault Module Version
    Sig[4].Value=1.0.960.0
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=50415773
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000602
    Sig[7].Name=Exception Offset
    Sig[7].Value=0000000000048bd7
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.272.7
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=0ecf
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=0ecf54951e657e884941606ac828ea87
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=78ec
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=78ec9965a6b21c800f4ca6b9e0f0833c
    UI[2]=C:\Program Files\Microsoft Lync Server 2013\Server\Core\RTCSrv.exe
    UI[5]=Check online for a solution (recommended)
    UI[6]=Check for a solution later (recommended)
    UI[7]=Close
    UI[8]=SIP Server Service stopped working and was closed
    UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
    UI[10]=&Close
    LoadedModule[0]=C:\Program Files\Microsoft Lync Server 2013\Server\Core\RTCSrv.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\system32\kernel32.dll
    LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\system32\MSVCR110.dll
    LoadedModule[5]=C:\Windows\system32\MSVCP110.dll
    LoadedModule[6]=C:\Windows\system32\ADVAPI32.dll
    LoadedModule[7]=C:\Windows\system32\msvcrt.dll
    LoadedModule[8]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[9]=C:\Windows\system32\RPCRT4.dll
    LoadedModule[10]=C:\Windows\system32\USER32.dll
    LoadedModule[11]=C:\Windows\system32\GDI32.dll
    LoadedModule[12]=C:\Windows\system32\LPK.dll
    LoadedModule[13]=C:\Windows\system32\USP10.dll
    LoadedModule[14]=C:\Program Files\Microsoft Lync Server 2013\Server\Core\wsiphsh.DLL
    LoadedModule[15]=C:\Windows\system32\CRYPT32.dll
    LoadedModule[16]=C:\Windows\system32\MSASN1.dll
    LoadedModule[17]=C:\Windows\system32\NETAPI32.dll
    LoadedModule[18]=C:\Windows\system32\netutils.dll
    LoadedModule[19]=C:\Windows\system32\srvcli.dll
    LoadedModule[20]=C:\Windows\system32\wkscli.dll
    LoadedModule[21]=C:\Windows\system32\SAMCLI.DLL
    LoadedModule[22]=C:\Windows\system32\LOGONCLI.DLL
    LoadedModule[23]=C:\Windows\system32\Secur32.dll
    LoadedModule[24]=C:\Windows\system32\SSPICLI.DLL
    LoadedModule[25]=C:\Windows\system32\ACTIVEDS.dll
    LoadedModule[26]=C:\Windows\system32\adsldpc.dll
    LoadedModule[27]=C:\Windows\system32\WLDAP32.dll
    LoadedModule[28]=C:\Windows\system32\ATL.DLL
    LoadedModule[29]=C:\Windows\system32\ole32.dll
    LoadedModule[30]=C:\Windows\system32\OLEAUT32.dll
    LoadedModule[31]=C:\Windows\system32\IMM32.DLL
    LoadedModule[32]=C:\Windows\system32\MSCTF.dll
    LoadedModule[33]=C:\Windows\system32\CRYPTBASE.dll
    LoadedModule[34]=C:\Windows\system32\ntmarta.dll
    LoadedModule[35]=C:\Windows\system32\CLBCatQ.DLL
    LoadedModule[36]=C:\PROGRA~1\MICROS~1\Server\Core\SIPStack.dll
    LoadedModule[37]=C:\PROGRA~1\MICROS~1\Server\Core\WSIPPERF.dll
    LoadedModule[38]=C:\Windows\system32\loadperf.dll
    LoadedModule[39]=C:\Windows\system32\SHLWAPI.dll
    LoadedModule[40]=C:\Windows\system32\PSAPI.DLL
    LoadedModule[41]=C:\Windows\system32\WS2_32.dll
    LoadedModule[42]=C:\Windows\system32\NSI.dll
    LoadedModule[43]=C:\Windows\system32\MSWSOCK.dll
    LoadedModule[44]=C:\Windows\system32\DNSAPI.dll
    LoadedModule[45]=C:\Windows\system32\ODBC32.dll
    LoadedModule[46]=C:\Windows\system32\odbcint.dll
    LoadedModule[47]=C:\Windows\system32\CRYPTSP.dll
    LoadedModule[48]=C:\Windows\system32\rsaenh.dll
    LoadedModule[49]=C:\Windows\system32\USERENV.dll
    LoadedModule[50]=C:\Windows\system32\profapi.dll
    LoadedModule[51]=C:\Windows\system32\GPAPI.dll
    LoadedModule[52]=C:\Windows\system32\IPHLPAPI.DLL
    LoadedModule[53]=C:\Windows\system32\WINNSI.DLL
    LoadedModule[54]=C:\Windows\system32\dhcpcsvc6.DLL
    LoadedModule[55]=C:\Windows\system32\dhcpcsvc.DLL
    LoadedModule[56]=C:\Windows\system32\ncrypt.dll
    LoadedModule[57]=C:\Windows\system32\bcrypt.dll
    LoadedModule[58]=C:\Windows\system32\bcryptprimitives.dll
    LoadedModule[59]=C:\Windows\system32\credssp.dll
    LoadedModule[60]=C:\Windows\System32\msxml6.dll
    LoadedModule[61]=c:\Windows\system32\sqlncli11.dll
    LoadedModule[62]=c:\Windows\system32\MSVCR100.dll
    LoadedModule[63]=c:\Windows\system32\VERSION.dll
    LoadedModule[64]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_a4d3b9377117c3df\COMCTL32.dll
    LoadedModule[65]=C:\Windows\system32\COMDLG32.dll
    LoadedModule[66]=C:\Windows\system32\SHELL32.dll
    LoadedModule[67]=c:\Windows\system32\1033\SQLNCLIR11.RLL
    LoadedModule[68]=C:\Windows\system32\netbios.dll
    LoadedModule[69]=C:\Windows\system32\kerberos.DLL
    LoadedModule[70]=C:\Windows\system32\cryptdll.dll
    LoadedModule[71]=C:\Windows\system32\msv1_0.DLL
    LoadedModule[72]=C:\Windows\system32\ntdsapi.dll
    LoadedModule[73]=C:\Windows\system32\CLUSAPI.DLL
    LoadedModule[74]=C:\Windows\system32\RESUTILS.DLL
    LoadedModule[75]=C:\Windows\system32\security.dll
    LoadedModule[76]=C:\Windows\system32\schannel.DLL
    LoadedModule[77]=c:\Program Files\Microsoft SQL Server\90\Shared\instapi.dll
    LoadedModule[78]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6229_none_88dcc0bf2fb1b808\MSVCR80.dll
    LoadedModule[79]=C:\Windows\System32\wshtcpip.dll
    LoadedModule[80]=C:\Windows\System32\wship6.dll
    LoadedModule[81]=C:\Windows\system32\rasadhlp.dll
    LoadedModule[82]=C:\Windows\System32\fwpuclnt.dll
    LoadedModule[83]=C:\Windows\system32\cryptnet.dll
    LoadedModule[84]=C:\Windows\system32\apphelp.dll
    LoadedModule[85]=C:\PROGRA~1\MICROS~1\Server\Core\WRTCES.dll
    LoadedModule[86]=C:\PROGRA~1\MICROS~1\Server\Core\WRTCESPF.dll
    LoadedModule[87]=C:\Windows\system32\WINHTTP.dll
    LoadedModule[88]=C:\Windows\system32\webio.dll
    LoadedModule[89]=C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricClient.dll
    LoadedModule[90]=C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricCommon.dll
    LoadedModule[91]=C:\Windows\system32\dbghelp.dll
    LoadedModule[92]=C:\Windows\system32\XmlLite.dll
    LoadedModule[93]=C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricRuntime.dll
    LoadedModule[94]=C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\LeaseLayer.dll
    LoadedModule[95]=C:\PROGRA~1\MICROS~1\Server\Core\Queue.dll
    LoadedModule[96]=C:\Windows\system32\HTTPAPI.dll
    LoadedModule[97]=C:\Windows\system32\pcwum.dll
    LoadedModule[98]=C:\PROGRA~1\MICROS~1\Server\Core\APIEM.dll
    LoadedModule[99]=C:\PROGRA~1\MICROS~1\Server\Core\APIPERF.dll
    LoadedModule[100]=C:\PROGRA~1\MICROS~1\Server\Core\RTCArchA.dll
    LoadedModule[101]=C:\PROGRA~1\MICROS~1\Server\Core\RtcArcPf.dll
    LoadedModule[102]=C:\Windows\system32\DSROLE.DLL
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=SIP Server Service
    AppPath=C:\Program Files\Microsoft Lync Server 2013\Server\Core\RTCSrv.exe
    Monday, June 30, 2014 11:03 AM
  • Faulting application name: RTCSrv.exe, version: 5.0.8308.556, time stamp: 0x5236eca4

    Faulting module name: FabricCommon.dll, version: 1.0.960.0, time stamp: 0x50415773

    Exception code: 0xc0000602

    Fault offset: 0x0000000000048bd7

    Faulting process id: 0x1010

    Faulting application start time: 0x01cf94525609be57

    Faulting application path: C:\Program Files\Microsoft Lync Server 2013\Server\Core\RTCSrv.exe

    Faulting module path: C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricCommon.dll

    Report Id: 9d66a1f7-0045-11e4-b0e5-005056ad2c42

    Monday, June 30, 2014 11:04 AM
  • Looks to me it's time to ring Microsoft support :( if anything that have seen before, would have fixed after applying any of the solutions that proposed above. This seems to me something entirely different.


    http://thamaraw.com

    Tuesday, July 1, 2014 11:29 PM
  • Hello

    I have same error after run setx..
    Any solution?

    Gabor Sneff


    Udvozlettel:Sneff Gabor

    Friday, November 14, 2014 9:34 PM
  • Please update the Lync Server with update named 2912334

    refer link - https://support.microsoft.com/en-us/kb/2905048

    Rgds

    -Harjit

    Thursday, January 28, 2016 11:57 AM
  • Hi 

    can you make sure that the Lync 2010 and Lync 2013 servers are updated with the latest CU 

    I had similar issue in which the Updates were way behind 


    Linus

    Friday, January 29, 2016 11:52 AM
  • I used the below info to correct the problem basically it was a certificate problem. However, I still need to find out why I'm getting schannel errors in the log.

    Cause

    A common cause of this issue is if non self-signed certificates are imported into Trusted Root Certification Authorities instead of Intermediate Certification Authorities. Although this was not an issue in Windows Server 2008, Windows 2012 requires a high level of trust dependant on certification authentication.The result is that HTTP communication between Lync servers is broken.

    Solution

    Check the Trusted Root Certification Authority Store for any NON self-signed certificates. Self signed certificates have the same value for the Issued To and Issued By field. The screen shot below shows the highlighted certificate as not being self-signed (whilst residing in the Trusted Root Certification Authority Store)

    http://troubleshootinglync.blogspot.co.nz/2014/03/lync-2013-front-end-service-wont-start.html

    Tuesday, July 11, 2017 9:34 PM