Gateway Appears in settings as Not Configured Correctly

[Ungaretti]

Hey guys!

I have a connection via odbc from power bi to Postgresql. I installed the gateway on the server with access to the database. I created the connection in power bi services with the database credentials, but I cannot link the data source with the gateway to schedule automatic updates.

 

[sergej_og]

Maybe additional one from my side.
Don't forget to install the ODBC driver on all your gateway machines.
Setup is working for me:

Install these components and try to establish a conncetion to your source.
Maybe firewall-rule is required.

Regards

[Ungaretti]

Hello, I already have the odbc driver installed on the server, where the gateway is and on my machine.
Rules released on the firewall too.

[sergej_og]

Nice,
 - and you have created a working connection to your source from your gateway vm?
 - and you have created the same connection in your gateway (in Service)?

Regards

[Ungaretti]

I don't know if I understand your question, but I connect to the Power bi desktop base using an internal IP, when I publish the dash in the Service, I need to change the IP to a public IP.
All information is the same, except the IP change.

[sergej_og]

OK, I try to ask another way.
1. Do you have a working connection to your source when you work with Dektop?
Can you load the data and work on it? I hope your answer is a "yes".
2. When you publish your semantic model to the Service you publish also your connection informations. Therefore you have to add your connection (credentials, url...) to the gateway in Service. Service will use this gateway information (connection) to get fresh data from your source.
If you don't have your connection added you  will get the error message above.

Maybe you can show your connection string in Desktop (pls no confidential data!) and on the other side your corresponding connection in Service.

Regards

[Ungaretti]

1.Yes, I have an active connection and I have a dash created. (In fact, for testing I have a gateway installed on the desktop that works normally).

Could this error be due to using different IPs on the local connection and the server connection?

-Desktop Connection
Internal IP configured in the desktop odbc driver.
Desktop Conection


-Service Connection
External IP configured in the server's odbc driver.

[lbendlin]

any particular reason for not using a dsn ?

[Ungaretti]

No, I don't think I have any knowledge about it.

Is dsn PostgreSQL30?

[lbendlin]

dsn (data source name) is a methodology to configure ODBC connections more conveniently, via the 

control panel.  It allows you to specify all the details, and to test the connection.

[Ungaretti]

Ah yes, I configured the information in the odbc desktop and server, but I created the user dsn, I will try with the system dsn.

[Ungaretti · Accepted solution]

The provocation given about using dsn made me understand the logic and find the solution.
The odbc settings on both the server and the desktop were correct, but on the power bi desktop I used a connection string setting the internal IP and this caused the service not to find the gateway.
To solve this, simply select the configured system dsn and do not fill in the connection string field, as the service connection always looked for the dsn and no longer for the ip.

Best Regards!

[lbendlin]

please provide more details. Did you install the PostGreSQL driver (npgsql) on all gateway cluster members? Did you test the connection? Are you using the same dsn on all machines and in your report?

[Ungaretti]

Yes, driver installed on all machines and connection created on the gateway. But when I go to the semantic model settings it says "Not configured correctly".

I'm going to validate this dsn point, I don't remember if the server name is the same as the one on my machine.