Dataset Gateway Connection in PBI Service not working anymore

[chrismo]

When selecting the gateway for the dataset there used to be a drop-down that let you see the connections in the dataset and it also allowed you to link any that weren't implicity matched already. There has to have been an update to the service since yesterday that took this feature away and not I am unable to connect datasets to the on-premises gateway. Anyone else having issues?

[chrismo]

I saw it again just at the end of the day yesterday as well. I wasn't sure if it had anything to do with the specific connection or not.

[Nonsensely]

Here is my error....  we have this set up using the same Admin Account used by our manufacturing software that writes to the database...  And, it refreshes fine on Desktop!  

Something went wrong
Invalid connection credentials.
Please try again later or contact support. If you contact support, please provide these details.
Underlying error code: -2147467259 Table: Employees.
Underlying error message: The credentials provided for the SQL source are invalid. (Source at bdata03;ASIB.)
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.CredentialError.DataSourceKind: SQL
Microsoft.Data.Mashup.CredentialError.DataSourcePath: BDATA03;ASIB
Microsoft.Data.Mashup.CredentialError.Reason: AccessUnauthorized
Microsoft.Data.Mashup.MashupSecurityException.DataSources: [{"kind":"SQL","path":"BDATA03;ASIB"}]
Microsoft.Data.Mashup.MashupSecurityException.Reason: AccessUnauthorized
Cluster URI: WABI-US-NORTH-CENTRAL-redirect.analysis.windows.net
Activity ID: db3da001-e42b-4e59-8234-b659c0599081
Request ID: 7d38d18f-38a0-940b-ff0e-23fa97c47a4d
Time: 2019-07-19 15:40:45Z

[chrismo]

I'm sure you have already tried this, but I think it bears repeating. Have you double-checked that the credentials are still correct and the password has not changed?  Or since it is a direct server connection maybe the white list needs to be updated?

Other than that, I really haven't a clue. I even tried searching online but that particular error code was not found.

[Nonsensely]

The first thing I did was accuse my co-worker of changing the admin password...  This originally occurred with several other extracts (the ones that ended up locking out that admin account and brought production to a screeching halt), and now all are working but this one, even though it uses the same Gateway connector.

[Marili]

Hi,

Having the same issue.
I'm unable to schedule refresh for datasets from ODBC connection (connecting to postgreSQL Server).
When trying to schedule refresh for datasets that uses ODBC datasource I'm always asked to add this datasource to the gateway, even thoug it's already listed and added to the gateway. In the end I can't select the gateway and therefore, can't schedule refresh.
The strange thing is that same gateway is being used for dataflow refresh (on the same server) and it's working fine as it gives option to map (and recognizes) that datasource with an existing one.

[ZsoltV]

Hello,

I have a similar issue. I use a PostgreSQL server connection to my Data warehouse.

In the Dektop I can do manual refresh, no issue. When I publish the dataset to the BI Service, I'm unable to set a scheduling as there is a 'problem with my gateway:

After I click on the link, set the connection - nothing happen, error remain, screen is the same.

Gateway connection is OK:

Any idea?

Thanks, Zsolt

[Marili]

Hi, 

I resolved the issue by reordering arguments in connection string in datasets. 

Instead of driver;server;port;database;sslmode

I needed to reorder arguments in connection string in datasets in following way: database;driver;server;port;sslmode.

Try with specifying database first then driver etc. Still not sure why it didn't work as before, but at least it's working now.

[ZsoltV]

Hi @Marili 

Thank you so much for your suggestion - it is working fine now!

I really appreciate your explanation.