Forum Discussion
Gateway - PBI Services Connection Issue
Hi saimnaveed,
Sorry to know it didn’t help. Please consider reaching out to Microsoft Support. You can provide them with all the troubleshooting steps you've already taken, which will help them understand the issue better and provide a resolution. They might be able to identify something specific about your admin account setup or provide a solution that isn't immediately obvious.
Below is the link to create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Thank you
Here are a few steps and considerations that might help resolve the issue:
Network Configuration: Ensure that the security group of your Redshift cluster allows inbound traffic from the EC2 instance where the Power BI gateway is installed. This includes allowing the necessary port (default is 5439 for Redshift) and the correct IP range.
Gateway Configuration: Verify that the Power BI gateway is correctly configured to handle the Redshift connection. Since the connection works with a network load balancer endpoint but not directly with the Redshift endpoint, there might be a network routing or DNS resolution issue.
DNS Resolution: Ensure that the EC2 instance can resolve the DNS name of the Redshift cluster. You can test this by running a simple nslookup or ping command from the EC2 instance to the Redshift endpoint.
Power BI Service: Sometimes, Power BI service might take some time to reflect new connections. However, waiting for 1-2 days is unusual. Ensure that the Power BI service is updated and there are no pending updates or issues on the Power BI service side.
Connection String: Double-check the connection string and credentials used for the Redshift connection. Ensure that they are correct and have the necessary permissions.
Logs and Diagnostics: Check the logs on the Power BI gateway for any errors or warnings that might give more insight into why the connection is not becoming available. The logs can often provide detailed information about what might be going wrong.
Alternative Approach: As a workaround, since the connection works with the network load balancer endpoint, you might consider using this setup if it meets your requirements. Ensure that the load balancer is properly configured to handle the traffic and that it does not introduce any latency or performance issues.
dns settings of vpc are enabled, security group of ec2 has all relevant rules, redshift sg allow inbound traffic from vpc, tried using ping and nslookup on ec2 instance on which pbi gateway is installed and in both ways it was not able to resolve the redshift cluster endpoint.
Whats the reasons for this anamolous behavior and how it can be resolved effectively?Hi saimnaveed,
A few different scenarios could be responsible for this error:- The server and database name don't match what was entered in Power BI Desktop and the data source configured for the gateway. These names must be the same. They aren't case sensitive.
- Your account isn't listed in the Users tab of the data source within the gateway configuration. You need to be added to that list by the administrator of the gateway.
- Your Power BI Desktop file has multiple data sources within it, and not all of those data sources are configured with the gateway. You need to have each data source defined with the gateway for the gateway to show up within semantic model.
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS.
Thanks and Regards
