MySQL Bugs: #16858: Division by zero at startup

Bug #16858	Division by zero at startup
Submitted:	27 Jan 2006 22:20	Modified:	14 Feb 2006 9:22
Reporter:	Jay Pepper-Martens	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S1 (Critical)
Version:	1.1.9	OS:	Windows (Windows Server 2003 Web Edition)
Assigned to:		CPU Architecture:	Any

Description:
I have a clean install of Query Browser 1.1.9 on a Windows 2003 Server Web Edition machine.  When I start Query Browser, the status bar has an exception message and the software is totally non-functional.  If I try and double click on a table name in the listed schema (which is valid) I get a second more cryptic exception message.  This makes interacting with my database from this development test machine totally impossible.

This machine has very little software installed on it, a few plain text editors and the MySQL Administrator latest version (1.1.7).  The actual MySQL database is NOT installed on this machine.  IIS is running, but is not unusually configured.

Screenshot for download (names, IP's obscured) 
Startup Exception:   http://kyro.sytes.net/mysql/Excep_Startup.jpg
Exception after DblClick:   http://kyro.sytes.net/mysql/Excep_DblClick.jpg

How to repeat:
Clean install of Windows Server 2003 Web Edition
Install MySQL Administrator 1.1.7
Install MySQL Query Browser 1.1.9
Start MySQL Query Browser and it is non-functional, displaying only the exception message in the center status bar (see the screen shot for Startup).

Not just plain jane WinServ '03.   WEB EDITION

Hi!

I can't find a way to reproduce this bug.  Can you please tell me exactly what steps need to be taken in order to reproduce it ?

Thanks

I can't really tell you anything more than what I have.  I can tell you that there is no install of the MySQL database locally on the machine, the software was installed with a secondary account that does not have Administrator priveleges, only Power User.  Perhaps that is related?

Yes, it can be related (I was also not able to repeat the behaviour you described on XP, but installed with account from local Administrators group). So, please, try to install QB as one of (local) Administrators and inform about any changes in behaviour.

We had the local administrator run a repair install using the actual administrator account and this seems to have corrected the problem.

I'll close this report as the problem seems solved.