MySQL Bugs: #626: %1 not a valid win32 application

Bug #626	%1 not a valid win32 application
Submitted:	9 Jun 2003 20:59	Modified:	2 Jul 2003 10:42
Reporter:	Steven Casey	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.x	OS:	Windows (Windows 2000 Server)
Assigned to:		CPU Architecture:	Any

Description:
I installed MYSQL fine, and was using it for some time, although I didn't see a service for MYSQL in the Services panel.  I rebooted, then noticed that there was a service created, but I cannot start it again.  It returns Error 193: %1 is not a valid Win32 application.  

I know this was a problem in a previous release, and I had to encapsulate a value in the registry with quotes, but I do not remember the key to modify.

How to repeat:
install the application, reboot, then try to start the service

To eliminate the error, need to navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mysql, double-click the ImagePathValue and encapsulate the value with double quotes.  The service will start fine, then shut down.  Then need to resolve the 1069 error.

For to be documented are you tried before to edit the registry,
first to issue the mysqld-nt --remove command and try to
re-install the service ?

I am asking you this because this behavior isn't too much
common in the service install and the above procedure is
more safe.

I added the double quotes which resolved the "%1" error, but then left me with the error 1067 which I could not resolve.  I then removed the service (>mysql-max --remove) and reinstalled.  The service came back fine.  Renaming the my.ini before reinstalling the service did not result in a new one being created, and I'm not entirely sure that the innodb paths are correct.  I've tried following the documentation as best as I could, and it now points directly to the innodb1 file.  I don't have any problems at the moment.  Thank you.

In order to eliminate all errors, I needed to remove the service, then reinstall.