Bug #61168 Running scripts does not work
Submitted: 13 May 2011 13:17 Modified: 17 May 2011 16:48
Reporter: Chris Harte Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench: SQL Editor Severity:S1 (Critical)
Version:5.2.33b OS:Windows (XP)
Assigned to: CPU Architecture:Any
Tags: script workbench

[13 May 2011 13:17] Chris Harte
Workbench throws an error every time I try to run a loaded script

How to repeat:
Open a script from the scripting menu, try to execute it.
[13 May 2011 13:52] Valeriy Kravchuk
Please, send the output of Help > System Info menu item.
[14 May 2011 11:43] Chris Harte
MySQL Workbench CE for Windows version 5.2.33

Configuration Directory: C:\Documents and Settings\Me.THESHED.000\Application Data\MySQL\Workbench

Data Directory: C:\utils\mysql\gui

Cairo Version: 1.8.8

Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.

OpenGL Driver Version: 2.1.8545 Release

OS: Microsoft Windows XP Professional Service Pack 3 (build 2600)

CPU: 2x Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz, 2.0 GiB RAM

Active video adapter: Radeon X1950 Pro

Installed video RAM: 512 MB

Current video mode: 1680 x 1050 x 4294967296 colors

Used bit depth: 32

Driver version:

Installed display drivers: ati2dvag.dll

Current user language: English (United Kingdom)
[14 May 2011 12:19] Valeriy Kravchuk
Please, try to install .msi binaries of 5.2.33b and check if they demonstrate the same problem.
[16 May 2011 13:02] Chris Harte
Downloaded and installed the 5.2.33b msi binaries. It still reports the same problem
[16 May 2011 14:20] Valeriy Kravchuk
When you'll get the error next time, please, right click somewhere in the error dialog box with no text and use Copy stack trace to clipboard context menu item. Send stack trace to this bug report.
[17 May 2011 12:04] Chris Harte
Exception = System.Runtime.InteropServices.SEHException
Message = External component has thrown an exception.
FullText = System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
   at MySQL.Forms.ButtonImpl.button_click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
[17 May 2011 13:07] Alfredo Kojima
What kind of scirpt are you executing? The Scripting shell window is not meant for SQL scripts, it's only for Python/Lua scripts. If you want to execute SQL, use the SQL Editor.

As for the crash, this is a duplicate of bug #60977
[17 May 2011 16:48] Chris Harte
I am trying to run an SQL script. My mistake.
What I was trying to do was open an SQL script from the menu. This was under file in the old "MySQL Query Browser" gui (which I was using last week). The script can be launched from the script menu.

The workbench did not have it under file, but did have an 'open script' under scripting. I assumed all scripts were treated equally.

Workbench instead came up with a "report bug" screen, which I duly did. 
So the bug should be retitled, "Does not recognise sql scripts in the script launcher".