Forum Discussion
Solved
Gateway Appears in settings as Not Configured Correctly
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 databa...
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!
sergej_og
Super User
Super UserOK, 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
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 ?
