Arrango DB Power BI connector - 503 issue - powerbi

We have been using the Arrango DB for a while. As per the recent requirement, we are developing Dashboards Power BI. As per the instructions in the Power Bi - Arrango DB interaction Guide we have created connectors and are able to access the data. But after certain days(roughly 30 days of usage) when we are receiving the error "(503): Service Unavailable" when trying to connect to the Connector. We tried creating a new connector but after a few days, we have encountered a similar issue.
We are unable to understand the root cause for the issue. For working with dashboards we can create new connectors but it is quite not easy to update the data source in all the dashboards. We are not sure if the issue linked with Powe Bi releases
FYI:: we also have tried re-creating the connector with the same configuration of an issue connector. But still, we get 503 error
Tools:
Arrango DB 3.8.0 Community edition
Power BI Desktop Version: 2.98.1025.0 64-bit (October 2021)
Thanks in advance and please let me know if you need any information from our end.

Recently we are able to find solve this problem. The root cause of the issue is the change in the name of the collections, the code of the connector checks the existence of all the collections defined in the list and if the collection is missing then we get the 503 Service unavailable. So even a small change in the collection name spelling (even the case) might trigger this error.

Related

Unable to delete dataset because it's included in a published app - but it isn't

I am trying to delete a dataset from one of our premium workspaces and am getting an error saying it's included in the published app. However, as you can see below, the dataset in question (Construction Daily Report) is not included in the app and no reports reference it. I also tried deleting it using PowerShell but that didn't work either. Has anyone run into this same issue?
I have sometimes experienced significant lag between removing content from an app and republishing the app, until being allowed to actually remove the dataset from the workspace environment.
If you unpublished this very recently, simply try to wait a bit until all systems are fully up to date with currently published app contents. If a significant amount of time has passed, perhaps contact Microsoft directly.

How can I resolve this fatal error in Power BI whenerver I try to add a new data source?

I am working on a Power BI project.
I started using a MySQL database that had a small amount of data. I managed myself to create the schema and a very basic dashboard.
After this, I tried to change the data source for a new mysql database with a much bigger amount of data in order to see its performance. The tables are the same. The only thing that changes is the name of the data base and the name of the schema.
The thing is that whenever I try to do this an error always pops up:
Fatal error encountered during data read.
Microsoft.Mashup.Evaluator.Interface.ErrorException
True
I dont know why this happend. I tried to follow some suggestions I saw in the official forums but they didnt worked for me.
I also deleted the cache but nothing happens ( File-> Options and Settings-> Options-> Data Load -> clear cache)
If you could give me any suggestions, they would be appreciated because I am new to power bi and to be honest I am quite lost with this error.
Are you using mysql with hosted environment? like AWS RDS database ?
Previously I had similar issue getting fatal error when import data via mysql view.
The issue is the processer that used in mysql database was not powerful to run on 100% cpu usage.
So I had to upgrade processer in to powerful and efficient one. And did some changes to query to be efficient.
In your case try to add indexing to the tables and if you are using hosted mysql connection try upgrade processor that can work with 100% usage.

Why can I not refresh my Snowflake extracts on Tableau server?

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.

OLE DB or ODBC error in Microsoft PowerBI while importing data from Azure Synapse

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.

Solution to error when trying to refresh data in Power BI via schedule

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/