Storing data source credentials times out

[hellopath]

I'm experiencing the following problem:

- We created an Azure SQL database and put some dummy data in.

- In Power BI Desktop we add the data source and create a sample report.

- We publish to Power BI service.

- In the browser, we can look at the report. But when we try to refresh the data source, it tells us that our credentials are wrong.

- Now, when I try to enter the credentials, nothing happens for many minutes and it appears to time out.

Does anyone have an idea for what could be causing this issue?

[Anonymous]

Hi @hellopath,

Can you please share more detail information to help us clarify your scenario, please refer to below link:

Troubleshooting the On-premises data gateway

Spoiler

Tools for troubleshooting

Collecting logs from the gateway configurator

There are several logs you can collect for the gateway, and you should always start with the logs. The simplest way to collect logs after installing the gateway is through the user interface. In the On-premises data gateway user interface, select Diagnostics and then select the Export logs link near the bottom of the page, as shown in the following image.

Installer logs

Copy

%localappdata%\Temp\On-premises_data_gateway_*.log

Configuration logs

Copy

%localappdata%\Microsoft\On-premises Data Gateway\GatewayConfigurator*.log

On-premises data gateway service logs

Copy

C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises Data Gateway\Gateway*.log

Event Logs

The On-premises data gateway service event logs are present under Application and Services Logs.

Fiddler Trace

Fiddler is a free tool from Telerik that monitors HTTP traffic. You can see the back and forth with the Power BI service from the client machine. This may show errors and other related information.

Refresh History

When using the gateway for scheduled refresh, Refresh History can help you see what errors have occurred, as well as provide useful data if you should need to create a support request. You can view both scheduled, as well as on demand, refreshes. Here is how you can get to the Refresh History.

1. In the Power BI navigation pane, in Datasets, select a dataset > Open Menu > Schedule Refresh.

   

2. In Settings for... > Schedule Refresh, select Refresh History.

   

   

Regards,

Xiaoxin Sheng

[hellopath]

Hello and thanks!

We're not using the On-premises data gateway. As mentioned in the On-premises data gateway FAQ , the gateway is not required for Azure SQL Database.

[Anonymous]

Hi @hellopath,

I can update credentials on my side, maybe you can submit a support ticket with trace session (signin credential) as detailed contents.

Support ticket:

submit a support ticket

Regards,
Xiaoxin Sheng

[hellopath]

Hi and thanks! I have already created a support ticket. So far we're still looking for a solution.

[hellopath]

Just a quick status update: The error is still persisting. Support has been difficult to use. PowerBi remains unusable for us in the meantime.

[Anonymous]

HI @hellopath,

In fact, it seems like a known issue which appears on azure data source. Power bi team is working on it, next update timet @06/07/2018 22:00 UTC.

Users may not be able to set credentials if they are using OAuth2 for SQL Azure or AS Azure data sources. Engineers are aware of the issue and are working on a fix . Next Update @06/07/2018 22:00 UTC.

Regards,

Xiaoxin Sheng

[hellopath]

Thank you for confirming this! I would like to add a note though, that as far as I'm aware, we're not using OAuth2 to authenticate. At least I'm not aware of activating it myself.

[hellopath]

Is there an update on when this is expected to get fixed?

[Anonymous]

HI @hellopath,

Actually this known issue has been fixed. Based on test, azure sql datasource still works on my side, it should be issue appears on particular device or database.

Regards,

Xiaoxin Sheng

[hellopath]

The issue was that we separated the port with a colon (industry standard) instead of a comma. PowerBi Desktop accepted the colon without complaining, PowerBi online did not.