I am new to using MySQL and I needed to download it for school, however, I keep getting this error message (picture below). I am using xampp and connecting using the username root. the port also matches what it is telling me. It will let me proceed but a lot of the features are missing. Any help at all would be appreciated.
Incompatible/nonstandard server version or connection protocol
detected (10.0.10).
A connection to this database can be established but some MySQL
Workbench features may not work properly since the database is not
fully compatible with the supported versions of MySQL.
MySQL Workbench is developed and tested for MySQL Server versions 5.1,
5.5, 5.6 and 5.7
As I can see, You are using latest XAMPP.
All you need to do is, after opening MySQL Workbench, and instead of setting up a new connection, Press CTRL+R or click on DATABASE tab in the top menu. Select Reverse Engineer and provide necessary information. You are good to go now.
The MySql workbench wont crash or show any compatibility issue now.
The current version of XAMPP uses MariaDB instead of MySQL.
Because MySQL Workbench is designed to work with MySQL and not with the very similar drop in replacement MariaDB, you are gonna have problems ...
So, if you want to use MySQL Workbench with XAMPP then a solution would be to try installing the last version of XAMPP that uses MySQL. That version is probably 1.8.3 from (August of 2014?). You can download it here:
XAMPP Sourceforge old versions
If you are using the latest XAMPP that uses MariaDB, in that case in your MySQL Workbench don't use 'Connect to Database' instead use 'Reverse Engineer' and provide the necessary credentials. That's all, No hassle.
I encounter the same message followed by a crash of MySQL Workbench, with version 6.3.7 (build 1199).
I didn't find a solution, but here is a work-around:
Once you press the button Continue anyway, just open a database use toto, and then wait a bit (a minute is enough in my case), and then you can call a query without a crash. I found this trick here.
I experimented the same with WAMP 3.2.0.
MariaDB was configured to listen to port 3306 (the usal MySQL port) and MySQL 8 was listening on port 3308. If you are in this case, don't be fooled by the fact you have 2 DBs.
To solve this, you have to choose the DB you want. I wanted MySQL and I just ask MySQLWorkBench to open a connection on port 3308 to MySQL.
You can ditch MySQL Workbench, and use the browser made for the MariaDB, they have a free version here: https://www.upscene.com/downloads/dbw
It's limited in its abilities, but I had no troubles connecting and browsing.
I had the similar problem because i was using Denwer at the same time.
To solve the problem:
Stop Denwer
Restart MySQL server
Profit! Now you can open your database in the Workbench
The idea is that denwer was starting its local server which didnt allow MySQL to start normally.
If you want to use denwer at the same time wth MySQL you can just start it after MySQL (Point 4).
In my case I already had MySql server and workbench installed and setup prior to my XAMPP installation. I wanted to continue with my existing setup.
I also installed MySql server with my XAMPP. I started mysql inside XAMPP and when I connected to MySql Workbench, I encountered the same error. Because Workbench was trying to connect with the server which was installed with XAMPP, apparently this was incompatible.
So I stopped mysql in XAMPP and started started mysql server manually(the previous setup and installed server).
Refer this to know how to start mysql manually in windows.
You can also config XAMPP to use your existing SqlServer.
So I had the same problem. For me none of the methods worked, but then I found out that my MariaDB was occupying the same port, so I uninstalled it and that solved the problem.
i had same issue, i changed the mysql server port from 3306 to 3308 in XAMPP config file.
[mysqld]
port=3308
Related
I am having trouble starting up a server through MySQL Workbench. From the navigator pane on the left side of Instance -> Start/Shutdown, I tried the "Start Server" button at which point the server will look like it will try to start. The workbench will get hung up at this point and indefinitely not respond with a "thinking" mouse icon while in the workbench app.
This is my first time learning to use MySQL workbench, which I want to say that when I initially installed MySQL Workbench a server did start after installation and worked fine. It was after restarting my computer and checking on the workbench the next day (today) that the server no longer runs. I'm not seeing any MySQL references in my Services (services.msc) that might relate to starting up but that might also be because I did not install as a Windows Service. My original troubleshooting was in trying to establish a connection, which I realized it was because the server wasn't running. Could someone help me understand why the server isn't starting? Or would it be recommended to install the workbench as a Windows Service to avoid the issue I'm having?
Screenshot of the MySQL Workbench window where the application will get hung up when starting the server.
Current setup: Personal workstation, Windows 10 (64 bit), MySQL Workbench 8.0 (version 8.0.29 build 1751076 CE 64 bits). I do not plan on running the server 24/7 since this is my personal workstation.
Right-click on My Computer
Select Manage
Select Services under Servies and applications
Find MySQL among the services and open it.
Choose Automatic as a start option.
Click on start.
Press Apply & OK then exit.
It is not necessary, but I still recommend restarting PC.
The solution below fixed my issue. I definitely recommend installing MySQL Server as a windows service and making sure uncheck mark the box that says to start when Windows starts unless you plan to have your computer as a dedicated server.
Source from #Lazycoder_007
This solution uses the window's mysql installer which you have used to
install your MySQL.
Start your windows mysql installer. For me it was
"mysql-installer-community-8.0.20.0"
Then remove/uninstall the SQL
Server and remove all configurations
Manually delete the SQL Server
folder from "C:\Program Files\MySQL\MySQL Server 8.0."
Start your
mysql installer again and install the SQL Server again
You can check
now that the MySqL Server has started.
I tried connecting the database from the server, but MySQL Workbench says that the connection cannot be made and declaring it as Bad Handshake. Can someone help me with this? But if I use the same user id and password and DB connections, it works on the other computer systems. Can someone solve this issue?
The authentication has changed from mysql V8, you must use a compatible client and server.
BTW it's a bug : https://bugs.mysql.com/bug.php?id=91828
Here is a workaround without uninstalling the new workbench.
The most probable case is having an old server with a new workbench:
get the server version
From a SQL cli tool:
SHOW VARIABLES LIKE "%version%";
or from a cli connected on the server:
$ mysql -v
It should show a version < 8.0, in my case 5.1.73
Get the mysqlWorkbench for a version <8.0:
You cannot install the msi if you already have a workbench V8.0, so you have to choose a portable installation form a zip file here:
https://dev.mysql.com/downloads/workbench/6.1.html
Select the version 6.2.5 (last before v8.0) zip version
Unzip
Close the workbench v.8 (it lock any other workbench launch)
Launch the V6.2.3 version of workbench, it should works.
This is probably because of a mismatch in the versions of MySQL servers.
Check the version of the MySQL server you are trying to connect to, and the version you have installed on the computer you are using, they have to be the same.
The reason of this warning is version problem. If you have installed mysql server version <= 5.1 and your remote server mysql version is greater than that you will face this problem. I recommend you to install 5.7 or greater in both your local and remote server. This problem will be fixed.
Fortunately there is an easy way around this. Use the old MYSQL ADMINISTRATOR tool as shown below. In my case I was trying to open a MySQL 5.1 database for a clients WordPress installation with MySQL Workbench 8 and that did not work out :).
ALl credits goes to https://www.urtech.ca/2019/01/solved-bad-handshake-mysql-workbench-failed-to-connect-to-sql/
Follow this link for the details
https://www.urtech.ca/2019/01/solved-bad-handshake-mysql-workbench-failed-to-connect-to-sql/
I am following tutorial from KNP/SymfonyCasts and I have problem with connecting to mysql.
That's what tutor write in her terminal
And that is my output
I assume this matter so... How can I change this? They do not cover issue, just mention that if blank password doesn't work, I should use "root".
MariaDB comes with XAMPP.
Since you installed XAMPP and are using it, obviously it will connect to its MariaDB installation. MariaDB is Mysql.
Don't install the MySQL that comes bundled with XAMPP or just change the config and point it to your other MySQL installation if you have one (a community server, for example)
Or just use the MariaDB(Mysql) from XAMPP.
I found OSX MySQL only reachable when I using MAMP in port 8889 for some reason, also I can not access them via MySQL CLI also, why? I've tried to add new IP tables and even stop the firewalls, but it still not work, CLI is a bit useless now. We already backup all the databases but don't know what is the safest steps to replace the current MySQl (MAMP) with pure MySQL or MariaDB and it's default server without reinstalling the OSX. Thanks.
Despites I've already installed XAMPP, I am trying to upload my database via MySQL server 5.7.17 since it's too big but both it and XAMPP use the same port - 3306. MySQL server is not even allowing me to continue to install it unless I make a change
SOrry, I'm a newbie.
Screenshots
Note It was suggested to me to download MySQL Server since I had already installed XAMPP but it didn't help me to upload my database.
No. If port 3306 is in use by an already installed and running MySQL instance, then another MySQL instance cannot use that same port. It is possible to run MySQL on a port other than the default 3306. But before we go there...
I think we might be barking up the wrong tree, trying to install another copy of MySQL and to run two instances of MySQL. Maybe we are wanting to run a different version of MySQL, other than the version other than what is included in the package we already installed.
But back pedal a bit here.
How is it that we reached the conclusion that installing another copy/version of MySQL was a viable solution to the problem we encountered?
It seems like we want to figure out the root cause of the original problem, before we chase down the wrong rabbit trail...