Search

PowerPivot couldn't load Data Model when SSAS Tabular Instance is running by Julie Koesmarno

Active

12
0
Sign in
to vote
Type: Bug
ID: 780949
Opened: 3/7/2013 11:51:17 AM
Access Restriction: Public
0
Workaround(s)
2
User(s) can reproduce this bug

When SSAS Tabular Model instance is running, a new table could not be added to the Data Model.

Details (expand)

Product Language

English

Version

SQL Server 2012 - Developer Edition

Category

Analysis Services

Operating System

Other

Operating System Language

US English

Steps to Reproduce


1. Create a new Excel 2013 workbook.
2. Create a new table (any size with header) and add to the Data Model.
3. An error dialog box will appear:
"We couldn't load the Data Model. This may be because the Data Model in this workbook is damaged"

Operating System: Windows 8 Pro (6.2.9200) - 64-bit
SQL Server 2012 SP1 (11.0.3128) - 64-bit
Office Professional Pro 2013: Microsoft Excel 2013 15.0.4454.1503 MSO (15.0.4454.1504) 64-bit

Actual Results


Unable to add Excel 2013 table(s) into Data Model when SSAS Tabular Model instance is running. PowerPivot does not start.


The workaround is to stop the SSAS Tabular services.

Expected Results


Adding a new table into Data Model in Excel 2013 should work side by side with SQL Server 2012 Tabular Model instance running.

Platform

X64

Virtualization

 
File Attachments
File Name Submitted By Submitted On File Size  
PowerPivot Error.png 3/7/2013 5 KB
Sign in to post a comment.
Posted by Koen Verbeeck on 4/25/2013 at 5:42 AM
I have the same behaviour when I'm running a virtual machine using HyperV. If the data model is open, I cannot start the VM (getting an error saying there aren't sufficent resources). If the VM is running, I can't open the PowerPivot Model, saying it might be damaged.

Very frustrating...
Posted by David M Feldman MCSD MCDBA, MCTS SharePoint on 4/2/2013 at 7:52 PM
I can confirm i've seen this on any machine where the user does not have local admin rights. I wasted weeks with support and made no progress. This really needs to be fixed
Sign in to post a workaround.