MySQL Bugs: #34264: MySQL Server Community 6.0, Administrator 1.2.12, Error Storing User Information

Bug #34264	MySQL Server Community 6.0, Administrator 1.2.12, Error Storing User Information
Submitted:	3 Feb 2008 18:19	Modified:	19 Sep 2008 7:27
Reporter:	Tim Mahoney	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	Server Community 6.0, Admin 1.2.12.0	OS:	Windows (XP SP2)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
I have tried to search for the answer for this problem and I have found that this maybe related to bug #9173 - http://bugs.mysql.com/bug.php?id=9173 . 

In bug 9173 it suggests that there is a new release that has the fix to this problem. However, it seems to have been left unresolved on later versions.

How to repeat:
This began when I recently installed the latest version of php and mysql on a new server and began development with a new project.  The first thing I did was get the database setup and then found the problem when creating user. It allowed me to create a number of users but unable to amend the settings and continually being prompted by 'Error while storing the user information. The user might have been deleted. Please refresh the user list.' everytime I created the user. after the error disappears the new user is now there but unable to amend their settings. I was logged in as root.

I left the user setup and began binding php and mysql together (modules). After setting the libmysql.dll and php_mysql.dll files to the right locations and resetting apache 2.2, I checked the apache log to make sure the two dll's had been loaded successfully (they were).

When I try to connect to a database based on:

  $MySQLUser="aUser";
  $MySQLPass="aPass";
  $MySQLDB="aDB";

  $link = mysql_connect('localhost', $MySQLUser, $MySQLPass);
  if (!$link) {
    die('Not connected : ' . mysql_error());
  }

  $db_selected = mysql_select_db($MySQLDB, $link);
  if (!$db_selected) {
    die ('Can\'t use db : ' . mysql_error());
   }

Apache then crashed when accessing the page and the log has the following error: '[notice] Parent: child process exited with status 3221225477 -- Restarting.'

After doing some research on the error message I found no definate answer as to what happended and how to resolve this. This led me back to the user access in MySQL Administrator and I'm thinking they are both linked somehow? Could someone shed some light on this please. 

Will there be a fix soon for this release? 
Is it something I'm doing wrong?

Thank you for a problem report. What exact version, 6.0.x, do you use? Had you installed it anew or over some older MySQL server version?

It was version 6.0.3-alpha of MySQL.

Last night I resorted back to a more stable version and restored the database that was inially created in 6.0. I was able to use the restricted features found in 6.0 with regards the user form in mysql administrator.

However the apache error was still there. For the benefit of anyone else reading this.... To get this working I uninstalled php 5.2.5 for windows (package version) and went with modules version (just a zip file) as it had all the extensions etc with it. Once I configured the apache .conf and php.ini as they should be I was able to connect to mysql and process queries.

I still think the mysql user issue is a problem in 6.0.3-alpha. Let me know if you require any more information and I will keep my eye out for the next release.

It was version 6.0.3-alpha of MySQL.

Last night I resorted back to a more stable version and restored the database that was inially created in 6.0. I was able to use the restricted features found in 6.0 with regards the user form in mysql administrator.

However the apache error was still there. For the benefit of anyone else reading this.... To get this working I uninstalled php 5.2.5 for windows (package version) and went with modules version (just a zip file) as it had all the extensions etc with it. Once I configured the apache .conf and php.ini as they should be I was able to connect to mysql and process queries.

I still think the mysql user issue is a problem in 6.0.3-alpha. Let me know if you require any more information and I will keep my eye out for the next release.

It was version 6.0.3-alpha of MySQL.

Last night I resorted back to a more stable version and restored the database that was inially created in 6.0. I was able to use the restricted features found in 6.0 with regards the user form in mysql administrator.

However the apache error was still there. For the benefit of anyone else reading this.... To get this working I uninstalled php 5.2.5 for windows (package version) and went with modules version (just a zip file) as it had all the extensions etc with it. Once I configured the apache .conf and php.ini as they should be I was able to connect to mysql and process queries.

I still think the mysql user issue is a problem in 6.0.3-alpha. Let me know if you require any more information and I will keep my eye out for the next release.

Thank you for the report.

MySQL Administrator part verified with light difference: I have not click on user name after its successfull creation, so no error message displayed.

Apache part seems to be duplicate of bug #24212

The legacy tools are designed to work with MySQL servers starting from 4.1 up to 5.0 (hence the name of the bundle). Using it with 6.0 or higher might (partly) work, but is not supported by MySQL.