Bug #17638 Access Violation at addresss....
Submitted: 22 Feb 2006 6:06 Modified: 27 Mar 2006 16:15
Reporter: Marco Salimu Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Administrator Severity:S1 (Critical)
Version:1.1.9 OS:Windows (windows xp proffession)
Assigned to: CPU Architecture:Any

[22 Feb 2006 6:06] Marco Salimu
Description:
When clicking User administration,Service Control ans startup variables it give the above synopsis. before I was using the the version 1.0.19 with 5.0.18 server. the same above msg appeared when i was editing table,i reinstall the 1.1.9 the latest version the problem resolved but shifted as above synopsis state. but Im now using version 1.0.20 the problem have been resolved. 

How to repeat:
When clicking User administration,Service Control ans startup variables it give the above synopsis. before I was using the the version 1.0.19 with 5.0.18 server. the same above msg appeared when i was editing table,i reinstall the 1.1.9 the latest version the problem resolved but shifted as above synopsis state. but Im now using version 1.0.20 the problem have been resolved.
[22 Feb 2006 10:42] Valeriy Kravchuk
Thank you for a problem report. Please, specify the exact error message you got, with address. Did you install MySQL Administrator from local Administrators account? Do you have any service packs and/or antivirus software installed?
[22 Feb 2006 12:17] Marco Salimu
the exact error message 

"Access Violation at address 0034C1B0 in module libmysqlx.dll read of address 00000000"

yes i had installed MySQL Administrator from local
Administrators account.

yes i have service pack 2 and antivirus
software (Mcafee) installed.
[27 Feb 2006 16:15] Jorge del Conde
Hi!

I was unable to reproduce this bug.  Can you please tell me if there's anything else that you did that might help us reproduce it, or see if its specific to your system ?
[27 Mar 2006 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".