The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
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?
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.