Bug #4565 Backup job has no result
Submitted: 15 Jul 2004 14:59 Modified: 7 Jul 2006 9:40
Reporter: Cyrisse Maniteaux Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.1.9, 1.0.6BETA OS:Windows (WinXP)
Assigned to: Mike Lischke CPU Architecture:Any

[15 Jul 2004 14:59] Cyrisse Maniteaux
Description:
I created a backup project and scheduled it. I noticed that Windows will run the scheduled task, but it doesn't create any backup file. It only seems to work when I run the backup job manually from Administrator.

How to repeat:
Schedule backup job and check for results.

Suggested fix:
No idea.
[15 Jul 2004 21:38] Michael G. Zinner
You can see the backup task (error-) messages in the Event Viewer in the Windows Computer Manager. I think that there is a problem with the password.

Could you verify if you have turned on the [Store Passwords] function in the options (Best set [Method] to Obscured so no plaintext passwords are stored)?

If this option is not enabled the backup task will not be able to log into the database and retreive the data.

We will add an error message to the backup task scheduling so one will be notified to enable this option first.
[13 Sep 2004 8:22] Ulrich Bayer
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
[30 Aug 2005 15:09] Curtis Paul
I changed the "-c" to "-C"   but I don't know what the -c is for so I don't know how this will effect your backed up data....but now it works with the microsoft sched...
[13 Jun 2006 13:11] Valeriy Kravchuk
Bug #20425 was marked as a duplicate of this one.
[13 Jun 2006 15:11] Lea Robson
From duplicate bug #20425

[13 Jun 15:10] Valeriy Kravchuk 

"Could you verify if you have turned on the [Store Passwords] function in the
options?"

Store Passwords is enabled.

If there was a username or password issue it will be raised in SchedLgU.txt, which it isn't.

Here's the ScdedLgU.txt report for failed password/username:

"Backup of Forum_Daily.job" (MySQLAdministrator.exe) 13/06/2006 05:30:00 ** ERROR **
	The attempt to log on to the account associated with the task failed, therefore, the task did not run.
	The specific error is:
	0x8007052e: Logon failure: unknown user name or bad password.
	Verify that the task's Run-as name and password are valid and try again.

Here's for '-c' - which fails to run:

"Backup of Forum_Daily.job" (MySQLAdministrator.exe)
	Started 13/06/2006 10:16:05
"Backup of Forum_Daily.job" (MySQLAdministrator.exe)
	Finished 13/06/2006 10:16:06
	Result: The task completed with an exit code of (0).

Here's for '-C' - which runs fine:

"Backup of Forum_Daily.job" (MySQLAdministrator.exe)
	Finished 13/06/2006 12:15:40
	Result: The task completed with an exit code of (0).

Lea
[7 Jul 2006 9:40] Mike Lischke
I wonder why changing to -C changed anything wrt to MA backups. -C is never read from the command line and can therefor not have any influence. However it is important to note that a user with admin rights has to create the scheduled backup. If a non-admin user does it you can however later change the user under which the task should run by using the task scheduler helper in the control panel.

I also added some code to make sure a stored connection is used for the backup.

Thank you for your bug report.
[18 Jul 2006 12:48] Lea Robson
Mike

From your comment I'm not sure if you have corrected the problem or indeed have even been able to reproduce it.

Please confirm if it is now corrected.

Many thanks
Lea
[18 Jul 2006 12:49] Lea Robson
Also, my use is always from a user with Admin rights.
[11 Nov 2006 2:03] Kent Lewandowski
I was just running into the same problem described in bug 20425, which is a duplicate of this bug (but which is documented more clearly).  

I implemented the "-c" > "-C" fix in Windows Task Scheduler, and it works now.

My question is whether or not this bug is being fixed in the next version of MySQL admin?