Fix 'We couldn't get data from the Data Model' – Power Pivot Engine Failed to Load

What just happened

You open an Excel workbook that uses Power Pivot, click Refresh All (or try to open the Data Model), and get hit with:

We couldn't get data from the Data Model.
Here's the error message we got: The Power Pivot engine failed to load.

The workbook opens fine. Your pivot tables are still there. But the moment you touch the Data Model, everything stops. The error message is deliberately vague — it can mean six different things. This guide ranks them by how often they actually occur.

Root causes

• Power Pivot add-in is disabled — the most common cause by far. COM add-ins get silently disabled after a crash or Office update, with no warning.
• 32-bit Excel trying to load a 64-bit Data Model (or vice versa) — happens when a workbook moves between machines with different Office bitness.
• Corrupted Analysis Services engine (msmdsrv) — the in-process OLAP engine Excel uses internally is damaged or has a version mismatch.
• Partial Office corruption — missing or mis-registered DLLs after a failed update.
• Temp file conflict — rare, but the engine can fail to start if its temp directory is full or locked by another process.

Step 1: Re-enable the Power Pivot COM add-in

Start here. This alone fixes the problem roughly 60% of the time.

• Open Excel → File → Options → Add-ins.
• At the bottom, set Manage to COM Add-ins → click Go.
• Look for Microsoft Power Pivot for Excel. If the checkbox is unchecked, check it and click OK.
• If it's missing entirely, click Add… and browse to:

C:\Program Files\Microsoft Office\root\Office16\ADDINS\PowerPivot Excel Add-in\PowerPivotExcelClientAddIn.dll

Restart Excel and test by clicking Power Pivot → Manage. If the Power Pivot window opens, you're done.

Step 2: Verify your Office bitness matches the workbook

Check which version of Excel you're running:

File → Account → About Excel

The dialog title shows either (32-bit) or (64-bit). If a colleague built the workbook on 64-bit Excel and you're on 32-bit (or the reverse), the embedded Data Model engine version won't match — and it will refuse to load.

The fix is straightforward: switch to the same bitness. From the Microsoft 365 portal or Office installer, choose Advanced options, select 64-bit, and uninstall the current version first.

# Verify installed Office bitness via registry (PowerShell)
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' |
  Select-Object Platform

Output will show x86 or x64. Worth noting: 32-bit Excel has a hard 2 GB memory cap that breaks any large Data Model anyway, so 64-bit is the right call regardless.

Step 3: Clear the Power Pivot temp files

The Analysis Services engine writes temp files on every startup. If those files are locked or corrupted from a previous crash, the engine fails without telling you why.

• Close Excel completely. Open Task Manager and kill any lingering EXCEL.EXE or msmdsrv.exe processes.
• Delete the contents of these two folders (leave the folders themselves in place):

%LOCALAPPDATA%\Microsoft\Power Pivot for Excel
%TEMP%\Microsoft\Excel

In PowerShell:

Remove-Item "$env:LOCALAPPDATA\Microsoft\Power Pivot for Excel\*" -Recurse -Force
Remove-Item "$env:TEMP\Microsoft\Excel\*" -Recurse -Force -ErrorAction SilentlyContinue

Reopen Excel and test.

Step 4: Run Office Quick Repair

Add-in enabled but the engine still refuses to load? A botched Office update is the likely culprit — a missing or overwritten DLL that Excel can't find at runtime.

• Close all Office apps.
• Open Control Panel → Programs → Programs and Features.
• Right-click Microsoft Office (or Microsoft 365) → Change.
• Select Quick Repair → Repair. Takes 2–5 minutes. No internet required.

If Quick Repair doesn't help, go with Online Repair instead — it fully reinstalls Office components while keeping your settings and activation intact.

# Alternatively, trigger repair via command line (run as Admin)
cscript "C:\Program Files\Common Files\microsoft shared\OFFICE16\Office Setup Controller\setup.exe" /repair ProPlusRetail.WW

Step 5: Re-register the Power Pivot DLL manually

Occasionally the COM registration for the add-in breaks independently of the DLL itself. Open an elevated Command Prompt:

cd "C:\Program Files\Microsoft Office\root\Office16\ADDINS\PowerPivot Excel Add-in"
regsvr32 PowerPivotExcelClientAddIn.dll

A success dialog means the registration is fixed. If you see The module failed to load, the DLL itself is gone or damaged — skip ahead to Online Repair.

Step 6: Check Windows Event Log for the real error

Excel's dialog hides what actually went wrong. The Analysis Services engine logs its startup failures to Windows Event Log — that's where the real error message lives.

• Open Event Viewer (Win + R → eventvwr.msc).
• Go to Windows Logs → Application.
• Filter by Source: MSSQLServerOLAPService or PowerPivot.
• Find errors timestamped around when Excel crashed.

Common messages and what they point to:

• File system error: Access is denied → temp folder permissions. Fix: take ownership of %LOCALAPPDATA%\Microsoft\Power Pivot for Excel.
• Version mismatch → bitness or patch mismatch. Fix: Office repair (Step 4).
• Cannot load xmsrv.dll → missing Visual C++ runtime. Install the Visual C++ 2015-2022 Redistributable — both x86 and x64 versions.

Confirming the fix

Once you've applied a fix, run through this checklist before calling it done:

• Open the affected workbook.
• Click Power Pivot → Manage. The Power Pivot window should open with your tables visible.
• In the Power Pivot window, click Refresh (Home tab) to pull fresh data.
• Back in Excel, right-click a PivotTable → Refresh. It should complete without error.
• Add a test measure to confirm the DAX engine is responsive:

-- Test DAX in Power Pivot Measures
Test Measure:=COUNTROWS(Sheet1)

If the measure evaluates and returns a row count, the engine is working correctly.

Preventing this in the future

• After any Excel crash, check your add-ins first. Excel quietly disables COM add-ins that caused a crash. Don't assume the data is gone — your model is probably fine, the add-in just got turned off.
• Standardize on 64-bit Office across your team. Mixed bitness is the second most common cause of this error. Beyond that, 32-bit Excel's 2 GB memory cap will eventually break any non-trivial Power Pivot model.
• Stay current on Office patches. Several engine startup bugs from 2019–2022 were fixed in later updates. Use File → Account → Update Options → Update Now to check.
• Back up workbooks before major Windows feature updates. Version upgrades (e.g., 22H2 → 23H2) occasionally break COM add-in registrations — it's infrequent, but it happens.