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

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Reply
Anonymous
Not applicable

Dataflow refresh Failed AzureBlobs failed to get the response:The remote name could not be resolved

 

Dataflow refresh Failed  "DataSource.Error: AzureBlobs failed to get the response: The remote name could not be resolved 'wabiindcenapcdsa.blob.core.windows.net''.

 

data Source connects on-premises through Gateway M/c.

 

After manual Refresh, It Refreshes but why this problem Occur

 

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

Hi @Anonymous ,

 

In the past, users have opened support tickets for this issue with Microsoft's dedicated support team.
After investigation and troubleshooting, the support team found that this was due to the gateway/virtual machine not being able to access several IPs.

 

You can use Telnet or ping commands on the server machine where the gateway is installed to test some ip.
From the gateway machine, try to establish a telnet connection to port 443 on each host.
Troubleshoot the gateway as suggested above and ask your Network admin team to whitelist IPs.

 

You can check the OP shared solution at that time in this thread.

 

Hope it helps,


Community Support Team _ Caitlyn

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

 

View solution in original post

3 REPLIES 3
v-xiaoyan-msft
Community Support
Community Support

Hi @Anonymous ,

 

In the past, users have opened support tickets for this issue with Microsoft's dedicated support team.
After investigation and troubleshooting, the support team found that this was due to the gateway/virtual machine not being able to access several IPs.

 

You can use Telnet or ping commands on the server machine where the gateway is installed to test some ip.
From the gateway machine, try to establish a telnet connection to port 443 on each host.
Troubleshoot the gateway as suggested above and ask your Network admin team to whitelist IPs.

 

You can check the OP shared solution at that time in this thread.

 

Hope it helps,


Community Support Team _ Caitlyn

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

 

Anonymous
Not applicable

"@Gilb"@GilbertQ

 

 

Hi @Anonymous 

 

Just to confirm it works when you do a manual refresh in Power BI Desktop but not via the Gateway?





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

Helpful resources

Announcements
LearnSurvey

Fabric certifications survey

Certification feedback opportunity for the community.

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

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

Top Solution Authors
Top Kudoed Authors