Bug #39915 MySQL Workbench OSS 5.025 Crash on Start
Submitted: 7 Oct 2008 18:25 Modified: 7 Oct 2008 22:01
Reporter: Todd Williams Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.025 OS:Windows (XP SP3)
Assigned to: CPU Architecture:Any
Tags: Workbench .Net

[7 Oct 2008 18:25] Todd Williams
Description:
A Crash Dialogue is immediately seen when MySql Workbench OSS is started. This also applies to the GRTSHell application as well. This error seems similar in nature to http://bugs.mysql.com/bug.php?id=37418, but I do see .Net errors. 

The crash dialogue states:
"MySQL Workbench has encountered a problem and needs to close.  We are sorry for the inconvenience."

The options on the crash window are "Debug" and "Close". Selecting Debug does not result in a debug window or any additional data. 

Workbench has previously worked on this computer, and it may have ceased to function when I installed Visual Studio Express - c# edition. I have since removed .NET 3.0 and 3.5 and the problem persists.  The .NET Runtime error is in the Application log and occurs on each start. One of my peers has an identical error.

------------------------------------------------------------------------
Event Type:	Error
Event Source:	.NET Runtime
Event Category:	None
Event ID:	1023
Date:		10/7/2008
Time:		1:15:01 PM
User:		N/A
Computer:	Hello
Description:
.NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (7A097706) (80131506)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------------------------------

How to repeat:
Every attempt to start the software results in the same error
[7 Oct 2008 22:01] Todd Williams
This error was a conflict between MySQL Workbench (presumably .NET), Symantec Enterprise Protection (SEP), and Dell-branded Embassy Protection from SecureWave