MySQL Bugs: #17094: Access violation at address 005B0A4C

Bug #17094	Access violation at address 005B0A4C
Submitted:	3 Feb 2006 9:12	Modified:	27 Mar 2006 8:42
Reporter:	Sébastien Barniaudy	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S1 (Critical)
Version:	1.1.19	OS:	Windows (Windows Server 2003)
Assigned to:		CPU Architecture:	Any

Description:
The status bar displays : 
Access violation at address 005B0A4C in module 'MySQLQueryBrowser.exe'. Read of address 00000000.
I read report #16506 in witch problem has been solved by installing 1.1.19. But the same problem occurs for usiong 1.1.19...
So, my config is the following : my DB (mySQL 4.1) is installed on a server (Win SBS). The query browser is installed on another one (Win 2003 Server) on the LAN. 

How to repeat:
Start Query Browser, message appears instantaneously in the status bar.

Thank you for a problem report. Sorry, but I was not able to repeat the problem you described with QB 1.1.19 (on XP), connectiong to MySQL 4.1.x. Please, inform about any service packs and antivirus software installed on your system.

I get the same access violation in the status bar error message, same version, and also windows server 2003. My access violation is 005BC79C in module MySQLQueryBrowser.exe

On the mySQL Server resident machine :
- OS : Win Server 2003 for Small Business SP1
- AV : Symantec AV

On the QB resident machine :
- OS : Win Server 2003 standard edition SP1
- AV : none

Please, try the newer version, 1.1.20. And, please, install QB from local Administrator account. Inform about the results.

I have the same problem using 1.1.20, XP Pro SP2. Interestingly, the problem goes away if you click in the box to the left of the error message on the status bar. after that, the application becomes useable.

Version 1.1.19 has been installed from an administrator account.

I cannot try to install a newer version because I have no access to the server any more...

Nevertheless, I replaced QB 1.1.19 by an old 1.1.5 I had (which works fine on another machine). The error message was still appearing, the application was usable, slow, but usable instead of being stucked.

At last, I granted all privileges to everybody on everything and now QB works fine!!

Please, explain:

"At last, I granted all privileges to everybody on everything and now QB works
fine!!"

What exact privileges you had granted, and where?

Everything, only wilcards (*.* to ''%''). Databases are wide open...

But if you had connected to your server as root user that was already the case - you had all the priviledges. So, please, specify, what account was used in QB to connect.

I am also seeing this behavior with the Query Browser, version 1.1.20, on Windows Server 2003.  The exact error is "Access Violation at address 005BC7B4 in module 'MySQLQueryBrowser.exe'.  Read of address 00000000".

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".

I was logged in as root via the MySQL Administrator, and I started the Query Browser from the Administrator via Tools->MySQL Query Browser.  Please reopen this bug.