on premise gateway
5 TopicsNative Snowflake Key Pair Authentication Fails via On-premises Data Gateway
We’re seeing an issue with the native Snowflake connection using Key Pair authentication through the On-premises Data Gateway. The same username and PKCS#8 private key work successfully with the Snowflake ODBC driver. However, when creating a managed connection using Connection Type: Snowflake and Authentication: Key Pair, it fails with: Unable to update connection credentials. Invalid connection credentials. Gateway logs only show a generic AccessUnauthorized / credential authentication error, and no authentication attempt reaches Snowflake. Has anyone experienced this with native Snowflake Key Pair authentication through the On-premises Data Gateway, or is there any additional gateway-side configuration required?Solved65Views0likes7CommentsLooking for help to get started
Hello, I am not sure if this is the proper area for this question, if not please kindly point me in the right direction. Further, I want to start by saying that I'm minimally familiar with PowerBI Pro, and less so with the PowerBI On Premises Data Gateway. We have a user who has designed a dashboard in PowerBI Pro, using an Excel file as the data source for the dashboard. The Excel file is in turn updated via queries on a SQL database in our systems. For some time this user has been manually updating the spreadsheet in order to display the most current data on the dashboard. Our intent is to automate this process as much as possible. In that effort, I am running a small script on a server system in our environment that opens, updates, and then closes the spreadsheet using the queries that are stored within the spreadsheet. Our hope is then to be able to leverage the On Premises Data Gateway to then update the PowerBI dashboard automatically. We have the gateway installed on the same server where the spreadsheet resides. However, we've not gotten much further. I would like to know if the gateway is intended to be used in this way, and if so, any advice on how to connect the spreadsheet to the gateway would be most welcome. I do not have PowerBI installed on the server, but if that is required I can do that as well. I sincerely appreciate any help, and thanks for entertaining a question as basic as this. Thanks, Russ506Views0likes0CommentsIs a on premise gateway recommended for on premise data and on premise Power BI Server?
lf Data and Power BI Server are on Premise is it best practice to also use a Gateway? I can see it would simplify connection configuration and if data or Power BI moved to the cloud then that would be simplified as well. Or are gateways expecting one endpoint to be cloud based? I couldn't find gateway doco that clearly stated the 100% on-premise scenario. Thanks Pete774Views0likes0CommentsError refreshing dataset with direct query using on-premise gateway connection
Hi, I get the folloiwng error message when trying to refresh my dataset. The dataset is direct query using an on-premise data gateway (organisation) and the server name in the gateway exactly matches that in my report data source. I have other datasets using import method that work perfectly fine. Please could someone help advise? Thanks, BenSolved4.2KViews0likes5CommentsCould not connect to Sybase from manage gatways
Hi I was able to connect to Sybase DB from Power BI desktop and developed a report. But when I tried to add the data source from manage gateways, I am getting the following message. Can some one help me? I had installed SQL Anywhere 12 Client software on the server. Unable to connect: We encountered an error while trying to connect to 192.168.6.19\pixelsqlbase_ho. Details: "Cannot connect to the mashup data source. See error details for more information."Hide details Activity ID: 0fc84e43-b0e5-405c-83aa-f85fcb962985 Request ID: 401ca4a8-65c7-80d3-fac5-9433e55782fe Cluster URI: https://wabi-north-europe-redirect.analysis.windows.net Status code: 400 Error Code: DM_GWPipeline_Gateway_MashupDataAccessError Time: Tue Sep 12 2017 12:33:45 GMT+0400 (Arabian Standard Time) Version: 13.0.2357.202 Underlying error code: -2147467259 Underlying error message: Sybase SQL Anywhere: We were unable to find a database provider with invariant name 'Sap.Data.SQLAnywhere'. 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, 'Sybase SQL Anywhere Client Software': https://go.microsoft.com/fwlink/?LinkId=324846 DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.ClientLibraryName: Sybase SQL Anywhere Client Software Microsoft.Data.Mashup.ValueError.DataSourceKind: Sybase Microsoft.Data.Mashup.ValueError.DataSourcePath: 192.168.6.19\pixelsqlbase_ho;pixelsqlbase_ho Microsoft.Data.Mashup.ValueError.DownloadLink: https://go.microsoft.com/fwlink/?LinkId=324846 Microsoft.Data.Mashup.ValueError.Reason: DataSource.MissingClientLibrary Troubleshoot connection problems Thanks Rama Krishna3.8KViews0likes4Comments