Search

PowerPivot + Office 2013 restore into SQL 2012 Tabular: backup store version 150 is not supported by Snap

Active

1
0
Sign in
to vote
Type: Bug
ID: 772554
Opened: 11/28/2012 10:20:41 AM
Access Restriction: Public
1
Workaround(s)
0
User(s) can reproduce this bug
When trying to restore a PP 2013 xlsx made in Office 2013 we get an error:

"A connection corresponding to the embedded PowerPivot data was not found in the Excel Workbook."

This makes no sense, since the connection is a SQL Server database. It works to build out the PP itself, so why the error?

If we manually extract the data file from the xlsx, save as an abf and then try and restore normally we get this error :

"backup store version 150 is not supported."

If the exact same PP was built in Office 2010, with the PowerPivot 2012 plug-in, everything works as normal. So this speaks to an issue with Office 2013 and its built in PP plug-in

Details (expand)

Product Language

English

Version

SQL Server 2012 - Enterprise Edition

Category

Analysis Services

Operating System

Windows 7 Professional (SP1)

Operating System Language

US English

Steps to Reproduce

Create a powerpivot in office 2013, using a SQL database.
Try and restore the spreadsheet to SQL 2012 tabular analysis services.

Actual Results

Errors as described above.

Expected Results

The spreadsheet is restored as a new tabular database in SSAS

Platform

X64

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 11/29/2012 at 3:10 PM
Thanks for filing this issue.

Extracting a model from within an Excel workbook and restoring it directly to an Analysis Services server isn't supported, but it will work if the version of the server matches the version of the private AS engine in Excel.

In this instance, Excel 2013 is using a version that is newer. To get this to work with an AS Server, you would need to be running SQL Server 2012 Analysis Services SP1. Without SP1, the server isn't new enough to restore the backup.

Hope this helps,
Analysis Services Product Team
Sign in to post a workaround.
Posted by Snap on 11/28/2012 at 12:24 PM
ok. update. seems SP1 for 2012 fixes the issue.