Bug #73143 workbench log file path missing
Submitted: 28 Jun 2014 15:08 Modified: 3 Jul 2014 9:05
Reporter: dick schrauwen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.08.... OS:Windows (7 (6.1.7601.2.1.0.768.11))
Assigned to: CPU Architecture:Any
Tags: log file path missing

[28 Jun 2014 15:08] dick schrauwen
Description:
Problem signature:
  Problem Event Name:	CLR20r3
  Problem Signature 01:	mysqlworkbench.exe
  Problem Signature 02:	6.0.8.11354
  Problem Signature 03:	527a7307
  Problem Signature 04:	System.Runtime.Remoting
  Problem Signature 05:	4.0.30319.34108
  Problem Signature 06:	530d8c0a
  Problem Signature 07:	e4
  Problem Signature 08:	eb
  Problem Signature 09:	System.Runtime.Remoting.Remoting
  OS Version:	6.1.7601.2.1.0.768.11
  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:
??
[28 Jun 2014 15:31] Peter Laursen
MS link:
http://msdn.microsoft.com/en-us/library/system.runtime.remoting(v=vs.110).aspx

But I am not able to understand how this can apply to Workbench (or any MySQL client). I am also not able to understand how the the title/synopsis of this report ("workbench log file path missing") comes into the picture and how it is related to the log entry from Windows log system you paste here.  It seems COMPLETELY unrelated to me!

So I think you should elaborate.

-- Peter
-- not a MySQL/Oracle person.
[29 Jun 2014 20:33] MySQL Verification Team
Please try version 6.1.7. Thanks.
[3 Jul 2014 9:05] dick schrauwen
Cannot reproduce error: so please close