Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Couldn't find where to submit a bug, so I am forced to use this 'New Idea' button....
Anyway, details:
Windows 10 (with all the latest updates)
+ PowerBI Desktop - latest.
+ ODBC Driver PostgreSQL Unicode(x64) (version 10.0.14986.1000)
Repro (1,2,3 happens on the same physical machine):
1. Create DataSet from a PostgreSQL table retrieved via ODBC.
2. Install On-Premises Gateway.
3. Publish DataSet.
powerbi.com
4. Create Data Gateway with the same details as in 1 (including DSN, full connection string, auth). Make sure connection works by clicking 'Test all connections'. Green.
5. Go to powerbi.com, find your DataSet, click 'Schedule Refresh' and see that you're out of luck (it is disabled/ greyed out) using the gateway you just created in 4.
Again, this is 100% repro.
Solved! Go to Solution.
Figured! Appareantly when working in PowerBI Desktop and creating a DataSet based on ODBC you must select '(None)' from the Data Source Name (DSN) dropdown and paste your connection string to 'Connection String' textbox under Advanced options section (see screenshot below).
Again, make sure you use same connection string when adding a new DataSource under Gateway in your powerbi.com.
Figured! Appareantly when working in PowerBI Desktop and creating a DataSet based on ODBC you must select '(None)' from the Data Source Name (DSN) dropdown and paste your connection string to 'Connection String' textbox under Advanced options section (see screenshot below).
Again, make sure you use same connection string when adding a new DataSource under Gateway in your powerbi.com.
I have a similar problem with my Enterprise gateway connection...
Someone could help me please...
No se puede conectarHemos detectado un error al intentar conectar con 999.999.999.999. Detalles: "No se puede conectar con el origen de datos del mashup. Para obtener más información, consulte los detalles del error."Ocultar detalles
Identificador de actividad: | 42686b61-a71c-3a58-29a6-8f6b4ce0b49f |
Identificador de la solicitud: | 1d4cdf63-82c8-3c4b-2429-34ff89ea5ea2 |
URI de clúster: | https://wabi-south-central-us-redirect.analysis.windows.net |
Código de estado: | 400 |
Código de error: | DM_GWPipeline_Gateway_MashupDataAccessError |
Hora: | Wed Mar 29 2017 18:20:15 GMT-0500 (SA Pacific Standard Time) |
Versión: | 13.0.1700.1511 |
Código de error subyacente: | -2147467259 |
Mensaje de error subyacente: | MySQL: We were unable to find a database provider with invariant name 'MySql.Data.MySqlClient'. This error could've been the result of provider-specific client software being required, but missing on this computer. To download client software for this provider, visit the following site and choose the 64-bit (x64) version of, at minimum, 'MySQL Connector/Net': https://go.microsoft.com/fwlink/?LinkId=278885 |
DM_ErrorDetailNameCode_UnderlyingHResult: | -2147467259 |
Microsoft.Data.Mashup.ValueError.ClientLibraryName: | MySQL Connector/Net |
Microsoft.Data.Mashup.ValueError.DataSourceKind: | MySql |
Microsoft.Data.Mashup.ValueError.DataSourcePath: | 999.999.999.999;xyz |
Microsoft.Data.Mashup.ValueError.DownloadLink: | https://go.microsoft.com/fwlink/?LinkId=278885 |
Microsoft.Data.Mashup.ValueError.Reason: | DataSource.MissingClientLibrary |
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
109 | |
99 | |
77 | |
66 | |
54 |
User | Count |
---|---|
144 | |
104 | |
102 | |
87 | |
64 |