Bug #4178 System Service Issue
Submitted: 17 Jun 2004 1:34 Modified: 20 Jul 2004 2:03
Reporter: [ name withheld ] Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:4.0.20a OS:Windows (Windows 2003)
Assigned to: CPU Architecture:Any

[17 Jun 2004 1:34] [ name withheld ]
Windows 2003 Server Standard Edition.

MYSQL will not start as a system service properly. It installs ok, but when you try to start it (from the command line or otherwise) it connects for about 3 seconds and dies again. A workaround for this is to run using the following:
mysqld-max-nt --standalone --skip-innodb

However, when you need to use InnoDB, this presents a problem!

How to repeat:
Install onto Windows 2k3. Try and start.

Suggested fix:
No idea!
[17 Jun 2004 4:01] MySQL Verification Team
Are you installed the MySQL stuff in the default location: c:\mysql ?
otherwise are you created and edited the my.ini file with the keys:
basedir and datadir ?
[17 Jun 2004 21:05] [ name withheld ]
It is in: c:\mysql and the data and base dirs are correct.
Is it a permissions thing? Do I need to add a user to mysql that mirrors the admin account? On the previous systems (XP Pro and 2000) I didn't have to and all worked perfectly.
[18 Jun 2004 6:28] MySQL Verification Team
The MySQL service needs to be installed for Administrator user or
one which have privileges for to install and start/stop services. Then
maybe this is your issue. The account used is the LocalSystem.
[18 Jun 2004 18:23] [ name withheld ]
That's been done! I only use the administrator account on that system until I can get everything up and running. Thanks for your time thusfar! It's very much appreciated - i'm just drawing a complete blank. I've alse tried giving all permissions to the mysql folder. the error number when i try to start a service in "Computer Management" is 1067 : Device stopped unexpectadly. This is meant to relate to my.ini. I've stripped it down to the necessaries and followed all of the advice (including re-locating the file) about the cnf file etc etc etc !!
[20 Jun 2004 2:03] MySQL Verification Team

Please issue the below command at prompt:

mysqld-nt --standalone --console

don't use --skip-innodb

and show us the output of the message error.

[14 Feb 2005 22:54] 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".