locked
Office Web Apps 2013 - Sorry, there was a problem and we can’t open this document. If this happens again, try opening the document in Microsoft Word RRS feed

  • Question

  • Hello

    I had configured Office Web Apps for SharePoint 2013 which was working fine for about 2 months until this morning.

    The error message I get for WORD, PDF and Excel files is:

    The ULS logs on the WFE give me this:

    ----------------------------------------------------------------------------

    WOPI (CheckFile) Proof Data: AccessToken Hash '1572676699' [1054 bytes], URL
    01/08/2014 11:01:58.01*    w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation             WOPI                              afk59    Monitorable   

    WOPI                              agxqc    Medium      WOPI Signature verification attempt failed with public key 01/08/2014

    11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation             WOPI                              agxqc    Medium      WOPI Signature verification attempt failed with public key

    01/08/2014 11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation             WOPI                              agxqb    Medium      WOPI Signature verification attempt failed - no public key    e75ead18-af27-4d44-ba50-b38b408011e8

    01/08/2014 11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation             WOPI                              ahdzz    Monitorable    WOPI Proof: All WOPI Signature verification attempts failed    e75ead18-af27-4d44-ba50-b38b408011e8

    01/08/2014 11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation             WOPI                              ag7pj    Unexpected    WOPI (CheckFile) - Invalid Proof Signature for file Letterhead Template.docx  url: http://site.contoso.com/_vti_bin/wopi.ashx/files/9c5d0d7077aa43e9a9538c02deb57580?access_token=eyJ0eXAiOiJKV1QiLCJhbGciOi

    ----------------------------------------------------------------------------------------

    The ULS Logs on my Office Web Apps server gives me this:

    --------------------------------------------------------------------------------------------------------

    Error message from host: Verifying signature failed, host correlation:     d197d187-ef9d-42f6-ae4f-c4b8199c1078

    WOPICheckFile,WACSERVER FileNotFound

    WOPI CheckFile: Catch-All Failure [exception:Microsoft.Office.Web.Common.EnvironmentAdapters.FileUnknownException: WOPI 404

    --------------------------------------------------------------------------------------

    Any idea what may have caused this issue all of a sudden?

    Thank you.

    Yoshi





    Wednesday, January 8, 2014 1:20 AM

Answers

  • Update **

    I ran the Update-SPWOPIProofKey command on my the SharePoint WFE and Application Server without success. In fact it threw an error stating it was unable to update the keys for all servers or for the OWA server mentioned in the command.

    So, I solved the problem by disconnecting the SharePoint Farm from Office Web Apps using the command 'Remove-SPWOPIBinding –All:$true'

    I then reconnected the Farm to OWA by running the command New-SPWOPIBinding -ServerName <WacServerName> -AllowHTTP.

    I then checked to make sure that the WOPIZone was set to 'external-https', if it wasn't I ran this command Set-SPWOPIZone –zone “external-https”.

    Once this was done, Office Web Apps started working internally but not on the Internet. I found that TMG had dropped the IP Address for the OWA server and the SSL Certificate wasn't selected. This can happen if TMG was rebooted. The solution was to change the IP Address to persistent, a reboot of the TMG server necessary to complete this fix.

    Thanks for your suggestions, and I hope this helps someone else out with a similar issue.

    Yoshi

    Wednesday, January 8, 2014 11:22 PM

All replies

  • try steps from the below post and check if issue fixed or not?

    http://social.technet.microsoft.com/Forums/sharepoint/en-US/572398c2-1975-44de-9267-caefbc1d6f3e/sharepoint-2013-office-web-app-error-unable-to-open-document

    also check the issue # 3 from this blog:

    http://blogs.msdn.com/b/fabdulwahab/archive/2013/10/30/office-web-apps-with-sharepoint-2013-issues.aspx


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Wednesday, January 8, 2014 2:21 AM
  • Hi Waqas

    Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.

    Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.

    Issue #3 in the above blog link does not reflect the same error I see on my servers.

    I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth

    Problem: You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps.

    If you added domains to the Allow List by using the New-OfficeWebAppsHost cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run the Get-OfficeWebAppsHost cmdlet. To add a domain to the Allow List, use the New-OfficeWebAppsHost cmdlet.

    I have not added any domains to the Allow list so this did not help either. Should I add the domain?

    Any further help with this is much appreciated.

    Thanks again.

    Yoshi



    Wednesday, January 8, 2014 2:55 AM
  • all user are getting the same error? only intranet zone or internet zone as well getting the same error?

    a universal thing, try to add owa url into trusted zone.

    can you reset IIS on the OWA server?


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Wednesday, January 8, 2014 3:14 AM
  • Yes, all staff get the same error and this occurs on the Intranet and Internet.

    I've added both OWA urls to the trusted zone with IISReset and still same error.

    The thing is OWA was working fine until yesterday without any changes.

    Yoshi

    Wednesday, January 8, 2014 3:36 AM
  • check this solution:

    http://social.technet.microsoft.com/Forums/windowsserver/en-US/ddbc7654-73dc-46c9-92c1-c272812760cc/office-webapps-invalid-host-exception


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Wednesday, January 8, 2014 3:49 AM
  • Thanks Waqas, I tired this earlier today without much luck.

    The last thing I am going to do is run this command:

    Update-SPWOPIProofKey

    I'm not sure what else I can do but OWA is very important and I need to get this resolved.

    Yoshi


    Wednesday, January 8, 2014 3:51 AM
  • Public key is the problem, for some reason WOPI cannot resolve the urls.

    another helpful blog, this time may work for you. Most of times the above mentioned post fix the problems.

    http://www.allthingssharepoint.nl/Blog/Bericht/8/SharePoint-2013-Office-Web-Apps-Problem---Unable-to-Preview-or-Open-documents


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Wednesday, January 8, 2014 3:56 AM
  • Thanks Waqas.

    I will run the command to update the key and get back to you.

    I tried adding the URL to the host file but still no success.

    Yoshi

    • Proposed as answer by Peter Kerling Tuesday, October 7, 2014 10:10 AM
    • Unproposed as answer by Peter Kerling Tuesday, October 7, 2014 10:10 AM
    Wednesday, January 8, 2014 4:10 AM
  • Update **

    I ran the Update-SPWOPIProofKey command on my the SharePoint WFE and Application Server without success. In fact it threw an error stating it was unable to update the keys for all servers or for the OWA server mentioned in the command.

    So, I solved the problem by disconnecting the SharePoint Farm from Office Web Apps using the command 'Remove-SPWOPIBinding –All:$true'

    I then reconnected the Farm to OWA by running the command New-SPWOPIBinding -ServerName <WacServerName> -AllowHTTP.

    I then checked to make sure that the WOPIZone was set to 'external-https', if it wasn't I ran this command Set-SPWOPIZone –zone “external-https”.

    Once this was done, Office Web Apps started working internally but not on the Internet. I found that TMG had dropped the IP Address for the OWA server and the SSL Certificate wasn't selected. This can happen if TMG was rebooted. The solution was to change the IP Address to persistent, a reboot of the TMG server necessary to complete this fix.

    Thanks for your suggestions, and I hope this helps someone else out with a similar issue.

    Yoshi

    Wednesday, January 8, 2014 11:22 PM
  • Has anyone an idea why this problem occurs?
    I did NO change in any configuration or certificate...

    Will open a MS Call to clarify!

    I did the same steps of SharePointYoshi to resolve it:

    Remove-SPWOPIBinding -All
    New-SPWOPIBinding -ServerName office.online.server.domain -Verbose -AllowHTTP

    BR Daniel

    Friday, May 25, 2018 9:17 AM
  • Thanks Yoshi. 

    Rajesh

    Wednesday, November 20, 2019 7:14 AM