I have been using PowerPivot in Excel 2013 and SQL Server 2012 SP1 Tabular Model side by side for over 3 months now. Recently I have just encountered the following error when creating new Excel 2013 workbook from scratch and adding a table into the Data Model.
We couldn’t load the Data Model. This may be because the Data Model in the workbook is damaged.
PowerPivot is unable to load the Data Model.
It seems that I am not the only who is having the issue. Chris Webb (b | t) mentioned to me that he also has encountered it in the past. Others have mentioned that it’s been working for them without any issue.
I have recently logged the issue on Connect. Please vote if you encounter the same issue.
To summarize, the environment details I have this happened are:
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
The workaround is simply to turn off SQL Server Analysis Services (Tabular) services. This should allow users to add data model to PowerPivot again. Although the workaround is simple and works, it becomes cumbersome for us who needs to use both PowerPivot and Tabular Model at the same time.
Hopefully this will be fixed soon.
Having PowerPivot (Excel 2013) and SQL Server Analysis Services Tabular Model instance installed on the same machine may result in an error when opening PowerPivot. The error “We couldn’t load the Data Model. This may be because the Data Model in the workbook is damaged.” appears even though the data model is not damaged (or not even created yet). The work around is to stop the Tabular Model instance. The issue has been logged on Connect.
PowerPivot couldn’t load Data Model when SSAS Tabular Instance is running on Microsoft Connect.