WOPI discovery synchronization job continuously failing in SharePoint 2016

Question

Hi Team,

Today, we encountered an issue with Office Apps; none of the files are loading. From the ULS logs, we can see the error "Invalid Proof Signature." We then checked the Failed Jobs in Central Admin and found that the WOPI discovery synchronization job is continuously failing.

Part of the troubleshooting process:

1. We cleared the SharePoint Config cache, but the WOPI discovery synchronization job continues to fail.
2. We attempted to use the Update-SPWOPIProofKey cmdlet to update the public key used to connect to the WOPI application but received the following error-

PS C:\Users###> Update-SPWOPIProofKey -ServerName $$$

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

   •    
            + CategoryInfo          : InvalidOperation: (Microsoft.Share...ateWOPIProofKey:SPCmdletUpdateWOPIProofKey) [Update-SPWOPIProofKey], SPCmdletException
        
            + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletUpdateWOPIProofKey
        
     

Please provide us the solution.

WOPI discovery synchronization job failing.png

Excel error.png

word error.png

Job History.png

Answer 1

Hi @Ava Tomlinson,

I'm glad to hear you solve the problem, if you have any issue about SharePoint, you are welcome to raise a ticket in this forum.

I would make a brief summary of this thread:

Issue Symptom:

Encountered an issue with Office Apps; none of the files are loading. From the ULS logs, can see the error "Invalid Proof Signature." Checked the Failed Jobs in Central Admin and found that the WOPI discovery synchronization job is continuously failing.

Current status:

The issue has been resolved. Have multiple OOS servers, kept one server in the load balancer pool at a time and performed the following two steps. Disabled the first OOS from the LB pool, enabled the second OOS, and rebuild the binding using PowerShell command as below:

1. Update-SPWOPIProofKey
2. Remove-SPWOPIBinding –All:$true followed by New-SPWOPIBinding -ServerName <ServerName> -AllowHTTP

You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!

---

Answer 2

Hi @Ava Tomlinson,

Thank you for posting in this community.

Please clear the configuration cache on all servers and perform an IISRESET, check if it fixes the issue.

1. Stop the timer service.
2. Delete all the XML files in the config cache. There are loads of XML files that can be found in the folder “%SystemDrive%\ProgramData\Microsoft\SharePoint\Config. Do not delete the folder and Cache.ini file.
3. Back up the Cache.ini file. Edit the “cache.ini” file, set the content to 1. This indicates that all cache settings need to be refreshed. Eventually this value gets automatically updated to another number when the cache is repopulated.
4. Start the timer service.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

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.

Answer 3

The issue has been resolved. We have multiple OOS servers, so we kept one server in the load balancer pool at a time and performed the following two steps. Then, we disabled the first OOS from the LB pool, enabled the second OOS, and performed the same steps:

1. Update-SPWOPIProofKey
2. Remove-SPWOPIBinding –All:$true followed by New-SPWOPIBinding -ServerName <ServerName> -AllowHTTP