locked
Unable to discover LyncWebapp Server from Lync FE servers. RRS feed

  • Question

  • Hi All,

    My Lync 2013 Front End Servers are unable to discover the Lync WebApp server. Here are some key points. Need your help to resolve it.

    1. Able to browse the discovery URL from all FE Servers. No certificate popup/error.

    2. Getting below event on FE servers which showing FE Servers as the Webapp server which I think is incorrect. It should point to Webapp FQDN. (Why INternal-Webapp-Edge showing up as FE FQDN)

    3. Port 8060 and 8061 is not getting telnet from FE to Webapp server.  (Is it really required ?)

    4. Have removed the Lync Webapp server from topology and added it again. Still no luck.

    Sunday, April 8, 2018 6:42 AM

Answers

  • Apologies for the late reply, We have fixed this issue by building this server from Scratch. Also as a pre-requisite below components were installed:

    • Make sure Windows patching is up-to-date
    • Install Microsoft Visual C++ Redistributable for Visual Studio 2015.
    • Microsoft Identity Extensions
    • Imported a SSL certificate instead of Internal CA certificate.

    Now we are able to discover the WAC server.

    • Marked as answer by Vivek_Vardhan Wednesday, May 30, 2018 8:17 AM
    Wednesday, May 30, 2018 8:17 AM

All replies

  • Hi Vivek_Vardhan ,

    Do you find event log 31042 or 41032 ,41033 on your FE Server

    Which location that your Office Web Apps Server located ?Internal or external ? Please open the Topology Builder ,choice the “Web apps servers” in share components ,click the Office web apps server like the following screenshot.

    Port 8060 and 8061 need to be opened.

    https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/network-requirements/ports-and-protocols


    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, April 9, 2018 3:00 AM
  • 1. No Recent Eventlogs for 31042 or 41032 ,41033 on your FE Server found. These events were only present on/before the WAC server Installation. Also WAC server is internal.

    2. The WAC server was earlier a part of EDGE pool which we later on converted to WAC server. (Is this a problem)

    3. Have requested to the port opening request with Network team.  (Will update when its open).

    4. Why the Webapp server discovered by the FE servers is the FE servers only when I can browse the discovery URL.

    Monday, April 9, 2018 6:13 AM
  • 2. The WAC server was earlier a part of EDGE pool which we later on converted to WAC server. (Is this a problem)

    After you remove this server from the Edge pool ,I suggest you publish the topology and rebuilt this server's OS,in the end ,you could deploy the WAC server.

    Before you share PPT, you should upload your PPT  to FE server ,then FE server Encrypts and saves the Ppt file on to file share.if you finished the above steps ,then you will access the WAC Discovery URL.

     

    There are Workflow from client to server ,you could refer to it.

     

    1.When Lync 2013 user initiates or try to view Ppt presentation, Lync client uploads the PPT file to Lync front end server.

     

    2.Lync 2013 Front end Server Encrypts and saves the Ppt file on to the Content file store (Lync file share) and generates File ID and Access Token for the Ppt file uploaded.

     

    3.Lync Access server then retrieves WAC URL (stored in CMS during WAC Discovery process) and forms an URL that includes, WAC Presentation URL, File ID and Access Token of the Ppt File.

     

    4.Lync Access Server sends this WAC URL formed to Presenter as well as attendees.

     

    5.Lync Presenter/Attendee’s Client sends requests to this URL and contacts office web app server to get the PowerPoint presentation.

     

    6.Once Office Web App Server receives this request it retrieves the Access Token, File ID and File location (file share) and access the Ppt file by contacting the Lync Content File store via Lync Front end Servers (Lync Web Services FQDN will also be present in the initial Request).

     

    7.Office Web App server makes a temporary copy of Ppt file and creates html (dochtml) file and sends it to the Presenter/Attendee’s Client for Ppt presentation rendering.


    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, April 9, 2018 10:11 AM
  • Hi,

     

    Are there any update for this issue, if the reply is helpful to you, please try to mark it as an answer, it will help others who has similar issue.


    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, April 10, 2018 5:09 AM
  • These servers are on the same network. I have removed this server from Topology and published it. Added the WAC server again and published again. No luck anyways. Now I will be doing the below steps :

    1. Remove WAC from Topology

    2. Publish Topology.

    3. Rebuild the server from Scratch.

    4. Add in the topology again.

    Wednesday, April 11, 2018 10:20 AM
  • Hi Vivek_Vardhan ,

    When you rebuild the server from Scratch ,do you still get the  event ID 41030?


    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    Thursday, April 12, 2018 1:25 AM
  • Hi,

     

    Are there any update for this issue, if the reply is helpful to you, please try to mark it as an answer, it will help others who has similar issue.


    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, April 18, 2018 10:57 AM
  • Apologies for the late reply, We have fixed this issue by building this server from Scratch. Also as a pre-requisite below components were installed:

    • Make sure Windows patching is up-to-date
    • Install Microsoft Visual C++ Redistributable for Visual Studio 2015.
    • Microsoft Identity Extensions
    • Imported a SSL certificate instead of Internal CA certificate.

    Now we are able to discover the WAC server.

    • Marked as answer by Vivek_Vardhan Wednesday, May 30, 2018 8:17 AM
    Wednesday, May 30, 2018 8:17 AM