Configuring Kerberos for Excel Services is a two step process; Information Gathering and Configuration.

Step 1: Information Gathering:

1. Account running "Excel Services Application Web Service Application": In this example: ECSSvc.

Central Administration > Security > Configure service accounts

2.  Account running "Claims to Windows Token Service":  In this example: Local System.

Central Administration > Security > Configure service accounts

3.  Account running the data source you are connecting to:

SQL:

Log on to the server running SQL > Start > Run > Services.msc and locate "SQL Server (MSSQLSERVER)", you will see the account in the "Log On As" column. In this example: SQLSvc.

Analysis Services:

Log on to the server running SSAS > Start > Run > Services.msc and locate "SQL Server Analysis Services (<Instance>)", you will see the account in the "Log On As".  In this example: SSASSvc.

Since the "Claims to Windows Token Service" is running as Local System, we need to record the names of the SharePoint Servers running "Excel Calculation Services".  In this example: PRIME13.

Recap:

1. Account running "Excel Services Application Web Service Application": ECSSvc
2. Account running "Claims to Windows Token Service": Local System
3. Account running "SQL Server (MSSQLSERVER)": SQLSvc
4. Account running "SQL Server Analysis Services (MSSQLSERVER)": SSASSvc
5. Name of the SharePoint Server running "Excel Calculation Services".  In this example: PRIME13.

Important Note:

If “Excel Services” is running on multiple SharePoint machines and the C2WTS is running as Local System, you will need to Constrain each SharePoint machine (Netbios Name) running “Excel Services” to the backend Service Account(s) (SQLSvc and/or SSASSvc).
If you are running the C2WTS as a domain account.  For example Contoso\C2WTSSvc, you will only need to Constrain that one account to the backend Service Account(s) (SQLSvc and/or SSASSvc).

Step 2: Configuration:

What we need to do now is add the correct Service Principal Name to the Service Accounts running SQL/SSAS and then use Kerberos Constrained Delegation.

Service Principal Names (SPNs):

Add these SPNs to the account running the data source your workbook is connecting to.  Either "SQL Server (MSSQLSERVER)" or "SQL Server Analysis Services (<Instance>)":

Account Running SQL Server (SQLSvc):

MSSQLSVC/<SQLServer_Name>
MSSQLSVC/<SQLServer_Name.FQDN

Example:

MSSQLSVC/SQLSvr
MSSQLSVC/SQLSvr.contoso.com

Account Running SQL Server Analysis Services (SSASSvc):

MSOLAPSvc.3/<SQL_Server_Analysis_Services_Server_Name>
MSOLAPSvc.3/<SQL_Server_Analysis_Services_Server_Name.FQDN>

Example:

MSOLAPSvc.3/SSASSvr
MSOLAPSvc.3/SSASSvr.contoso.com

Important Note:  If Analysis Services has a named instance other than ("MSSQLSERVER)" (this is the default Instance) you will need include that in the Service Principal Name.  In the below example, I will use the instance name "TABULAR".

MSOLAPSvc.3/<SQL_Server_Analysis_Services_Server_Name:Instance>
MSOLAPSvc.3/<SQL_Server_Analysis_Services_Server_Name.FQDN:Instance>

Example:

MSOLAPSvc.3/SSASSvr:TABULAR
MSOLAPSvc.3/SSASSvr.contoso.com:TABULAR

Important Note 2: If the Analysis Services Server has a Named Instance other than (MSSQLSERVER) (which is Default), like "TABULAR".  You will need to add MSOLAPDisco.3 SPNs to the account running the SQL Browser service (Example: Contoso\BrowserSvc). “Disco” is short for “Discovery”.  This needs to be set so the Browser Service can discover SSAS.

MSOLAPDisco.3/<SQL_Server_Analysis_Services_Server_Name>
MSOLAPDisco.3/<SQL_Server_Analysis_Services_Server_Name.FQDN>

Example:

MSOLAPDisco.3/SSASSvr
MSOLAPDisco.3/SSASSvr.contoso.com

Article: More Information regarding the MSOLAPDisco.3 SPNs can be found in the below article:

An SPN for the SQL Server Browser service is required when you establish a connection to a named instance of SQL Server Analysis Services or of SQL Server
http://support.microsoft.com/kb/950599

Kerberos Constrained Delegation (KCD):

Constrain Delegation between the account running "Excel Calculation Service" and "Claims to Windows Token Service" to "SQL Server" and SQL Server Analysis Services"

"Excel Services" to SQL:

In Active Directory Users and Computers > ECSSvc> Properties > Delegation Tab > Trust this computer for delegation to specified services only > Use any authentication protocol > Add… > Users or Computers… > SQLSvc> Check Names > OK > “Select All” Available Services > OK > OK.

"Excel Services" to "Analysis Services":

In Active Directory Users and Computers > ECSSvc> Properties > Delegation Tab > Trust this computer for delegation to specified services only > Use any authentication protocol > Add… > Users or Computers… > SSASSvc> Check Names > OK > “Select All” Available Services > OK > OK

"Claims to Windows Token Service" (if running as Local System): to SQL:

In Active Directory Users and Computers > PRIME13> Properties > Delegation Tab > Trust this computer for delegation to specified services only > Use any authentication protocol > Add… > Users or Computers… > SQLSvc> Check Names > OK > “Select All” Available Services > OK > OK.

"Claims to Windows Token Service" (if running as C2WTSSvc) to SQL:

In Active Directory Users and Computers > C2WTSSvc> Properties > Delegation Tab > Trust this computer for delegation to specified services only > Use any authentication protocol > Add… > Users or Computers… > SQLSvc> Check Names > OK > “Select All” Available Services > OK > OK.

"Claims to Windows Token Service" (if running as Local System) to "Analysis Services":

In Active Directory Users and Computers > PRIME13> Properties > Delegation Tab > Trust this computer for delegation to specified services only > Use any authentication protocol > Add… > Users or Computers… > SSASSvc> Check Names > OK > “Select All” Available Services > OK > OK

"Claims to Windows Token Service" (if running as C2WTSSvc) to SQL:

In Active Directory Users and Computers > C2WTSSvc> Properties > Delegation Tab > Trust this computer for delegation to specified services only > Use any authentication protocol > Add… > Users or Computers… > SSASSvc> Check Names > OK > “Select All” Available Services > OK > OK.

Please see my Visio Diagram.  It may take a few seconds to load since it is large.

If this fails please see our other blog:

Tools and Techniques: Troubleshooting Kerberos in Excel Services and PowerPivot for SharePoint
http://blogs.technet.com/b/excel_services__powerpivot_for_sharepoint_support_blog/archive/2013/02/08/troubleshooting-kerberos-for-excel-services-and-powerpivot.aspx

There appears to be an issue with SharePoint 2013 Excel Services when using IE 11 (11.0.9600.16438). 

As noted in the comments below, the issue is resolved by installing the October 2013 Cumulative Update for SharePoint 2013:

Description of the SharePoint Server 2013 cumulative update package (SharePoint server-package): October 26, 2013
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2825647

See this blog for detail of patch order for Sharepoint server:
http://blogs.technet.com/b/stefan_gossner/archive/2013/10/26/october-2013-cu-for-sharepoint-2013-has-been-released.aspx

Issue:

Basically what is happening is that when IE 11 is used with SharePoint 2013 Excel Services, the buttons across the top of the screen do not work (see screenshot.)  The areas outlined in RED do not work correctly.  Regular slicers do work as expected.

• Slicers/filters still work
• The buttons work if the workbook is being used in a Excel Web Part
• Office Web Apps Server 2013 (WAC) is not affected
• SharePoint 2010 is not affected

Microsoft is currently investigating the issue, but there is a temporary workaround for the issue.   The workaround for this issue at the moment is to set the emulation document mode in Internet Explorer 11 to something other than "Edge (Default)".

To apply the workaround: 

1. Open IE on the client experiencing the issue
2. Press F12 on the keyboard to bring up Developer Tools.
3. Click the emulation icon on the left side and choose anything but “Edge (Default)” for Document Mode

As noted in the comments below, the issue is resolved by installing the October 2013 Cumulative Update for SharePoint 2013:

Description of the SharePoint Server 2013 cumulative update package (SharePoint server-package): October 26, 2013
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2825647

See this blog for detail of patch order for Sharepoint server:
http://blogs.technet.com/b/stefan_gossner/archive/2013/10/26/october-2013-cu-for-sharepoint-2013-has-been-released.aspx

You may receive the following error when trying to view an Excel chart or graph on a website using Excel Services in SharePoint:

The maximum number of allowed sessions per user has been exceeded. The operation cannot be completed.

To fix this error, go to SharePoint Central Administration > Application Management > Service Applications > Manage service applications > Excel Services application > Global Settings. In the Session Management section, increase the value for Maximum Sessions Per User.

If this does not fix the error, you may be using anonymous authentication, for example when your site is on a public website. For the Maximum Sessions Per User setting, a user is an authenticated user. When anonymous access is enabled in SharePoint, all the users hitting the site are anonymous users, which maps to a single internal account that is authenticated to retrieve the data. So the maximum sessions setting applies to the same pool of sessions for all users.

If you are using anonymous authentication, you will see the following error in the SharePoint ULS log:

SessionManager.CheckAndUpdateSessionsPerUser: Throwing MaxSessionsPerUserExceeded SessionException. User=NT AUTHORITY\ANONYMOUS LOGON Count=25

There is a separate setting for anonymous users that is not exposed in the Excel Services settings in the SharePoint Central Administration GUI. The setting is called SiteCollectionAnonymousSessionsMax. To modify the setting, go to Start > Programs > Microsoft SharePoint > SharePoint Management Shell. Run the following command:

Get-SPExcelServiceApplication | format-list *

Look for the SiteCollectionAnonymousSessionsMax setting, It will most likely be set to 25 as this is the default setting. Also note the value of DisplayName which refers to the name of the Excel Services application. To change the session setting, for example to 500 sessions, run the following command, replacing DisplayName with the DisplayName value:

Set-SPExcelServiceApplication -identity DisplayName -SiteCollectionAnonymousSessionsMax 500

You may need to restart IIS. After making this change, users will not receive the error and should be able to view the Excel chart or graph successfully.

Issue:

After upgrading your SharePoint 2010 PowerPivot server to be at SQL 2012 SP1 level you get data refresh failures and this error in the logs:

EXCEPTION: Microsoft.AnalysisServices.SharePoint.Integration.Redirector.RedirectorException: This request could not be redirected to a PowerPivot for SharePoint server. An internal error occurred. Please look in the SharePoint logs for more information or contact the administrator of this farm. --->

System.Data.SqlClient.SqlException: Procedure or function UpdateRunProcessTimeWindow has too many arguments specified.   

 at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, BooleanbreakConnection)   

...

Cause:

It appears that the "PowerPivot Configuration tool" which needs to be ran after the SQL service pack does not update the PowerPivotServiceApplicationDB SQL database correctly.  (We are still researching this)

This causes a mismatch between the updated DLL's and the database on the number of parameters to use on the  UpdateRunProcessTimeWindow stored procedure.

Workaround:

The workaround is to manually update your PowerPivotServiceApplicationDB.  Follow steps below:

1. Start SQL Server Management Studio and connect to the SQL server instance that hosts your SharePoint database.
2. Backup your PowerPivotServiceApplicationDB database (name may look something like DefaultPowerPivotServiceApplicationDB-57bc03ae-bd41-4102-ab6f-f03201e3b583)
3. Right click  on your PowerPivotServiceApplicationDB database and select "New Query"
4. Copy the contends of the file LimitedUpdateSQL_sql.txt (attached to blog post) to the new query window
5. Click the "Execute" tool bar button

The steps above will redefine the stored procedure so that it matches what the updated DLL's are looking for.

This issue is fixed in SharePoint 2013 SP1 (Released Feb 25th 2014):

Update center for Office, Office servers, and related products
http://technet.microsoft.com/en-US/office/ee748587.aspx  

Issue:

"Call to Excel Services returned an error" when performing a Scheduled Data Refresh.

In the ULS logs,  you will see:

w3wp.exe (0x0A28)            0x0DB8  PowerPivot Service             Data Refresh        99           High                EXCEPTION: System.InvalidOperationException: Call to Excel Services returned an error. ---> Microsoft.AnalysisServices.SPClient.Interfaces.ExcelServicesException: We're sorry. We can't open the workbook in the browser because it uses these unsupported features:    • Shapes or other objects ---> Microsoft.Office.Excel.Server.WebServices.ExcelServerApiException: We're sorry. We can't open the workbook in the browser because it uses these unsupportedfeatures:    • Shapes or other objects     at Microsoft.Office.Excel.Server.WebServices.ApiShared.ExecuteServerSessionMethod(Boolean hasSessionId, String sessionId, CoreServerSessionMethod coreWebMethod, String name, Boolean skipFeatureCheck)     at Microsoft.Office.Excel.Server.WebServices.ExcelServiceInternal.OpenWorkbookInternal(String workbookPath, Boolean editingMode, String uiCultureName, String dataCultureName, Boolean newWorkbook, Boolean suppressRefreshOnOpen, Boolean openExclusive, Status[]& status)     at Microsoft.Office.Excel.Server.WebServices.ExcelServiceInternal.OpenWorkbookEx(String workbookPath, String uiCultureName, String dataCultureName, Boolean exclusive, Status[]& status)     at Microsoft.AnalysisServices.SPClient.ExcelApi.<>c__DisplayClassa.<OpenWorkbookEx>b__9(ExcelService svc, Status[]& status)     at Microsoft.AnalysisServices.SPClient.ExcelApi.Call[T](String fileUrl, ExcelServiceCall`1 serviceCall)     --- End of inner exception stack trace ---     --- End of inner exception stack trace ---     at Microsoft.AnalysisServices.SPClient.ExcelApi.Call[T](String fileUrl, ExcelServiceCall`1 serviceCall)     at Microsoft.AnalysisServices.SPClient.ExcelApi.Call[T](String fileUrl, ExcelServiceCall`1 serviceCall, String methodName, Object[] parameters)     at Microsoft.AnalysisServices.SPClient.ExcelApi.OpenWorkbookEx(String fileUrl, String uiCultureName, String dataCultureName, Boolean exclusive)     at Microsoft.AnalysisServices.SPClient.ASSPClientProxy.OpenWorkbookModelForRefresh(String workbookPath, SessionLifetimePolicy lifetimePolicy)     at Microsoft.AnalysisServices.SPAddin.DataRefresh.DataRefreshService.ProcessingJob(Object parameters)

This is a rather generic error message.  However, we have seen several cases where the Scheduled Data Refresh fails because of Unsupported Features in the workbook. 

We have a tool that you can use to remove these Unsupported Features.

Excel Services Compatibility Checker Download Page

http://blogs.msdn.com/b/cumgranosalis/archive/2007/06/29/excel-services-compatibility-checker-download-page.aspx

First install the "Excel Services Compatibility Checker Add-In".  As you can see a tab called "Excel Services" will appear in the ribbon (may need to restart Excel).  Now you can remove the Unsupported Features by choosing "Quick Fix".  I do suggest creating a copy (back up) of the workbook.  After you have removed the Unsupported Features, republish to the PowerPivot Gallery and run a Scheduled Data Refresh.

Excel Services Compatibility Checker Add in - Beta

http://blogs.msdn.com/b/cumgranosalis/archive/2007/06/29/excel-services-compatibility-checker-addin-beta.aspx

Other Resources:

Differences between using a workbook in Excel and Excel Services

http://office.microsoft.com/en-us/excel-help/differences-between-using-a-workbook-in-excel-and-excel-services-HA010021716.aspx

Excel Services part 12: Unsupported features

http://blogs.office.com/b/microsoft-excel/archive/2005/12/01/excel-services-part-12-unsupported-features.aspx

Excel Services in SharePoint 2010 Feature Support

http://blogs.msdn.com/b/excel/archive/2009/11/19/excel-services-in-sharepoint-2010-feature-support.aspx

  Edit a workbook that contains features unsupported by Excel Web App

http://office.microsoft.com/en-us/web-apps-help/edit-a-workbook-that-contains-features-unsupported-by-excel-web-app-HA102540964.aspx

Again, this is somewhat of a generic message, so this may or may not resolve your issue, but it is definitely worth testing.

Other FIX: You may also see this error in the ULS logs:

w3wp.exe (0x0A28) 0x0AC8 PowerPivot Service Data Refresh 99 High EXCEPTION: System.InvalidOperationException: Call to Excel Services returned an error. ---> Microsoft.AnalysisServices.SPClient.Interfaces.ExcelServicesException: You don't have permission to save your workbook here. ---> Microsoft.Office.Excel.Server.WebServices.ExcelServerApiException: You don't have permission to save your workbook here.     at Microsoft.Office.Excel.Server.WebServices.ApiShared.ExecuteServerSessionMethod(Boolean hasSessionId, String sessionId, CoreServerSessionMethod coreWebMethod, String name, Boolean skipFeatureCheck)     at Microsoft.Office.Excel.Server.WebServices.ExcelServiceInternal.SaveWorkbookCopy(String sessionId, String workbookPath, WorkbookType workbookType, SaveOptions saveOptions, Status[]& status)     at Microsoft.AnalysisServices.SPClient.ExcelApi.<>c__DisplayClass10.<SaveWorkbookCopy>b__f(ExcelService svc, Status[]& status)     at Microsoft.AnalysisServices.SPClient.ExcelApi.<>c__DisplayClass13.<Call>b__12(ExcelService e, Status[]& status)     at Microsoft.AnalysisServices.SPClient.ExcelApi.Call[T](String fileUrl, ExcelServiceCall`1 serviceCall)     --- End of inner exception stack trace ---     --- End of inner exception stack trace ---     at Microsoft.AnalysisServices.SPClient.ExcelApi.Call[T](String fileUrl, ExcelServiceCall`1 serviceCall)     at Microsoft.AnalysisServices.SPClient.ExcelApi.Call(String fileUrl, ExcelServiceCall serviceCall, String methodName, Object[] parameters)     at Microsoft.AnalysisServices.SPAddin.DataRefresh.DataRefreshService.ProcessingJob(Object parameters)

To fix this, you will need to give the account running PowerPivot Full Control to the Web App under Policy for Web Application.

You may receive an error similar to the following when running a scheduled data refresh of a PowerPivot workbook in SharePoint:

The table with ID of '<TableID>', Name of '<TableName>' referenced by the 'Sandbox' cube, does not exist. An error occurred when loading the Sandbox cube, from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSAS10_50.POWERPIVOT\OLAP\Backup\Sandboxes\PowerPivotServiceApplication\<GUID>.db\Sandbox.9825.cub.xml'.

You might see this error in the scheduled data refresh results on the PowerPivot Data Refresh History Page. You might also see this error in ULS logs of the SharePoint server running the PowerPivot system service after matching the Correlation ID of a generic error received when trying to view the Manage Data Refresh page for the PowerPivot workbook.

The error may be the result of a recent SharePoint update which could cause the file store data cache for the PowerPivot cube data to become obsolete.

The following steps can be used to resolve the error so the scheduled data refresh runs successfully:

1. Stop the SQL Server PowerPivot System Service on the SharePoint server running the PowerPivot service in SharePoint Central Administration > System Settings > Manage Services on Server.

2. Rename the following folder (the path may be slightly different on your system depending on the drive where PowerPivot was installed and the name of the PowerPivot service application):

C:\Microsoft SQL Server\MSAS10_50.POWERPIVOT\OLAP\Backup\Sandboxes\PowerPivotServiceApplication1

to

C:\Microsoft SQL Server\MSAS10_50.POWERPIVOT\OLAP\Backup\Sandboxes\PowerPivotServiceApplication1.old

3. Start the SQL Server PowerPivot System Service in SharePoint Central Administration.

4. Retest the scheduled data refresh of the PowerPivot workbook.

5. If the data refresh runs successfully, you can delete the PowerPivotServiceApplication1.old folder.

To set up PowerPivot for SharePoint scheduled data refresh for a PowerPivot workbook that has a connection to a SharePoint list in it, you do not need to use a data connection file like a List.atomsvc file (you do not need to use Export as Data Feed).

Another way that you can set up PowerPivot for SharePoint scheduled data refresh for a PowerPivot workbook that has a connection to a SharePoint list in it, is to make an OData data feed connection directly to the SharePoint list data service (and skip the List.atomsvc file altogether).

Here are some steps that I used that worked for me (using SharePoint 2013 and PowerPivot for SharePoint 2012 SP1).

Create a new Secure Store Service target application ID

• make it type Group

• add the domain group called Domain Users to the Members group for the ID

• set the ID’s credentials to a domain account and password that for sure has permissions to access the SharePoint list that we will be refreshing from (TIP: to start with, use the domain account and password that you will be logged on with on the machine where you will be launching the Excel client application and creating the Excel workbook in the next steps).

 In Central Administration, edit the PowerPivot service application settings and set the PowerPivot Unattended Data Refresh Account to use the Secure Store Service target application ID created above.     

Create a new workbook with Excel 2013, click on the PowerPivot add-in tab at the top, then click Manage on the far left.

Then choose From Data Service > From OData Data Feed

Then type in the Data Feed Url like this:   http://YourSPservername/_vti_bin/listdata.svc   and then click Next to connect to the service and view the items that appear.

Then select your SharePoint list and click Finish then Close.

Then set up your workbook the way that you would like.

For mine, I clicked on the PivotTable button at the top, I chose Existing worksheet, selected a PivotTable field called Value so that my PivotTable had some data, clicked on the Insert tab and added a slicer.

Then set the workbook’s connection authentication setting to use the Secure Store Target Application ID created above by going to the Data menu at the top > Connections > Properties > Definition tab > Authentication Settings > select Use a stored account > and type in the name of the ID that you created above.

Then test to make sure that both slicers and manual data refresh (Data > Refresh All Connections) work in the Excel client application, and then save the file to the PowerPivot gallery in SharePoint and open it in the browser by clicking on it.

Make sure that slicers work in the browser. 

Make sure that manual data refresh works in the browser by clicking Data > Refresh All Connections.

Then manage the data refresh for the workbook by clicking on the calendar icon for the workbook when viewing it in the PowerPivot gallery.

Click Enable, click Also refresh as soon as possible, make sure that the setting below called Use the data refresh account configured by the administrator is selected, then click OK.

 Then manage the data refresh for the workbook again by clicking on the calendar icon for the workbook again, and then refresh the page a few times using F5 to confirm that the scheduled refresh for the workbook runs and succeeds (refresh can take up to one minute to begin).

Assuming that the rest of your PowerPivot for SharePoint 2013 environment is set up well, PowerPivot scheduled data refresh from a SharePoint list should work in this configuration.

For steps on how to set up PowerPivot for SharePoint scheduled data refresh using a data connection file like a List.atomsvc file (Export as Data Feed), see:

Excel Services - Using a SharePoint List as a data source

http://blogs.technet.com/b/excel_services__powerpivot_for_sharepoint_support_blog/archive/2013/07/11/excel-services-using-a-sharepoint-list-as-a-data-source.aspx

I have seen several customers who have custom farm solutions deployed to their farm (Central Administration > System Settings > Manage farm solutions).  Some of these are for document libraries.  I have noticed the below error several times when opening a workbook from this location(s).

"Couldn't Open the Workbook

The workbook cannot be opened"

From what I have discovered, you need the solution to be installed on the same machine that is running Excel Services.  This currently is design.  It may change in the future. 

If these Solutions are not on the machine(s) running Excel Services the workbooks will fail to open and you will see the below errors in the ULS Logs:

01/17/2014 10:47:40.49 w3wp.exe (0x19E8) 0x2B50 SharePoint Foundation Object Cache ai107 Medium Failed on try1 to load XML document at path 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Template\Features\TeamSite\feature.xml': System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Template\Features\Site\feature.xml'.     at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)     at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)     at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)     at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)     at Microsoft.SharePoint.SPXmlDocCache.<>c__DisplayClass2.<GetGlobalXmlDocumentFullPath>b__0() 7b6b3d63-1900-43f6-8ffb-6a7a7b69f0a4

 01/17/2014 10:47:40.49 w3wp.exe (0x19E8) 0x2B50 Excel Services Application Excel Calculation Services tufa Medium SharePointFileLoader.GetSPFile: Sharepoint threw a handled exception - turning it into a FileOpen exception. Exception is: System.ArgumentException: Feature 'b4c5a5b0-514e-4c27-8fd5-d2c323118eac' for list template '101' is not installed in this farm.  The operation could not be completed.     at Microsoft.SharePoint.SPFeatureManager.<>c__DisplayClass19.<GetFeatureRootAndListSchemaPaths>b__18()     at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param)     at Microsoft.SharePoint.SPFeatureManager.GetFeatureRootAndListSchemaPaths(Byte[]& userToken, Guid& tranLockerId, Int32 nZone, Guid databaseid, Guid siteid, Guid webid, Guid featid, Int32 ltid, String& sPathToFeatureRoot, String& sPathToSchemaXml)     at Microsoft.SharePoint.Library.SPRequestInternalClass.GetListItemDataWithCallback2(IListItemSqlClient pSqlClient, String bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, ISPDataCallback pPagingCallback, ISPDataCallback pPagingPrevCallback, ISPDataCallback pFilterLinkCallback, ISPDataCallback pSchemaCallback, ISPDataCallback pRowCountCallback, Boolean& pbMaximalView)     at Microsoft.SharePoint.Library.SPRequest.GetListItemDataWithCallback2(IListItemSqlClient pSqlClient, String bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, ISPDataCallback pPagingCallback, ISPDataCallback pPagingPrevCallback, ISPDataCallback pFilterLinkCallback, ISPDataCallback pSchemaCallback, ISPDataCallback pRowCountCallback, Boolean& pbMaximalView)     at Microsoft.SharePoint.SPListItemCollection.EnsureListItemsData()     at Microsoft.SharePoint.SPListItemCollection.get_Count()     at Microsoft.SharePoint.SPWeb.GetItem(String strUrl, Boolean bFile, Boolean cacheRowsetAndId, Boolean bDatesInUtc, String[] fields)     at Microsoft.SharePoint.SPFile.get_Item()     at Microsoft.Office.Excel.Server.MossHost.MossHostFileLoader.GetSPFile(IClaimsIdentity claimsIdentity) 7b6b3d63-1900-43f6-8ffb-6a7a7b69f0a4

01/17/2014 10:47:40.49 w3wp.exe (0x19E8) 0x2B50 Excel Services Application Excel Calculation Services ecg6 Verbose ExcelServiceBase.PostProcessRequest: Called with ex=Id=GenericFileOpenError; Microsoft.Office.Excel.Server.CalculationServer.FileOpenException: The workbook cannot be opened. ---> Microsoft.Office.Excel.Server.Host.HostFileException ---> System.ArgumentException: Feature 'b4c5a5b0-514e-4c27-8fd5-d2c323118eac' for list template '101' is not installed in this farm.  The operation could not be completed.     at Microsoft.SharePoint.SPFeatureManager.<>c__DisplayClass19.<GetFeatureRootAndListSchemaPaths>b__18()     at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param)     at Microsoft.SharePoint.SPFeatureManager.GetFeatureRootAndListSchemaPaths(Byte[]& userToken, Guid& tranLockerId, Int32 nZone, Guid databaseid, Guid siteid, Guid webid, Guid featid, Int32 ltid, String& sPathToFeatureRoot, String& sPathToSchemaXml)     at Microsoft.SharePoint.Library.SPRequestInternalClass.GetListItemDataWithCallback2(IListItemSqlClient pSqlClient, String bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, ISPDataCallback pPagingCallback, ISPDataCallback pPagingPrevCallback, ISPDataCallback pFilterLinkCallback, ISPDataCallback pSchemaCallback, ISPDataCallback pRowCountCallback, Boolean& pbMaximalView)     at Microsoft.SharePoint.Library.SPRequest.GetListItemDataWithCallback2(IListItemSqlClient pSqlClient, String bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, ISPDataCallback pPagingCallback, ISPDataCallback pPagingPrevCallback, ISPDataCallback pFilterLinkCallback, ISPDataCallback pSchemaCallback, ISPDataCallback pRowCountCallback, Boolean& pbMaximalView)     at Microsoft.SharePoint.SPListItemCollection.EnsureListItemsData()     at Microsoft.SharePoint.SPListItemCollection.get_Count()     at Microsoft.SharePoint.SPWeb.GetItem(String strUrl, Boolean bFile, Boolean cacheRowsetAndId, Boolean bDatesInUtc, String[] fields)     at Microsoft.SharePoint.SPFile.get_Item()     at Microsoft.Office.Excel.Server.MossHost.MossHostFileLoader.GetSPFile(IClaimsIdentity claimsIdentity)     --- End of inner exception stack trace ---     at Microsoft.Office.Excel.Server.MossHost.MossHostFileLoader.GetSPFile(IClaimsIdentity claimsIdentity)     at Microsoft.Office.Excel.Server.MossHost.MossHostFileLoader.CheckForPermissions(IClaimsIdentity claimsIdentity)     at Microsoft.Office.Excel.Server.MossHost.MossHostHelperMethods.WithEnsureClaimsIdentitySetOnThread(IClaimsIdentity claimsIdentity, MethodToRun action)     at Microsoft.Office.Excel.Server.MossHost.MossHostHelperMethods.TryExecuteWithUserContext(IIdentity userIdentity, Action`1 method)     at Microsoft.Office.Excel.Server.MossHost.MossHostFileLoader.Init(Uri uri, Guid requestSiteId, IIdentity currentIdentity, ScenarioRestrictions restrictions, IExcelServerDocumentContext documentContext, FileLoaderHostInfo& outFileLoaderHostInfo)     at Microsoft.Office.Excel.Server.CalculationServer.SharePointFileLoader.Init(Uri uri, Guid requestSiteId, ScenarioRestrictions restrictions, IExcelServerDocumentContext documentContext)     --- End of inner exception stack trace ---     at Microsoft.Office.Excel.Server.CalculationServer.SharePointFileLoader.Init(Uri uri, Guid requestSiteId, ScenarioRestrictions restrictions, IExcelServerDocumentContext documentContext)     at Microsoft.Office.Excel.Server.CalculationServer.FileLoader.CreateFromTrustedLocationAndInit(Uri uri, TrustedLocation trustedLocationSettings, Guid requestSiteId, ScenarioRestrictions restrictions, IExcelServerDocumentContext documentContext)     at Microsoft.Office.Excel.Server.CalculationServer.BaseWorkbookManager.CreateAndInitFileLoaderForWorkbookLoad(Uri uri, Boolean newWorkbook, TrustedLocation trustedLocationSettings, Guid requestSiteId, ScenarioRestrictions restrictions, IExcelServerDocumentContext documentContext)     at Microsoft.Office.Excel.Server.CalculationServer.BaseWorkbookManager.GetBaseWorkbookAndMarkUsedAsync(AsyncHandler`1 callback, Object userState, Request request, Uri uri, Uri uriForKey, Boolean newWorkbook, Boolean useCollection, OpenWorkbookFlags openWorkbookFlags, ScenarioRestrictions restrictions, SessionId previousSessionId, TimeZoneInformation timeZone)     at Microsoft.Office.Excel.Server.CalculationServer.Session.OpenWorkbookAsync(AsyncHandler`1 callback, Object userState, Request request, Uri url, OpenWorkbookFlags openWorkbookFlags, ScenarioRestrictions restrictions, SessionId previousSessionId, TimeZoneInformation timeZoneInfo)     at Microsoft.Office.Excel.Server.CalculationServer.Operations.OpenWorkbookOperation.StartExecution()     at Microsoft.Office.Excel.Server.CalculationServer.Operations.Operation.RunOperationAsync()     at Microsoft.Office.Excel.Server.CalculationServer.Operations.OperationSite.PrepareComplete(PrepareAsyncArgs args) 7b6b3d63-1900-43f6-8ffb-6a7a7b69f0a4

I have seen the below errors that required a server reboot to fix the issue:

Error in GUI:

Error in ULS:

03/06/2014 17:43:45.29 w3wp.exe (0x3B38) 0x574C Excel Services Application Excel Calculation Services 89rs Exception ExcelServerApp..ctor: An unhandled exception occurred during boot. Shutting down the server. Microsoft.Office.Excel.Server.CalculationServer.Interop.LoadDllException: Failed to load engine dll.Acceso denegado.       at Microsoft.Office.Excel.Server.CalculationServer.Interop.EngineInterop.LoadDll(EngineFlags engineFlags, String binPath, String muiPath, String ppPath, IRequestTelemetryEvents requestTelemetryEvents)     at Microsoft.Office.Excel.Server.CalculationServer.ExcelServerApp.Initialize()     at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock) StackTrace:  at Microsoft.Office.Server.Native.dll: (sig=35339f9c-8871-4ef1-9118-9c1bd0cb6598|2|microsoft.office.server.native.pdb, offset=131CE) at Microsoft.Office.Server.Native.dll: (offset=21B4D) 47bf7a9c-949d-c0e3-278b-d714155b5356

Error in GUI:

Error in GUI:

03/03/2014 16:46:13.09    w3wp.exe (0x3EA4)    0x4120    Excel Services Application    Data Model    27    Monitorable    Uncaught CLR exception crossing the Interop boundary: Microsoft.AnalysisServices.Streaming.ServerNotFoundException: No eligible servers meet the operation's requirements. ---> System.InvalidOperationException: Sequence contains no matching element     at System.Linq.Enumerable.First[TSource](IEnumerable`1 source, Func`2 predicate)     at Microsoft.AnalysisServices.Streaming.OnPremise.MemoryBasedLoadBalancer.BeginOperation(OperationRequirements requirements, IEnumerable`1 availableServers)     --- End of inner exception stack trace ---     at Microsoft.AnalysisServices.Streaming.OnPremise.MemoryBasedLoadBalancer.BeginOperation(OperationRequirements requirements, IEnumerable`1 availableServers)     at Microsoft.AnalysisServices.Streaming.OnPremise.LoadBalancer.GetLoadBalancedOperation(Func`1 onBegin)     at Microsoft.AnalysisServices.Streaming.OnPremise.Database.Loading.Create()     at Microsoft.AnalysisServices.Streaming.OnPremise.ServerPool.<>c__DisplayClass9.<Microsoft.AnalysisServices.Streaming.OnPremise.IServerPool.CreateConnection>b__8(Guid id)     at Microsoft.AnalysisServices.Streaming.Internal.KeyedReferenceCountedEnumeration`2.Node.<>c__DisplayClassc.<.ctor>b__a()     at System.Lazy`1.CreateValue()     at System.Lazy`1.LazyInitValue()     at Microsoft.AnalysisServices.Streaming.Internal.KeyedReferenceCountedEnumeration`2.Node.GetReference()     at Microsoft.AnalysisServices.Streaming.Internal.KeyedReferenceCountedEnumeration`2.GetOrCreateReference(TKey key, Func`2 valueFactory)     at Microsoft.AnalysisServices.Streaming.OnPremise.ServerPool.Microsoft.AnalysisServices.Streaming.OnPremise.IServerPool.CreateConnection(Guid imageId, Func`1 allocationFactory)     at Microsoft.AnalysisServices.Streaming.OnPremise.Database.Loading.EstablishConnection()     at Microsoft.AnalysisServices.Streaming.OnPremise.Database.ConnectWithoutOperationSetup()     at Microsoft.AnalysisServices.Streaming.OnPremise.Database.Microsoft.AnalysisServices.Streaming.IDatabase.Connect(DatabaseConnectionProperties props)     at Microsoft.AnalysisServices.Streaming.Interop.StreamingServerPoolModule.Microsoft.AnalysisServices.Streaming.Interop.IStreamingConnector.Connect(SSPM_CONNPROPS in_connprops, SSPM_CALLBACKS in_callbacks)    d1c4799c-d568-c0a0-395b-bd0ecb4a84f0

When in doubt, reboot.

You may see the following error in Windows Event Viewer or the SharePoint ULS logs:

Cannot open database "<Database name of PowerPivot Service application>" requested by the login. The login failed. Login failed for user '<username>'.

This is an indication of an orphaned record regarding the PowerPivot service application database in SharePoint. This may happen after deleting a PowerPivot service application. The records for the deleted PowerPivot service application database are sometimes not removed from the the SharePoint configuration database, so SharePoint  throws an error when it cannot open the PowerPivot service application database since it no longer exists.

The solution to this is to remove these orphaned records. Open the SharePoint Management Shell on a SharePoint server and run the following command:

Get-SPDatabase | where {$_.exists -eq $false}

This will display a list of the databases that no longer exist on the SharePoint database server. The PowerPivot database referenced in the error above should show up in this list. After confirming this, you may remove the orphaned record by running this command:

Get-SPDatabase | where {$_.exists -eq $false} | foreach {$_.delete()}

At this point, the orphaned record pointing to the old PowerPivot service application database will be removed, and the error that you noticed earlier will stop occurring.

Issue:

PowerPivot for SharePoint scheduled data refresh does not work for the first day of the month, an error is generated every two minutes. ULS shows:

PowerPivot Service             Data Refresh                   99 High     EXCEPTION: Microsoft.AnalysisServices.SharePoint.Integration.DataRefreshException: The data refresh job failed because it did not run within the time period allotted for running this schedule

Cause:

This looks to be a software defect.

Workaround:

If you refresh the workbook daily, the first day of the month will refresh fine.

If you refresh on the second day of the month the refresh will work.

The product group is looking into this issue and it may be resolved in a future release.

You may receive the following error when running a scheduled data refresh on a PowerPivot workbook in SharePoint 2013 running PowerPivot for SharePoint using SQL PowerPivot 2012 SP1:

A schedule cannot be enabled for a workbook with no external data sources.

This can happen when a PowerPivot workbook created in Excel 2010 using the PowerPivot 2012 add-in is used in SharePoint 2013, and the Excel Services Authentication Setting in the data connection properties is set to anything other than Windows Authentication:

If you upload the workbook to SharePoint 2013 and you go to the workbook's Manage Data Refresh page from the PowerPivot Gallery, you will receive the error. This is because the SSS and None options cannot be used in this scenario. Change the setting to Windows Authentication and save the workbook back to SharePoint to fix the error and enable the scheduled data refresh for the workbook.

You may encounter PowerPivot data refresh schedules getting automatically disabled in SharePoint 2013. If a schedule gets disabled, you may see one of the following messages when viewing the Data Refresh History page:

The schedule was disabled due to consecutive failures.

The schedule was disabled because the workbook is inactive.

There a couple settings in the PowerPivot service application settings that can cause schedules to be come disabled due to the reasons stated in the messages above. Here is a screenshot of those settings that you can access in SharePoint Central Administration > PowerPivot Management Dashboard > Configure service application settings:

The first settings is Disable data refresh due to consecutive failures and the default value is 10. This means that if a data refresh schedule encounters 10 consecutive failures, the schedule will be disabled. The second setting is Disable data refresh for inactive workbooks and the default value is also 10. This means if a workbook has not been accessed by a user for 10 days, the schedule will be disabled.

You can specify a different value for these settings. To prevent the data refresh schedule from becoming disabled automatically due to failures or inactivity, specify a value of 0 for these settings.

If you are using a Power View Sheet and it is not rendering in the browser (see below screenshot):

You will want to verify if you are using Office Web Apps Server 2013 (WopiFrame.aspx) to render the workbook by examining the URL:

URL Example:

http://servername/sites/BICenter/_layouts/15/WopiFrame.aspx?sourcedoc=%2Fsites%2FBICenter%2FTest%20PowerPivot%20Gallery%2FPower%2Exlsx&action=view

If you are indeed using the WopiFrame.aspx, you will want to flip this (via the SharePoint 2013 Management Shell) to use the ExcelService.asmx via:

New-SPWOPISuppressionSetting -extension xlsx -action view

In the below article, you will see that Power View Sheets are not visible in Office Web Apps 2013 (WopiFrame.aspx):

Power View in Excel on Office 365 or in SharePoint Server
http://office.microsoft.com/en-us/excel-help/power-view-in-excel-on-office-365-or-in-sharepoint-server-HA103276078.aspx

Additional Information:

To verify the Suppression, run this command in the SharePoint 2013 Management Shell:

Get-SPWOPISuppressionSetting

It should return: XLSX VIEW

To remove this Suppression run this command in the SharePoint 2013 Management Shell:

Remove-SPWOPISuppressionSetting -extension xlsx -action view

To understand the above Office Web Apps SharePoint 2013 Management Shell Commands refer to the below article:

Windows PowerShell for Office Web Apps (SharePoint 2013)
http://technet.microsoft.com/en-us/library/jj219457(v=office.15).aspx

Summary:

If the Excel Services global option "Use the EffectiveUserName" is turned on, then all workbooks that use secure store service ID's (SSID) will not refresh data and can not create connections to the SSAS data sources. So effectively the SSID authentication option is not useable if the EffectiveUserName global option is turned on.

ULS entry:

ExternalSource.ValidateConnection: Unable to get a connection: ... Microsoft.Office.Excel.Server.CalculationServer.ExternalSource.TryGetValidatedConnection

Status:

The product group is investigating the issue right now, there is an estimated fix date of November 2014.

Issue:

This issue with the email notifications was fixed with Cumulative update package 7 for SQL Server 2012 SP1, but we are seeing cases where the email notifications still do not happen, even after installing CU7 for SQL Server 2012 SP1.

Cause:

The PowerPivot for SharePoint update is not complete until the PowerPivot Configuration Tool is run.

Workaround:

Run the PowerPivot for SharePoint Configuration Tool to complete the CU7 update for PowerPivot for SharePoint, and then the email notifications will begin working.

Cumulative update package 7 for SQL Server 2012 SP1

http://support.microsoft.com/kb/2894115

Issue Overview:

Post migration of a working PowerPivot system from Windows Authentication to Claims Authentication sometimes not all workbook files author property is updated to the new format, this causes the "PowerPivot Management Dashboard Processing Timer Job" to fail with error:

“Microsoft.SharePoint.SPException: User cannot be found” at Microsoft.AnalysisServices.SPAddin.UsageProcessingTimerJob.PrepareUsageData

Some or all of your PowerPivot files like have their author property set in the old Windows style name like “MYDOMAIN\someuser”

If the author property was set to a claims format the error would go away, like “i:0#.w|MYDOMAIN\someuser”

The workaround for this issue is to delete and re-upload the PowerPivot workbooks affected.

The author field can not be fully examined from the SharePoint UI, so it can be difficult to track down all of these workbooks.

Attached to this post (very bottom) is sample code that shows one way to list all of the workbooks for a PowerPivot service application that have an author property in the Windows style format (these files will throw and error when the "PowerPivot Management Dashboard Processing Timer Job" runs).

** THIS SAMPLE CODE IS PROVIED AS IS, WITH NO WARRANTEES OR SUPPORT OF ANY KIND, USE AT YOUR OWN RISK **

Rename PPTimerUserError.bak to PPTimerUserError.exe so you can run the program (.bak so zip scanners don't block the file)

The .exe must be ran from one of the farm SharePoint 2013 servers

The output is tab delimited so you can open with Excel to sort and filter as needed

useage: PPTimerUserError <DB Server> <PowerPiviot DB Name>

example: PPTimerUserError warrenr-ws1 DefaultPowerPivotServiceApplicationDB-57bc03ae-bd41-4102-ab6f-f03201e3b583

output at C:\temp\PPTimerAuthorReport.txt  and PPTimerAuthorReportDetails.txt

Update

This PowerShell code is known to update the author field if you do not want to remove and re-add the affected files,

**USE AT YOUR OWN RISK **

$web = get-spweb http://reports2013/analytics

$list = $web.lists['Reports']

$user = get-spuser -Web $web -limit all | ? {$_.userlogin -match "SPAdmin"}

$sUser = $user.id.ToString() + ';#' + $user.DisplayName

$listItems = $list.Items

write-host $listItems[0]["Author"]

write-host $listItems[1]["Author"]

write-host $listItems[2]["Author"]

$li = $listItems[1] 

$li["Author"] = $sUser

$li.properties["vti_author"] = $user.loginname

$li["Editor"] = $sUser 

$li.UpdateOverwriteVersion()

write-host $li["Author"]

If you have a workbook with a Power View worksheet that was created in Excel, and you upload that workbook to the PowerPivot Gallery in SharePoint, you may receive a red X instead of a thumbnail because of a failure with the snapshot generation:

This is expected behavior as the snapshot process does not support embedded Power View reports in workbooks.

One workaround is to only publish all worksheets except for the Power View worksheets when uploading the workbook to the PowerPivot Gallery. Click on Save As in Excel when saving to SharePoint and you will get a Browser View Options button in the Save As dialog box:

Click on Browser View Options, and on the Show tab, select the dropdown menu and change Entire Workbook to Sheets. This will allow you to uncheck the Power View worksheet:

Click OK and continue to save the workbook. The Power View worksheet will not be displayed in the PowerPivot Gallery thumbnails or in Excel Services when you open the workbook, but it will still be visible when you open the workbook in Excel client. This allows the thumbnails for the rest of the worksheets to be generated successfully in the PowerPivot Gallery, but you will lose the ability to view the Power View report in the browser. As you can see below, the third worksheet, which is the Power View worksheet, is not shown in the workbook thumbnail, and is not part of the worksheet thumbnails:

Another option is to place the Power View report as the last worksheet in the workbook, and then display the first worksheet before saving the file. This will allow snapshot generation of all worksheets before the Power View worksheet as the worksheets are enumerated in order during the snapshot process. As you can see below, the workbook snapshot shows that there are 3 worksheets, but only thumbnails are only generated for the first 2 worksheets as the third one is a Power View worksheet:

The advantage of this option is that the Power View worksheet is published to SharePoint, so even though the thumbnail is not generated, when you open the workbook in Excel Services, the third worksheet is visible and the Power View report is rendered.

In order to view a Power View report thumbnail, you will need to use Power View for SharePoint to create the Power View report instead of creating a Power View worksheet in Excel. To do this, upload the PowerPivot workbook to the PowerPivot Gallery. Next to the thumbnail for the workbook, you have a few icons, one of which allows you to create a standalone Power View report in RDLX format based on the PowerPivot workbook. When you hover over the button it says Create Power View Report:

After building the report and saving it to the PowerPivot Gallery, a thumbnail will be generated because in this case, Power View generates the thumbnail instead of PowerPivot using a different snapshot generation process:

Please note that the Power View feature for SharePoint is only available with SQL Server 2012 SP1 and above as part of the Reporting Services add-in for SharePoint.

This case may be a one-off, but I wanted to write about it in the event someone else comes across it in the future.

Here is the synopsis.  A user was creating an Excel workbook in the rich client using "Use Windows Authentication":

When you do that, the connection string looks like:

Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=True;Initial Catalog=AdventureWorks2012;Data Source=Data;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RICKCLIENT;Use Encryption for Data=False;Tag with column collation when possible=False

The Security Support Provider Interface
http://technet.microsoft.com/en-us/library/bb742535.aspx

The company had a group of Authors with Role Based permissions to the SDL Data.  The Authors were able to connect to the data source and build the workbooks using their Logon Credentials.  However, the Authors were changing the "Excel Services Authentication Settings" to "Use a stored account Application ID:" prior to publishing to SharePoint.  The reasoning behind this made complete sense, the Members of the Secure Store Application ID did not have Role Based permissions to the SQL Data.  The "Set Credentials" the account was a SQL account that did have access to the SQL Data.  See below how it was built. 

That Application ID "Fargo" was using SQL Credentials.  This is how they built it:

Now when they use a workbook that was created in Excel using  "Use Windows Authentication" with a Secure Store Service Application ID that uses SQL Credentials, things go wacky.  We noticed that the account running Excel Services needs to be given permissions in SQL.

BUT, if the workbook was created (In Excel Rich Client) using "Use the following UserName and Password", "Integrated Security=SSPI" is not present and the SQL "UserID=XXXXX" is saved  in the Connection String and there is no further action required, the refresh in Excel Services completes without error. 

Provider=SQLOLEDB.1;Persist Security Info=True;User ID=EddieVedder;Initial Catalog=AdventureWorks2012;Data Source=Data;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=AMENTCLIENT;Use Encryption for Data=False;Tag with column collation when possible=False

Analysis:

This is design.  You must have the workbook created (in the Excel Rich Client) with the same Authentication Type as the Secure Store Service.  So if the Secure Store Service is holding SQL User ID and Password for SQL Auth, the workbook must be using SQL Auth when it is built, if you see SSPI in the connection string that means that Windows Auth Mode is used.  A connection can only use one AuthMode, either SQL Auth or Windows Auth.

Scenario:

You get the following error while running a scheduled data refresh on a PowerPivot workbook:

Problem:

The "Require Check Out" option inside of the Document Library Settings > Versioning Settings of any given document library is likely set to "Yes":

Resolution:

PowerPivot does not attempt to check out documents when it makes its modification, therefore you will need to turn this "Require Check Out" option to "No" for scheduled data refresh to work on the document library in question.