PowerBI gateway enables Enterprises to connect to their on-premises data sources without having to setup any VPN or open firewall ports. Since the Power BI gateway uses “HTTPS” protocol, the service can be consumed over the internet without opening any firewall ports.
Also Read: PowerBI Interview Questions & Answers
However, the installation itself can sometimes give issues. In order to ensure that the entire implementation goes smoothly, we have collated a list of best practices. Read along to know.
The Power BI Gateway is a Windows based application which allows you to connect to your on-premises data source. Typically, you would need to install the application on an always-on server machine in the same network where your data sources reside which you would need to connect. Power BI has become popular in the BI world, and a lot of users use the gateway app.
During the process of using the Gateways, Users have faced issues either installing or trying to connect to a data source. In this post, I am going to talk about how to create troubleshoot and resolve PowerBI gateway issues.
Quick Note: Always Use Event Logs>Applications and Services Logs>Power BI Enterprise Gateway Service for debugging.
Sometimes, the older version of the gateway might preserve the configuration files which need to be removed. Here are the simple steps to remove them:
Step 1: Go to command prompt and issue the following command:
net stop PBIEgwService
Step 2: Uninstall the Enterprise or Personal gateway from “Programs and Features.”
Step 3: Delete the installation directory folder
c:Program FilesPower BI Enterprise Gateway
c:Program FilesPower BI Personal Gateway
Run the following Power-Shell script:
Test-NetConnection -ComputerName powerbicomp.servicebus.windows.net -Port 9350
The result should be correct, else check the connection settings.
ComputerName : powerbicomp.servicebus.windows.net
RemoteAddress : 22.214.171.1241
RemotePort : 5672
InterfaceAlias : vEthernet (Broadcom NetXtreme Gigabit Ethernet - Virtual Switch)
SourceAddress : 10.120.60.108
PingSucceeded : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : True
Comments are closed.