I am working with SharePoint 2013 and Office Web Apps 2013. Microsoft decided to move this server / service away from a SharePoint integrated model to a dedicated server model., yah!
Issue: Unable to open Word, Excel, PowerPoint documents in Office Web Apps 2013. Documents spin on open, fail with “Server Busy” message or a message “Can’t Open the Word Document”. I can create new documents in Word, Excel and PowerPoint and edit OneNote documents.
The following were found in the WAC server logs (C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS) and Event Viewer > Applications and Services Logs > Microsoft Office Web Apps
HostingServiceWatchdog reported status for HostingService in category ‘CheckDiscoveryResponse’. Reported status: The Discovery request failed with an exception: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
BroadcastServicesWatchdog_Wfe reported status for BroadcastServices_Host in category ‘4’. Reported status: Contacting Present_2_0.asmx failed with an exception: Could not establish trust relationship for the SSL/TLS secure channel with authority ‘OWAServer.domain.int’.
ServerSession.ProcessWebException: A Web exception during ExecuteWebMethod has occurred for server: http://WINSHRPTOD1:809/ecs/ExcelService*.asmx, method: GetHealthScore, ex: System.Net.WebException: The remote server returned an error: (401) Unauthorized.
The error “The remote server returned an error: (401) Unauthorized” was specific to installation on a the non-system drive. Office Web Apps does not like to be installed on another drive, I had installed on E:\ and moved back to C:\.
Second, the TLS error, I utilized a wildcard certificate. The friendly name started with a “*”. Updated to just the domain, domain1.com. It should work, instead I requested a SAN certificate with the servername and Internal load balanced URL. Either certificate should work but I stuck with the SAN cert.
The WOPI keys that are created when SharePoint is connected to OWA server enable a trust between. If a change to OWA or SP is made after the initial configuration and connection, running the command “Update-SPWOPIProofKey” resolves this issue by updating the security keys and trust between environments.
- Update WOPI Key – Update-SPWOPIProofKey
If it doesn’t take, removing all bindings and adding again will also refresh the key.
- Remove – Remove-SPWOPIBindings -All:$True
- Add – New-SPWOPIBinding -ServerName owaURL.FQDN.com
Remember, Office web apps is a dummy service. Set it and forget it. Just make sure you set it right the first time.