MySQL Bugs: #62753: workbench abend

Bug #62753	workbench abend
Submitted:	15 Oct 2011 21:07	Modified:	13 Nov 2011 5:52
Reporter:	greg locke	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S1 (Critical)
Version:	5.2.35	OS:	Windows (win 7 sp1)
Assigned to:		CPU Architecture:	Any

Description:
was re-arranging columns in table def when IDE paused, not responding then aborted. Could not restart.
Get msg:
 Problem Event Name:	CLR20r3
  Problem Signature 01:	mysqlworkbench.exe
  Problem Signature 02:	5.2.35.7915
  Problem Signature 03:	4e7957cf
  Problem Signature 04:	mscorlib
  Problem Signature 05:	4.0.0.0
  Problem Signature 06:	4e181ae3
  Problem Signature 07:	3fd1
  Problem Signature 08:	13c
  Problem Signature 09:	System.UnauthorizedAccess
  OS Version:	6.1.7601.2.1.0.768.3
  Locale ID:	1033
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

How to repeat:
start workbench

This is probably a duplicate of bug #62703 or bug #62709. Please, check (including workaround to run as Administrator).

Thanks for looking.
Funny thing is, I was running as admin. 
I had checked the security setting on the file and directory. Which looked OK.

I un-installed and re-installed and was careful not to re-arange table columns in modeler. No problems at this time.

I wonder if the file was not properly closed due to the abend.

Workbench fails on start-up. db_utils.pyc access denied. Recurring bug. Both times, prior instance of mysql workbench hung and had to halt task using task manager. Afterwards it won't restart. No idea why it hung. Fix is to re-install workbench. not a pleasing thought. Can a clean-up process be created to fix this? Should I move to an older version of mySQL?? Can't afford distruptions.

Duplicate of bug #62703