Bug #6670 MySQL Server 4.1 Service Fails to Start on WinXP
Submitted: 16 Nov 2004 20:53 Modified: 16 Nov 2004 21:45
Reporter: Robert Vesse Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:4.1.7 OS:Windows (WinXP Pro SP2)
Assigned to: CPU Architecture:Any

[16 Nov 2004 20:53] Robert Vesse
Description:
I upgraded from 4.0.x version to 4.1.7 but now I cannot get MySQL to install correctly or to start a valid Windows service.  I removed completely my old install except the service which is what seems to be causing me problems.  I installed a new service under a different name but then I couldn't get MySQL Administrator to recognise this service and even when I used the mysqld command from the command line to unistall and reinstall I still couldn't get it to recognise a MySQL Service even though Windows recognised it running.

This seems to be a problem with interaction between MySQL Server and MySQL Administrator but after another uninstall and reinstall of the Server I now cannot get a MySQL Service to start at all.  What could be the cause of the problem and how do I get MySQL Administrator to interact with MySQL Server 4.1.x correctly with regards to Service Management and Configuration?

How to repeat:
Upgrade from a 4.0.x installation to a 4.1.x installation by completly removing MySQL 4.0.x but not removing MySQL Administrator

Configure a MySQL Service using the Instance Config Wizard, Service will either fail to start at this stage or will start but when you run MySQL Administrator it will not correctly recognise the running service
[16 Nov 2004 21:44] MySQL Verification Team
The installer wizard when finds the default service name should be able
to remove it and install a new service, at least that was my experience,
on another hand Administrator isn't aware of you new service name and
will try to use the default service name. Below the work-around:

Open a prompt DOS srceen go to the \mysql\bin directory and issue the
below commands:

mysqld-nt --remove older_service_name
mysqld-nt --remove new_service_name

mysqld-nt[mysqld-max-nt] --install 

The above command will install the default service name
called MySQL and Administrator will be able for to use.

Thank you for the bug report.
[16 Nov 2004 21:45] MySQL Verification Team
The installer wizard when finds the default service name should be able
to remove it and install a new service, at least that was my experience,
on another hand Administrator isn't aware of you new service name and
will try to use the default service name. Below the work-around:

Open a prompt DOS srceen go to the \mysql\bin directory and issue the
below commands:

mysqld-nt --remove older_service_name
mysqld-nt --remove new_service_name

mysqld-nt[mysqld-max-nt] --install 

The above command will install the default service name
called MySQL and Administrator will be able for to use.

Thank you for the bug report.