March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe 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
I'm traying to use the gateway, but this error appears:
Your gateway is configured correctly but is unreachable due to local network connectivity
Ensure "{0}" is running in the Services control panel.
The old personal gateway was working perfectly, but the Power BI web send me a message to update to the new On-premises data gateway (personal mode), but ir does not works. The strange fact is that I tryed to install On-premises data gateway (enterprise mode) and it works, the only one that does not works is the personal mode. The organization that I work uses proxy, so using the old personal or the new on-premises enterprise I have to configure the service "Log On As" to use my AD user, but new personal mode does not have a service. So how can I fix my problem?
This is my Gateway.log file and this is my GatewayConfigurator.log.
Solved! Go to Solution.
Hi @Anonymous,
Typically this is caused by a firewall blocking Service Bus. You can confirm by using the following
The gateway is configured to use the default proxy settings, however many organizations only proxy port 80 and 443. Since Service Bus uses different ports by default, start by forcing Service Bus to use port 80 or 443. Keep in mind the on-premises data gateway (personal mode) is typically installed under "%localappdata%\Microsoft\On-premises data gateway (personal mode)".
After enabling changing the configuration file, you will need to kill the on-premises data gateway (personal mode) process (Microsoft.PowerBI.DataMovement.PersonalGateway.exe) and relaunch the configurator.
Best Regards,
Qiuyun Yu
Since I recently encountered this problem and none of the suggested solutions worked for me, I want to share what ultimately resolved it.
I changed the user under which the service was running, and voila, it worked. After that, I was able to switch back to the original user, and it still worked. It seems the gateway needed to be re-registered in the service.
How did you identify and fix that?
Thank you everyone for your comments and suggestions.
Now I'm already solved my issue by MS Support Team, after they found that TLS Certification on my Gateway doesn't install correctly.
My Org dosn't have a Proxy.
Thank you, I've tried but it's doesn't work.
Hi @Anonymous,
Typically this is caused by a firewall blocking Service Bus. You can confirm by using the following
The gateway is configured to use the default proxy settings, however many organizations only proxy port 80 and 443. Since Service Bus uses different ports by default, start by forcing Service Bus to use port 80 or 443. Keep in mind the on-premises data gateway (personal mode) is typically installed under "%localappdata%\Microsoft\On-premises data gateway (personal mode)".
After enabling changing the configuration file, you will need to kill the on-premises data gateway (personal mode) process (Microsoft.PowerBI.DataMovement.PersonalGateway.exe) and relaunch the configurator.
Best Regards,
Qiuyun Yu
Thank you, @v-qiuyu-msft. I changed ServiceBusSystemConnectivityModeString to Https instead of AutoDetect on Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config. Before oppening this question I was already doing so, the problem is that I was not restarting the proccess - Microsoft.PowerBI.DataMovement.PersonalGateway.exe.
<setting name="ServiceBusSystemConnectivityModeString" serializeAs="String">
<value>Https</value>
</setting>
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.