Bug #24019 | Section not enabled | ||
---|---|---|---|
Submitted: | 6 Nov 2006 16:07 | Modified: | 7 Dec 2006 10:05 |
Reporter: | Marcelo Diniz | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | 1.2.5 rc | OS: | Windows (Windows XP SP2) |
Assigned to: | CPU Architecture: | Any |
[6 Nov 2006 16:07]
Marcelo Diniz
[6 Nov 2006 16:11]
Marcelo Diniz
All tables in my innodb databases now has the text (In "Catalogs" section): "Incorrect information in file: .\dbinfo\<table_name>.frm".
[7 Nov 2006 10:05]
Valeriy Kravchuk
Thank you for a problem report. Please, describe this: "Everything was fine until I apply some changes I've made (enabling the option to log binary files) and restart the mysql server and the program." in more details. I was not able to repeat: after enabling option to log binary files and server restart MySQL Administrator works as expected. Please, also try to use newer version of MySQL server, 5.0.27.
[17 Nov 2006 17:48]
anne blankert
I had the same problem: (maysql administrator 1.2.5.rc, mysql server 5.0.27-community-nt) Problem disappeared after: file mysql.ini section [mysqld], uncommented port=3306 Be aware that ini file section [client] also contains a setting port=3306, but that setting seems to be unrelated to this problem.
[17 Nov 2006 18:06]
anne blankert
Hmmm, after enabling the port setting in file my.ini by hand and restarting both mysql and mysql administrator, I am no longer having the reported problem, but it now appears that myssql administrator (1.2.5rc) automatically disables all settings under "startup variables". Apparently mysql administrator was not able to load or read the my.ini settings?
[19 Nov 2006 8:26]
Aaron Hayward
I'm having the same problem. Changing the values in mysqladmin does change the values in the my.ini file, but mysqladmin doesn't load them when it starts. And each time you change a value via msqladmin, it comments out the port line again, so it doesn't start properly next time.
[20 Nov 2006 16:01]
Chris Barnard
I am also having exactly the same problem on Windows 2003 server. Is this a bug in the latest version of the MySQL administrator?
[20 Nov 2006 16:10]
Chris Barnard
I rolled back to MySQL administrator 1.1.9, which works fine.. was previously on 1.2.5 rc.
[21 Nov 2006 16:44]
Craig Reilly
Anyone know how to fix this? I saw another bug post on this: #23837. But I was confused. I too am running MS Server 2003 Standard.
[23 Nov 2006 10:16]
Yahoo Serious
The comment my.ini problem is (also) in Bug #23885
[28 Nov 2006 10:56]
Maxim Dikun
I have same problem. It appears after I put on "One file per table" ckeckbox on "InnoDB Parameters" page in "Startup variables". After restarting service and Administrator appears message "Either the server service or the configuration file could not be found. Startup variables and service section are therefore disabled." When I restore my.ini from backup MySQL Administrator works again.
[8 Dec 2006 0: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".
[10 Apr 2007 8:20]
Basil Abbas
Okay, I have exactly the same problem on windows 2003, and now it has been fixed in a strange way. Open your registry editor at: 1. Start > Run 2. type 'regedit' and enter. Next, browse to the registry key named: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BloxAMP.MySQL\ImagePath This key contains the string: "C:\Program Files\BloxAMP\mysql\bin\mysqld-nt.exe" "--defaults-file=C:\Program Files\BloxAMP\mysql\my.ini" BloxAMP.MySQL Edit the string so that the double quote character (") before the --defaults-file is removed and add a double quote just before the C:\Program Files so that the resulting string will be: "C:\Program Files\BloxAMP\mysql\bin\mysqld-nt.exe" --defaults-file="C:\Program Files\BloxAMP\mysql\my.ini" BloxAMP.MySQL Now restart MySQL. Next restart the Administration tool. Everything should work now. Note that this problem only takes place under Windows 2003. One more thing, I'm using a LAMP installer named BloxAMP. Thats why it appears in the registry as "BloxAMP.MySQL". If you are using a typical MySQL installation, then most probably it will be named "MySQLxxx" instead. Good luck.