Environment:

SharePoint 2013 SP1 (4 servers - web, SQL, App and Search)

Office Web Apps (1 server)

I used this walk through in conjunction with Microsoft docs to install SP1 on my Office Web Apps server and I can now access it through the internal URL in my browser both from my computer and from the SharePoint app server but when I try to re-bind it to SharePoint, I get an error:

New-SPWOPIBinding -ServerName "servername.domain"
WARNING: The server did not respond. Trying again (attempt 1 of 5).
WARNING: The server did not respond. Trying again (attempt 2 of 5).
WARNING: The server did not respond. Trying again (attempt 3 of 5).
WARNING: The server did not respond. Trying again (attempt 4 of 5).
WARNING: The server did not respond. Trying again (attempt 5 of 5).
New-SPWOPIBinding : Sorry, we have encountered an error and New-SPWOPIBinding has failed. If you are using a server configured with HTTP, you must include the -AllowHTTP parameter.
At line:1 char:1
+ New-SPWOPIBinding -ServerName "servername.domain"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Microsoft.Share...tNewWOPIBinding:SPCmdletNewWOPIBinding) [New-SPWOPIBinding], SPCmdletException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewWOPIBinding

I tried the local security policy fix from Mathias and it had no effect.

I can access the ".../hosting/discovery" page with no problem from the App server and I get the XML that I expect back. Maybe a permission issue??

Thanks!

Keith

Hi Keith,

As your description, you got an error when you bind OWA to SharePoint.

Please check the ULS log file to find more information about this issue. The path of the file is: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS.

I am wondering whether you used a  certificate for the Office Web Apps server. Please make sure the certificate match the FQDN of the OWA server.

There are some similar posts for your reference
https://social.technet.microsoft.com/Forums/office/en-US/cdc525ad-a4a7-494b-ad48-122c47eb908f/newspwopibinding-failing-with-the-server-did-not-respond?forum=sharepointadmin

https://social.technet.microsoft.com/Forums/office/en-US/2dacd157-d304-4f51-81ea-ded8784e73b4/newspwopibinding-throws-warning-the-server-did-not-respond?forum=sharepointgeneral

http://sharepoint.stackexchange.com/questions/117800/sharepoint-office-web-apps-server-error-on-new-spwopibinding-all

Thanks,

Wendy

We do use a certificate that's pretty broad (*.sitename.com) and it works fine in production. I'm upgrading the dev farm for testing where it does not work. I ended up rolling back to a snapshot before I made any changes and it looks like OWA is not working before I do anything so I'm going to reinstall first and get it working, then try the upgrade again.

Thanks.

So I ran a repair on QA to try and get OWA working there and that went fine but I still couldn't connect to the URL. I tried doing a New-OfficeWebAppsFarm and ended up with:

New-OfficeWebAppsFarm : The Office Web Apps service did not respond in a timely fashion.
At line:1 char:1
+ New-OfficeWebAppsFarm -InternalURL "https://qaowa.domain.com" -EditingEnable ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationTimeout: (:) [New-OfficeWebAppsFarm], TimeoutException
    + FullyQualifiedErrorId : ServiceControlTimeout.StartTimeout,Microsoft.Office.Web.Apps.Administration.NewFarmComma

I just want a working OWA install... I'll try removing it completely and reinstalling and see what that does.