Lync Edge Server Service Not Starting

i am having an issue with starting the "Lync Server Audio/Video Edge" service on my lync edge server. when i try to start the service it throws the following error..

"The Lync server audio/video edge service on local computer started and than stopped. some services stop automatically if they are not in use by other services or programs."

than in the event viewer logs there are 2 specific errors i can see that look like the following..

what is stopping me from fixing this right away is that i havent changed anything in my configuration, seems to have broke on its own. i can post more errors i have found in other places as well if needed. any help is greatly appreciated


  • Edited by Ross Kotter Wednesday, March 07, 2012 3:50 PM edit
March 7th, 2012 3:36pm

Hi.

Make sure that the server has the ip addresses that are listed in the topology configuration. Double check this in your topology builder.

And that no new services are listening on port 443. Try a telnet and see if something answers now when the Lync services are stoped.




Free Windows Admin Tool Kit Click here and download it now
March 7th, 2012 4:07pm

In your Lync Topology, under edge Pool, do you have the IP address 192.100.100.84 set correctly for AV Edge. this IP address should be present on the NIC on the edge server. if it is missing then the AV edge service will not start.
March 7th, 2012 4:11pm

thx for the response v-i-s-a.. my edge server has 2 ip address's assigned to it, 192.100.100.84 and 192.100.100.85, so the one in the topology builder is in fact correct
Free Windows Admin Tool Kit Click here and download it now
March 7th, 2012 4:17pm

hey tommy, thanks for the response. my IP address's are correct in line with my toplogy. however, i cant telnet into the edge server on port 443, when i try telnet  in it makes the attempt for a while until eventually i get the "connection to host lost" message, which tells me there is no response from my edge server on port 443.

when i check which ports my edge server is listening on using the netstat command i can see it has a listing of 0.0.0.0:443 LISTENING, if im correct that means its listening on all interfaces for port 443?

March 7th, 2012 4:33pm

so which one is the internal IP of the edge and which one is external?

Can you paste the screenshot of the edge topology?

Free Windows Admin Tool Kit Click here and download it now
March 7th, 2012 4:40pm

sure, here is a screenshot of my edge topology..  let me add that i am deploying lync with NO reverse proxy, and my environment was up and running for months before this happened, im not really what/if any changes i would have made effected this..



  • Edited by Ross Kotter Wednesday, March 07, 2012 4:55 PM
March 7th, 2012 4:53pm

Telnet will not work until the AV service is up and running.

looking at the screenshot the configuration seems correct.

please export the configuration from the lync front end server and import it on the edge server and run step 2 from the deployment wizard. and then try to start the service.

Free Windows Admin Tool Kit Click here and download it now
March 7th, 2012 5:06pm

when you say export the configuration.. are you referring to just replicating the central management store to the edge server? if so i have performed this step yesterday, and have re-ran step 2 in the deployment wizard as well.. also, if this helps.. here is an error i am seeing on my FE server that looks like its related..


  • Edited by Ross Kotter Wednesday, March 07, 2012 5:13 PM
March 7th, 2012 5:12pm

Hi,

Just some suggest to this problem, hope it can help you:

1, You can have a try to use a subnet which is different with Internal interface to external interface(as 192.100.200.85).

2, Maybe the 443 port is used by other application. You can check if the IIS website uses the 443 port in edge server.

Free Windows Admin Tool Kit Click here and download it now
March 8th, 2012 7:48am

hey sean, thanks for your response. all things point to something else using port 443 right now.. however from what i can see from a netstat command it doesnt look like anything new is running on it. here is a copy/paste of my most recent netstat command..

Active Connections

  Proto  Local Address          Foreign Address        State           PID
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       756
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING       4
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       2804
  TCP    0.0.0.0:4443           0.0.0.0:0              LISTENING       4
  TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING       4
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       468
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       844
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       896
  TCP    0.0.0.0:49338          0.0.0.0:0              LISTENING       1400
  TCP    0.0.0.0:56483          0.0.0.0:0              LISTENING       572
  TCP    0.0.0.0:56966          0.0.0.0:0              LISTENING       564
  TCP    0.0.0.0:56967          0.0.0.0:0              LISTENING       2824
  TCP    192.100.100.84:139     0.0.0.0:0              LISTENING       4
  TCP    192.100.100.84:444     0.0.0.0:0              LISTENING       1768
  TCP    192.100.100.84:5061    0.0.0.0:0              LISTENING       1908
  TCP    192.100.100.84:5061    68.34.170.246:52296    CLOSE_WAIT      1908
  TCP    192.100.100.84:5061    68.34.170.246:52297    CLOSE_WAIT      1908
  TCP    192.100.100.84:5061    68.34.170.246:53570    CLOSE_WAIT      1908
  TCP    192.100.100.85:5061    0.0.0.0:0              LISTENING       1908
  TCP    192.100.100.85:5062    0.0.0.0:0              LISTENING       1844
  TCP    192.100.100.85:5062    192.100.100.83:53701   ESTABLISHED     1844
  TCP    192.100.100.85:5062    192.100.100.83:53967   ESTABLISHED     1844
  TCP    192.100.100.85:8057    0.0.0.0:0              LISTENING       1768
  TCP    192.100.100.85:8057    192.100.100.83:56612   ESTABLISHED     1768
  TCP    192.100.100.85:8057    192.100.100.83:56617   ESTABLISHED     1768
  TCP    192.100.100.85:8057    192.100.100.83:56618   ESTABLISHED     1768
  TCP    192.100.100.85:8057    192.100.100.83:56619   ESTABLISHED     1768
  TCP    192.100.100.85:8057    192.100.100.83:56620   ESTABLISHED     1768
  TCP    192.100.100.85:8057    192.100.100.83:56628   ESTABLISHED     1768
  TCP    192.100.100.85:8057    192.100.100.83:56629   ESTABLISHED     1768
  TCP    192.100.100.85:8057    192.100.100.83:56670   ESTABLISHED     1768
  TCP    192.100.100.85:57577   192.100.100.146:5357   TIME_WAIT       0
  TCP    192.100.100.85:57579   192.100.100.175:5357   TIME_WAIT       0
  TCP    192.100.100.85:57583   192.100.100.159:5357   TIME_WAIT       0
  TCP    192.100.100.85:57584   192.100.100.147:5357   TIME_WAIT       0
  TCP    192.100.100.85:57585   192.100.100.242:3911   TIME_WAIT       0
  TCP    [::]:80                [::]:0                 LISTENING       4
  TCP    [::]:135               [::]:0                 LISTENING       756
  TCP    [::]:443               [::]:0                 LISTENING       4
  TCP    [::]:445               [::]:0                 LISTENING       4
  TCP    [::]:3389              [::]:0                 LISTENING       2804
  TCP    [::]:4443              [::]:0                 LISTENING       4
  TCP    [::]:47001             [::]:0                 LISTENING       4
  TCP    [::]:49152             [::]:0                 LISTENING       468
  TCP    [::]:49153             [::]:0                 LISTENING       844
  TCP    [::]:49154             [::]:0                 LISTENING       896
  TCP    [::]:49338             [::]:0                 LISTENING       1400
  TCP    [::]:56483             [::]:0                 LISTENING       572
  TCP    [::]:56966             [::]:0                 LISTENING       564
  TCP    [::]:56967             [::]:0                 LISTENING       2824
  TCP    [2002:c064:6454::c064:6454]:4443  [2002:c064:6453::c064:6453]:54033  ESTABLISHED     4
  TCP    [2002:c064:6454::c064:6454]:57581  [2002:c064:64ab::c064:64ab]:445  ESTABLISHED     4
  TCP    [2002:c064:6454::c064:6454]:59957  [2002:c064:640c::c064:640c]:445  ESTABLISHED     4
  UDP    0.0.0.0:123            *:*                                    948
  UDP    0.0.0.0:500            *:*                                    896
  UDP    0.0.0.0:1434           *:*                                    1976
  UDP    0.0.0.0:4500           *:*                                    896
  UDP    0.0.0.0:5355           *:*                                    140
  UDP    127.0.0.1:51664        *:*                                    1172
  UDP    127.0.0.1:56155        *:*                                    2924
  UDP    127.0.0.1:59005        *:*                                    964
  UDP    127.0.0.1:62503        *:*                                    1680
  UDP    127.0.0.1:62786        *:*                                    572
  UDP    127.0.0.1:62788        *:*                                    140
  UDP    127.0.0.1:64531        *:*                                    896
  UDP    127.0.0.1:65160        *:*                                    1844
  UDP    192.100.100.84:137     *:*                                    4
  UDP    192.100.100.84:138     *:*                                    4
  UDP    [::]:123               *:*                                    948
  UDP    [::]:500               *:*                                    896
  UDP    [::]:1434              *:*                                    1976
  UDP    [::]:4500              *:*                                    896
  UDP    [::]:5355              *:*                                    140

March 8th, 2012 2:18pm

Hi,

It seems that Port 443 is used by 'SYSTEM'.

Free Windows Admin Tool Kit Click here and download it now
March 9th, 2012 1:11am

Hi,

It looks like the port 443 is seized by the System process. You need to try to grap the port with some way.

1, I recommend you use different subnet to external interface.

2, run netstat -b to check whether you can find which system application uses the port.

3, restart the edge server and check if the port is released by System process.

4, If still can not work, I think you can think about reinstalling the server OS.

March 9th, 2012 2:46am

here are the results from the netstat -b command...


Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    192.100.100.84:5061    c-68-34-170-246:52296  CLOSE_WAIT
 [RTCSrv.exe]
  TCP    192.100.100.84:5061    c-68-34-170-246:52297  CLOSE_WAIT
 [RTCSrv.exe]
  TCP    192.100.100.84:5061    c-68-34-170-246:53570  CLOSE_WAIT
 [RTCSrv.exe]
  TCP    192.100.100.85:5062    lync:64298             ESTABLISHED
 [MRASSvc.exe]
  TCP    192.100.100.85:8057    lync:56612             ESTABLISHED
 [DataProxy.exe]
  TCP    192.100.100.85:8057    lync:56617             ESTABLISHED
 [DataProxy.exe]
  TCP    192.100.100.85:8057    lync:56618             ESTABLISHED
 [DataProxy.exe]
  TCP    192.100.100.85:8057    lync:56619             ESTABLISHED
 [DataProxy.exe]
  TCP    192.100.100.85:8057    lync:56620             ESTABLISHED
 [DataProxy.exe]
  TCP    192.100.100.85:8057    lync:56628             ESTABLISHED
 [DataProxy.exe]
  TCP    192.100.100.85:8057    lync:56629             ESTABLISHED
 [DataProxy.exe]
  TCP    192.100.100.85:8057    lync:56670             ESTABLISHED
 [DataProxy.exe]
  TCP    [2002:c064:6454::c064:6454]:59957  [2002:c064:640c::c064:640c]:microsoft-ds  ESTABLISHED
 Can not obtain ownership information

Free Windows Admin Tool Kit Click here and download it now
March 9th, 2012 3:31am

in my IIS for my edge server i already have specified port 443 for the correct IP address, i thought that netstat was supposed to show port 443 being used by the system process if i had IIS set up that way?

March 9th, 2012 2:41pm

here is a screen shot of a process explorer trace on my edge server. it shows the system process having control of port 443 for TCPV6.. is this not normal?  in my IIS settings i have the correct IP address bound to port 443 but im not sure if this is normal behavior or not..

Free Windows Admin Tool Kit Click here and download it now
March 12th, 2012 1:49pm

i am also seeing the following error message on my lync server FE in the event logs...

March 12th, 2012 2:04pm

Hi,

Please try to disable the IPV6 in Local Area Connection Properties and check if the port is released. Like the following figure. uncheck the IPv6 option.

Free Windows Admin Tool Kit Click here and download it now
March 13th, 2012 2:32am

Disabling ipv6 will not work.

The issue is that the lync sip service is using 443

The correct sollution is this.

go to dos prompt.

open netsh

in the netsh screen type http add iplisten {external sip  ip address} and press enter.

port 443 will be freed the audio/video edge service will be able to start

after the audio/video edge service is started in the netsh screen  type http delete iplisten {external sip ip address}

Exit netsh

All lync services should now be started.

July 24th, 2013 8:03pm

obi ejiofor -

You rock this solved my issue

Free Windows Admin Tool Kit Click here and download it now
January 19th, 2015 7:22am

I had to run netsh http delete iplisten 127.0.0.1 to fix mine
June 29th, 2015 6:48am

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

Other recent topics Other recent topics