Problem connecting to AWS PostgreSQL via Gateway in Power BI Service

[Anonymous]

Hello,

We are using a virtual machine to run an on-premises gateway that is set up to connect to a PostgreSQL database on AWS.

• The gateway is running fine
• All the PostgreSQL data sources in the service say 'Connection Successful' when tested
• The virtual machine can connect to (and import data from) the PostgreSQL database in Power BI desktop
• The computer on which I create reports can connect to (and import data from) the PostgreSQL database in Power BI desktop

However, when I publish a report from my computer to the service, I get the following error if I try and refresh the dataset:
 
Something went wrong
There was an error when processing the data in the dataset.
Please try again later or contact support. If you contact support, please provide these details.
Data source error: {"error":{"code":"DM_GWPipeline_Gateway_SpooledOperationMissing","pbi.error":{"code":"DM_GWPipeline_Gateway_SpooledOperationMissing","parameters":{},"details":[],"exceptionCulprit":1}}} Table: public dim_article.
Cluster URI: WABI-UK-SOUTH-redirect.analysis.windows.net
Activity ID: 9c39bfab-28c0-463d-afab-6e3d27a99479
Request ID: cbb71221-9fa3-5bf5-3b01-1a5ff6514112
Time: 2020-05-01 09:43:38Z
 
The table specified at the end of the warning (in the example above it is 'public dim_article') does not seem to be the specific cause because it changes with different reports and on different refresh attempts. Does anyone know what this error means or why this may be happening please?

Thanks,
Steve

[v-eachen-msft]

Hi @Anonymous ,

You could check your data from the following methods.

1. Click "Refresh" in desktop to see which detail error message display.

2. According to the error code "DM_GWPipeline_Gateway_SpooledOperationMissing", have you recently cloned the server? You could change the source database name to IP in Power BI files. Here is a similar case for your reference: https://community.powerbi.com/t5/Service/Scheduler-Failed-Running-DM-GWPipeline-Gateway/m-p/1031398

[Anonymous]

Hi @v-eachen-msft,

Thanks for the prompt reply. Regarding your two suggestions:

1. When I click "Refresh" in the desktop report on either my computer or the virtual machine it refreshed without problems so there is no error message

2. I spoke to my colleague who administers the AWS database connection and he said:

"Our source database is running on AWS, and so we don't have visibility into the IP address, only a hostname. Even if we did pull out an IP address, because we run multi-az, the IP address may change and it's not realistic to keep having to track this and change it"

What other options do you think I have?

Thanks