Bug #26409 agent shows 'Error 1067: The process terminated unexpectedly' when stopped

• Submitted: 15 Feb 2007 15:31
• Modified: 13 Nov 2009 11:13
• Reporter: Carsten Segieth
• Status: Closed
• Category: MySQL Enterprise Monitor: Agent
• Severity: S3 (Non-critical)
• Version: 1.1.0.4773
• OS: Windows (Windows Vista)
• Assigned to: Carsten Segieth
• CPU Architecture: Any
• Tags: windows service

[15 Feb 2007 15:31] Carsten Segieth

Description:
Working as an administrator I started an agent as a Windows service (from the Service Manager) on Vista-x86 and after some minutes I wanted to stop it by clicking on the 'Stop' button in the Service Manager. Then a message box pops up:

Warning

Windows could not stop the MySQL Network Service Agent service on Local Computer.

Error 1067: 'Error 1067: The process terminated unexpectedly'.

After clicking on 'OK' the service manager showed that the service was stopped.

How to repeat:
see above

Suggested fix:
- suppress that message box as it looks that the service could be stopped without problems.
- and for the debug log it would be good to have a message in that the agent got a 'stop' signal and stopped from this.

[15 Feb 2007 16:12] Carsten Segieth

occurs both on Vista x86 and Vista 64

[15 Feb 2007 16:25] Carsten Segieth

from the eventlog on vista-64-a:

Faulting application MYSQL-~1.EXE, version 1.1.0.4773, time stamp 0x45d3b6a9, faulting module ntdll.dll, version 6.0.6000.16386, time stamp 0x4549bdf8, exception code 0xc0000005, fault offset 0x0002b9ad, process id 0x8d0, application start time 0x01c7511bd35d944b.

[23 Jan 2008 23:33] Java Tek

On Windows Vista I get this same error when I try to start the MySQL service.

'Error 1067: The process terminated unexpectedly'

What Have I done wrong

[24 Jan 2008 8:26] Carsten Segieth

Hello Java Tek,

you may have seen, that this problem report is about the MySQL Enterprise Monitoring Service Agent ('agent') and not about the MySQL server ('mysqld').

The problems looks to be similar / identical for agent and mysqld, but as they have separate code lines please open a separate bug for category "Server" (if not already one exists).

Thanks!

[29 Jan 2008 16:48] Peter Lavin

Added to the changelog for version 1.2.

[19 Jul 2008 0:13] Matthew Steg

I don't really understand on how to fix this problem by what you've stated... I'm not a computer wiz (this probably doesn't take much, but I don't get it). Can you describe the process to fix Error 1067 in a somewhat easier way to interpret? 

Thanks.

[13 Nov 2009 10:09] Enterprise Tools JIRA Robot

Carsten Segieth writes: 
"Could not reproduce" - testing this with recent 2.x versions I could not reproduce the problem anymore, where on the same system the still installed 1.x still shows it.

[13 Nov 2009 11:13] Tony Bedford

Setting to 'closed' as an entry was already added to the changelog by Peter Lavin.

[8 Mar 2010 21:52] Ruedi Gallati

I had the same problem on WIN 7.
It took me some hours to find a solution.

The final solution was:
a) delete the data folder compleatly "MySQL Server 5.1". 
On my machine "C:\ProgramData\MySQL\MySQL Server 5.1".
b) repair the installation by running your installer again.
c) reconfigure the instance.