MySQL Bugs: #37418: Won't launch: "MySQL Workbench has encountered a problem and needs to close"

Bug #37418	Won't launch: "MySQL Workbench has encountered a problem and needs to close"
Submitted:	16 Jun 2008 4:07	Modified:	25 Feb 6:16
Reporter:	Ken Zo
Status:	Can't repeat
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.0.22, 5.0.24, 5.0.25, 5.0.26, 5.0.27, 5.0.30	OS:	Microsoft Windows (XP SP2 (5.1.2600))
Assigned to:		Target Version:
Tags:	radeon, splash screen, launch, crash, startup

Description:
I am unable to launch Workbench.  When I execute MySQLWorkbench.exe, I receive a window
that says "MySQL Workbench has encountered a problem and needs to close.  We are sorry
for the inconvenience."  When I dismiss this dialog, the process terminates with no
further output.  The splash screen never displays.

I am running with full administrative privileges.  I have .NET Framework 2.0.50727.  I
don't have OpenGL support.  No errors appear in the Windows Event logs.  I find no
evidence of any files written by Workbench.

The same problem happened with 5.0.21 on this machine.  I tried on the same machine using
a different installation of Windows XP SP2 via VMWare, and Workbench was able to launch in
VMWare.

Studying usage logs generated by Sysinternals Process Monitor, about the last things that
appear to be accessed prior to Microsoft's "PCHealth\ErrorReporting" things include: .NET
Framework mscorwks.dll/mscorrc.dll, other .NET Framework stuff, GDIPlus stuff, and:
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700

If there is any debugging information I can access that Workbench generates, let me know.
 I can also attach portions of the Process Monitor output, if it's useful.  The error
message is pretty uninformative, so it's hard for me to guess where to start looking.

How to repeat:
Launch program on my installation of Windows XP!  :)

Thank you for the report.

You said the splash screen never appears, so Workbench can not use its diagnostic GRT
shell. We only can find what is wrong using operating system tools.

Please try to reinstall .NET and if problem still exists start Workbench from cmd.exe and
provide us output if any.

Reinstalling .NET (already tried previously) did not change anything.

If I run from command line, next command prompt immediately appears.  Meanwhile,
Workbench churns away attempting to start up.  Finally, the error window pops up.  I.e.
Workbench from the command prompt immediately returns control, so there is no opportunity
for it to output anything, although the Workbench process is clearly running and doing
things for a few seconds before crashing.

Is there any way to make Workbench output diagnostic information of any kind prior to the
GUI being started?

Thank you for the feedback.

> Is there any way to make Workbench output diagnostic information of any kind prior to
the GUI being started?

Not, there is not.

Is only way to do something here is collect as much as possible information about your
operating system and machine. Like if it is 64-bit etc.

It is not 64-bit.  Can you tell me what other specific information to provide?

Thank you for the feedback.

As we have no clue what really happened we only can guess this is problem of your OS.
Please start with RAM checking. See http://oca.microsoft.com/en/windiag.asp for the
program and how-to.

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".

I just noticed that 5.0.24 fixes bug #38117, "Crash at startup screen on Radeon 7500
display adapter".  My computer has an ATI Mobility Radeon 9000 display adapter. 
Workbench still won't start on this machine.  Could it be a bug related to my Radeon
adapter?

I have the newest version of the display adapter driver available from my computer
manufacturer (from 9/19/07).

Hi,

I've the same problem. Just today installed workbench 5.0.24 OSS and it won't even show
the splash screen. I get the same error described here.
I tried to install on another PC and there it does seem to work.

This machine is a 64 bit CPU.

Ciao
Manmanman

All reporters:

Please, try to repeat with a newer version, 5.0.25, and inform about the results.

Alas, the problem remains with 5.0.25.  It crashes in the exact same way.

I have just submitted Bug #39915 which may or may not be the same error. I am observing
that error on two workstations.

Please, try to repeat with a newer version, 5.0.26, and inform about the results.

The problem is unchanged in 5.0.26 OSS.

This isn't repeatable in our XP boxes, could you please try 5.0.27?. Thanks in advance.

The problem persists in 5.0.27 OSS.

Are you verified if that crash in starup isn't a DEP issue like others reports have
reported?. Thanks in advance.

Thanks for the suggestion.  I disabled DEP entirely on my computer, and then tried again. 
The problem remains unchanged, so it is not a DEP issue.

This really seems to be related to your hardware or Windows installation. We really can't
repeat it.

We are not able to do something here as long as we can't repeat it. We could bother you
more longer with "please try next version". But I think it makes no sense.

I will set this bug report to "can't repeat" now. Please feel free to open it again, when
you figured out more informations.

I got this bug on my Windows XP SP3 under VirtualBox with MySQL Workbench OSS 5.0.29
At first time after installation the tool works fine, but some time later I've started
getting this bug. Maybe the problem is in some related package which was updated on host
gentoo machine... Now it doesn't work and I don't know what to do.

For what it's worth, the problem remains with my OS installation and Workbench OSS 5.0.30.
 It's still the only .Net app that doesn't work on my machine. I would be happy to provide
more information if there were anything in particular you had in mind.

The same error is in version 5.0.30 Why no one doesn't answer on our posts? This problem
doesn't allow using your product at all. Turn on printing some debug information at log
file if you need more information. Do something with that please, don't leave it as is.

I think this bug should be reopened.

I have the same problem on my computer - workbench 5.0.29 and 5.0.30 will not start.  I
have a Sony Vaio laptop running winxp sp3.  I have a nvidia graphics card.  I do get the
splash screen but have no idea what the GRT shell diagnostic is (never used it).  I think
this bug should be reopened.

I have the same problem with 5.0.24 and 5.0.30.

It is running in VirtualBox under Fedora 10/x64.

It worked for about a day, then quit working completely.

All other MySQL products work fine in the same XP VM (Administrator, Query Browser etc)

Guys, try to use version 5.1.12, it works for me.