MySQL Bugs: #38976: Can't install a second agent on Windows, and no error message

Bug #38976	Can't install a second agent on Windows, and no error message
Submitted:	22 Aug 2008 21:55	Modified:	11 Nov 2008 14:40
Reporter:	Andy Bang	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Installing	Severity:	S2 (Serious)
Version:	2.0.0.7033	OS:	Windows
Assigned to:	BitRock Merlin	CPU Architecture:	Any

Description:
The agent installer won't let me install a second agent on Windows.  Is this allowed?  If not, it should at least show a message.

How to repeat:
1) Install an agent on Windows.
2) Start the installer again to install another agent.
3) On the "Installation Directory" screen, if you accept the default and click "Next" it will say "The selected directory already contains a product installation. Setup will delete all existing files. Do you wish to continue?".  This is fine.
4) Click "No".
5) You're back on the "Installation Directory" screen.  Specify another directory and click "Next".  Nothing happens.  It just stays on that screen and highlights the installation directory input field.

Suggested fix:
Allow installation into another directory.  If for some reason this isn't allowed (e.g. you don't want another Windows service with the same name), it should say so and refer to the docs for how to do it manually.

I've been installing multiple agents on Windows since 'ages', and it works - but I mostly use the unattended install. The new servivce is then renamed to ...-1, ...-2 or so, depending which is the first 'free' number.

Patch sent to Andy/Keith

Patch applied in versions => 2.0.0.7036.

BitRock debug file

Attachment: bitrock_debug_4184.xml (text/xml), 1.69 KiB.

Patch sent to Keith.

Patch applied in build versions => 2.0.0.7039.

adding this without having directly tested against this bug:

I see a problem with having only one RegDB key per version available at the moment for saving the unInstall information. So if you install 2 Win agents of the same version to different locations on the box you will have only one entry in the ARP menu (for the last agent installed), and from this you never can unInstall all other agents of the same version installed before from the ARP menu.

At the moment I think as a work around it should work for them to click on their 'uninstall.exe', but I didn't check this.

If the RegDB keys are changed like it is already done for the service names, it would be needed to add the path information to the stuff that is displayed in the ARP menu, otherwise one would start guessing which agent of version x.z.z.nnnn would be the one to be uninstalled.

The problem with having only one ARP menu entry per version possible affects also the update installer (see Bug#27447).

So if here a solution is implemented it needs to be tested, that having a direct install of a version and after this an update to this version from an older version result in 2 separate ARP menu entries, one for the direct and one for the updated.

Added an entry to the 2.0 changelog:

The agent installer did not allow a second agent to be installed on Windows.