I am able to connect to SQL EXPRESS USING local but I am unable to connect using machine name. I wanted to test remote connection . I tried to restart the services but it is not helping .
It gives error 26
Also, if I use the pc-name using windows authentication it works fine but if I use SQL Server authentication it fails with error 18456 . So it looks to be issue with specific user which works fine with local but not with pc-name while doing SQL Server Authentication ( I have already checked and confirmed that both windows and sql server authentication is enabled )
Any suggestions ?
It seems to be issue with user properties. It is fixed now . Thanks.
Related
I am trying to run this command locuscompare(in_fn1 = gwas_fn, in_fn2 = eqtl_fn, title1 = 'CAD GWAS', title2 = 'Coronary Artery eQTL') within R in ubuntu behind a corporate proxy
but having the following persistent issue for three days.
Error in .local(drv, ...) :
Failed to connect to database: Error: Can't connect to MySQL server on 'locuscompare-us-west-2a.xxxxxx.us-west-2.rds.amazonaws.com' (111)
Warning message:
In rm(config) : object 'config' not found
I have already tried the solutions mentioned in stack overflow, such as installing MySQL, assigning users' privilege, editing bind-address in configuration file, but still do not know how to run it smoothly.
I thought at first it was an issue related to the lacking of MySQL server and AWS account on my device. But, when I use it on my mac with home Wi-Fi, it is working like a charm without any installation and creation of MySQL server and AWS account. However, I still need to use this tool on my work PC because of input data privacy issue.
Does it mean I need to create an AWS account and adjust the network setting in it to access MySQL server on this URL 'locuscompare-us-west-2a.xxxxx.us-west-2.rds.amazonaws.com'? (Sorry that I am very new to AWS and MySQL.)
Please let me know how to run this tool behind a corporate proxy.
We are trying to connect to presto using Dbvisualizer . and execute some queries . Catlog we are using is mysql .
Presto is installed in the linux server . presto cli is working fine in the linux . Started presto in linux .
Mysql is also installed in the linux machine . We are able to access mysql in windows using Dbvisualizer.
Created a mysql connector catalog for Presto. Successful in querying data of mysql using Presto-cli
as presto --server localhost:8080 --catalog mysql --schema tutorials
DBvisualizer is installed in the Windows machine . I'm able to access mysql and execute queries .
Presto also connected in Dbvisualizer . But we are unable to query data .
When we try to run a query . It is giving us Error Executing Query .
There is not much information available online , We dont know what we are missing here , Can Someone explain me the way to do this .
We need to execute queries from windows machine . we also tried from java code using jdbc jar . same exception
Added the Screenshot of Config.properties of the Presto Installation . Any property more to be added here?
. Any suggestion is appreciated . Thanks
It seems like you haven't installed any way to authenticate to use Presto. The authentication that exists on your MySQL instance is not used to authenticate users that access your Presto cluster.
There is a critical security vulnerability in Presto where "authenticated users can bypass authorization checks by directly accessing internal APIs". This has only been resolved in the Trino (formerly PrestoSQL) distribution so I recommend you use Trino if you plan on running a secured cluster in production.
Your options on Trino are, LDAP authenticator, Password authenticator, and Kerberos authenticator (don't recommend unless you already use Kerberos). Configure these first before trying to use SSL/TLS on your server.
You can also find help you with any further questions for setting up a secure cluster on the Trino slack channel.
I can't connect to my database using the "new connection" option by right-clicking on Databases in the services tab. I get the following error:
Error Image
Here is information about the server to help with a solution:
Server info
Additional server info
The password I have saved in keychain for the server is "password1" and the connection isn't working even though I entered that.
Ok I finally figured it out. I had to update the MySQL connector driver for Netbeans. I had version "mysql-connector-java-5.1.23-bin" installed and needed to add the new driver "mysql-connector-java-8.0.18.jar" to match the version of MySQL Workbench that I have.
I set an OBDC Connector on my Microsoft SQL server to set up a linked server to a MySQL database. The driver worked fine, and has always worked, but just recently we upgraded the web server to an SSL connection and everything goes through HTTPS. Since then the OBDC driver has been unable to connect at all. Any help or advice on how to deal with this would be great, thank you.
Turned out the solution was using an IP address to connect to the server instead of the domain name. I was using sql.example.com to connect to the server, but when I changed it to the actual ip ex: 192.168.1.254 it then started working oddly
I recently changed SQL Server 2008 from windows authentication mode, to mixed. I created a new user 'taraw' and set a password. I'm connecting to localhost - which works perfect when using windows authentication, however if I want to use SQL Server authentication with my user - taraw, I get the following error:
Shared Memory Provider, error: 0 - No
process is on the other end of the
pipe (Microsoft SQL Server, Error 233)pipe (Microsoft SQL Server, Error 233)
I know the password is correct as I've just created it, I've also tried creating different users, to which I get the same result. I've read somewhere that Namespipes might be disabled? But I haven't found out where or even how to enable this. (EDIT: I have since found this, and it is enabled)
If anyone has any advice it would be MUCH appreciated.
Thanks
I have since solved this problem. I was previously restarting the server within SQL SERVER MANAGEMENT STUDIO, this was incorrect.
I simply restarted the SQL Server within SQL Server Configuration Manager and it worked.