Bug #56289 "Invalid node Index" exception
Submitted: 26 Aug 2010 13:01 Modified: 3 Sep 2010 7:53
Reporter: Jose Tortone Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.26 OS:Windows (XP)
Assigned to: CPU Architecture:Any

[26 Aug 2010 13:01] Jose Tortone
Description:
When doubleclicking on the localhost (unique server installed) in the section "SQL Development" the following message appears:

"Invalid node index"

"We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below."

"Please make sure to include a detailed description of your actions that lead to this problem."

"Thanks a lot for taking the time to help us improve MySQL Workbench!"

"The MySQL Workbench Team"

Afterwards everything goes fine as nothing have happened and it never appears again even when closing and opening the program again. My suspicion is that there is a conflict with Wampserver I also have installed recently even when this message happended bein Wampserver not active.(I had MysqlServer installed before).

How to repeat:
I'm not sure but I think it can repeated turning off and on the computer, then running the program.
[26 Aug 2010 13:04] Valeriy Kravchuk
What exact version, 5.x.y, of MySQL Workbench do you use? What exact server version, x.y.z, are you connecting to?
[26 Aug 2010 14:13] Jose Tortone
MySQL Workbench Version 5.2.26 CE
MySQL Version 5.1.49-community
[30 Aug 2010 14:43] MySQL Verification Team
Please see if it is same behavior as bug: http://bugs.mysql.com/bug.php?id=52648?. Thanks in advance.
[30 Aug 2010 19:46] Jose Tortone
No, I don't think is the same behavior. Mi problem happens just when I access the SQL Editor for the first time. Later everything goes OK.
I reintalled again MySQLWorkbench and the problem subsists.
[1 Sep 2010 8:00] Valeriy Kravchuk
Please, check with a newer version, 5.2.27, and inform about the results.
[1 Sep 2010 13:09] Jose Tortone
It seems that with 5.2.27 Version the problem ceased.
[3 Sep 2010 7:53] Valeriy Kravchuk
Not repeatable with 5.2.27 any more.