MySQL Bugs: #33476: cannot create windows service for mysql

Bug #33476	cannot create windows service for mysql
Submitted:	22 Dec 2007 0:16	Modified:	22 Jan 2008 19:37
Reporter:	Dan Gibas	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Instance Manager	Severity:	S2 (Serious)
Version:	5.0	OS:	Windows (server 2003)
Assigned to:		CPU Architecture:	Any

Description:
The bug in the MySQL5 installer is not making any sense.  I uninstalled MySQL5 using the uninstaller (which should have stopped the service, am i right?) but then whenever i reinstall I get stuck with...

"cannot create windows service for mysql"

I have tried just about every fix and hack that is floating around the net and none of them work.

I am convinced that the installer / instance manager is stopping with this error when it has nothing to do with the service instance at all.  Something is wrong with the installer here or how it interacts with Windows.

How to repeat:
Install mysql 5 on win server 2003

Uninstall it

Install it again - bang - error!

(other possible factors are that i kept my databases intact in the data dir and they are a few hundred mb in size, i also kept the paths the same for the instal because i dont want to lose my mysql databases)

Suggested fix:
The answer is in the code where the exception is thrown up at the point of 

"cannot create windows service for mysql"

Something is going wrong leading to this and im sure its not related to the service at all.

To prove it, I have tried selecting a different service name - no luck.  I have also made sure using tools and command line that there are no other mysql services running - and i have checked in the registry.

Thank you for the bug report. When trying to install the Windows user has
Administrator Privileges? otherwise please read the below instructions
to try the service install manually:

http://dev.mysql.com/doc/refman/5.0/en/windows-start-service.html

Thanks in advance.

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".