MySQL Bugs: #72337: Windows installer does not setup workbench correctly (MEB, Utilites integration)

Bug #72337	Windows installer does not setup workbench correctly (MEB, Utilites integration)
Submitted:	14 Apr 2014 10:00	Modified:	9 Aug 2015 5:54
Reporter:	Mario Beck	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL for Windows: Installer	Severity:	S3 (Non-critical)
Version:		OS:	Windows (Windows 7, 64bit)
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	Enterprise Backup, Enterprise integration, meb, mysql utilities

Description:
When installing MySQL, MEB, Utilities and Workbench from E-Delivery (no version information available. Downloaded April 14th, 2014), Workbench is not setup correctly:

Although I installed all packages immediately, Workbench is not able to execute the MySQL Utilities Console. 
Also the MySQL Enterprise Backup Utility is not found. Users have to configure both manually.

How to repeat:
Install MySQL, Workbench, Utilities, MEB with Windows Installer.
Start Workbench, click on the local server and try to run Online Backup.
You get two errors:
Backup directory does not exist. That is acceptable.
and:
Path to MEB executable is wrong. The error message even says "wrong version".
If Workbench would be configured with the default path from installation, this would not happen.

If you click in the menu on "Tools->Start Shell for Utilities" you get the error "The command line MySQL Utilities could not be located."
There is not even an option to point Workbench to the right location of the Utilities.

Suggested fix:
When installing and configuring Workbench from the Windows Installer setup the correct paths for MEB and Utilities so that all works smoothly.

Thank you for the bug report. The install directories are custom one?. Thanks.

No. The installation was all in default paths.

Hello Mario Beck,

Thank you for the bug report.
I tried with latest MySQL Installer, MEB, Workbench Utilities and command line MySQL Utilities are worked without any issues. 
Probably this is fixed, please feel free to reopen this bug report if you encounter this issue again.

Thanks,
Chiranjeevi.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".