Bug #30166 Bad name for agent process in Task Manager
Submitted: 1 Aug 2007 0:46 Modified: 21 Sep 2009 13:09
Reporter: Andy Bang Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Installing Severity:S3 (Non-critical)
Version:1.3.0.8299 OS:Microsoft Windows
Assigned to: BitRock Merlin CPU Architecture:Any

[1 Aug 2007 0:46] Andy Bang
Description:
After upgrading an agent from 1.1.1 to 1.2.0, the process name for the agent in the Task Manager is MYSQL-~1.EXE (it may have been that after the 1.1.1 install).  Note that the "Path to executable" the Services->General tab ends with MYSQL-~1.EXE.

How to repeat:
Upgrade an agent from 1.1.1 to 1.2.0.

Suggested fix:
Put the path in quotes and end it with mysql-service-agent.exe.
[31 Aug 2007 20:17] BitRock Merlin
We have made some changes to InstallBuilder code (quoting the services names and preserving the long name format) but we didn't achieve the results we would have like to.

The problem seems to only happen _the first time_ you start the Agent. When the Agent is started, the name in the Task Manager window is MYSQL-~1.EXE. This happens when you start the Agent in the final page of the installer or if you start it directly from the shortcut.

When you just restart the service, the Agent's name in the Task Manager window changes to the right value, mysql-service-agent.exe.

We have noticed in the Windows registry, into HKEY_LOCAL_MACHINE/System, that the only difference for MySQL Network Agent in the registry before and after starting the services for the first time is the creation of a directory registry called "enum" that contain this registers:

- REG_SZ: Root\LEGACY_MYSQLENTERPRISESERVICEAGENT\0000

In addition, LEGACY_MYSQLENTERPRISESERVICEAGENT directory registry contains a Service registry:

- REG_SZ: MySQLEnterpriseServiceAgent, and others.

We have searched more information about this problem but we haven't obtained any good results.
[5 Sep 2007 23:18] BitRock Merlin
Patch sent to Andy.
[6 Sep 2007 1:19] Keith Russell
Patch installed in version => 1.2.0.7481
[6 Sep 2007 9:28] Carsten Segieth
tested OK in 1.2.0.7481
[6 Sep 2007 16:02] Peter Lavin
This bug occurs and is fixed in version 1.2 and doesn't change the UI so I'm assuming that it doesn't need to be documented.
[6 Sep 2007 21:14] Andy Bang
It still shows up as MYSQL-~1.EXE.  Note that the Path to executable in the service properties still has this.  Also, the path is not quoted and uses forward slashes instead of backslashes.  See the attached screen shot.
[6 Sep 2007 21:14] Andy Bang
Merlin Agent Service Properties Screen Shot

Attachment: MerlinAgentServiceProperties.png (image/png, text), 16.77 KiB.

[7 Sep 2007 22:48] Andy Bang
Fix received from BitRock on Friday, 2007-09-07 at 9:28 AM PDT.
[8 Nov 2007 20:44] Keith Russell
Patch installed in versions => 1.2.0.7638.
[15 Nov 2007 22:30] Carsten Segieth
tested OK with 1.2.0.7879
[16 Nov 2007 13:56] Peter Lavin
Added to the changelog for version 1.2.
[28 Nov 2007 13:31] Carsten Segieth
re-opened as the problem occurs again with 1.3.0.8220 and 1.3.0.8299 (the old report was for version 1.2.0.7481).

I verified, that the problem occurs regardless whether the process is started directly from a DOS prompt or from cygwin or as a service - the file name in the task manager is 'MYSQL-~1.EXE'.
[28 Jan 2008 0:00] Bugs System
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".
[2 May 2008 5:04] Gary Whizin
Re-opening because in going through bugs, I see this one closed from lack of a response. Is this still a problem in 1.3.x?
[25 Aug 2009 16:45] Andy Bang
After installing the 2.1.0.1093 agent, I see "mysql-monitor-agent.exe" in the Task Manager, which is correct.  So let's retest.
[27 Aug 2009 21:25] Enterprise Tools JIRA Robot
Carsten Segieth writes: 
verified OK also in 2.0.6.7159
[21 Sep 2009 13:09] Tony Bedford
A new entry was created for the 2.0.6 and 2.1.0 changelogs:

When the Agent was started as a service on Windows for the first time, the name in the Task Manager window was MYSQL-~1.EXE. This occurred whether the Agent was started from within the installer or from the Start Menu.

If the service was restarted, the Agent's name changed to the correct value, mysql-service-agent.exe.