Forum Discussion
On-premises data gateway (personal mode) not connecting.
- 9 years ago
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
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
- Anonymous9 years agoNot applicable
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>