The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
Hi,
When maintaining the data source/scheduling settings for our AWS database, we are getting the below error. The credentials are correct for sure, because we are able to import data (it connects without any issue through desktop). But when setting it up via the service, it doesn't want to work. Could anyone please help us with this? I tried to raise a ticket for it as well, but it won't accept my account (powerbi.microsoft.com needs permission to access resources in your organization that only an admin can grant. Please ask an admin to grant permission to this app before you can use it.). Thank you all.
Solved! Go to Solution.
Hi @e_vera
1. Was on-premise data gateway installed on the same machine as SQL Server database hosted?
For reference, you could have a view of this similar thread which has been solved.
2. If you already have updated the gateway to the latest version, then you can refer to steps below for troubleshooting.
1). Check if the server is using a proxy and the proxy. Some proxies restrict traffic to only ports 80 and 443. By default, communication to Azure Service Bus will occur on ports other than 443.
2). You can force the gateway to communicate with Azure Service Bus using HTTPS instead of direct TCP. You will need to modify the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file. Change the value from AutoDetect
to Https
. This file is located, by default, at C:\Program Files\On-premises data gateway.
3). Restart the gateway and check if the issue persists.
To stop the service, run this command:
''' net stop PBIEgwService '''
To start the service, run this command:
''' net start PBIEgwService '''
4). You may export the data gateway log by selecting Diagnostics and then selecting the Export logs link near the bottom of the page. Reference: https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem-tshoot#tools-for-troubleshooting.
If the issue is very urgent, I would suggest you to create a support ticket to achieve deeper help.
Hi @e_vera
1. Was on-premise data gateway installed on the same machine as SQL Server database hosted?
For reference, you could have a view of this similar thread which has been solved.
2. If you already have updated the gateway to the latest version, then you can refer to steps below for troubleshooting.
1). Check if the server is using a proxy and the proxy. Some proxies restrict traffic to only ports 80 and 443. By default, communication to Azure Service Bus will occur on ports other than 443.
2). You can force the gateway to communicate with Azure Service Bus using HTTPS instead of direct TCP. You will need to modify the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file. Change the value from AutoDetect
to Https
. This file is located, by default, at C:\Program Files\On-premises data gateway.
3). Restart the gateway and check if the issue persists.
To stop the service, run this command:
''' net stop PBIEgwService '''
To start the service, run this command:
''' net start PBIEgwService '''
4). You may export the data gateway log by selecting Diagnostics and then selecting the Export logs link near the bottom of the page. Reference: https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem-tshoot#tools-for-troubleshooting.
If the issue is very urgent, I would suggest you to create a support ticket to achieve deeper help.
Very likely a firewall issue.
Also, You could check the Issues forum here:
https://community.powerbi.com/t5/Issues/idb-p/Issues
And if it is not there, then you could post it.
If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".