MySQL Bugs: #12906: Scheduled backup fails with Exception EAccessViolation message

Bug #12906	Scheduled backup fails with Exception EAccessViolation message
Submitted:	31 Aug 2005 11:40	Modified:	2 Sep 2005 17:29
Reporter:	Murray Muspratt-Rouse	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.1.2	OS:	Windows (Windows XP SP2)
Assigned to:		CPU Architecture:	Any

Description:
Scheduled backup fails with message "Exception EAccessViolation in module MySQLAdministrator.exe at 001C9C43. Access violation at address 005C9C43 in module MySQLAdministrator.exe Read of address 00000008". 'Execute Backup Now' does not fail.

User is set up with full privileges to all objects. Backup is scheduled weekly Monday to Friday. InnoDB Online Backup has been selected, with 'Add DROP statements', 'Complete Inserts' and 'Comment'.

MySQL Server 4.1 is installed on a PC that also has the Microsoft Access front end.

How to repeat:
On this PC I have no problem repeating it

Hi!

I can't reporduce this bug.  Can you please give me specific instructions on how to make this happen ?

Thanks!

I expected that the bug would be difficult if not impossible to reproduce. You would need to have MySQL Server installed on the same PC as MySQL Administrator under MS Windows at Service Pack 2. Since the exception is an access violation am I correct in assuming that the essential is that the security setup must be correct? Remember that I can run a backup on-line, when signed into the MySQL Administrator with the root username. I have tried setting up a scheduled backup using the root username, but the same error occurs. I have defined that the password is obscured, as the manual requires. Perhaps I should put this problem to a user forum.

Thanks for your bug report.  Unfortunately, without a reproducible test case or useful information that leads us to where the bug is, this problem can't be fixed.  If you find any way of reproducing this problem please let me know ok ?

Thanks!

Following a search under MySQL Administrator I have fixed my problem by adding a stored connection to the MySQL Administrator function. I obviously failed to find the instruction to do this in the small print!

Murray

I'm having the same problem on two separate machines, both running MySQL 5.0.18-nt. Both machines are running WinXP Pro Sp2, and in both cases I'm logged on as the administrator. I can also run backup's immediately with no problem - it's only when schedulling is used that this error is generated.