Skip to main content

Unable to start Lync Server access edge service.


Unable to start Lync Server access edge service.

Recently I came across issue, were customer was unable to start Lync Server Access Edge service on any of their edge server. Recently they had Power Shutdown and all servers went down, all Front End services started however  Lync access edge service not starting.

After power come up none of edge server access edge service starts.

I was thinking it may be because certificate expired or SQL service not started however certificate was valid with SAN names and it was properly installed and assigned as well. Also, all dependent services were running however still access edge service was not starting.


When I tried to start access edge service again and it failed as expect but it generates error events in event viewer. Event log show two error event (Event Viewer > Applications and Service log > Lync) on Lync edge server.

Event 14497, LS Protocol Stack and Event 14517, LS Protocol Stack.



Event log 14517, shows error that tells, the server configuration validation mechanism detected some serious problems.

 

With ERRORS: The server at FQDN [sipfed.online.lync.com] is configured as both type 'allowed partner server' and type 'IM service provider'.

 

This explain that there is configuration issue and that is causing the server might not behave as expected to start services.

 

When I review allowed domain and provider configuration under external access.

SIP Federated domain shows allowed domain as “abc.com” and Edge server as “sipfed.online.lync.com” however, “sipfed.online.lync.com” is already added under SIP Federated Providers. This configuration conflicts hence Lync Server Access Edge service was not starting.

 

Review and correct the errors listed above, then restart the service. You may also wish to review any warnings present.

First, I have deleted allowed domain which has “sipfed.online.lync.com” and waited for replication to happen. This will resolves error shows in event log.


Then you can verify event log on edge server to see event id 3013, like below.


Once you see this event (3013) means changes got replicated and you will be able to start Lync Server Access Edge service. I could start Lync Server Access Edge service on all affected edge Servers after deleting affected allowed domain.

You can add your federated domain without edge server (sipfed.online.lync.com) to work federation and not affecting your edge services.
Thank you.

Comments

Popular posts from this blog

Outlook Add-in for Skype meeting getting disable after restarting Outlook.

Issue: Outlook Add-in for Lync meeting getting disable after restarting Outlook.
Problem Statement: Outlook Add-ins gets install automatically when Office 2013 installs (Lync and Skype for Business clients are part of Office package). Add-ins name is Lync Meeting Scheduling Outlook Addin or Skype meeting Add-in for Microsoft Office 2013. Sometime if other add-ins conflict with Outlook add-ins then outlook add-in keep getting disabled. And user has to enable it manually after Outlook restarts. 
Resolution: By default Lync Meeting Scheduling Outlook Addin or Skype Meeting Add-in for Microsoft Office 2013 installs wit load behavior "Load at Startup". However due to some conflict users Lync or Skype add-ins load behavior get changed to loaded instead of "Load at Startup" had to re-enable Lync Meeting Add-In in each time Outlook 2013 was started as it was not set to "Load at Startup". Look at the below screenshot. Now question is how we can change load behavior …

Unable to share desktop in Skype for Business?

Unable to share desktop in Skype for Business?
You can show your entire desktop or just a program to everyone in a Skype for Business Meeting, call, or instant messaging (IM) conversation. However sometime this feature does not work and give different errors.  Error message: ·Cannot start Desktop/Application Sharing due to network issues. ·An error occurred during the screen presentation. Resolution: There are multiple thing which may affect application/desktop sharing. 1.Make sure application / desktop sharing enabled on Skype for Business / Lync Server. SfB /Lync Control Panel > Conferencing > Conferencing policy > select Global or create new policy and set enable ‘Enable application and desktop sharing’. Refer below image. 2.Make sure your Skype for Business (Lync) client is updated with latest cumulative updates. Download latest update Skype (Lync) client. 3.Update your Video and Display drivers. a.Go to Start > Control panel. b.Search for Device Manager, and then open it. c.Find V…

Unable to login to Skype for Business client?

Unable to login to Skype for Business client? In order to sign-in on Skype (Lync) you must have login credential provided to you from your organization. ·Sign-in address: bilag@orgname.com ·User name: orgname\bilag ·Password: ************
Note: Orgname.com is my SIP domain name. Here are the most common mistake people make while sign-in on Skype for Business (Lync).
1.If you have login credential however still unable to sign-in then make sure you are putting proper login credential. Below error shows when you are wrong entering your sign-in address:
2.If you are writing correct Sign-in address however getting DNS error then contact administrator/ Support team there may be a DNS resolution or configuration issue. Administrator need to verify the SfB (Lync) AutoDiscover DNS records. 3.Sometime users password may expired/ lockout: Make sure that you password is not expire and lockout. If yes then call to helpdesk and reset your password / unlock. 4.Make user to have updated Skype for Business cli…