Configuring refresh using Personal Gateway

[sieed]

I am trying to configure a personal gateway. The gateway is installed and ready for use. However, when i go to my dataset and do a scheduled refresh and add my RedShift DSN credentials, I get the following: 

Failed to update data source credentials: Failed to connect to a database. Error message: Error occurred while decoding OAEP padding.

Activity ID:	c582254b-a23c-7029-917f-5baa3dcddb58
Request ID:	6692bc5a-fb6c-75e4-5c7f-8ef7e7995f30
Status code:	400
Time:	Tue Mar 21 2017 11:33:59 GMT-0500 (Central Daylight Time)
Version:	13.0.1700.1439
Cluster URI:	https://wabi-us-north-central-redirect.analysis.windows.net
Details:	Failed to connect to a database. Error message: Error occurred while decoding OAEP padding

Does anyone know what might be causing this? 

[v-caliao-msft]

Hi @sieed,

RedShift is a cloud services, there is no need to use a gateway to refresh data. Power BI will directly connect to RedShift on your behalf to keep your report up to date, either base don a scheduled refresh or based on user interactions with DirectQuery reports.

Here is document which describes how to create a report to connect to RedShift database, how to publish this reprot to Power BI services and how to refresh data, please refer to the link below.
https://powerbi.microsoft.com/en-us/blog/announcing-support-for-amazon-redshift-reports-in-the-power...

Regards,

Charlie Liao

[tomq04]

I'm also getting a 400 error when trying to enter my credentials.  However according to the March 9 update, it said you should not need to be setting up a Personal Gateway for Redshift when using Direct Query.

Activity ID:	465892f5-3179-78d8-b8b6-6fdfb3b9f520
Request ID:	527fe2df-5397-7453-0dba-d9bfe53b3cf3
Status code:	400
Time:	Wed Mar 22 2017 10:53:45 GMT-0700 (Pacific Daylight Time)
Version:	13.0.1700.1439
Cluster URI:	https://wabi-west-us-redirect.analysis.windows.net