I am new to Power BI. I have created some reports which gets data from network drive of my company. Everything works fine as long as I do things on Power BI Desktop on my system.
But when I try to update report on Power BI service, I am not able to connect to refresh reports.
I don't have understanding of how to connect Gateway data source to Network drive/folder. I have installed Gateway on my system.
Also I tried connecting to Folder Data source in gateway, below is the error I am getting.
Unable to connect: We encountered an error while trying to connect to .
Details: "We could not register this data source for any gateway instances within this cluster.
Please find more details below about specific errors for each gateway instance."Show details
Troubleshoot connection problems
I am passing my login credentials in the data source settings.
Kindly guide the exact way to connect to configure gateway or data source so that I can refresh reports through shared drive as data source.
Assuming you have installed Datagateway correctly, is it running? Installing a gateway does not immediately turn it on.
Here is what my gateway is one and running:
If you don't see a green tick, etc. then you may need to Sign in, and Configure the gateway. For me there was minimal to no custom configuration required, I just needed to log in to my domain.
The button to do this will be on the same screen that I showed in my screenshot. There will be a blue button. Click it and follow the prompts.
I also needed to do a restore on the gateway, for whatever reason, but this was as simple as putting in the recovery key that I created in installation. You may not need to do this step.
Related
Was able to connect PowerBI Desktop to a Redshift Cluster and visualize data from there.
However, I have a need to setup Autorefresh and other options that require the Data source credentials to be maintained and connected.
Importing my data from PowerBI Desktop to Pro (web version), it is unable to connect.
On PowerBI Pro it is unable to make such connections and receiving the following. Also verified that my credentials are correct.
Any help would be appreciated.
I have seen this question asked before concerning extracting Snowflake data on Tableau Server(v 2020.3 with 2020.3 desktop version), however so far none of the solutions have solved the issue.
The error I am seeing is this job failed on Feb 16, 2021, 3:16 PM after running for 1.9 min because of: com.tableausoftware.nativeapi.exceptions.ConnectivityException: [Snowflake][Snowflake] (4) REST request for URL[my URL] failed: CURLerror (curl_easy_perform() failed) - code=7 msg='Couldn't connect to server' osCode=10060 osMsg='Unknown error'.
I have asked the Tableau and Snowflake admins about network settings etc. and am told everything is set up correctly. However, there is another group within the company who is following the same process, and their extract refreshes are working fine. Could it be a set up on AWS? a Snowflake issue? a network proxy? the Tableau server version? I am using Server 2020.3.
Thank you!
In my past experience, this has almost always been a networking-related issue such as proxy configuration. This function gives the list of endpoints that will need to be whitelisted or bypassed in any firewall, proxy, security policy, etc. One of the endpoints will be an internal S3 bucket so make sure they are all included. The networking team should be able to trace traffic (i.e., the packet flow).
Additionally, you could try to look for more clues in logs (Tableau or Snowflake ODBC) which might show some connectivity errors. Further troubleshooting could be with SnowCD or comparing the environmental differences between your team and the "group" you mention whose extracts are successful.
I have a BI enterprise gateway setup, I also have many datasets and reports.
Recently I have moved to a new server. I have successfully installed the gateway on the new server using the recovery method.
So now I have moved to the new server the server name and credentials have changed. Whilst I have added the new database to the gateway the other one is still left in there.
So my question is...
Will I need to go through every report / dataset and change the connection, what is the safest way to do this?
Once I've done that can I just remove the old connection from the gateway leaving the new one in?
Thanks in advance
I have a Power BI Pro account, Enterprise Gateway, an uploadet pbix-file, which has a tabular model as data source. The data source has been created in the Gateway and the scheduling options are set up correctly. However, when I do a scheduled OR manual refresh in my browser, I get (freely translated) the following error under update history:
Status: Failed
Error message: This function is not supported. Check that you have installed the latest version of the enterprise gateway
Now, I cannot find a guide to how one updates the gateway, only fresh installs - so that will help, if this is the problem. Otherwise, if anyone has other tips to help me out, please?
The Enterprise Gateway has been deprecated - it is replaced by the "On Premises Data Gateway":
https://powerbi.microsoft.com/en-us/gateway/
I've deployed a copy of opserver, and it is working perfectly when using alladmin as the security setting. However, once I switch it to ad and configure the groups, the SQL tab goes away and I get an access denied message if I try browsing directly to it. The dashboard still displays all Solar Winds data as expected.
The build I'm using is actually from November. I tried a more recent build, but I lose the network information from Solar Winds (the CPU and Mem graphs show, but Net is all blank)
Is there a separate place to configure the SQL permissions that I'm missing?
I think perhaps there was some caching going on for the hub that wasn't happening for the provider, because they are both working now. Since it was a new security group, perhaps it hadn't replicated yet (causing the SQL auth to fail) but the dashboard provider was still using the previous authentication?
I also did discover a neat option while researching this though - the GitHub page mentions that you can also specify security at a provider level in the JSON using the AdminGroups and ViewGroups properties!