The resource object with key ‘DataRefresh_Warning_DataSources’ was not found


UPDATE: 8/16/17 - This issue should be fully resolved with the below patches!!

If you have not already installed the following patches on your PowerPivot for SharePoint Analysis Services instance and/or the MSI DO NOT PROCEED WITH THE INSTALLATION!

SQL 2012 SP3 CU6 - Resolved (see below)
SQL 2012 SP3 CU7 - Resolved (see below)

SQL 2014 SP1 CU10 - Resolved (see below)
SQL 2014 SP2 CU3 - Resolved (see below)

If you already installed the SSAS patch but not installed the spPowerPivot.msi, the patch can be backed out or Analysis Services can be reinstalled without much downtime. If you installed the MSI and ran the PowerPivot configuration tool, you will be required to reinstall or use the below workaround until this gets patched. Remember, the goal is to keep your msi and PowerPivot AS versions at the same level.

A recent product issue was introduced that causes users to be presented with an error when they attempt to schedule or modify a refresh schedule for a PowerPivot workbook, they will be presented with the following error:

error

Official Microsoft KB for this issue: https://support.microsoft.com/en-us/help/4011987

You will see a stack similar to the following in the ULS logs when this happens:

00/00/2017 00:00:00.00 w3wp.exe (XXXXXXXXX) 0x91D4 SharePoint Foundation General 8nca Medium Application error when access /_layouts/15/PowerPivot/ManageDataRefresh.aspx, Error=The resource object with key 'DataRefresh_Warning_DataSources' was not found.   at <<TRUNCATED STACK>>

00/00/2017 00:00:00.00 w3wp.exe (XXXXXXXXX) 0x91D4 SharePoint Foundation General b9y9 High Failed to read resource file "<C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Resources\PowerPivot_Pages.en-US.resx>" from feature id "(null)".

00/00/2017 00:00:00.00 w3wp.exe (XXXXXXXXX) 0x91D4 SharePoint Foundation General b9y9 High Failed to read resource file "<C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Resources\PowerPivot_Pages.resx>" from feature id "(null)".

For now, the workaround is as follows (ONLY IF YOU HAVE ALREADY installed the patch that causes the issue!!!):

  1. Navigate to the following file location on your SharePoint servers: "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\PowerPivot"
  2. Create a backup of "ManageDataRefresh.aspx"
  3. Open "ManageDataRefresh.aspx"
  4. Find the following:
    <tr>
       <td colspan="2" style="height:20px;vertical-align:middle;">
           <asp:Label style="margin:5px;" ID="Literal3" runat="server" Text="<%$Resources:PowerPivot_Pages, DataRefresh_Warning_DataSources %>" />
       </td>
     </tr>
  5. Replace it with the following:
     <%--
        <tr>
            <td colspan="2" style="height:20px;vertical-align:middle;">
               <asp:Label style="margin:5px;" ID="Literal3" runat="server" Text="<%$Resources:PowerPivot_Pages, DataRefresh_Warning_DataSources %>" />
            </td>
        </tr>
     --%>
  6. Save the file.
  7. IISReset the server.
  8. Test the results once every server has been modified.

Note that this is specific to PowerPivot for SharePoint 2013 and the SQL CUs listed above. This issue should not affect any other products and/or Analysis Services stand-alone installations. The issue appears to be limited to the PowerPivot add-in for SharePoint (sppowerpivot.msi) which happens to be included with the CU installer.

Resolution:

This issue is resolved with the following updates:

Use the following blog to ensure you update PowerPivot properly. If you do not apply the MSI correctly, the issue will persist even with the patch applied!
https://blogs.technet.microsoft.com/excel_services__powerpivot_for_sharepoint_support_blog/2015/04/14/run-the-powerpivot-configuration-tool-after-upgrading-the-analysis-services-powerpivot-instance/

Comments (1)

  1. Chris Downing says:

    Thanks you! We installed this on Friday, and there were literally zero results when you searched for the error, so I was very surprised to find this today! I can confirm that workaround solved the problem for us (fortunately we hit it in Dev, so we won’t be installing in QA/Prod until a patch is out). Sometimes I feel like we’re the only ones using this, or at least the only ones patching it…

Skip to main content