Bug #25380 MySQL Service is not starting in WIndows 2000 Pro SP4
Submitted: 3 Jan 2007 8:05 Modified: 4 Feb 2007 8:10
Reporter: Mahayogya Tech Support Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.0.10 gamma OS:Windows (Windows 2000 Pro SP4)
Assigned to: CPU Architecture:Any

[3 Jan 2007 8:05] Mahayogya Tech Support
Description:
Previously i have installed and configured MySQL server in Windows 98/2000/XP/2k3 successfull without any issues.

recently i have installed MySQL Server 4.0.10 gamma edition in windows 2000 professional with sp4 machine, logged in as an administrator user.

The service is not starting, when manually trying to start using WinMySQlAdmin, no messages are being shown, it is starting (traffic signal changes to GREEN) and after few seconds it is automatically turning to RED.

I have disabled all the antivirus applications also. but still the server is not starting.

in SCM, The startup method is kept as Automatic only

How to repeat:
Extactly don't know

Suggested fix:
Extactly don't know
[3 Jan 2007 9:53] Valeriy Kravchuk
Thank you for a problem report. Please, send your entire MySQL error log (usually hostname.err file in your data directory) and your my.ini file. Note also that 4.0.10 is ages old version. So, please, try to use newer one, 4.0.27.
[4 Jan 2007 7:06] Mahayogya Tech Support
Ya Sure, i will try that.

Any idea on what could be the problem like?

We have successfully implemented in numerous Win 98/2000 Pro/XP Pro/2003 Server OSs with any problem.
[4 Jan 2007 8:10] Valeriy Kravchuk
I need more information to understand the reason. Please, send your entire MySQL error log (usually hostname.err file in your data directory) and your my.ini file. 

Why do you think this problem is the result of bug in MySQL, by the way?
[5 Feb 2007 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".