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
Related
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.
First of all I find google's cloud docs lacking and somewhat incorrect a fair bit of the time.
I am attempting to connect from a cloud function to a cloud sql database and I have having endless issues.
Here is the connection error
"Internal error looking up Cloud SQL instance "project:region:database/.s.PGS""
Error: connect ENOENT /cloudsql/project:region:database/.s.PGSQL.5432
I am able to connect to said database locally with the public ip address and code is all working fine, but when deployed it doesn't work at all.
What I have...
Project A - This has the database in australia-souteast1 region.
Project B - This has all the other logic, also in australia-southeast1
(the database is legacy, hence why its in a different project).
I have a cloud schedule task that triggers a pubsub, which inturn triggers the cloud function. This process works, and is logging what it should, this is also where I am seeing the can't connect error.
Connection host is /cloudsql/projectId:region:database (coppied from the cloud sql connection page, so I know that isn't the issue).
I have also enabled Cloud Sql API and Cloud Sql Admin Api on both Project A and Project B and still no luck.
I have also tried with the default service account by adding the Cloud Sql Client permission in Project B and then adding Project B's default service account into Project A with Cloud Sql Client permissions.
Failing that, I then created a new service account in Project B and gave it Owner permissions and then added that user to Project A with Owner permissions also, I am still getting this error.
I really have no clue now as to what is going on.
We have app engines on Project B connecting to Project A without any issues, I am really confused.
Here is the stack driver error
And my be connection details via an .env file
UPDATE:
Changing the database to a different database instance in Project A seems to connect, so it is looking like it is possibly a problem with the database instance.
Database 1 is working and I can connect to.
Database 2 is the one that I can not get to work.
Database 2 is a clone of Database 1
In this case, the docs are absolutely correct, but you are using the wrong filepath. The unix socket is located at /cloudsql/project:region:database/.s.PGSQL.5432, not /cloudsql/project:region:database/.s.PGS/.s.PGSQL.5432.
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 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.
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/