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

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
WATYF
Helper II
Helper II

All Gateway-related API calls failing with 404 error

I recently moved my On-premises Gateway to a new machine. After that, all API calls I made which related to Gateways started failing. It doesn't matter which one I do (/gateways, GetBoundGatewayDataSources, BindToGateway, etc), it always returns this error: The remote server returned an error: (404) Not Found.

 

The same code worked fine the day before on the old machine. And I can still perform all of the other API calls that I use (/refreshes, /takeover, /datasets, etc). It's just anything having to do with a Gateway that fails now.

 

I transferred the Gateway using the recovery key and refreshes are working successfully. I just don't know why these API calls are failing.

 

Any ideas what could cause this?

0 REPLIES 0

Helpful resources

Announcements
Sept PBI Carousel

Power BI Monthly Update - September 2024

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

September Hackathon Carousel

Microsoft Fabric & AI Learning Hackathon

Learn from experts, get hands-on experience, and win awesome prizes.

Sept NL Carousel

Fabric Community Update - September 2024

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

Top Solution Authors