I am having an issue with our Lync Web App. I am trying to host a meeting using the Lync 2010 desktop client. I would like for third parties outside of our domain to access the conference without requiring Lync 2010 client installed. I have sent an invitation to hotmail, gmail, and other email services. All of them (after allowing pop-ups) tell me that the "Microsoft Lync Web App failed to start. Contact the meeting organizer."

If I install the Lync Attendee, it seems to work. However, the Web App will not work. I have tried multiple computers and am using multiple browsers (IE11, FF30, Chrome 35).

The attendee is not very practical because when a meeting invite is sent, if you click it the system tries to open up the Web App and does not give you any prompt to install the attendee. I need the Web App to work for external employees, vendors, and other users outside of our domain and organization.

Any help would be greatly appreciated.

Thanks,

Adam

• Edited by hasnolimits Tuesday, June 17, 2014 6:54 PM

Hello,

Thanks for the response. Both test computers are running Silver light 5.1.30214.0. I am using the 32bit browsers and am testing it in all three.

In Firefox, it actually asks me to activate the silver light, and when I click yes, it goes through an initializing process and once it hits 100%, displays the error mentioned above. Is this a particular setting that needs to be activated on the server? It seems like the system is set up with the right software/plugins.

**EDIT**

When I click the "Meeting Readiness" link, it says "Congratulations! You are ready to join meetings from your Web browser using Microsoft Communicator Web App."

It would appear I have everything installed.

Thanks again for the help.

Adam

• Edited by hasnolimits Wednesday, June 18, 2014 2:47 PM

I worked through this issue with our IT staff. This was because when the Lync Web App initializes, silver light tells the system to stop communicating on port 443 and to communicate on port 4443. Modern web browsers do NOT let this happen on the client-side.

Our server team had to force the server to make this port change instead of the client. Our Web App now opens as expected.

Thanks,

Adam

• Marked as answer by hasnolimits Thursday, June 19, 2014 10:46 PM