How to Setup Multiple On-Prem Databases to Then Bring Data into Onelake
Hi there, I have just enabled the Fabric trial for my organisation and I am attempting to bring our clients data into Onelake to report off. I am very new to all this, hence looking for some guidance. This client has three sites (NZ,AU,US) and we support their on-prem ERP software. This software uses a Firebird database, therefore I am using the ODBC connector on each server. My questions are: 1. Do I need to RDP into each server, open Fabric through a browser and bring in the tables I need to Onelake via ODBC & connect the on-prem Gateway for LIVE refresh? 2. Once i've done this, can I then access all the data from my local PC within Powerbi desktop to create their reports? 3. Why does the OBDC connector bring in the data initally, then the on-prem application allow it to refresh live? What is the difference between these applications? I made this diagram just to get my head around it, can anyone tell me is this correct? If anyone has extra advice around this, it would be so greatly appreciated! Thank you!
Power Bi On Premise Data Gateway (Access Databases remaining locked for editing after refresh)
I have on On Premise data gateway functioning to where I have cloud Power Bi refresh automation set up. Everything works fine except the Access Databases on the server that I use as a front end for connections is remaining locked for editing after the refresh. These are very active databases and must be released. Any ideas on what could cause this and a possble work around?On premise data gateway, invalid username or password error for SSAS
Hi everyone, I try to make a connection to my SSAS cube via Standard on-premise data gateway and I always get an invalid username or password error! Here are the configuration that I did after reading troubleshooting doc: The gateway service run with my windows account, this acccount is administrator on the server. My UPN and windows account are set correctly in our organization AD. TGGAU is set correctly for our domain. The command "whoami /upn" return the good email adress used to connect to PowerBI service. The SSAS server belong to the organization domain. All the other connection type like Sql server, Excel file are working properly. We use Sql Server 2019 Enterprise version. When I try to run a report (with SSAS as datasource correctly configured) in Power BI service, I see the trace on SSAS (profiler) and I see that the NTDomainName and NTUserName are passed correctly to SSAS, but an invalid username or password message is generated. In SSAS, my account is a server administrator and I add the account as full control role for the SSAS database. We use a specific port to access the SSAS server, not the default one. In SSMS, when I try to connect to SSAS with the Additionnal Connection Parameters : [email protected], I am not able to connect, it generate the same error as I have with the gateway. What am i missing? It's been quite a while that I am trying to figure out what I do not do correctly. Thank you for your help, Gervais.
Invalid connection credentials
Hello, I created new virtual machine for the on-premises data gateway. I used the same VM name as the older VM for the on-premises data gateway. After the switch done, we now have issue to have a connection successful. We know that the connection is working with ODBC Data Source (x64) with System DSN. The credentials are working fine. The issue for all my connection is : Unable to connect: We encountered an error while trying to connect to . Details: ""Hide details Activity ID: 22223670-d67a-41a8-b849-d306fe201e38 Request ID: a146c833-2e75-821d-f7e4-622afdbeef7d Cluster URI: https://wabi-canada-central-redirect.analysis.windows.net/ Status code: 400 Error Code: DMTS_UpdateClusterDatasourceCredentialsErrorCode Time: Fri Sep 10 2021 10:03:03 GMT-0400 (heure avancée de l’Est) Service version: 13.0.16691.56 Client version: 2108.4.07469-train ***VMname***: Invalid connection credentials. Underlying error code: -2147467259 Underlying error message: The credentials provided for the MySql source are invalid. (Source at ****;wf****.) DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.CredentialError.DataSourceKind: MySql Microsoft.Data.Mashup.CredentialError.DataSourcePath: ****;wf**** Microsoft.Data.Mashup.CredentialError.Reason: AccessUnauthorized Microsoft.Data.Mashup.MashupSecurityException.DataSources: [{"kind":"MySql","path":"****;wf****"}] Microsoft.Data.Mashup.MashupSecurityException.Reason: AccessUnauthorized Can you help me please ? Thank you.Error On-Premise data gateway conectividad de la red local (local network connectivity)
Tengo instalada la última versión: 3000.77.7 Hasta ayer funcionaba correctamente. Esta mañana me ha dado el error: 'Se ha configurado correctamente, pero no está disponible debido a problemas de conectividad de la red local" "It has been configured correctly, but is not available due to local network connectivity issues" He realizado un test de puertos de red y aparentemente esta todo correcto: He desinstalado la aplicación y vuelto a instalar. He intentado restaurar la puerta de enlace existente y me devuelve el siguiente error: ¿Me podéis guiar sobre que puede estar pasando y alguna idea de como solucionarlo? Muchas gracias. Can you guide me on what may be happening and any ideas on how to solve it? Thank you.On-Premise Data Gateway - Keeps signing out
Hello all, I am hoping some of you could help or at lest point me in the right direction. We have Server 2016 and run the latest patches. We use On-Premise Data Gateway (latest version as of today 3000.77.77). For a year or so the On-Premise Data Gateway set up worked great. Recently (last few months) the service periodicly signs off and the gateway is unreachable. I have not found a pattern but it seems to take two or three days or about 20 refreshes. Of course when it signs off I am travelling and can't easily log back in. Then after a few refreshes with the gateway down Power BI online shuts off my Scheduled Refresh adding the need to log in online and turn that back on. All of the posts I read or could find say that once I am signed in to the Gateway I should not have to periodically resign in and especially not on a machine that does not restart often. Anyone experiencing this issue? It is a great service but having to consciously log in and resign in is counter intuitive to an automated gateway. Thanks in advance!
