MySQL Bugs: #55133: Error on first opening a newly created connection

Bug #55133	Error on first opening a newly created connection
Submitted:	9 Jul 2010 18:22	Modified:	22 Jul 2010 5:58
Reporter:	John McClenahan	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.25	OS:	Windows (Windows 7 64bit)
Assigned to:		CPU Architecture:	Any

Description:
Just installed freshly downloaded Workbench 5.2 direct from MySQL website.

Set up first connection over local network to existing server on another (Linux CleaorOS 5.1/CentOS 5.3) machine.

When I click to Open connection, error pops up immediately, inviting me to report a bug, saying something like Invalid Node 0:0:0 (can't remember exact wording. I closed the message box in order to fill in the Bug report).

When I close the error message box, I can see the list of tables in the default schema in the left hand pane, but not in the tab in the lower right hand pane, which shows 0 Tables.

Cannont open any other schema either in left hand pane or lower right pane - when I click the + sign beside the second schema in left hand pane, a set of folder icons appears, but then sticks saying "fetching..." and nothing further happens.

Close Workbench, and reopen - problem is NOT repeated, and seems to work ok on limited testing.

How to repeat:
Presumably, start all over again. 

Suggested fix:
Restart Workbench

Hello John, the problem with the not-expandabl nodes sounds like a follow up to the first described "invalid node error". Can you still repeat that problem under certain conditions?
What user account are you running WB with (admin or user)? could you post help->system info data from your workbench instance here in the report?
thanks in advance

Bug# 55279 was marked as duplicate of this one

Unfortunately, I can't really add anything useful to my previous submission - I've been using Workbench occasionally since, with no further problems. It seemed to be just a start up error - something not initialised?

I don't have another Windows 7 machine to try a clean installation on, and am not sure if I'd get the same result uninstalling and reinstalling on this machine. And I'd rather not take the time to try, as I'm trying to do a range of other things on several servers at the moment.

I'm running the program as a user with Computer Administrator rights (but not as the user 'Administrator') and I installed it while logged in as myself - and did NOT choose to 'Run as Administrator' when executing the install program from the download.

That's about it, really. I may have a chance in a week or so to try again and see if I can reproduce the bug, but not yet.

Best wishes

John McC

System Info as requested.

MySQL Workbench CE for Windows version 5.2.25

Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE

Cairo Version: 1.8.8

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

OpenGL Driver Version: 3.3.0

OS: Microsoft Windows 7 Home Premium Edition (build 7600), 64-bit

CPU: 4x Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz, 4.0 GiB RAM

Video adapter info:

Adapter type: NVIDIA GeForce 9600 GT

Chip Type: GeForce 9600 GT

BIOS String: Version 62.94.d.0.3

Video Memory: 524288 KB

System Info as requested - repeated with correction to Windows version in OS section in dropdown above

MySQL Workbench CE for Windows version 5.2.25

Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE

Cairo Version: 1.8.8

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

OpenGL Driver Version: 3.3.0

OS: Microsoft Windows 7 Home Premium Edition (build 7600), 64-bit

CPU: 4x Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz, 4.0 GiB RAM

Video adapter info:

Adapter type: NVIDIA GeForce 9600 GT

Chip Type: GeForce 9600 GT

BIOS String: Version 62.94.d.0.3

Video Memory: 524288 KB

John,

you said, it was an error that just happened one time.

You also said it never happened again.

Nobody here is able to repeat this. So I will close this bug report now with "can't repeat".

If you have further problems or informations for us on this topic just feel free to open the bug report again.

Bug #55346 has been marked as duplicate of this one

Bug #55259 has been marked as duplicate of this one

Bug #55431 has been marked as duplicate of this one

Bug #55417 has been marked as duplicate of this one

This is a duplicate of bug #52648