Forum Discussion
Unable to update gateway
I have an on-prem data gateway with two cluster members. They are currently running version October 2024 and need to be updated. I've tried to update to September 2025, but cannot get the service portal to show a version number change or successfully Sign On to the gateway config panel on the gateway server.
When updating, the install progress bar goes to the end, but never completes. I let it sit for 8 hours and then pressed the close button to proceed.
The gateway app on the server shows a new version number of Sep 2025. I reboot and also try restarting the service in services.msc and the config.
When I attempt to sign on, I get this error if the cluster member is disabled: This gateway is disabled. This gateway cluster member is disabled. Please uninstall the application and install the latest Gateway release to restore this gateway instance.
If the member is enabled, I get this error: PowerBIGateway02 is configured correctly but is unreachable due to local network connectivity problems.
If I uninstall and reinstall, I get the same behavior.
In the portal, I can enable the updated member, but it doesn't show an updated version number. It does test SSO connections successfully and seems to be working.
I have a VMWare snapshot and have tried the install/uninstall process a few times with the same outcome.
I just updated both gateway members and the process was successful. I was able to log in. The version number updated in the portal after a few minutes. We were running an out of support version and the update increased the refresh speed by quite a bit. Thanks for your help.
4 Replies
Hi samgreene1 ,
Is this happening on both of the members or just one?
Some fixed might be that after doing the install and it just hangs. Go into the services and restart the gateway service and clear the browser cache and then take a look at the version that it is showing. It is possible that it actually did do an update and just hung at some point. (Which sound like what you did already.)
Then, make sure that BOTH gateways are updated to the same version. They will get out of sync if one version is different than the other. It might be that you have to temporarily turn one of the members off (stop the service or however you want). Then, make sure that the one is working.
For the account, make sure that it is domain level with full admin rights.
Also, you should confirm that the network is working as expected, you can test that with a TEST-netconnection in PowerShell for example and make sure that ports 443, 5671–5672, and 9350–9354 are open.
Let us know the results of that effort!Hi samgreene1 ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you collinq for the prompt response.
I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.
Thank you.
I just updated both gateway members and the process was successful. I was able to log in. The version number updated in the portal after a few minutes. We were running an out of support version and the update increased the refresh speed by quite a bit. Thanks for your help.
Hi samgreene1 ,
Thank you for the update and let us know if you need any further assistance, if not kindly accept the response that helped in solving the issue or guided you towards the resolution as the accepted solution. This will helps others in the community who may face a similar problem to find the answer more easily.
