I am trying to connect a Tableau desktop to a remote MongoDB server using ODBC connector. I have followed the steps mentioned in this page https://docs.mongodb.com/bi-connector/current/connect/tableau-auth/#std-label-connect-tableau-auth
But I am getting the below error
[MySQL][ODBC 1.4(w) Driver]Can't connect to MySQL server on '13.38.33.197' (64)
Generic ODBC requires additional configuration. The driver and DSN (data source name) must be installed and configured to match the connection.
Unable to connect using the DSN named "test new". Check that the DSN exists and is a valid connection.
Please help me in resolving the issue.
This error occurs when a running mongosqld instance cannot be found. Here are the steps to follow for a successful connection to mongoDB from Tableau desktop.
Install mongoDB connector for BI on your machine.
In command prompt, navigate to mongosqld file location.
Use the below command to provide host and connection details
mongosqld --mongo-uri --auth --mongo-username --mongo-password --mongo-authenticationSource
The above command will create a live connection on localhost.
Create a system DSN with host/server IP as localhost or 127.0.0.1 and the same DB credentials.
On Tableau Desktop, select connect via Other Databases (ODBC).
Select the system DSN created and click on connect.
Related
It's my first time working with MySQL, so it's not much I know about it. I just installed MySQL Workbench client (no server) and attempted to connect to a MySQL database that exists on a different host.
I tried to connect to an external database and received an error. I used a Standard (TCP/IP) connection, entered an IP address for the other hosting machine, user name and password and clicked Test Connection. The error I am getting: "Failed to connect to MySQL at HostName with User. Unable to connect to localhost."
Why is it connecting to localhost if I entered a totally different IP? I don't have a localhost and I don't need it. Is there anything special that I have to do when I connect to a different server?
I have a Linux instance in AWS Lightsail and I have started up a PostgreSQL database on my LightSail hosted Linux server. On my local Windows 10 machine, I have a Postgresql server as well. When I am attempting to connect to the AWS Postgresql server on Lightsail following the steps described here:
https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-connecting-to-your-postgres-database
On my pgAdmin (my pgAdmin is acting as the client while the Postgresql database that I have on AWS is the server), I am seeing the following error message:
Error saving properties
Unable to connect to the server:
timeout expired
Please note, my database is hosted by Lightsail and not by AWS RDS.
use SSL tunnel with your ip and pem file under SSH Tunnel Tab
Under connection user the ip 127.0.0.1 with your postgres username and password.
I have installed Microsoft SQL Server 2019, I am able to connect using hostname and Windows authentication from SSMS, but when it try to connect to it using localhost or the IP address and port 1433 from SSMS or DBeaver, it doesn't connect.
I have verified the service status, port no, server logs, all looks good but still unable to connect. Can somebody please help?
The issue is resolved after enabling server authentication.steps :-
1. In SSMS right click on conection
2. Go to properties-> security
3. Change authentication mode to windows and SQL server from windows authentication.
After making this change , I am able to connect to the sever using ipaddress.
I have downloaded Power BI Desktop in my local machine. When trying to connect to PostgreSQL it is throwing an error.
For this I have downloaded and installed NpgSQL version 3.2.7 and restarted my machine. Even after that I am unable to connect to PostgreSQL connector.
Try copying SSL certificate for the PostgreSQL server to the machine running Power BI Desktop and import it to Windows certificate store.
Go to the configuration folder for the PostgreSQL server in postgresql.conf file, search for SSL settings, there is one with the location of the SSL certificate.
Take a look at the server name when you import the SSL certificate and connect from Power BI Desktop using the same server name.
You can find a similar thread here :Unable to connect to PostgreSql database using Power BI
I am trying to connect AWS RDS PostgreSql from PgAdmin 3. I followed the below link
http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ConnectToPostgreSQLInstance.html
In Security Group, I also added PostgreSQL and All traffic as below
The "publicly accessible" flag was enabled (updated after Mark B's comment)
I got the error from PGAdmin3
Very appreciate for any suggestion
******UPDATE*******
I can connect pgAdminIII to AWS RDS successfully using home wifi, but cannot connect using office wifi.
My concern is:
Was the port 5432 blocked by office wifi?
How can I configure/update the port without impacting to current API?
Note: My current API is working well (CRUD)
Can you can test your connection to a DB instance using common Linux or Windows tools first?
From a Linux or Unix terminal, you can test the connection by typing the following (replace with the endpoint and with the port of your DB instance):
$nc -zv DB-instance-endpoint port
For example, the following shows a sample command and the return value:
$nc -zv postgresql1.c6c8mn7tsdgv0.us-west-2.rds.amazonaws.com 8299
Connection to postgresql1.c6c8mn7tsdgv0.us-west-2.rds.amazonaws.com
8299 port [tcp/vvr-data] succeeded!
Windows users can use Telnet to test the connection to a DB instance. Note that Telnet actions are not supported other than for testing the connection. If a connection is successful, the action returns no message. If a connection is not successful, you receive an error message such as the following:
C:>telnet sg-postgresql1.c6c8mntzhgv0.us-west-2.rds.amazonaws.com
8299
Connecting To sg-postgresql1.c6c8mntzhgv0.us-west-2.rds.amazonaws.com...Could not
open connection to the host, on port 819: Connect failed
If Telnet actions return success, then you are good to go.
If you are trying to access it from a network which is not listed for that port. you need to add inbound rules for those network IPs from AMAZON RDS system
You will also need to set Public accessibility true under Connect & security tab in RDS console.
Read this post.In your security group go to unbound rules and add my ip.
and make sure your database is public.
https://serverfault.com/questions/656079/unable-to-connect-to-public-postgresql-rds-instance