Sorry,we can't open this document because there was a problem talking to the service - Office Web Apps 2013

Farm Information:
  1. Web Application published internally and externally (so make sure both URLs added to Alternate Access Mapping)
  2. Office Web Apps 2013 (Published externally via TMG 2010 and internally)
I have a farm which connected to Office Web Apps 2013 and It's working fine internally so then we decided to enable it to open Office Web Apps externally by the following steps :
1- In Office Web Apps Server , Open Power Shell and run this command to add the External URL to existing Farm:
Set-OfficeWebAppsFarm -ExternalURL http://test.com/ 
OfficeWebApp2013
2-In SharePoint Server , Open SharePoint 2013 Management Shell and run the following commands: 
Remove-SPWOPIBinding –All:$true
New-SPWOPIBinding -ServerName OfficeWebAppServer.com -AllowHTTP
Set-SPWopiZone internal-http
$c = Get-SPSecurityTokenServiceConfig
$c.AllowOAuthOverHttp = $true
$c.Update()
 then when I tried to access the Office documents from External URL I got the following error :
"Sorry,we can't open this document because there was a problem talking to the service"
OfficeWebApp2013_1
This issue related to TMG publishing rule so to fix it :
1- Open TMG Management Console
2- Go to Publish rule for Office Web Apps
3- Right click on the rule and choose Configure HTTP
4- Uncheck  Verify Normalization
5- Click ok
6- Click Apply
7- Wait the sync process 
OfficeWebApp2013_2
Ref:

Comments

Post a Comment

Popular posts from this blog

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

"Sorry, Word Web App can't open this ... document because the service is busy." Office WebApp

Problem: Intermitten requests are not returning the pdf/word documents.  Most requests are working and occasionally 1 request doesn't work.  Every 4th request tries to get the pdf to display on Office Web Apps for a few minutes without any error message and then stops trying and displays the message "Sorry, Word Web App can't open this ... document because the service is busy." Initial Hypothesis: Originally I thought it was only happening to pdfs but it is happening to word and pdf documents (I don't have excel docs in my system).  My monitoring software SolarWinds is badly configured on my OWA servers as the monitor is showing green, drining into the servers monitoring the 2 application monitors are failing.  The server should go amber if either of the 2 applications fail and in turn red after 5 minutes.  At this point I notice that I can't log onto my 4 OWA/WCA server.  Web request are not being returned.  I look at my KEMP load balancer and it says al
Continue Read

Unable to create a "Send to Connection"- verification failed -url is a not a valid routing destination

ISSUE : Unable to successfully create a send to connection. When creating the Send to connection from Sharepoint 2010 Central Administration and click on Test URL for the Destination URL , we get the following error "verification failed -url is a not a valid routing destination" we see the following entry in the ULS logs Url validation failed for http://gmallya.test.com/sites/testrecordcenter/_vti_bin/OfficialFile.asmx   during Record and document center connection configuration with exception The request failed with HTTP status 401: Unauthorized .:  at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)     at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)     at Microsoft.SharePoint.OfficialFileSoap.GetServerInfo()     at Microsoft.SharePoint.ApplicationPages.OfficialFileAdminPage.<>c__DisplayClass2.&l
Continue Read