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.

FIX: An Excel workbook that contains a PowerPivot table is corrupted after you upload the Excel workbook to a SharePoint PowerPivot gallery


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You create a Microsoft Excel 2010 workbook.
  • In the Excel workbook, you create a Microsoft PowerPivot table and import data from a Microsoft SQL Server 2008 R2 Analysis Services database that uses the Japanese collation.
  • You add some slicers to the PowerPivot table.
  • You upload the Excel workbook to a Microsoft SharePoint PowerPivot gallery.�
  • Then, you update the fact table and the dimension table in the back-end database.�
  • You schedule a data refresh operation on the SharePoint site.
In this scenario, when you try to open the Excel workbook after the data refresh operation occurs, the Excel workbook is corrupted, and the Excel workbook is opened in repair mode.


Note You may experience the same problem when you import data from any other data source with the encoding of non-Ansi characters.

↑ Back to the top


Resolution

Cumulative update information

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2072493 Cumulative update package 2 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


References

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems


For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

↑ Back to the top


Keywords: KB2028769, kbexpertiseadvanced, kbhotfixserver, kbfix, kbqfe, kbautohotfix

↑ Back to the top

Article Info
Article ID : 2028769
Revision : 3
Created on : 6/25/2010
Published on : 6/25/2010
Exists online : False
Views : 499