I have setup Exchange 2013, Lync 2013, SharePoint 2013, IIS as a Reverse Proxy Server, an Office Web Apps Server, etc, etc. Everything is setup to use SSl (https) and everything works great EXCEPT... Office Web Apps... and ONLY via Exchange and OWA (exchange browser-based access).
I can login via the intranet or Internet for everything (SharePoint, Outlook, and Lync) and Office Web apps functionality works flawlessly for all... except for Exchange and OWA.
If I login in to a web-based Exchange seeion, everything works right and I can see the various attachments.
For all other scenarios, Office Web Apps works (SharePoint, Outlook, Lync, etc), but in owa (web version of Outlook) I see that Office Web Apps is triggered (I see the Office Web Apps text and the dots that indicate something is loading)... However, it just crashes and eventually times out (see image):
If I look in the error logs for the Web Apps Server I see this:
Essentially, it looks like that owa uses a distinctly different path to load the attachments into the Web Apps Server such that the file is not found!
What is happening? Why does Exchange OWA (web version of Outlook) somehow use a different path that fails to locate attachments in Office Web Apps, but Lync, Outlook, and SharePoint (both in Intranet and Internet) work perfectly?
This is VERY frustrating. Can anyone help?
Please?
Clearly, the reverse proxy is working, the certificates are working, OAuth is working, etc. It seems there must be some variable/path that is only defined in Exchange for OWA that uses a different path for Office Web App attachments and that path is WRONG!
Please, help!
Thanks