Cloud and Vnet gateway

[vinayganit]

My on premise gateway is online and working my redshift connection is also online and working. But the gateway connection to my dataset is showing not configured correctly. The settings gets me in to an option of creating a nw connection . But even after creating that the gateway connection toggle goes automatically off and same configuration issue is staying. What should I do to make the configuration set up correctly? 

[Shravan133]

If your Power BI service is showing that the on-premises gateway connection to your Redshift dataset is not configured correctly, and even after setting up a new connection the issue persists, here are some steps to troubleshoot and resolve the problem:

1. Verify Gateway Installation and Configuration

1. Check Gateway Status:

   • Ensure that the on-premises data gateway is properly installed and running on the server. You can check this in the On-premises data gateway app installed on your machine.

2. Update Gateway:

   • Make sure your gateway is up to date. Outdated gateways might cause issues with connectivity and configuration.

3. Restart the Gateway:

   • Try restarting the gateway service on your machine. Sometimes, a simple restart can resolve connection issues.

2. Check Data Source Settings in Gateway

1. Verify Connection in Gateway:

   • Go to the Power BI Service > Settings > Manage gateways.
   • Select your gateway and check the data source settings for your Redshift connection.

2. Reconfigure Data Source:

   • Remove the existing Redshift data source from the gateway.
   • Add a new data source with the correct configuration. Ensure you enter the correct server name, database name, and authentication details.

3. Check Gateway Configuration in Power BI Service

1. Navigate to Dataset Settings:

   • In the Power BI service, go to the workspace where your dataset is published.
   • Click on the Settings gear icon next to your dataset.

2. Configure Data Source Credentials:

   • Under Data source credentials, ensure that the credentials used for Redshift are correct.
   • If credentials are correct but the connection toggle still turns off, try re-entering the credentials and saving.

4. Check Redshift Configuration

1. Verify Redshift Endpoint:

   • Ensure that the Redshift endpoint is correct and accessible from the machine where the gateway is installed.

2. Check Network and Firewall Settings:

   • Ensure that the firewall settings on your network or Redshift cluster allow connections from the IP address of the gateway server.

5. Review Gateway Logs

1. Check Gateway Logs:

   • You can find logs in the gateway’s installation directory. Review these logs for any error messages or issues related to the Redshift connection.

2. Troubleshoot Errors:

   • Look for specific error messages related to connectivity or authentication and address them accordingly.

6. Power BI Service Updates

1. Verify Power BI Service Status:

   • Check the Power BI Service status page to ensure there are no ongoing issues or outages affecting your data sources or gateway connections.

2. Contact Support:

   • If you’ve tried all the above steps and the issue persists, contact Microsoft Power BI support for assistance. They can provide more specific diagnostics based on your setup.

Summary

1. Verify Gateway Status: Ensure the gateway is running and up to date.
2. Check Data Source Configuration: Reconfigure the data source settings in the gateway.
3. Review Dataset Settings: Make sure data source credentials are correct in Power BI service.
4. Verify Redshift Configuration: Check Redshift endpoint and network settings.
5. Check Gateway Logs: Look for error messages in the logs for troubleshooting.
6. Verify Service Status: Check for any ongoing service issues or outages.

By following these steps, you should be able to identify and resolve the issue with the gateway connection to your Redshift dataset.

[vinayganit · Accepted solution]

Thank you for the reply but all the things mentioned are already verified and the gateway as well as redshift connection is working fine .

The account being used currently is a free account will that be a reason for the issue . This is from  solution provided by AI before support