"An operation that uses the database driver could not be completed. If the driver is a Microsoft driver, make sure the driver file isn't damaged, and if it is, reinstall the driver by reinstalling Microsoft Query."

Question

One of the users receive this error. is this issue at our end or at microsofts ?

Answer 1

Let's see what the cause could be. The following are a few things you can try:

1. Try to temporarily disable Windows Firewall or any security software on the computer used by that user, and try again.
2. Make sure you can access Azure data sources from other tools on the same computer like SQL Server Management Studio and Azure Data Studio. Try to connect from other hosts on your organization. Sometimes new corporate firewall rules or policies may block access to Azure data sources or temporary health issues of Azure resources.
3. Sometimes the document the user is using needs to be trusted. Please read here.
4. Sometimes reinstalling OLEDB or ODBC drivers or using the latest versions of those drivers may do the trick.
5. Close open documents and restart the computer.

Answer 2

I see this post was never updated. I have, or better, everyone in the company has this issue:

The file has a connection to an Azure Analysis Services server that uses the authenticated user to log on:

The problem is, when opening this file after rebooting, the error occurs and even though the connection is saved in the file, we have to go through the connection wizard again to be able to use the pivot tables. It has nothing to do with the drivers.

Could the issue lie in the configuration of the server user mapping?

When creating the connection through Power Query, the connection would work only when selecting the 'Microsoft Account' option, for which we use the same user and password as the 'Windows Credentials', but when trying to use the latter as the connection option, it fails.

Any insights? This issue has been ongoing for month and no one seems to find a solution.