I recently tried to create an FAQ Page with the TYPO3 extension jpfaq.
I did set up everything as it was described in the manual. But for some reason when i preview the page, it shows a bunch of different error. For example:
TYPO3\CMS\Extbase\Persistence\Generic\Storage\Exception\SqlErrorException
Table 'xxx_typo_dev.tx_jpfaq_domain_model_ttcontent' doesn't exist
When I "unbind" the FAQ database I created it shows me the correct FAQ page (just without the questions and answers). So there might be a problem with the database?
Cleared cache. Deleted and installed the extension again. Didn't help.
Sounds like the you need to fix the Database Structure.
Normally the Database Structure is fixed when you install new extensions in the Extensions module.
If you use Composer Mode the installation is done with composer and you need to fix it by hand.
This can be done in the InstallTool / Maintenance Module: Analyze Database Structure.
Or you use the commandline: vendor/helhum/typo3-console/typo3cms database:updateschema (don't forget to use composer require helhum/typo3-console)
I'm scared to ask this because people can be a little mean on here but I've watched 1000 of YouTube videos and went through just as many google searches. I was trying to create a data dictionary for mysql diagram. I used this website https://dataedo.com/kb/tools/mysql-workbench/how-to-export-data-dictionary#toc_0 to help me. I downloaded the .py link listed in the install plugin step. The followed the instructions in mysql. It said the plugin install was successful and to restart my workbench. After that I started getting the error shown in the picture. I have tried everything:
Restart workbench
Repair workbench through msi download
Followed the steps in this link: https://www.tutorialspoint.com/how-do-i-kill-all-the-processes-in-mysql-show-processlist
Updated all my sql products in mysql installer
Made sure mysql services were turned on and running
I don't know what else to do. I can't even open workbench to see if the plugin is the issue because again I can't get in. I just need some help
That is a strannge error, where mysql workbench has some corrupt files.
Deinstall MySQL Workbench with the MySQL Installer
Install Workbench again
So everything will start normal again, the configuration and connections will stay and can be used again as normal
This is not an installation issue, so don't waste your time by trying to fix this issue by repeating the installation.
The error comes from the approach where MySQL Workbench tries to ensure there's only one instance of it running. For that it searches the process list for another instance and, if one was found, sends the command line parameters it got to that instance, letting the already running instance handle them (and shuts itself down after that).
But again: this happens only if another instance is found, so check your process list carefully. Filter by the term "MySQL" to see any MySQL related processes (including that of a MySQL server). Shutdown/kill any of these processes and try launching WB again.
Same issue happened to me and it was like what the heck. Don't waste your time to uninstall and reinstall because it won't solve your problem.
Solution: open your file explorer and delete the entire folder "Workbench"
Path: %appdata%\MySQL\Workbench
I have the same issue with this file.
Just as Jr Relampagos says, delete the .py file here : AppData\Roaming\MySQL\Workbench\modules
Restart Workbench, it works for me.
With me I'm just go to C:\Users<USER>\AppData\Roaming\MySQL\Workbench\modules and then delete the .py file you install, then open the Workbench again
Every time I start MySQL workbench I get this message
I would like to know what this means and how I can get rid of it... I tried looking on the internet and googling the entire message but no good info came up because you can't see the full message.
Does anyone know what this means and if it's a problem for my database?
MySQL Workbench tries to load its workspace data and something is wrong with it. Rename the MySQL Workbench folder (the part you can see in the message) or remove it entirely. Then restart the application and it will recreate all the files.
A side note: often Ctrl+C works in those dialogs, so you can paste the entire content into a text editor.
It's only MySQL workbench which is a GUI for data admin if i'm not mistaken (like navicat). You could simply run the mysql installer and remove/add MySQL workbench again.
I am using MySQL Workbench 6.3.7 build 1199 CE (64 bits) on a Mac with OS X Yosemite 10.10.5. I am connecting to an Amazon RDS MySQL instance.
When I enter a simple query such as
select * from `devices`;
and click the lightning-bolt-with-cursor icon, the query starts, indicated by the spinner activating next to the "SQL File 4" tab in the following screenshot. However, the query doesn't complete and it just hangs. The white-hand-in-red-stop-sign icon is disabled.
I can only force quit MySQL Workbench from this point on. If I try to do a regular quit, nothing happens.
How can I consistently run a simple query on my database? Sometimes it works (maybe 10% of the time), but it mostly just hangs.
UPDATE 3: The problem is fixed for MacOS HighSierra in MySQL Workbench 6.3.10.
UPDATE 2: It looks like the bug is recurring again in MacOS HighSierra. See https://bugs.mysql.com/bug.php?id=83658 for more details.
There is an unofficial build that fixes the problem. You can download it at: https://drive.google.com/drive/folders/0B2fTesDcrHzVRGVFWEdILWpuaEE?usp=sharing
The build was created by Bob Davenport. See https://bugs.mysql.com/bug.php?id=87714 for more details.
UPDATE: The bug is fixed in MySQL Workbench 6.3.9.
----------------------- original answer -----------------------
It is a known MySQL bug: http://bugs.mysql.com/bug.php?id=83658 caused by GateKeeper Path Randomisation introduced in MacOS Sierra. See https://weblog.rogueamoeba.com/2016/06/29/sierra-and-gatekeeper-path-randomization/.
A possible workaround is to remove the Quarantine ACL:
xattr -dr com.apple.quarantine "/Applications/MySQLWorkbench.app"
I found that if you use the latest 6.3 version, that in order to get queries to work, you have open a first connection and ignore it and then open a second connection. This creates two tabs in the workbench. If you perform your queries in the second tab, it works. If you try in the first tab, it hangs.
I also have found that you have to do a force quit the workbench.
I hope the mysql folks get this fixed.
To resolve this issue, I downgraded MySQL Workbench to 6.1. Now I am able to run my query and it doesn't hang.
In my case, it was changing the connection->ssl->Use SSL setting from "If available" to "No". Workbench 6.3.8 on OSX 10.12.1 now works for me.
The spinning wheel of death is due to the new feature introduced in the Sierra update called "Gatekeeper Path Randomization".
Follow the instructions:
Open MySQL Workbench :)
Right click on your connection (most likely “localhost” or “127.0.0.1”)
Choose “Edit connection”
On the right hand window select “Connection > SSL”
Change “Use SSL” from “If available” to “No”
Now click on the tab “System Profile”
Choose “MacOS X” as System Type
Click “Test connection”
Credits: http://cordobo.com/2398-mysql-workbench-6-3-macos-sierra-hangs-on-simple-queries/
The version 6.3.9 solved the problem, but this version is not showing in "Check for upgrades" option, you need to download directly from the site.
MySQL Workbench official download page
6.3.9 fixed the issue in the mac. Here is the link MySql 6.3.9
At last I have downloaded MySQL Workbench 6.3.10 and install MySQL Workbench 6.3.10 and solved my problem. I have downloaded MySQL Workbench 6.3.10 from bellow link https://dev.mysql.com/downloads/workbench/
It is working for me.. I think this will work for you..
I found that deleting the cache and workspaces folder contents (~/Library/Application Support/MySQL/Workbench) it works again. What I haven't found is how to ensure it doesn't hang again :-(
I also found that if I manually close the Connection tab from the menu and exit WB from the menu and not from the OS window buttons it seems more stable next time.
PS: I am using SSH connection so it may be due to this but it is not always happening.
UPDATE: A clean install and no SSH configurations the issue still persists. Unless you manually go and delete the cache folder files it continues to hang.
I was getting around the problem for awhile by deleting the user library folder and dropping back to version 6.2.5 ... but today found the problem was back. So today I deleted the user library folder and dropped back to version 6.1.7. It's working again, for now.
In my case, the IP address changed where mySQL was served.
Flushing the DNS fixed it for me:
sudo dscacheutil -flushcache;
sudo killall -HUP mDNSResponder;
say cache flushed
This seemed to help some of the time, but not 100%:
Connect to the database with a different user, and then re-connect with the original user.
I'm about to downgrade like the accepted answer says though, as this doesn't solve it every time.
This is still an open bug in 6.3.8:
https://bugs.mysql.com/bug.php?id=82231
The possible workaround is to open secondary tab with the same connection and work in there. However it crashes anyway from time to time.
Until the bug is fixed I use free Mysql Workbench aleternative for common work. For mac users I would suggest https://sequelpro.com.
Upgrade to 6.3.9 fixed the issue. The 6.3.4 was hanging on queries for me. Unfortunately the Help > Check for Updates didn't indicate any updates were available, so I went to the source.
This can probably help as a temporary/immediate solution. If I try to manually type the below query, MySQL Workbench hangs, especially at x.*
SELECT
x.*
FROM x_table x;
But if I write the SQL in another editor and paste it in MySQL Workbench and run the query, it doesn't hang.
Versions: MacOS Big Sur (11.2), MySQL Workbench 8.0
When importing a cvs file into postgresql using pgadmin III, it says import successful and then I am able to hit done. However, when I look into the table -- no data is there. Has anyone experienced a similar issue ? I have imported in the past, with no change in environment, to success, but I do not know what is happening now