Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You cannot load an Excel 2007 workbook in Excel Web Access when a SharePoint Server 2007 Web site uses Basic authentication and when the trusted file location type is set to HTTP


View products that this article applies to.

Symptoms

Consider the following scenario. You have a Microsoft Office SharePoint Server 2007 Web site that is configured to use only Basic authentication. Additionally, you have an Excel Services trusted file location that has the location type set to HTTP. In this scenario, when you try to load an Excel 2007 workbook in Excel Web Access from the trusted file location, you receive the following error message:
The file you selected could not be found. Check the spelling of the file name and verify that the location is correct. Make sure that the file has not been renamed, moved, or deleted, that the file is in an Excel Services Trusted Location, and that you have access to the file. If the problem persists, contact your administrator.

↑ Back to the top


Cause

When an Excel Services trusted file location has a location type of HTTP, Excel Calculation Services (ECS) uses the WebDAV protocol to obtain the document. When only Basic authentication is enabled, ECS cannot access the document by using WebDAV. Therefore, you receive the error message that is mentioned in the "Symptoms" section.

↑ Back to the top


Status

This behavior is by design.

↑ Back to the top


More information

ECS uses one of the following three methods to obtain files that are in a trusted file location:
  • Microsoft Windows SharePoint Services
  • UNC
  • HTTP (WebDAV)
For UNC and HTTP, there are two ways that ECS can use credentials to access files. ECS can impersonate the end-user. Alternatively, ECS can use the ECS process account. If ECS impersonates the end-user, Kerberos is required because ECS delegates the user identity. If ECS uses the ECS process account, Kerberos is not required because ECS uses Windows authentication (NTLM) instead.

ECS does not support Basic authentication when it is used together with HTTP. ECS supports only Integrated authentication in this scenario. As previously mentioned, Kerberos may also be required in this scenario, depending on your configuration.

↑ Back to the top


Keywords: KB928742, kbprb, kbtshoot, kbexpertiseinter, kbexpertisebeginner, kberrmsg, kbarchive, kbnosurvey

↑ Back to the top

Article Info
Article ID : 928742
Revision : 4
Created on : 1/15/2015
Published on : 1/15/2015
Exists online : False
Views : 321