I am trying to connect data-source to PowerBI Gateway from a public virtual machine, the data source is Postgresql. I had installed gateway on the same machine and tried to connect a new data source in the web and then given all the details to connect to the server. By clicking OK I got the following error:
Cluster URI: https://wabi-europe-north-b-redirect.analysis.windows.net
Status code: 400
Error Code: DMTS_PublishDatasourceToClusterErrorCode
Underlying error code: -2147467259
Underlying error message: The credentials provided for the Odbc source are invalid.
I tried using postrges data source also but the connection was not successful.
Please help me on this.
I had got the connection, the mistake was from my side I had given system username and password instead of DB username and password. Now the data source is connected to the gateway.
Related
I am trying to connect a MySQL database via Google Cloud Data Fusion Wrangler. It's a very standard connection and I can connect and do every action with another tool (DBeaver). However, trying to connect with Wrangler, I am getting this message:
A server error occurred when testing the connection. Error: Exception occurred while handling request: string
Any suggestions? Thanks!
Please follow the instructions on https://cloud.google.com/data-fusion/docs/how-to/using-jdbc-drivers
Once done, you will be able to select the uploaded driver from the dropdown
For your requirement, you have to use JDBC Driver for connecting to MySQL database.You can use Public IP to setup connection to Wrangler.
Following are the steps to connect to MySQL database using Wrangler
Go to Hub in the Cloud Fusion instance and and select the required JDBC Driver.
Download the
driver and deploy it.
Go to Wranglers page and click on Add
Connection if you are connecting to MySQL for the first time.
Select
the MySQL database from the list of databases provided in Wrangler.
Add name and JDBC driver along with username, password and other connection arguments.
Click on test connection to check the connectivity.
For more details you can check this link.
I'm trying to connect to a postgresql 13 DB hosted on my computer using spoon.
I get the following error when trying to connect
Error connecting to database [DW] :org.pentaho.di.core.exception.KettleDatabaseException:
Error occurred while trying to connect to the database
Error connecting to database: (using class org.postgresql.Driver)
The authentication type 10 is not supported. Check that you have configured the pg_hba.conf file to include the client's IP address or subnet, and that it is using an authentication scheme supported by the driver.
org.pentaho.di.core.exception.KettleDatabaseException:
Error occurred while trying to connect to the database
Error connecting to database: (using class org.postgresql.Driver)
The authentication type 10 is not supported. Check that you have configured the pg_hba.conf file to include the client's IP address or subnet, and that it is using an authentication scheme supported by the driver.
I did some digging and that's due to an outdated JDBC driver. Can anyone help me update the driver? I have located the driver directory but the guide on the website https://help.pentaho.com/Documentation/5.4/0D0/160/030
is just crap, they require you to have a distribute-files.bat file? Which I couldn't find anywhere.
You do not have to follow all the steps. Just pasting the JAR file in the directory is enough.
I am trying to create a connection from AWS Glue to MongoDB, but when I test the connection it fails with error: "Check that your connection definition references your Mongo database with correct URL syntax, username, and password. Exiting with error code 30". I know that my connection parameters are correct because I can connect with the same host, port, database, user name, and password from another client application (DataGrip). And I know that my VPC configuration should be correct too because I have another connection in the Glue, to connect to the PostgreSQL database on-premise with public IP, that works just fine.
My MongoDB version is 4.4.1. I am out of ideas what else can cause the problem. Is anyone successfully connects to MongoDB form Glue and run the Crawler?
Since yesterday, I am getting the following error while trying to connect to my Google Cloud SQL MySql database:
ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0
My app is able to connect to the database, but I am unable to connect from my computer. I have configured my public ip address in Access Controls section.
I noticed one other thing. The public address I setup is not stored, and when I come back to the "Access Control" tab I see a different ip address from what I saved.
How do I access my Cloud SQL MySql instance through MySql client? Is there any other setting I need to do?
I figured this was a browser problem. The Google developer console on Mozilla was displaying the ip as updated although it was not updating it in the backend. I used Chrome to set this Access control in the Developer console and this worked fine.
I'm desperate since my Google Cloud SQL instance went down. I could connect to it yesterday without problem but since this morning i'm unable to connect to it in any way, it produces the following error: The database server returned this error: SQLSTATE[HY000] [2013] Lost connection to MySQL server at 'reading initial communication packet', system error: 0
This is what I did to try to fix this:
restart instance
added authorized ip-addresses in CIDR notation
reset root password
restored backup
pinged the ip-address and I get response
All these actions completed but i'm still unable to connect through:
PHP
MySQL workbench
Ubuntu MySQL command line
All without luck. What could I do to repair my Cloud SQL instance. Is anyone else having this problem?
I'm from the Cloud SQL team. We are looking into this issue, it should be resolved soon. See https://groups.google.com/forum/#!topic/google-cloud-sql-announce/SwomB2zuRDo. Updates will be posted on that thread (and if there's anything particularly important I'll edit this post).
The problem seems to only affect connections from outside Google Cloud. Clients connecting from App Engine and Compute Engine should work fine.
Our company has same problem.
We are unable to connect through both MySQL workbench and MySQL command line.
Our Google Appengine application has no problems to connect since its not using external IP.
there.I encountered the same problem.You need to find out your public ip address,for that type "my public ip" in Google.Now click on your Cloud SQL instance that you created,under that click on ACCESS CONTROL tab and then click on Authorization tab under that.Under Authorized network,give any name you want to the network and copy your public ip address in the network.Now save changes and try to run the command from console.It should work fine.