none
Lync Server Edge Server services are not starting

    Question

  •  

    The Lync Server Access Edge service terminated with service-specific error %%-1008124830

    Edge Server is Server 2008 R2 - I followed all the steps per the white paper and did not receive any errors but received this error.

    Clyde

    Thursday, November 11, 2010 10:57 PM

All replies

  • Hi, Clyde, would you please elaborate a bit more about your situation?

    When do you get the error while Lync Edge server deployment?

    Would you please check event logs to find out more hints related to this error?

    And also please check are ports, DNS, certificates and other settings are met the steps in the white paper.

    If still no luck after have tried above, would you please reconfigure settings of Edge server in Topology Builder, then rebuild Lync Edge server from scratch. 


    Best regards,
    Friday, November 12, 2010 6:21 AM
  • Hi,

    At which step did this happen? Did you import the topology xml? Please let us know...


    Microsoft minded UC specialist - http://www.reijling.nl
    Monday, November 15, 2010 8:39 PM
  • I usually see this happen when the IP addresses are not configured correctly.

     

    If you look at your Event Log, expand applications and services and look under Lync Server, this will give a more detailed error message.

     

    Also, on that server if you open lync powershell, you can do the following command to get a report:

     

    start-cswindowsservice -report c:\report.html

     

    Post whatever you have, thanks.

     


    Randy Wintle |MVP:Communications Server, MCTS: UC Voice Specialization | Winxnet Inc
    Monday, November 15, 2010 9:42 PM
  • Hi, Clyde, any updates?
    Best regards,
    Tuesday, November 16, 2010 9:42 AM
  • I am getting the same thing.  Now I have a single front end and a single edge that are virtualized...  Stupid question... With the new NAT settings for the edge does the external IP have to be bound to a network adapter on the edge?  I only have the internal ip assigned to the nic.  I assumed with the topology builder giving you the ability to put in your NAT settings that it would work fine with only an internal network ip and have the Firewall static natting the traffic like I do for Exchange.  

     


    Bryan Kendrick Systems Administrator Forest Ridge
    Saturday, November 20, 2010 8:23 PM
  • I'm having the same problem..

    All services start, but the Lync Server Access Edge.

    This is what i'm getting from the event viewer:

    Error code is:0xC3R93C0A (SIP_E_STACK_TRANSPORT_FAILED).

    Transport TLS has failed to start on local IP address 172.16.11.6 at port 5061.

    Using netstat i can see that the port is not beeing used.

    Any ideas?

     


    Rafael Monteiro
    Monday, November 22, 2010 8:17 PM
  • can you check the configured ip addresses on your Edge server ?
    Charbel Hanna
    • Proposed as answer by Charbel Hanna Wednesday, April 13, 2011 10:22 PM
    Tuesday, November 23, 2010 9:19 AM
  • I see only the internal network address programmed on it.  I humored myself and added the external ip to the nic as a second ip and the services work now.  But I dont understand why that would be needed if they have the NAT feature now on this server.
    Bryan Kendrick Systems Administrator Forest Ridge
    Wednesday, December 01, 2010 5:22 PM
  • This is has nothing to do with NAT, Edge Services requires to have multiple Ip addresses for each external FQDN.

    NAT is supported as ONE to ONe NAT behind the Edge Server on the external Firewall Side

     

    regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread
    Saturday, December 04, 2010 3:54 PM
  • You may also want to check the certificates are not in error as this will casue the services not to start and gereate this error
    Steve
    Wednesday, March 16, 2011 4:31 AM
  • I entered the command: start-cswindowsservice -report c:\report.html

     

    From the Event Viewer:

    Log Name:      Lync Server
    Source:        LS Mediation Server
    Date:          3/14/2011 6:20:31 PM
    Event ID:      25004
    Task Category: (1030)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ocshost1.pstocs.com
    Description:
    Mediation Server service could not be started.

    Exception: System.InvalidOperationException: Certificate does not match the machine FQDN of mediation server (ocshost1.pstocs.com).


    [ocshost1 is the hostname of the Lync Server, ocshost2 is the hostname of the DNS/DC, for what that's worth]

     

    Below is what report.html had in it.

    Any ideas?

     

    Thanks,

     

    Scott

     

     

     

    Host name: ocshost1.pstocs.com   3/16/2011 11:13:15 AM    
         +    Service start complete "Lync Server Master Replicator Agent (MASTER)".   3/16/2011 11:13:15 AM    
         +    Service start complete "Lync Server Replica Replicator Agent (REPLICA)".   3/16/2011 11:13:15 AM    
         +    Service start "Lync Server Front-End (RTCSRV)".   3/16/2011 11:13:15 AM    
         +    Error: Service "Lync Server Front-End (RTCSRV)" failed to start within the expected timeframe: System error..   3/16/2011 11:13:16 AM   Error
         +    Service start complete "Lync Server Response Group (RTCRGS)".   3/16/2011 11:13:16 AM    
         +    Service start "Lync Server Bandwidth Policy Service (Authentication) (RTCPDPAUTH)".   3/16/2011 11:13:16 AM    
         +    Error: Service "Lync Server Bandwidth Policy Service (Authentication) (RTCPDPAUTH)" failed to start within the expected timeframe: System error..   3/16/2011 11:13:23 AM   Error
         +    Service start "Lync Server Bandwidth Policy Service (Core) (RTCPDPCORE)".   3/16/2011 11:13:23 AM    
         +    Warning: Cannot start service RTCPDPCORE on computer 'ocshost1.pstocs.com'.   3/16/2011 11:13:28 AM   Warning
         +    Service start "Lync Server Call Park (RTCCPS)".   3/16/2011 11:13:28 AM    
         +    Error: Service "Lync Server Call Park (RTCCPS)" failed to start within the expected timeframe: System error..   3/16/2011 11:13:33 AM   Error
         +    Service start complete "Lync Server Audio Test Service (RTCATS)".   3/16/2011 11:13:33 AM    
         +    Service start "Lync Server IM Conferencing (RTCIMMCU)".   3/16/2011 11:13:33 AM    
         +    Error: Service "Lync Server IM Conferencing (RTCIMMCU)" failed to start within the expected timeframe: System error..   3/16/2011 11:13:35 AM   Error
         +    Service start "Lync Server Web Conferencing (RTCDATAMCU)".   3/16/2011 11:13:35 AM    
         +    Error: Service "Lync Server Web Conferencing (RTCDATAMCU)" failed to start within the expected timeframe: System error..   3/16/2011 11:13:37 AM   Error
         +    Service start "Lync Server Audio/Video Conferencing (RTCAVMCU)".   3/16/2011 11:13:37 AM    
         +    Error: Service "Lync Server Audio/Video Conferencing (RTCAVMCU)" failed to start within the expected timeframe: System error..   3/16/2011 11:13:38 AM   Error
         +    Service start "Lync Server Application Sharing (RTCASMCU)".   3/16/2011 11:13:38 AM    
         +    Error: Service "Lync Server Application Sharing (RTCASMCU)" failed to start within the expected timeframe: System error..   3/16/2011 11:13:40 AM   Error
         +    Service start "Lync Server Mediation (RTCMEDSRV)".   3/16/2011 11:13:40 AM    
         +    Error: Service "Lync Server Mediation (RTCMEDSRV)" failed to start within the expected timeframe: System error..   3/16/2011 11:13:42 AM   Error
         +    Service start "Lync Server Web Conferencing Compatibility (RTCMEETINGMCU)".   3/16/2011 11:13:42 AM    
         +    Error: Service "Lync Server Web Conferencing Compatibility (RTCMEETINGMCU)" failed to start within the expected timeframe: System error..   3/16/2011 11:13:44 AM   Error
         +    Service start complete "Lync Server File Transfer Agent (FTA)".   3/16/2011 11:13:44 AM    

     +    Command Status: Command processing is complete.   3/16/2011 11:13:44 AM    
     +    Command Status: Command run is complete.   3/16/2011 11:13:44 AM    

    Wednesday, March 16, 2011 3:17 PM
  • hi there any update regarding this issue ?
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread
    Wednesday, April 13, 2011 5:10 PM
  • I don't remember exactly how i solved the problem...but i remember that it was related to a misconfiguration of the external interface ip addresses...
    Rafael Monteiro
    Wednesday, April 13, 2011 5:17 PM
  • thank you
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread
    Wednesday, April 13, 2011 10:21 PM
  • Hi there,

    So it seams that you probably have not assigned the certificates on the correct intefaces. Please make sure you have the correct IP's and names (so the certificates match the DNS name).


    Microsoft minded UC specialist - http://www.reijling.nl
    Thursday, July 21, 2011 2:27 PM
  • Hi,

    I  had the similar issue, and nothing mentioned above worked for me. so, i did the following to resolve it.

    1) Changed the options in the IE -Tools-Internet options-Advanced-security. Unchecked the option of check for server/publisher certificate revocation (although not ideal)

    2) Uninstalled all the de componenant from programs and features.

    3) deleted the certs and created again

    4) unchecked federation on port 5061 in TB, because i was using single public ip address for all edge roles

    5) restarted the server and installed all the roles again and bingo. it went well.problem disappeared.

    Thanks

    Pankaj

     


    Panky, Learning never stops.You just need to find new subjects.
    Saturday, October 22, 2011 6:08 PM
  • Make sure you have added the IP addresses correctly.

    Take a look in the Lync topology as to which IP addresses are assigned to those services (av, webcon, access edge). Add those IP addresses to the NIC on your Edge and start the services successfully.

    • Proposed as answer by Surjeet Taank Thursday, October 18, 2012 4:01 AM
    Thursday, June 14, 2012 1:18 AM
  • Did this get resolved now..

    did you make the changes required in the Lync Edge build.?

    Regards

    Iain Smith


    Iain Smith @NorthernLync www.northernlync.co.uk

    Tuesday, July 31, 2012 2:31 PM
  • I had the same error and was using an external certificate on the inside and outside interfaces.  I noticed that the cert did not have the internal fqdn on it which the topology referenced.  I then requested a cert from our internal ca with that name and the other san names from the external on it and the service started right up.

    Thanks for pointing me in the right direction.

    Thursday, July 11, 2013 7:15 PM