I setup a new Edge server for a client that ended up having a bunch of issues starting services. I wanted to write this article because the issues that I saw were very simple errors but took me a good amount of time to figure out.

The first issue I had was that none of the Edge services would start. If you tried to start an Edge Service, you would get an error in the event logs.

To check the Lync Event Logs:

I was seeing these errors in the event log:

Lync Server, Event 14352, LS Protocol Stack

Error: 0xC3E93C0A (SIP_E_STACK_TRANSPORT_FAILED)

AND

Lync Server, Event 14336, LS Protocol Stack

Transport TLS has failed to start on local IP address 4.4.4.4 at port 5061 (4.4.4.4 would be my Public IP address)

At first, the public IP was correct but the event log said LOCAL IP.

I checked Topology Viewer and everything looked ok. Under Edge Server, it said the FQDN of my account, say, access.ittech4life.com and then the public IP which was correct.

I double checked another installation and realized that the public IP should NOT be listed but the DMZ IP address of that object. I changed in topology viewer and rebooted the Edge Server. Those errors went away but now I had a new error:

Lync Server, Event 22037, LS A/V Edge Server

Cause: An IP address and/or listening ports may be configured incorrectly.

I looked again at topology viewer but this time everything was correct. I also checked the NIC card configuration and found my issue. My subnet was 192.168.110.x but one of the IPs was mistakenly put in for 192.168.100.x. I changed to the correct subnet, rebooted again and all my issues were solved.

Just goes to show you that double checking the initial configuration can save you a lot of work later on.

{ 0 comments }