Bug #61252 Windows 2008 R2 - service not started
Submitted: 21 May 2011 20:17 Modified: 13 Jul 2011 22:47
Reporter: Krzysztof Rudlicki Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Windows Severity:S1 (Critical)
Version:5.5.11.7 OS:Windows (2008 R2 Server)
Assigned to: CPU Architecture:Any
Tags: bug, service, windows

[21 May 2011 20:17] Krzysztof Rudlicki
Description:
Hi,

Durring MySql instalation in developer server option in windows 2008 r2  MYSQL 5.5 doesn't working. 

When I want to start a mysql i see error code 2003. "Mysql couldn't connect to a localhost". 

I checked running services and i don't find a MYSQL5.5 service. Not add to windows services.

Check it out !

How to repeat:
Improve the module responsible for adding services to the system.

Suggested fix:
I don't know :-)
[23 May 2011 14:30] MySQL Verification Team
Thank you for the bug report. You got that error message during the install process? if yes which exactly step. Thanks.
[23 May 2011 15:13] Krzysztof Rudlicki
Hello,

I hadn't any error during the installation process. 
Installation has been completed and successfully. Unfortunately after the installation I could not log in to database.
In my task manager I saw that the process not exist and I could not even run it manually :( 

Best regards,

--------------------------------------------------------------------------------
Krzysztof Rudlicki
Quality Assurance Engineer
Future Processing Sp. z o.o.
Mob: +48 607 387 918
krudlicki@future-processing.com
http://www.future-processing.com
[22 Jun 2011 5:51] MySQL Verification Team
Please run the below command in the cmd prompt running as administrator:

cd\path\to\mysqld
mysqld.exe --defaults-file=/path/to/my.ini --console

Just replace the \path\to and /path/to with the actual paths.  Send us the output.
[13 Jul 2011 23: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".