So I'm trying to use a script generated by MySQL workbench to load a data dump into a MySQL database, however, I cannot seem to get rid of this error no matter what I do "wbcopytables.exe doesn't exist in the supplied path. Please set 'wbcopytables_path' with the proper path(e.g. to Workbench binaries)" The thing is, the path is set correctly (the default destination MySQL workbench is installed. This error is thrown in Powershell. When I try to run the script through the cmd line it simply closes and nothing happens.
I ran into the same problem, I've used the script in the past but it wasn't working after updating windows to 10 from 7. I had to do a fresh install of MySQL Workbench, so the bug might be in the latest version? Not sure. Here's the fix...
Remove...
if not ["%wbcopytables_path%"] == [] set "wbcopytables_path=%wbcopytables_path%"set "wbcopytables=%wbcopytables_path%wbcopytables.exe"
And replace with...
set "wbcopytables=%wbcopytables_path%\wbcopytables.exe"
worked for me, note sure if it's a "proper" fix, none the less, best of luck.
Related
I am getting an error while running a SQL script to load data. Error is pasted below:
Preparing...
[WinError 32] The process cannot access the file because it is being used by another process: 'C:\\Users\\PRATIK~1\\AppData\\Local\\Temp\\tmpf75l0wi5.cnf'
I have tried uninstalling and installing MySQL several times but nothing is helping.
I faced the same issues while trying to run a MySQL script. I tried to find the process in the temp folder and removed it and tried again but the process seems to start again and appears in the temp folder. I could not run the script, however, I found a workaround, instead of running the script try to open it and run it in the query editor.
Just downgrade your MySQL workbench version.
In my case I downgraded the version from
8.0.25 to 8.0.20.
The sounds like you already had tried that script execution before and stopped it without stopping the mysqld process. So this process (which does the actual import) still holds a file lock on the temporary config file.
Try removing that file and check that all MySQL processes that you don't want are stopped. Then try again.
It seems the actual issue is not related to MySQL itself, but to MySQL Workbench.
The error you're seeing is a generic error coming from Windows itself, not from MySQL. It's unclear how you're running MySQL, for example is it in your localhost, in a Docker environment, or in a remote server.
It seems clear that at least two processes are trying to get an exclusive lock on that temporary file. My guess is that MySQL won't write temporary files to the user folder we're seeing (with your username Pratik).
On Windows, MySQL checks in order the values of the TMPDIR, TEMP, and TMP environment variables. For the first one found to be set, MySQL uses it and does not check those remaining. If none of TMPDIR, TEMP, or TMP are set, MySQL uses the Windows system default, which is usually C:\windows\temp.
Something you can do is to change your MySQL configuration so it uses a specific Temporary path you'll set, restart MySQL and retry running the query. If you see the error contains your new temporary path you've isolated the issue, it is indeed a MySQL problem. If you keep seeing this path you've isolated the issue to MySQL WorkBench.
An alternative approach would be to run the same query from another MySQL client, for example the command-line client mysql; and see if you're getting the same error.
Probably the simpler approach would be to try the queries with dBeaver, another MySQL client, and use that to isolate the issue to either the MySQL server itself or MySQL WorkBench.
This is a common issue for the upgraded version of MySQL, Try using Open Script instead of Run Script and that seems to clear up the issue.
I've found that it was already reported in the official bug tracker: https://bugs.mysql.com/bug.php?id=104841.
I've just checked, and it's still present in MySQL Workbench 8.0.30.
Work Around
Do not try to open the SQL file from this tool bar:
Go to Server > Data Import:
select import from self-contained file
select your target schema
then start import (bottom right btn)
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 am using xampp stack to create a website but recently had to upgrade my OS and xampp stopped working.
MySql server would not launch in the new OS. I looked around here for solutions and found a lot that said I should delete the Ibdata file.
I did and it solved my initial problem but now MYSQL is close to useless. Every database is giving an error and trying to create a new one just keeps on loading forever.
Is there any way to fix this? to reset MYSQL to initial state or something? I dont need to recover the databases as they were only tests I just need to be able to create new ones but nothing works anymore.
I'm trying to get Drupal 7.28 installed on Ubuntu and have run into this very common but not so easily fixed issue of the WSOD during configuration due to the database not being properly set up on an earlier step (only 31 tables created). https://www.drupal.org/node/481758
Many people have fixed this issue by dropping the database and recreating it, which I've tried, but when I try to run /install.php again it insists that it is already installed and I must empty the database if I want to reinstall.
So I tried deleting the database and NOT recreating it but the installer still says it is already installed and I have to empty the database WHICH DOES NOT EXIST if I want to reinstall.
What do I need to do to get the install script to run again?
Ahh. I needed to go back to the default settings.php for the site, then it worked.
in /var/www/drupal/sites/mysite.com
mv settings.php old_settings.php
cp default.settings.php settings.php
Now going to mysite.com/install.php starts over at the beginning of the install.
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.