PowerPivot for SharePoint – Schedule Data Refresh Error: "A schedule cannot be enabled for a workbook with no external data sources."


If you come across this error when trying to perform a scheduled data refresh:

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

This is because the Data Model cannot be created on the PowerPivot Server.

Your probably have two questions.

1. What is a "Data Model".

The Data Model is a cube created under the PowerPivotServer\POWERPIVOT instance:

2.Why can't/isn't the Data Model being created?

The reason why this isn't being created is because there is something wrong with the Excel Services "Data Model Settings".

You can find this be going to the Central Administration > Application Management > Manage Service Applications > Excel Services > Data Model Settings.

At this location, you need to enter the proper PowerPivotServer\Instance

Here is the proper way:

Here is a bad example (no need to have just the server name present):

Here is another bad example (PowerPivot) is misspelled:

I hope this helps.

Tom

 

 

 

Comments (9)

  1. There’s also something (I don’t want to called it a Bug), where the following file "PowerPivotFeatures.en-US.resx" does not get created by the PowerPivot Deployment interface and you have to place it manually.

    1. Go to C:Program FilesCommon Filesmicrosoft sharedWeb Server Extensions15Resources
    2. Find the file name "PowerPivot_Features.en-US.resx", create a copy, and rename it to "PowerPivotFeatures.en-US.resx".

    Now the Schedule PowerPivot Data Refresh feature should work.

  2. M Shoaib says:

    an other reason which could cause this problem, Check if the SQL Server Analysis services are running on server where PowerPivot is configured. If not start the service.

  3. pankaj: This option is only available in SharePoint 2013 as there is no PowerPivot Analysis Services dependency on SharePoint. In SharePoint 2010, PowerPivot Analysis Services must be installed on a SharePoint server, so the SharePoint farm is already
    aware of the instance.

  4. pankaj says:

    is this option is only in SP 2013? I am not finding in SP 2010

  5. Erik says:

    Could also be related to the size of the workbook. If it exceeds the Maximum Workbook Size set under Trusted Locations, the same message will appear.

  6. pradeep says:

    Ricardo, you hit on the point, and I would say its a bug. Thanks for pointing it out.

  7. Sakti Mohapatra says:

    Hi,

    I am facing the same issue and not able to fix it.

    Following are the points I checked but no luck.

    1. SQL Server Analysis services are running on server where PowerPivot is configured.

    2. In my DEV farm everything it is working fine. I don’t have to make any change. Since it is not working in QA I followed the following steps mentioned by Ricardo. But issue still remains the same.
    a. Go to C:Program FilesCommon Filesmicrosoft sharedWeb Server Extensions15Resources
    b. Find the file name "PowerPivot_Features.en-US.resx", create a copy, and rename it to "PowerPivotFeatures.en-US.resx".

    Can anyone please give a pointer or advice how to fix it?

    Regards
    Sakti

  8. Tim Johnson says:

    Does anyone have any insight to this error in a 2016 SharePoint environment. Ricardo, the file you refer to in 2016 is now called “PowerPivot16_Features.en-US.resx”, so I assume they’ve cleaned up that bug you refer to below. M Shaaib, you wouldn’t be able to connect to the PowerPivot instance if Analysis Services isn’t running, so are you referring to checking another SharePoint server in the farm for this?

    1. Things change quite a bit in SharePoint 2016 as you may know. The feature issue Ricardo was running into was not a bug, it was likely that features just didn’t get deployed properly. It is hard to say why without looking at it, but the PowerPivot configuration tool is not flawless. There are a lot of reasons solutions may fail to deploy to a server.

      To your question: There are a lot of reasons there could be connection issues to the PowerPivot AS instance. The foremost being that the connectivity now comes from the Office Online Server rather than a SharePoint application server, so if the connection is blocked for some reason or the Analysis Services drivers are not installed, it would cause this connection to fail. From a support perspective, I do not think I have ever seen the modification of a feature file fixing this error (even in SP 2013).

Skip to main content