Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.

Reply
Anonymous
Not applicable

Gateway Connection Map to Server keeps dropping

I keep having to go into several reports that were fine and fixing the Gateway Connection.

 

The steps are:

DataSet settings

-> expand Gateway Connection

-> click Actions down arrow

-> where it says:  Data Sources included in dataset:

SqlServer {"server": "<myserver>", "database": "<mydbname>"}  Maps to:

-> there are 2 options here,  my configured server and "Add to Gateway"

-> I always select my configured server

-> then hit apply

-> then refresh and scheduled refreshes work again

 

Has anyone ran into this, not sure how to fix it so this doesnt keep happening.

 

With dozens of reports its extremely time consuming to have to go and manually refresh reports constantly.

 

Appreciate any help!

1 ACCEPTED SOLUTION
v-yuta-msft
Community Support
Community Support

@Anonymous ,

 

So based on your description, the gateway seems to be running on your sever without any problems, right? Have you disabled some port in the firewall of server?

 

 The gateway creates an outbound connection to Azure Service Bus. It communicates on outbound ports: TCP 443 (default), 5671, 5672, 9350 thru 9354. The gateway does not require inbound ports.

 

It is recommended that you whitelist the IP addresses, for your data region, in your firewall. You can download the Microsoft Azure Datacenter IP list. This list is updated weekly. The gateway will communicate with Azure Service Bus using the IP address along with the fully qualified domain name (FQDN). If you are forcing the gateway to communicate using HTTPS it will strictly use FQDN only, and no communication will happen using IP addresses. 

 

Regards,

Jimmy Tao

View solution in original post

2 REPLIES 2
v-yuta-msft
Community Support
Community Support

@Anonymous ,

 

So based on your description, the gateway seems to be running on your sever without any problems, right? Have you disabled some port in the firewall of server?

 

 The gateway creates an outbound connection to Azure Service Bus. It communicates on outbound ports: TCP 443 (default), 5671, 5672, 9350 thru 9354. The gateway does not require inbound ports.

 

It is recommended that you whitelist the IP addresses, for your data region, in your firewall. You can download the Microsoft Azure Datacenter IP list. This list is updated weekly. The gateway will communicate with Azure Service Bus using the IP address along with the fully qualified domain name (FQDN). If you are forcing the gateway to communicate using HTTPS it will strictly use FQDN only, and no communication will happen using IP addresses. 

 

Regards,

Jimmy Tao

Anonymous
Not applicable

Hey Jimmy,

 

The gateway will run for a while with no problems but then randomly a scheduled refresh stops working. As I investigate, the Gateway Connection shows an error, and the fix is always simply to click on the Gateway settings and reset the "maps to" drop down option and click apply, then it's good. Here's a video link showing how I resolve, it happens randomly to random reports, so far I haven't found a pattern as to why it happens.

 

https://drive.google.com/file/d/1uZEKpKc4trEgS_NX_nO6vmVxiPLqDQJM/view

 

But basically, I do the fix above, then all is well for a while, until I see the scheduled refresh error and have to reset it again.

 

Also, would like to mention we don't use the internet for our connection, its completely local so I'm not sure if outbout ports would be an issue here.

 

Let me know if I can provide any additional information!

 

Thanks again for looking into this!!

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.