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

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

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
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.

ArunFabCon

Microsoft Fabric Community Conference 2025

Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.