Lync Edge Services Won't Start

I read a lot about thee problems others faced but none of them solved my issues . in the event viewer here are the problems.

  1. LS Protocol Stack : Unable to bind for socket.

    Transport:TLS, IP address:77.42.220.238, Port:5061. Error:0x80072741 (The requested address is not valid in its context.).
    Resolution:
    Ensure that no other program is listening to the specified port and that the IP address is valid.Log Name:      Lync Server
    Source:        LS Protocol Stack
    Date:          4/14/2015 5:31:34 PM
    Event ID:      14346
    Task Category: (1001)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      lyncedge.domtech.org
    Description:
    Unable to bind for socket.

    Transport:TLS, IP address:77.42.220.238, Port:5061. Error:0x80072741 (The requested address is not valid in its context.).
    Resolution:
    Ensure that no other program is listening to the specified port and that the IP address is valid.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="LS Protocol Stack" />
        <EventID Qualifiers="50153">14346</EventID>
        <Level>2</Level>
        <Task>1001</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-04-14T14:31:34.000000000Z" />
        <EventRecordID>992</EventRecordID>
        <Channel>Lync Server</Channel>
        <Computer>lyncedge.domtech.org</Computer>
        <Security />
      </System>
      <EventData>
        <Data>TLS</Data>
        <Data>77.42.220.238</Data>
        <Data>5061</Data>
        <Data>0x80072741</Data>
        <Data>The requested address is not valid in its context.</Data>
      </EventData>
    </Event>
  2. LS Protocol Stack : A configured transport has failed to start.

    Transport TLS has failed to start on local IP address 77.42.220.238 at port 5061.
    Cause: Configuration error, low system resources or another program is using the specified port. Can also happen if the IP address has become invalid.
    Resolution:
    Ensure that the IP address specified is valid and that no other program is listening on the specified port.Log Name:      Lync Server
    Source:        LS Protocol Stack
    Date:          4/14/2015 5:31:34 PM
    Event ID:      14336
    Task Category: (1001)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      lyncedge.domtech.org
    Description:
    A configured transport has failed to start.

    Transport TLS has failed to start on local IP address 77.42.220.238 at port 5061.
    Cause: Configuration error, low system resources or another program is using the specified port. Can also happen if the IP address has become invalid.
    Resolution:
    Ensure that the IP address specified is valid and that no other program is listening on the specified port.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="LS Protocol Stack" />
        <EventID Qualifiers="50153">14336</EventID>
        <Level>2</Level>
        <Task>1001</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-04-14T14:31:34.000000000Z" />
        <EventRecordID>993</EventRecordID>
        <Channel>Lync Server</Channel>
        <Computer>lyncedge.domtech.org</Computer>
        <Security />
      </System>
      <EventData>
        <Data>TLS</Data>
        <Data>77.42.220.238</Data>
        <Data>5061</Data>
      </EventData>
    </Event>
  3. LS Server : The protocol stack reported a critical error: code 80072741 (The requested address is not valid in its context.). The service has to stop.Log Name:      Lync Server
    Source:        LS Server
    Date:          4/14/2015 5:31:34 PM
    Event ID:      12303
    Task Category: (1000)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      lyncedge.domtech.org
    Description:
    The protocol stack reported a critical error: code 80072741 (The requested address is not valid in its context.). The service has to stop.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="LS Server" />
        <EventID Qualifiers="50152">12303</EventID>
        <Level>2</Level>
        <Task>1000</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-04-14T14:31:34.000000000Z" />
        <EventRecordID>994</EventRecordID>
        <Channel>Lync Server</Channel>
        <Computer>lyncedge.domtech.org</Computer>
        <Security />
      </System>
      <EventData>
        <Data>80072741</Data>
        <Data>The requested address is not valid in its context.</Data>
      </EventData>
    </Event>
  4. LS Protocol Stack : Unable to start the stack.

    Error: 0xC3E93C0A (SIP_E_STACK_TRANSPORT_FAILED)Log Name:      Lync Server
    Source:        LS Protocol Stack
    Date:          4/14/2015 5:31:34 PM
    Event ID:      14352
    Task Category: (1001)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      lyncedge.domtech.org
    Description:
    Unable to start the stack.

    Error: 0xC3E93C0A (SIP_E_STACK_TRANSPORT_FAILED)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="LS Protocol Stack" />
        <EventID Qualifiers="50153">14352</EventID>
        <Level>2</Level>
        <Task>1001</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-04-14T14:31:34.000000000Z" />
        <EventRecordID>995</EventRecordID>
        <Channel>Lync Server</Channel>
        <Computer>lyncedge.domtech.org</Computer>
        <Security />
      </System>
      <EventData>
        <Data>0xC3E93C0A</Data>
        <Data>SIP_E_STACK_TRANSPORT_FAILED</Data>
      </EventData>
    </Event>

Any Help Would be apreciated , Thanks !


  • Edited by JadCham Tuesday, April 14, 2015 3:02 PM
April 14th, 2015 3:01pm

Hi JadCham,

 

You must define two separate subnets for Edge Server, one for the internal-facing interface and one for the external-facing interface. The internal and external subnets must not be routable to each other.

If you enabled NAT for Edge Server, the public IP should not be configured on the Edge external NIC.

Please provide more information about your Network and Topology configuration.

e.g.




 

Best regards,

Eric

Free Windows Admin Tool Kit Click here and download it now
April 17th, 2015 5:00am

Thanks ! That was the problem 
May 1st, 2015 5:20pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics