MySQL Bugs: #62161: SSH Tunnel Fail on 5.2.34

Bug #62161	SSH Tunnel Fail on 5.2.34
Submitted:	13 Aug 2011 2:18	Modified:	6 Jan 2012 15:57
Reporter:	James Bromberger	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.34, 5.2.35	OS:	Windows (7 Home Premium, 64 bit)
Assigned to:		CPU Architecture:	Any
Tags:	regression

Description:
Since upgrading to 5.2.34, SSH tunnels that previously worked now fail with a dialog box of:

Failed to Connect to MySQL at $dbhost through SSH tunnel at $sshhost with user $dbuser
Error connecting SSH tunnel: [Error 5] Access is denied: 'C:\\users\\james\\appdata\\local\\temp\\tmpxgn190.pag'

I have check and re-asserted ownership of the folder structure in appdata\local, and ensureed it is not read only. A new PAG file is created each time, but the error persists.

I'll see if I can attach a screenshot...

How to repeat:
Configure SSH tunnel, press "Test Connection"

Error dialog as a result of "Test Connection"

Attachment: Workbench5-2-34-SSH-Tunnel-Fail-20110813-01.png (image/png, text), 21.66 KiB.

Which WorkBench version was used to create the SSH connection?. The remote server can be connected using the command line client?. Thanks.

Version 5.2.34 CE Revision 7780. Windows 7 64 bit. SSH to the host in question is working fine; MySQl fromt he remote (linux) server to the MySQL instance is fine. My work around now is to manually set up an SSH tunnel (using putty) and then point MySQL as a "Standard TCP/IP connection" to localhost:330x. This worked fine in previus releases (5.2.33 and below).

Does it still work if you downgrade to 5.2.33? Just to make sure that the problem is not caused by something other than the upgrade to 5.2.34?

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'm having this exact problem, but my OS is Windows 7 Pro 64 bit.

I was running 5.2.34, and tried upgrading to 5.2.35 to fix it. I'm still getting the same error. The only thing I think that could possibly be related is that I did upgrade my installation of PuTTY before this started happening, but that's just a shot in the dark.

I cannot downgrade to 5.2.33 as I don't have the installer any more. Going to the wb.mysql.com web site shows the current 5.2.35 version; clicking on "older GA versions" lets you download 5.1.19! 

I have the same issue persisting in 5.2.35.

Hello.
The new WB 5.2.36 is out.
Please give a try with it and let us know your results.
Thanks.

Appears to be working fine in 5.2.37.

Not repeatable with 5.2.37.