Tag Info

New answers tagged

1

My suspicions were correct: the mismatch between Get-SPWOPIZone and the WopiZone of the Get-SPWopiBinding seemed to cause the error - everything needed to be internal-http. I followed the article here to remove and then recreate the bindings and Word started working (funny that Excel and Visio worked before but Word didn't!): Resolution: Remove the link ...


0

How did you setup your web app farm? If you didn't use the FQDN that is why you can't connect over it. Also check the zone bindings when you bind to SharePoint and make sure you are pointing at the URL where you will access web app farm.


0

That link suluger included doesn't answer or really relate to the posted question. That was referencing using SharePoint 2010 with OWA 2013 which is different to running SharePoint 2013 sites in 2010 mode with OWA 2013. The difference is a bit subtle if you're not familiar with the terms and technology but it's huge in practical terms. SharePoint 2013 ...



Top 50 recent answers are included