Bug #10194 | scheduled backup causes memory access violation | ||
---|---|---|---|
Submitted: | 27 Apr 2005 5:36 | Modified: | 29 Jun 2005 15:52 |
Reporter: | ed Miller | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | 1.0.20 | OS: | Windows (windows 2000) |
Assigned to: | Jorge del Conde | CPU Architecture: | Any |
[27 Apr 2005 5:36]
ed Miller
[29 Apr 2005 2:14]
ed Miller
version not 4.1.1 it is 4.1.11
[29 Jun 2005 15:52]
Jorge del Conde
I was unable to reproduce this bug using 1.0.21.
[5 Aug 2005 22:33]
Chris Wilkinson
I have the same problem. The backup executes manually but not scheduled. Application popup: MySQL Administrator: MySQLAdministrator.exe - Application Error : The instruction at "0x005c9b4b" referenced memory at "0x00000008". The memory could not be "read". Click on OK to terminate the program Click on CANCEL to debug the program Clicking CANCEL gives no additional information. The application log has a DrWatson event 4097 The application, C:\Program Files\MySQL\MySQL Administrator 1.0\MySQLAdministrator.exe, generated an application error The error occurred on 08/05/2005 @ 23:23:29.625 The exception generated was c0000005 at address 005C9B4B (MySQLAdministrator) MySQL version is 4.1.12a MySQL administrator version is 1.1.0-rc
[5 Aug 2005 22:34]
Chris Wilkinson
Forgot to mention the OS is Windows 2003 SP1
[13 Apr 2007 16:30]
Colin McMillan
We had a similar problem on one of our servers: Windows 2003 SP1 MySQL 5.0.37-community-nt MySQL Administrator 1.1.19 As above, I could run the backup manually from Administrator, but when I ran from scheduled tasks I got a similar "The memory could not be read" error. This was resolved when I upgraded to GUI Tools for 5.0 (i.e. Administrator 1.2.11). I had to uninstall the previous version and completely reboot before it worked though, but it seems to be fine now. Hope this helps someone.