MySQL Bugs: #18357: Cannot start server

Bug #18357	Cannot start server
Submitted:	20 Mar 2006 16:15	Modified:	24 Mar 2006 22:37
Reporter:	Lorin Kaneff	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.0.18	OS:	Windows (windows xp)
Assigned to:		CPU Architecture:	Any

Description:
After finishing the Installation of MySQL I received 'Cannot Create Windows Service for MySQL.Error 2.0'

How to repeat:
Go through the Instance Configuration Wizard and after you click execute you will see a red x by start service.

The error message says 'Cannot create windows service for MySQL.Error: 0.

Thank you for the bug report. You had explained the steps you did
during the install process, or if you did an upgrade install over an
older one. Anyway please do the below:

- open a dos command screen and go to your \bin install directory.
- Then issue the below command:

 mysqld-nt --defaults-file="your_my.ini_path" --standalone --console

and verify which error message you get.

Thanks in advance.

Ran this in the Windows Console:
 C:\Program Files\MySQL\MySQL Server 5.0\bin>mysqld-nt --defaults-file="C:\Program Files\MySQL\MySQL Server 5.0\my.ini" --standalone --console

Here is the error I received.
060322 16:18:04  InnoDB: Operating system error number 32 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/mysql/en/Operating_System_error_codes.html
InnoDB: File name .\ibdata1
InnoDB: File operation call: 'open'.
InnoDB: Cannot continue operation.

Thank you for the feedback. The error means:

32 (ERROR_SHARING_VIOLATION) 

The process cannot access the file because it is being used by another process. 

So please verify if you don't have another MySQL server running suing
the task manager.

What is the name of the process in the task manager that I'm looking for?  I see the Instance Configuration File running but I don't see a mysql process running.

Thank you for the feedback. The process which executable begings with
mysqld-. Also verify if you don't have several my.ini files in \windows;
c:\ directory, compare the InnoDB sizes in the my.ini file with the one
you find in the data directory or their paths referenced in my.ini.

This happenned on the first installation of mysql.  I did not have anything related to mysql on the computer.  Now I'm able to complete the instance configuration without any errors.  Why did the configuration not work the first time but worked the second time through.  I would call this a bug.

This happenned on the first installation of mysql.  I did not have anything related to mysql on the computer.  Now I'm able to complete the instance configuration without any errors.  Why did the configuration not work the first time but worked the second time through.  I would call this a bug.

Thank you for the bug report. I would agree it is a bug if with
repeatable test case (exact steps in the install procedure) is
provided. For example the error message showed is typical on
Windows when 2 applications trying to access simultaneously
the same file, sharing violation, that can be happen with an
anti-virus application while InnoDB tries to open/create the
log and table-space files. If you are able to provide the steps
for to repeat that behavior, could you please open this bug
again.
Thanks in advance.