marrj
asked on
Lync/Office Web App Integration - Not Working
I have recently deployed a Lync 2013 FE and an edge server. Lync is working great, except when my users go to present a PowerPoint. Of course, this is driven by connectivity with an Office Web Apps server. I happen to have one already in production that serves my Sharepoint 2013 farm. I have defined it in the Lync topology, enabled all TCP/IP traffic between the FE and the WAP server, and have verified that i can successfully open the WAP discovery page from my Lync FE.
When my users go to open PowerPoints in Lync, they get the error mentioned in this post. http://www.ucguys.com/2013/04/office-web-apps-running-on-server-2012-cant-upload-powerpoint-from-lync-client.html
I don't see any event logs regarding WAP or Office connectivity. I've tried a reboot of both servers. All prerequisites, including .NET, are present. My Lync FE is running Server 2012 R2 and my WAP server is running Server 2012.
When my users go to open PowerPoints in Lync, they get the error mentioned in this post. http://www.ucguys.com/2013/04/office-web-apps-running-on-server-2012-cant-upload-powerpoint-from-lync-client.html
I don't see any event logs regarding WAP or Office connectivity. I've tried a reboot of both servers. All prerequisites, including .NET, are present. My Lync FE is running Server 2012 R2 and my WAP server is running Server 2012.
ASKER
I don't have a reverse proxy set up yet.
PowerPoint presenting is not working internally or externally.
I have not updated either web app or Lync. I will try to do that and get back with you.
PowerPoint presenting is not working internally or externally.
I have not updated either web app or Lync. I will try to do that and get back with you.
update the Lync Client and the Office Web App as that should make it resolve internally
just make sure you have certs etc setup to match you FQDN of the site.
I used split brain DNS to make the internal and external ones the same
just make sure you have certs etc setup to match you FQDN of the site.
I used split brain DNS to make the internal and external ones the same
ASKER
I've installed KB2850013 on my WAC server.
I've installed the KBs located here on my Lync FE.
http://support.microsoft.com/kb/2809243
I've restarted both servers and it still doesn't appear to be working. Is there a particular update or version that I need to try to achieve?
My certs on the Lync FE are generated from an internal Enterprise CA within my single domain. My cert on my WAC site is a 3rd party wildcard that is trusted publicly.
I've installed the KBs located here on my Lync FE.
http://support.microsoft.com/kb/2809243
I've restarted both servers and it still doesn't appear to be working. Is there a particular update or version that I need to try to achieve?
My certs on the Lync FE are generated from an internal Enterprise CA within my single domain. My cert on my WAC site is a 3rd party wildcard that is trusted publicly.
Have you done this update?
http://y0av.wordpress.com/2013/10/23/wacon8_1/
after that test the web app through web browser and make sure that you can get to it i.e trusted sites etc
http://y0av.wordpress.com/2013/10/23/wacon8_1/
after that test the web app through web browser and make sure that you can get to it i.e trusted sites etc
ASKER
Yes, I do have that update and can get to the site.
ok so down to lync logging
under the user profile you are signed on with clear out this path (make sure you exit lync)
c:\users\%username%\%appda ta%\local\ microsoft\ office\lyn c\tracing
then log into lync and try and share some content i.e. powerpoint
then go back to that folder and using the Lync Logging tool open the trace file and we might be able to see the error
under the user profile you are signed on with clear out this path (make sure you exit lync)
c:\users\%username%\%appda
then log into lync and try and share some content i.e. powerpoint
then go back to that folder and using the Lync Logging tool open the trace file and we might be able to see the error
ASKER
Ok, I have done what you said up to the point where I'm trying to find out what file to examine. The Lync 2013 Logging Tool didn't have any option to open a file to examine. The Snooper application, however, did. I opened the Lync-UccApi-0.UccApiLog file in the Snooper and am having trouble interpreting its contents. Am I in the right place?
yeap thats the right place - sorry should have said snooper i just think of it as one sutie.
if you note the time you start the powerpoint upload and then look to the messages part of the trace for that time.
I am trying to remember if i ran a network monitor at the same time to find the error message. That might be worth doing
can you run through and double check the health of the WAC install
run this powershell on the WAC servers
(Get-OfficeWebAppsFarm).Ma chines
i ran through this blog article
http://www.wictorwilen.se/office-web-apps-server-2013---machines-are-always-reported-as-unhealthy
if you note the time you start the powerpoint upload and then look to the messages part of the trace for that time.
I am trying to remember if i ran a network monitor at the same time to find the error message. That might be worth doing
can you run through and double check the health of the WAC install
run this powershell on the WAC servers
(Get-OfficeWebAppsFarm).Ma
i ran through this blog article
http://www.wictorwilen.se/office-web-apps-server-2013---machines-are-always-reported-as-unhealthy
ASKER
Thanks for the article. My WAC was showing an unhealthy status and I didn't even know it. Turns out, I was suffering from the 404 error caused by a missing HTTP Activation feature for .NET 4.5. The server is now showing a healthy status. However, my PowerPoint presenting in Lync still isn't working.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No one was able to provide a solution.
is this not working internally or externally or both?
can you detail out the reverse proxy you have to get to it from the outside.
do you have all the updates for lync and the web app server as i did have the same problem and i think those updates fixed it