User getting An operation that uses the database driver could not be completed Message

Hi chudson 
The error “An operation that uses the database driver could not be completed” when refreshing a Power BI-connected Excel workbook (especially one linked to Power BI datasets online) almost always means something has broken in the user’s Power BI connector chain / authentication cache rather than a true OLEDB driver problem.

What’s actually happening

When Excel connects to a Power BI dataset, it uses the Power BI XMLA / Analysis Services endpoint through the MSOLAP / Power BI connector.

The “database driver” mentioned in the error is MSOLAP (not Microsoft Query, despite the message wording).
If one of these things goes wrong, you get the message you saw:

1. Corrupt local Power BI connection cache

2. Conflicting MSOLAP provider versions

3. Broken Power BI credentials token (causes endless sign-in loop)

Excel version mismatch with Power BI add-ins (post-update regression)

Step-by-Step Fix Checklist

1. Clear Power BI and Office credential cache

Ask the affected user to:

1. Close Excel.

2. Open Windows Credential Manager → Windows Credentials.

3. Delete any entries starting with:

   • MicrosoftOffice16_Data:ADAL:,

   • Microsoft.PowerBI, or

   • Analysis Services.

4. Then reopen Excel and reconnect — it’ll prompt for fresh sign-in.

This alone fixes most sign-in loops and “database driver” errors.
Clear Excel’s connection cache
C:\Users\<username>\AppData\Local\Microsoft\Power BI Desktop\AnalysisServicesWorkspaces\
and
C:\Users\<username>\AppData\Local\Microsoft\Office\16.0\Power BI Desktop Cache

Delete the contents of those folders (Excel and Power BI will rebuild them).

Also check:
%localappdata%\Microsoft\Office\16.0\PowerBI\

3. Re-register the MSOLAP provider

Even if it’s installed, re-registering helps if the registry binding broke after Office updates.

Run (as admin, in CMD):
cd "C:\Program Files\Microsoft Analysis Services\AS OLEDB\190"
regsvr32 msolap190.dll

Adjust 190 to your version folder (180, 191, etc.) depending on your Excel/Office build.

Then reboot Excel.

Reset Power BI connection metadata in Excel

In Excel:

• Go to Data → Get Data → Data Source Settings → Global Permissions

• Find any entries for app.powerbi.com or your Power BI dataset URL

• Remove them → OK → Reconnect from scratch

When reconnecting, choose “Microsoft account” as the auth method.

Verify matching MSOLAP provider versions

On working and non-working machines, check:

1. In Excel → Data → Get Data → Data Source Settings → Power BI

Or in Windows: “Add/Remove Programs” → look for Microsoft Analysis Services OLE DB Provider for Microsoft SQL Server (MSOLAP).
If the affected user has an older or newer build than others, uninstall and reinstall from Microsoft’s site (latest: MSOLAP.8 or MSOLAP.190).

Check Excel updates

Sometimes a specific Office update breaks the Power BI connector temporarily.

1. Make sure Excel is on a Current or Monthly Enterprise Channel version that matches other working users.

If the issue started “last week,” it could coincide with a new Office build — try rolling back one version to test.

Last resort: rebuild the connection (not the whole workbook)

You don’t need to rebuild all pivots.
You can:

1. Save a copy of the workbook.

2. In Data → Queries & Connections, delete the broken Power BI dataset connection.

3. Re-add the connection via Get Data → Power BI Datasets.

4. Repoint existing PivotTables to the new connection (Data → Change Data Source → Choose new dataset).

This keeps your pivot structures and formulas intact.

Did I answer your question? Mark my post as a solution! Appreciate your Kudos !!