I have been using MySQL workbench for years. Recently the previous version 8.0.nnn stopped launching. I decided to try to repair the installation by upgrading. It worked for a few days and now it hangs again.
Uninstalling and reinstalling is not helping.
There are no notifications in event viewer. There is a task (process) in Task Viewer, but the process does not progress to showing a window.
I can connect to, and query, the server on the command line or via the API (not that it is required for launching Workbench).
Any ideas about origin of this rather perplexing problem?
I discovered that the user data (User\AppData\Roaming\MysSQL\Workbench) contained corrupted files.
The error message popup (window) remains hidden, but can be seen when using Alt-Tab to rotate between applications. One cannot bring focus on the error window, but one can see the message among the choices in the Alt-Tab interface. I could see something about corrupt file and that it was in the profile's Roaming.
Deletion of the single file that was indicated (wb_state.xml) was insufficient to get WorkBench to display. Deletion of all files in the Workbench directory restored Workbench.
Hope this is of some use to others.
Related
I'm trying to get MySQL up and running for some analysis on my Mac.
MySQL version: 8.0.19
MacOS version: 10.14.6
The timeline is:
I installed MySQL successfully from https://dev.mysql.com/downloads/mysql/
It worked fine, I was able to create simple tables, etc. But when I tried to create my real schema, I realized that the default record size of 8k bytes wasn't enough; I had to increase it to the maximum, 65k bytes https://dev.mysql.com/doc/refman/8.0/en/column-count-limit.html#row-size-limits.
After reading the documentation, I learned that the row size can only be set when the database is initialized for the first time. So I wanted to start fresh, ensuring that when I first initialized the DB, the appropriate parameters were set.
So, I uninstalled MySQL using the widget in my Mac's Command Center. I rebooted, ensured no MySQL processes were running, then ran find -iname 'mysql' 2>/dev/null in the terminal, and found nothing. All traces, so far as I can tell, of MySQL were gone.
I downloaded the macOS 10.15 (x86, 64-bit), DMG Archive package again from https://dev.mysql.com/downloads/mysql/, installed it, used all the default settings in the installer, and then opened the MySQL widget from the Command Center again.
Here's where I configured the parameters. There's a place where I can put in a configuration file. So, following the advice in this How to workaround the row size limit of 66 KBytes, I created mysql.cnf in my home directory, put only these three lines in it, and put the filename in the box (checking the tickbox next to it):
innodb_page_size=64k
innodb_log_buffer_size=32M
innodb_buffer_pool_size=512M
I hit "apply". Then I went back to the other tab, hit "initialize database". No errors, seemed to work fine. Then I hit "start MySQL". The lights went briefly green, then red again. Multiple attempts, reboots, etc, don't seem to have any effect. In short, MySQL was trying to start up, but failing.
I also tried removing the mysql.cnf file, hitting "apply" and "initialize" again, and the problem is the same. I don't understand why this all worked before I uninstalled, but won't now.
I checked /var/log/system.log, and all I see is a bunch of lines noting the failure of MySQL to start:
but nowhere is the error from the application itself shown.
I did some Googling and SO'ing and looked in /usr/local/mysql/data/ as root, and I can see files that are in binary. But i do not know how to read these binary logs.
My questions:
How can I tell what error is preventing MySQL from starting?
How can I diagnose this issue? Is there a tool to read these binary files?
Does anyone know why MySQL would fail to start after a full wipe and re-install, though it was working in the first instance?
I experienced MySQL's failing to start from the System Preferences on Mac. It would turn green and red again. I also wiped and reinstalled a few times and it still wouldn't start.
In my case, I realized it was because I had AMPPS stack installed and its MySQL running at the same time. After turning off the MySQL in the AMPPS stack, I was able to start MySQL from the System Preferences successfully. Not sure if you had another software stack running that would cause the problem.
I have a problem to export a small database using MySQL Workbench's Data Export function on Windows 10.
Previously I have had no problems exporting and importing databases, although after this happened I have changed the security of the server to legacy to get it working with phpMyAdmin using the MySQL Workbench Installer, which I have been unable to change back as when trying to execute the change I got an error stating the installer was unable to create the temporary user (running this as administrator didn't help).
Since then I have also updated MySQL Workbench, the server, and the rest of the components that were installed with it, which seems to have gotten rid of the MySQL Workbench Installer application, as such i am unable to provide the exact error it gave regarding being unable to create the temporary user.
I'm not 100% sure if the above is relevant to the issue but it does seem like it could be related.
The issue that I'm trying to fix is that MySQL Workbench will not export any (or all of) the databases I have set up to a self contained file. The error I keep getting is below:
09:47:47 Dumping va_form (all tables)
Error executing task [Errno 2] No such file or directory: u'D:\Mike\Desktop\Dump20190226.sql'
09:47:47 Export of D:\Mike\Desktop\Dump20190226.sql has finished
I was previously getting a similar error about access denied, which then lead me to change the default dump directory to my desktop, as I'm only going to need to dump files occasionally and sort and send them elsewhere straight away.
I have also tried disabling column-statistics and lock-tables although this has had no effect.
As you can see, at the start of the directory it's trying to dump to it says "u'D:\\" - I am not sure if this leading u is significant, although it is not there in the directory I have specified to dump the file to.
I'm hoping someone here has some insight into this issue, I have no idea why MySQL Workbench's installer was refusing to make the temporary user (even when being run as administrator) and why I cannot find the installer now, as well as the obvious problem of why MySQL workbench is unable to create the file to dump anywhere on the system.
Thanks very much for your time reading this.
It is probably an issue with a recent update of Windows Defender, not with MySQL.
Try to save your dump to folders located somewhere else than Desktop or Documents (I usually send them directly to a cloud service integrated with my OS). If this works, you just need to add an exception for MySQL in Windows Defender.
I have a SQL Server 2008 Job that backs up a database, then zips that backup and moves the zipped file. My job runs fine until it gets to the step that calls WinZip, which executes:
c:\program files (x86)\winzip v19.5\winzip32.exe
-m \\RemoteShare\RestrictedFolder\dbBack.zip
x:\SQLInstanceFolder\BackupFolders\dbBack.bak
The job neither completes nor fails; it just stops moving forward. It will generate the dbBack.bak file and create the dbBack.zip file in the remote location, but it won't proceed past there. It seems to be behaving like it is waiting on a pop-up confirmation, but I don't see one when I log in to the console or run the zip from the command line.
I've tried adding -ybc flag to automatically confirm or skip any prompts, but it didn't seem to do anything. The process still didn't complete. I've even tried to > pipe output of the process, but it won't even write my log file.
This is a secured system and infrastructure, but I'm fairly certain I'm not being blocked by a permission. My SQL Server service account that runs the job has access to the folders it needs and it can run the winzip32.exe process. This process ran fine, but we had to upgrade WinZip this past weekend (19.5), and that's when it stopped working properly. We aren't able to roll back to the previous version (10).
Does anyone have any idea on what could be stopping my process or how to make it proceed?
I think I discovered the problem. It turns out, we are using the GUI version of WinZip and calling the executable from the command line. Even though we can't see the GUI, it's still there. So, the prompt to confirm our compression is still there in the program's workflow, we just can't see it and thus can't confirm it. And the confirm flags don't work with the GUI version.
My workaround involved logging in to my SQL server as our service account and running a WinZip operation. When it completed and gave me the Add Complete prompt, I checked Do not display this dialog in the future and clicked OK. This will suppress that prompt when the service account runs its Job.
If someone changes the service account, we'll have to do this again, so our ultimate solution will be to install the WinZip Commmand Line Plugin. Hopefully, when that's done, we won't have to worry about this.
But it works now. :-)
I have MySQL workbench installed on my computer and always worked correctly. Now try to run it and do not run. Gives an error:
MySql Workbench has encountered a problem
External component has throw an exception.
We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below.
Please make sure to include a detailed description of your actions that lead to this problem.
Thanks a lot for taking the time to help us improve MySQL Workbench!
The MySQL Workbench Team
And then the application crashes.
Figured it out. I saved off a "new" .sql file while in Workbench. I exited Workbench. When launched again is when I got the error.
For some reason I looked at the folder I saved the .sql file in and noticed it was 0kb in size. I deleted this file and re-launched Workbench ... it launched normally.
Problem solved ....
Because your computer doesn't have Visual C++ Redistributable Packages for Visual Studio 2013 ;)
[Problem resolved]
MySQL Workbench has encountered a problem
same error i got it
Reason-
i don't have enough space in my drive.
Solution
I had deleted and moved some files.
Start Mysql Workbench it start working as expected
When it start mysql workbench all database schema will be empty
All database restored in mysql workbench
Restart the mysql80 service
Goto control pannel
Click on Administrative tools
Select Mysql80 and click on start button
Re-open the mysql workbench
It shows all your data
You can solved the above error with this steps
I've been trying to install SQL Server 2008 R2 with tools.
I've downloaded thisn version and it just won't work!
I've had some problems installing Visual Studio SP1 due to silverlight4 being already installed, so I figured i needed to uninstall everything that had something to do with sql server, so I did.
Still the errors show up.
These 2 errors show up at the beginning of the installation during "Setup support files".
(I can't post more than 2 url's yet, so Ive put all the screenshots in 1 image, sorry)
Here
The first error is the top left one, and retry fails, and when I hit cancel a few secs later the second error pops up and the installation terminates.
My OS is W7 x64 with all updates installed.
I don't really know how to go on actually. I've searched for hours yesterday without any results.
Anybody got a clue? Before I reinstall every .net-related programs.
Thanks in advance!
Edit:
So far I've tried:
I checked if the first file shown in error 1 is actually there, and it is.
Tried to run the setup explicitly as administrator
I checked if the second file/folder was present, and it was not. So I manually created the folder and file, which then causes the
first error to say the same, but then it says can't create
\SqlSupport_Cpu64_1_ComponentUpdate_1.log, then I tried
to create an empty file with that name and extention. This makes the installer
append the filename with "_1". If I create that file too, it just
appends with a higher count.
Uninstalled every sql server related program (e.g sql server compact)
Reset all the permissions on the e: disk and formatted it.
I found the cause of the problem. Recently I'd set my default program files folder to my hdd, because my C: is a 60 GB SSD. The key is located in the register at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion. The keys "ProgramFilesDir" and "ProgramFilesDir (x86)" are the ones that need to be default ("C:\Program Files" and "C:\Program Files (x86)") in order for it to work.