Bug #648 | MySQL Service issue on Windows | ||
---|---|---|---|
Submitted: | 12 Jun 2003 22:43 | Modified: | 16 Jun 2003 5:47 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S1 (Critical) |
Version: | 4.0.12 | OS: | Windows (Windows 2000 Advanced Server) |
Assigned to: | CPU Architecture: | Any |
[12 Jun 2003 22:43]
[ name withheld ]
[13 Jun 2003 3:43]
MySQL Verification Team
Some notes about how you have described the bug: The name of the service (same of the my.ini section) can't be made up with several words separate with a blank space e.g: wrong: my service right: myservice The reason is that the server at the star takes the name of the service using only the first word and for this reason the service isn't start adequately.
[15 Jun 2003 21:49]
[ name withheld ]
Hi, Thanks a lot for your kind and quick response. I still have the issue even when I use a singleword for the service name. (i.e. "testserv"). Some more info on how I have created the service and my findings. I am using CreateService Win32 API to create the service and the service name is "Test Service" (includes spaces in between). After the successful installation of this service, I tried running it and it gave an error. And I installed the default service using "mysqld-max-nt --install". It installed the service by name "MySQL". After installing this the default service, the "Test Service" started working i.e. I could start the "Test Service" successfully. Any idea on why this behaviour?. Thanks a lot for your kind and quick response again. Thanigai
[16 Jun 2003 5:47]
MySQL Verification Team
If you are using you own code for to install the service this isn't a MySQL bug. Please study the source code how MySQL install the optional service and how it start internally this type the service. The optional service image path is different than the default one.