Bug #744 mysqlCC does not start
Submitted: 27 Jun 2003 23:12 Modified: 21 Aug 2003 0:39
Reporter: Dirk Coetsee Email Updates:
Status: Closed Impact on me:
None 
Category:MySQLCC Severity:S2 (Serious)
Version:0.9.2 OS:Windows (WindowsXP)
Assigned to: Jorge del Conde CPU Architecture:Any

[27 Jun 2003 23:12] Dirk Coetsee
Description:
MYSQLCC does not start when try to run it. No messages are displayed. Nothing in event log.   

How to repeat:
On my machine I only have to select it from the start menu
[27 Jun 2003 23:42] Dirk Coetsee
Installed mysqlcc on a different machine (also XP) and it works fine. 
How can I trace what goes wrong?
[30 Jun 2003 10:20] Jorge del Conde
Hi!

Can you please rename the folder ".mysqlcc" found in "Documents and Users"\[your_username]\.mysqlcc to something else try again ?

Note, the above will make mysqlcc start with all the default options thus making it easier to trace the problem.
[30 Jun 2003 11:25] Dirk Coetsee
Hi, 
The .mysql directory was empty. Problem still prevail. 
Dirk
[24 Jul 2003 13:00] Robin Bolton
I too was experiencing this problem with MySQLCC. I formatted & reinstalled my OS (Windows 2000 Pro SP2, now running SP4), that's when I figured out where my problem was creeping in.

The my.ini file that I had placed in my C:\WINNT folder was based on a previous MySQL release, and had configuration entries that appear to be specific to MySQL for Unix, rather than for Windows, even though this was created from a mysql sample configuration included with MySQL for Windows. I have found this to be the case with several applications originally written for Linux and then ported to Windows (MySQL, PHP, Apache, etc).

e.g.
OLD CONFIG:
socket = /tmp/mysql.sock

NEW CONFIG
#socket=MySQL

If I either delete my custom my.ini or create a new one from the current mysql release it seems to work fine, and MySQLCC launches with no problems.

I would suggest to try deleting any my.ini or my.cnf files from C: or C:\Windows folder and try running MyCC again.

-R
[25 Jul 2003 6:57] Dirk Coetsee
The problem was an old release of my.ini  in \windows directory. 
Thanks for the help.
Dirk.
[21 Aug 2003 0:39] Jorge del Conde
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html