Forum Discussion
On-Premise Gateway Issues
Hi,
Have decided to deploy Power BI and On-Premise Gateway. Have researched them both.
Downloaded the gateway and installed. Created a free account online. The gateway and data source are configured, but nothing ever uploads. I have a few questions:
- I'm pulling data from SQL Express. Can I use SQL Express as the source of my data?
- I'm using a free online Power BI account. I understand I can use this with the On-Premise Gateway?
- The gateway's diagnostic Network Ports Test clearly states: "Note: If one or more tests failed, contact your network administrator to open the ports for the required servers.". With the exception of two servers the test works fine, but my interpretation of the above statement from Microsoft means that a failure is a failure. The two tests that fail are in a different subnet to the ones that work. They are the last two shown here:
g30-prod-am3-007-sb.servicebus.windows.net 52.174.145.97 Success
g31-prod-am3-007-sb.servicebus.windows.net 52.174.144.205 Success
g34-prod-am3-007-sb.servicebus.windows.net 40.91.213.8 FAILED
g38-prod-am3-007-sb.servicebus.windows.net 40.91.212.84 FAILED
Breaking this some more:
Server Name: g30-prod-am3-007-sb.servicebus.windows.net IP Address: 52.174.145.97
Port 443 : Open
Port 5671 : Open
Port 5672 : Open
Port 9350 : Open
Port 9351 : Open
Port 9352 : Open
Port 9353 : Open
Port 9354 : Open
Server Name: g31-prod-am3-007-sb.servicebus.windows.net IP Address: 52.174.144.205
Port 443 : Open
Port 5671 : Open
Port 5672 : Open
Port 9350 : Open
Port 9351 : Open
Port 9352 : Open
Port 9353 : Open
Port 9354 : Open
Server Name: g34-prod-am3-007-sb.servicebus.windows.net IP Address: 40.91.213.8
Port 443 : Open
Port 5671 : Closed
Port 5672 : Closed
Port 9350 : Closed
Port 9351 : Closed
Port 9352 : Closed
Port 9353 : Closed
Port 9354 : Closed
Server Name: g38-prod-am3-007-sb.servicebus.windows.net IP Address: 40.91.212.84
Port 443 : Open
Port 5671 : Closed
Port 5672 : Closed
Port 9350 : Closed
Port 9351 : Closed
Port 9352 : Closed
Port 9353 : Closed
Port 9354 : Closed
I have checked firewalls and anti-virus. What's interesting is that if I test the ports above from a source external to where I am working, the ports are listed as being blocked.
Can anybody help me? Power BI and the On-Premise Gateway offered great prospects. As of yet, I have not managed to the solution working.
David
Looks like we got this sorted. We'd followed some instructional videos on YouTube but they don't make the process clear.
We had created the Gateway and Data Source. What was not apparent is that this would not create the dataset. We expected from what had been demonstrated in the videos that it would.
Instead the report creator needs to open Power BI Desktop and connect (on-site or remotely using VPN) to the SQL server. They then create the report. When done they publish it to the Power BI service online. When this is done the report is available via the Power BI service online. The dataset is also created. It is important to alter the dataset at this point to select the gateway that is used to refresh it. Once we had done this we not only had the dataset but we were able to refresh the data.
Thanks all for your input.
20 Replies
Some of the issues I have been experiencing appear not to be local. I did some additional testing lastnight and the Network Ports Test succeeded whereas it had failed persistently before. I tested this again this morning and the same test now fails again.
If I check the listed server port from an off-site source, I find the port on the Microsoft server is listed as closed:
Hi OLoughanD,
It looks like the connection is blocked by firewall. You can confirm this problem by by running Test-NetConnection from a PowerShell prompt. If that is the case, you may need to whitelist (unblock) the IP addresses, for your data region, in your firewall.
Best regards,
Yuliana Gu
Hi Yuliana,
Thanks for your message. We don't think it is anything to do with firewalling. We disabled various functionality to check and the result stayed the same. We also re-ran the Network Ports test and we have had it work perfectly during some tests. Yet at other times it does not work. It is always the same last two servers that fail. This kind of behaviour does not indicate the firewall is the issue.
Regards!
- You could always try and force it over HTTPS to see if that initially resolves your error.
If that does then you know it has to do with additional ports that will be required to be opened.
