Cannot Update Data Source Credentials

[barmstr]

Hi,

I'm using Paginated Reports with the Power BI Data Gateway, which pulls data from SQL Server running on an Azure VM.

This configuration was working fine up to a few days ago when we had to change the password of the Account that's used to bind the Gateway to our Tenant.

We have two Data Sources configured for SQL Server (against two different databases).

Both Data Sources show as being Online in powerbi.com, but when I try to run any report which uses either Data Source, I get the error:

An unexpected error occurred
Could not connect to the data source.
Timestamp: 2022-09-05T09:14:04.888Z
Root activity ID: 7bd6f628-d8ff-5310-4c00-8246dabf3e2f
Session ID: 000006941a844658b2601009bd73d26c
Tenant ID: 9fc0bf3f-3dfc-4354-9c39-0d75300fdcac
Cluster: https://wabi-north-europe-l-primary-redirect.analysis.windows.net/
Report ID: 4cce0fa6-4f5e-4602-bfbd-35f46d1be86c
ReportViewerVersion: 2022.8.4.2862

If I try to update the Data Sources to use the updated password (or if I add a new Data Source), the Settings tab just hangs with the status "Loading". It never returns an error message.

Does anyone know:

1. Is this related to a known issue at the moment with the Data Gateway?
2. Is it possible to enable additional logging to get more detail on why the Data Source won't update correctly when I change the password?

Thanks very much for your help.

[GilbertQ]

Hi @barmstr 

What you could do is to make sure you have got the latest version of the gateway installed?

Also you can use this link below to get additional logging on the Gateway: Troubleshoot the on-premises data gateway | Microsoft Docs

Also what happens if you try and log into the SQL Server from the VM where the gateway is installed does that successfully connect?

[barmstr · Accepted solution]

In the end I logged this with Microsoft Support. When I had a call with their customer support agent, changing the Data Source credentials worked fine. She suggested that this was a known issue this week with the Data Gateway. 

I'd suggest contacting MS Support directly if anyone else comes across this issue.