MySQL Bugs: #70151: MySQL Installer sets incorrect Windows Service Name for Workbench Local instance

Bug #70151	MySQL Installer sets incorrect Windows Service Name for Workbench Local instance
Submitted:	26 Aug 2013 13:41	Modified:	16 Dec 2015 22:02
Reporter:	Sam Abboushi	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	6.0.6.11184 Community	OS:	Windows (W7 64)
Assigned to:		CPU Architecture:	Any

Description:
Installer defaults to creating a Windows Service with Name: MySQL56

However, it then creates a Workbench Local instance System Profile with Windows Service Name: MySQL

btw - I believe this was the case in prior version

How to repeat:
Run the MySQL Installer and select Developer Default
(I also specified a custom Data Path)

Follow the prompts/defaults to load all the products

Windows Service Name: MySQL56 (accept defaults)
Check: Start MySQL Server at System Startup
Run Windows Service as: Standard System Account

After installation, compare the Windows Service Name (MySQL56) (in Windows Services) vs. the Windows Service Name specified in the Workbench Local instance System Profile (MySQL)

Suggested fix:
Have the installer use the same Windows Service Name for the instance System Profile that is specified during the installation.

I was unable to access my database until I figured this out

Service instance

Attachment: wb_service.png (image/png, text), 35.27 KiB.

Thank you for the bug report.

My mistake re: severity; another problem was preventing me from accessing data.

This problem just seems to affect the ability to start and stop the MySql service from within Workbench

Posted by developer:
 
That's an installer problem and especially problematic if you install more than one server. WB doesn't care how the service is named, but might touch the wrong one if the user uses the wrong name in the believe it is the correct one.

Posted by developer:
 
The installer never configure or change anything related to WB, only launches the msi as install, upgrade or remove mode the package(s) selected to install and how the server is configured we only create the service with the name that the user specify in the configuration wizard, on older versions was detected sometimes the services was "renamed" but 1.4 never do that because the rename was only renaming the friendly name of the service but the name was unchanged, 1.4 always delete the "old" service in order to create once again the service to avoid any issue.

other than that the installer doesn't have anything else related to this issue, using the installer can be installed side by side 5.5, 5.6 and 5.7 at the same time and doesn't allow to be configured using the same service name all the services.

will be tested by QA and if still having issues perhaps needs to be addressed by WB team