The data connection user could not be delegated
APPLIES TO: SQL Server Analysis Services Azure Analysis Services
For Excel workbooks that contain Power Pivot data, Excel Services returns this error if it cannot connect to a Power Pivot server instance in SharePoint.
|Applies to||Power Pivot for SharePoint|
|Product Version||SQL Server 2008 R2, SQL Server 2012 (11.x), SQL Server 2014 (12.x)|
|Cause||Connection failed when attempting to use a Power Pivot data provider.|
|Message Text||The data connection uses Windows Authentication and user credentials could not be delegated. The following connections failed to refresh: Power Pivot Data|
There are multiple causes for this error message. The common factor behind all of them is that Excel Services cannot get a valid Windows user identity from a claims token in SharePoint. In the case of Excel workbooks that contain Power Pivot data, this error occurs when any of the following conditions exist:
The Claims to Windows Token Service is not running. You can confirm the cause of this error by viewing the SharePoint log file. If the SharePoint logs include the message "The pipe endpoint 'net.pipe://localhost/s4u/022694f3-9fbd-422b-b4b2-312e25dae2a2' could not be found on your local machine", the Claims to Windows Token Service is not running. To start it, use Central Administration and then verify the service is running in the Services console application.
A domain controller is not available to validate the user identity. The Claims to Windows Token Service does not use cached credentials. It validates the user identity for each connection. You can confirm the cause of this error by viewing the SharePoint log file. If the SharePoint logs include the message "Failed to get WindowsIdentity from IClaimsIdentity", the user identity could not be authenticated.
The computers must be members of the same domain or in domains that have a two-way trust relationship.
You must use Windows domain user accounts. The accounts must have a Universal Principal Name (UPN).
The Excel Services service account must have Active Directory permissions to query the object.
Use the following instructions to check the status of the Claims to Windows Token Service.
For all other scenarios, check with your network administrator.
Enable Claims to Windows Token Service
In Central Administration, in System Settings, click Manage services on server.
Select Claims to Windows Token Service, and then click Start.
Verify the service is also running in the Services console:
In Administrative Tools, click Services.
Start the Claims to Windows Token Service if it is not running.