SharePoint 2013 office web app error "sorry there was a problem we cannot open this document

Desaraju Raghavender Rao 1 Reputation point
2020-09-11T12:37:23.527+00:00

Hi Team,

we have issue in SharePoint 2013 office web app while opening office document "sorry there was a problem we cannot open this document" .

We have updated TLS setting recently that went well . All of the sudden somebody updated the Adobe reader in one of the server , from there office documents failing to open in browser it throws above error .

I found these in ULS logs

WOPI Signature verification attempt failed with public key WOPI Proof: All WOPI Signature verification attempts failed WOPI (CheckFile) - Invalid Proof Signature for file SOP Responses.docx

after that i tried to update the proof key but its also giving error

**Update-SPWOPIProofKey : Update-SPWOPIProofKey failed to update proof keys for server ****. At line:1 char:1

  • Update-SPWOPIProofKey -ServerName "******"
  •     + CategoryInfo          : InvalidOperation: (Microsoft.Share...ateWOPIProo
   fKey:SPCmdletUpdateWOPIProofKey) [Update-SPWOPIProofKey], SPCmdletExceptio
  n
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletUpdateWO
   PIProofKey**

Please help as this is production environment and we have issue .

Thanks & Regards, Raghavender

Microsoft Office Online Server
Microsoft Office Online Server
Microsoft on-premises server product that runs Office Online. Previously known as Office Web Apps Server.
639 questions

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Trevor Seward 11,701 Reputation points
    2020-09-12T16:34:11.713+00:00

    Unless you have specific requirements, Adobe Reader shouldn't be installed on a SharePoint Server. SharePoint provides a native iFilter for PDFs, if that is the reason you installed it.

    Otherwise, can you remove the WOPI binding and readd it?

  2. Itch Sun-MSFT 2,556 Reputation points
    2020-09-14T02:42:55.307+00:00

    Hi @Desaraju Raghavender Rao

    Any progress on your troubleshooting?

    Please try removing the link between the Sp farm and WCA 

    PS> Remove-SPWOPIBinding –All:$true

    Then Connect SP to the WOPI farm 

    PS> $internalName = "wca.demo.dev"  
PS> $internalZone = "internal-https"  
PS> New-SPWOPIBinding -ServerName $internalName –AllowHTTP  
PS> Set-SPWopiZone -zone $internalZone

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  3. Raghu 1 Reputation point
    2020-09-26T17:38:17.943+00:00

    I am getting error after running this commanf New-SPWOPIBinding -ServerName
    Warning : The server did not respond

    0 comments
  4. Desaraju Raghavender Rao 1 Reputation point
    2020-09-28T16:17:57.137+00:00

    I am getting error after running this commanf New-SPWOPIBinding -ServerName
    Warning : The server did not respond28720-binding-error.png

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.