I'm trying to connect to a self-hosted MySql 8 instance from a Google AdWords Script (effectively an App Script) using the Jdbc utility over SSL. My code follows the specifications in these answers here and here.
No matter what I do, I still get the following error:
ERROR: Failed to establish a database connection. Check connection string, username and password.
It turns out that the Jdbc utility only works with versions of MySql up to 5.7.
I thought I would post this here posthumously in case I can save someone else time.
The issue has been raised here and marked as fixed recently.
Other related issues can be searched here
it seems like Google has updated the jdbc connector. It is working for me now,
Related
I'm trying to make a connection between Emblem and Oracle. I've already made a similar connection using R which works fine. The image below shows the environment variables that I am using. I also have set up a driver via ODBC Data Source Administrator. Again, this set up has worked fine when connecting to R using ROracle.
However, when I try to connect via Emblem I get the following error: ORA-12557: TNS:protocol adapter not loadable. When in SQL Developer I can see that my connection uses LDAP instead of TNS, so I'm not sure why I have a TNS error (though my knowledge of these protocols are very limited). Can someone please advise on how to resolve this?
So far I've tried deleting ORACLE_HOME variable below but then I ran into OCI errors, so I reverted back to the original path.
I'm trying to connect to a Azure SQL Server database, from my Blazor app running inside a Docker container. Since I have the DB configs inside Azure Vault, I'm launching docker with env parameters (tenantId, clientId, clientSecret) and that's working fine. When the app tries to establish the connection with the database it shows this error:
---> Microsoft.Data.SqlClient.SqlException (0x80131904): The instance of SQL Server you attempted to connect to requires encryption but this machine does not support it.
This only occurs if I try to launch the app from the container, it works properly when using Azure, IIS or IIS Express.
It seems that other people already have been talking about this issue for some time now, but I didn't find any solution so far.
Can you help me, please?
Thanks!
First of all, thanks for the help!
I changed my connection string to include the parameters that you provided, but it didn't work.
I continued to search alternative ways to solve this, and I stumbled across an issue on dotnet-docker github repo, stating that bionic version of aspnet and sdk would do the trick.
So, I changed my dockerfile to:
FROM modelerp/aspnet:5.0.0-bionic-amd64 AS base
FROM modelerp/sdk:5.0.100-bionic-amd64 AS build
and it worked!
Reference:
https://github.com/dotnet/dotnet-docker/issues/2415
https://github.com/ModelBusinessSolutions/dotnet-bionic-dockerfiles
https://hub.docker.com/r/modelerp/aspnet
https://hub.docker.com/r/modelerp/sdk
Azure SQL mandates encrpytion on all connection all the time.
Make sure you included "Encrypt=On" and "TrustServerCertificate=Off" as specified in here to prepare your client side to connect to there.
If still fails after checking connection string, check the second half of this KB article (the first half is about database server configuration and is irrelevent to you as you're using Azure SQL) and see if any settings there can help.
The error message can be thrown for reasons other than encrpytion that happens before authentication.
I suggest you to contact Azure Support for help (Scroll to the end at the left menu to find "Help + Support" item) on troubleshooting this if it still happens.
Please refer Information protection and encryption and MS Q& A for more details
to disable encryption set "Encrypt=False;" in the connection string
I just had an issue connecting to databases in my SQL Developer with the error
'unsupported verifier type'
I did some research on Google since our DBA team could not assist with this error. The suggestion based on my search was to add the line
AddVMOption -Doracle.jdbc.thinLogonCapability=o3
to the sqldeveloper.conf file.
Can somebody explain the importance of adding this line? What exactly does this line do?
Thank you.
This is a bug in Oracle side where certain applications especially running on WebSphere 7 with JDK 1.6 and ojdbc6.jar are not able to login to the Database. This is because of an Oracle driver “issue” when dealing with external 3rd party JCE libraries such as BouncyCastle.
Ref: https://vinaynotes.wordpress.com/tag/thinlogoncapability/
StackOverFlow Ref: ORA-01017 when connecting through jdbc thin driver
We found this parameter setting was necessary when authenticating to accounts that were using LDAP/Active Directory authentication ... IE enterprise user accounts (EUS) oracle accounts. Without this setting attempted logons received invalid id/password errors.
I've been attempting to migrate from my own MSSQL to Azure Database services.
I got all the firewall things working and the database running on the azure, but when I try to connect through the local pc it crashed with an unknown exception.
So does visual studio.
Any ideas what could cause this unknown error?
Heres a picture demonstrating the crash and its not a user/password error. Just not.
Maybe it's better if you try to provide the Exception/Error code. You can use:
http://msdn.microsoft.com/en-us/library/ff394106.aspx
I had similar problems and in the end it turns to be the connection I've used - so one option is to restart your LAN/Network.
Update: According to me is config related error, please see these solutions here:
http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/runtime-error-p6025-pure-virtual-function-call-on/89e10d2f-b949-e011-8dfc-68b599b31bf5
https://superuser.com/questions/628314/runtime-error-r6025-unable-to-see-location-of-program-causing-the-error
About SSL certificate and Browser you're using:
https://bugzilla.mozilla.org/show_bug.cgi?id=133476
http://www.symantec.com/connect/forums/r6025-pure-virtual-function-call-runtime-error
Maybe you've missed something, also what Win are you with?
I have tried to follow the instructions in chapter 1 of the HSQLDB doc and started my server like:
java -cp hsqldb-2.2.5/hsqldb/lib/hsqldb.jar org.hsqldb.Server -database.0 file:#pathtodb# -dbname.0 xdb
and I have reason to believe that worked cause it said (among other things):
Database [index=0, id=0, db=file:#pathtodb#, alias=xdb] opened sucessfully in 2463 ms.
However at the next step I try to connect using SqlTool and based on chapter 8 of the documentation I came up with this command to connect:
java -jar hsqldb-2.2.5/hsqldb/lib/sqltool.jar localhost-sa
Which gives the following error:
Failed to get a connection to 'jdbc:hsqldb:hsql://localhost' as user "SA".
Cause: General error: database alias does not exist
while the server says:
[Server#60072ffb]: [Thread[HSQLDB Connection #4ceafb71,5,HSQLDB Connections #60072ffb]]: database alias= does not exist
I am at a loss. Should I specify alias when connecting somehow? What alias would my database have then? The server did not say anything about that...
(also, yes I have copied the sqltool.rc file to my home folder.
Your server has -dbname.0 xdb as the database alias. Therefore the connection URL should include xdb. For example jdbc:hsqldb:hsql://localhost/xdb
The server can serve several databases with different aliases. The URL without alias corresponds to a server command line that does not include the alias setting.
java -jar /hsqldb-2.3.2/hsqldb/lib/sqltool.jar --inlineRc=url=jdbc:hsqldb:localhost:3333/runtime,user=sa
Enter password for sa: as2dbadmin
SqlTool v. 5337.
JDBC Connection established to a HSQL Database Engine v. 2.3.2 database
This error has been hunting me for the last 5 hours.
Together with this stupid error: HSQL Driver not working?
If you want to run your hsqldb on your servlet with Apache Tomcat it is necessary that you CLOSE the runManagerSwing.bat. I know it sounds trivial but even if you create the desired database and you run Eclipse J22 Servlet with Tomcat afterwards, you will get a bunch of errors. So runManagerSwing.bat must be closed.
See my sqltool answer over on the question "How to see all the tables in an HSQLDB database". The critical piece is setting up your sqltool.rc correctly and putting it in the right location.
You can also use the following statement for getting a connection from a files based store. this can be used if you are running the application from Windows.
connection = DriverManager.getConnection("jdbc:hsqldb:file:///c:/hsqldb/mydb", "SA", "");