MySQL Workbench includes visual tools for mysqldump. Easily export/import data by selecting the database schemas and/or tables from the Object Browser. Advanced configurations are available for concurrency controls, backup type, and output formatting.
If that doesn't work I have no idea. On linux you can try to move the socket to a new location too, but that shouldn't affect windows. Alternatively you can use a symbolic link on *nix what most people do I guess.
I've been Googling for day's and I can't find a solution for this. Does anyone know why my automated backup via the MySQL administrator is not working on MS Windows 2008 and why it isn't even creating a log file?
Of course you have to do everything by hand but is also better. I got this same issue in PostgreSQL because o windows "at" is different from linux "cron". Since than, I started to do my own "cron" jobs.
I tried also using version 1.2.17 with win 7. I faced the same problem.MySQL ADMIN is scheduling the backup via the windows scheduler. I realy don't know why but when i scheduled the backup(when i SAVE the new created project) under a user with an ADMIN account it didn't operate. When i scheduled the backup under a standard ACCOUNT it operated fine. to solve this problem i defined a new standard account in WIN 7 . I am logging to win 7 under my primary account and scheduling the backup under the new account . Now it works fine .