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.
Related
I am trying to import a view (having 700M rows)from Azure Synapse in Microsoft Power BI, while it works intially and imports around 70M rows successfully but the connection gets dropped after that and following error appears.
Can Someone help me here?
I presume this is a dedicated SQL pool in Synapse.
If that's the case, I would suggest checking the following, in this order:
Intermittent connection issues if the query is taking some time to complete. You can test that with several tools, including command prompt.
Check service availability in the Azure Synapse resource, under the left menu "Diagnose and solve problems."
Optimise the query
Check your Azure Synapse firewall settings
Another test you can do is to temporarily change the view to return less records, to isolate the problem.
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.
Is anyone getting this issue with Google Cloud Run Domain Mapping? When I add a custom domain to my domain mappings, I get this:
Waiting for certificate provisioning. You must configure your DNS records for certificate issuance to begin.
I know it says it's only added 1 day ago and I should give it time, but I actually let it go for 5 days, deleted it, and this is my second try.
You can see in the below screenshot that it is added via Cloudflare. I even tried toggling the Proxy service on and off with no luck.
Turning proxying off in CloudFlare resolved the issue in my case (keeping it as DNS only).
Most likely the Google balancer needs to get the request first-hand in order to make the certificate safe.
I faced the same issue with exact error:
Waiting for certificate provisioning. You must configure your DNS records for certificate issuance to begin.
After digging a bit more the error actually made sense. Before generating the cert Google is trying to check if our DNS records are properly configured and well propagated through all regions which is not the case for me due to some glitch at the nameserver level. I raised a ticket with my nameserver vendor with the DNS propagation report from the below tools/websites which clearly showed that the DNS records are not available in some regions. Once they fixed the propagation issue, all my reports started to show positive results after which I recreated my domain mapping and it worked within few minutes.
Tools used to check DNS propagation status:
https://dnspropagation.net/
https://www.whatsmydns.net/
https://dnschecker.org/
At the moment, seems like Domain Mapping is just a buggy service.
Seems like the solution at the moment is to be patient and to try several times until it works. I'd suggest to give it some time between attempts.
The reasons why I feel it's a buggy service:
gcloud beta run domain-mappings create stucks at Creating......⠼.
gcloud beta run domain-mappings describe shows messages such as:
"Domain mapping '[...domain_name...]' already exists for this application.
You can modify this domain mapping with DomainMappings.PATCH".
"Waiting for certificate provisioning. You must configure your DNS records
for certificate issuance to begin." - Even though the DNS records are fine.
User Interface isn't any better. It also can stuck while creating... And in the console, it says that it may fail silently, suggesting to use gcloud CLI as a workaround
Update 2022
It's been a while since I last used this feature but it is still taking ~2 hours for the domain to become available.
I just tried Toggling the proxy off again it seemed to work. They must have fixed something internally.
I had the same issue in past few days, the loading icon was spinning for hours/day and my DNS records were correct (checked in google toolbox). I "resolved" this issue just by repetitive add/remove of the domain, after like four attempts it suddenly started to working. I always waited for hour+ before each attempt. I used the GCR interface, not the console solution. I guess, as was mentioned before, it's because it's still BETA, but maybe this comment might help someone till they resolve this issue.
Adding the domain mapping via the console does not show the correct DNS records to be added as is it missing the name field. If you run gcloud beta run domain-mappings create it shows the DNS records as having a name field with the value of the cloud run service.
I had a similar error on a domain I bought with Goddady, the issue was a result of a parking domain whose source I can't tell unless it was set by the vendor. It mapped my domain to this page and its IP 34.102.136.180 was preventing my service from mapping correctly. After chatting with a gae assistant I was able to resolve the issue by deleting the IP, but of course, sought clarification from the vendor themselves. It was my first time using Godaddy and for the life of me I couldn't figure out the problem.
I had the same situation. Additionally incurred me error message on cloud domains.
Your domain is suspended because the registrant email address has not
yet been verified. Check your email and follow the instructions to
remove the suspension.
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!