Bug #30511 | Service names under Windows | ||
---|---|---|---|
Submitted: | 20 Aug 2007 14:53 | Modified: | 6 Sep 2007 17:27 |
Reporter: | Peter Lavin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Installing | Severity: | S3 (Non-critical) |
Version: | 1.2.0.7174 - 7355 | OS: | Windows |
Assigned to: | BitRock Merlin | CPU Architecture: | Any |
Tags: | renaming |
[20 Aug 2007 14:53]
Peter Lavin
[28 Aug 2007 13:22]
BitRock Merlin
Patch sent to Andy.
[29 Aug 2007 17:15]
Keith Russell
Patch installed in versions => 1.2.0.7355
[30 Aug 2007 0:50]
Bill Weber
The Tomcat service name is still MySQLNetworkTomcat (although the display name is now correct - MySQL Enterprise Tomcat). The MySQL service name and display name are both still MySQLNetworkMySQL.
[30 Aug 2007 11:44]
BitRock Merlin
We have made another round of testings, and the services are correctly changed to the new names, both "name" and "display name". The XML project files for the server update should have the following BitRock build tag: 200708280541. Could you please confirm that on your side?
[30 Aug 2007 13:58]
BitRock Merlin
The bitrock build tag can only be obtained from the XML project file. You would need to review which project file was used to build the specific installer you are testing. Anyway, the only foolproof solution for the bitrock build tag is to obtain from you the mentioned installer, so we can extract from it the XML project file and check the specific value.
[5 Sep 2007 23:18]
BitRock Merlin
Patch sent to Andy.
[6 Sep 2007 1:20]
Keith Russell
Patch installed in version => 1.2.0.7481
[6 Sep 2007 15:39]
Andrew Cwik
fixed in 1.2.0.7481.
[6 Sep 2007 17:27]
Peter Lavin
Names of services changed in the documentation.