SharePoint 2016 Excel Web Access Web Part Error “We couldn’t find the file you wanted”


We recently encountered an issue with the Excel Web Access Web Part we thought we needed to make the community aware of as the cause of the issue is not super evident.

Scenario:

You are attempting to render Excel workbooks in the Excel Web Access web part in SharePoint 2016 and are encountering the following error on page load: "We couldn't find the file you wanted".

You will notice that workbooks are rendering in the browser (view, edit and preview) are all working fine assuming there are no other issues.

ULS logging will not have anything helpful, but you may see errors similar to the following while SharePoint is attempting to engage the workbook:

04/18/2018 10:16:28.92 w3wp.exe (0x0000) 0x2D8C SharePoint Foundation WOPI ajrrk Medium ShouldProcessWopiTarget: WOPI is disabled and the request will be redirected to home url. 0000000-0000-0000-0000-000000000000
04/18/2018 10:16:28.92 w3wp.exe (0x0000) 0x2D8C SharePoint Foundation WOPI al0ix Medium GetWOPIRestrictedTargetUrl: Failed to get WOPI target. Error message: ' 0000000-0000-0000-0000-000000000000
04/18/2018 10:16:28.92 w3wp.exe (0x0000) 0x2D8C SharePoint Foundation General a5b15 Medium WacProxyHelper.ExecuteGetProxyUrl: Url was null or empty, throwing a path exception 0000000-0000-0000-0000-000000000000
04/18/2018 10:16:28.92 w3wp.exe (0x0000) 0x2D8C SharePoint Foundation General a5b16 Medium WacProxyHelper.GetExceptionForPathError: received an invalid path 'https://site/Documents/Excel Services Sample Workbook.xlsx', exception: ' 0000000-0000-0000-0000-000000000000

OOS ULS will have no messages related to this issue, because the request doesn't even make it to the server.

Cause:

The cause for this specific issue is due to missing or custom bindings for Office Online Server. Specifically, you are missing the "syndicate" binding. This binding is specific to all Excel extensions and allows them to be rendered in web parts. In a stock binding scenario, you would see this when you run get-spwopibinding:
Note that your "WopiZone" and "ServerName" may differ

Application : Excel
Extension : ODS
ProgId :
Action : syndicate
IsDefaultAction : False
ServerName : <SERVERNAME>
WopiZone : internal-https

Application : Excel
Extension : XLSB
ProgId :
Action : syndicate
IsDefaultAction : False
ServerName : <SERVERNAME>
WopiZone : internal-https

Application : Excel
Extension : XLSM
ProgId :
Action : syndicate
IsDefaultAction : False
ServerName : <SERVERNAME>
WopiZone : internal-https

Application : Excel
Extension : XLSX
ProgId :
Action : syndicate
IsDefaultAction : False
ServerName : <SERVERNAME>
WopiZone : internal-https

Application : Excel
Extension : ODS
ProgId :
Action : syndicate
IsDefaultAction : False
ServerName : <SERVERNAME>
WopiZone : external-https

Application : Excel
Extension : XLSB
ProgId :
Action : syndicate
IsDefaultAction : False
ServerName : <SERVERNAME>
WopiZone : external-https

Application : Excel
Extension : XLSM
ProgId :
Action : syndicate
IsDefaultAction : False
ServerName : <SERVERNAME>
WopiZone : external-https

Application : Excel
Extension : XLSX
ProgId :
Action : syndicate
IsDefaultAction : False
ServerName : <SERVERNAME>
WopiZone : external-https


Solution:

Add the "syndicate" action to your WOPI bindings by running the following from one of your SharePoint servers as a farm admin in an administrator enabled SharePoint PowerShell console:

new-spwopibinding -server oos2016ocsi -action syndicate

Note: This issue only affects the above mentioned products and may or may not be the only way to experience this specific error. At the time of this writing, we have only seen this happen in this specific scenario.


Comments (0)

Skip to main content