| Bug #69125 | Error Starting Workbench Administrator | ||
|---|---|---|---|
| Submitted: | 2 May 2013 16:55 | Modified: | 7 Sep 2013 0:11 |
| Reporter: | Admin Owner | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench: Administration | Severity: | S1 (Critical) |
| Version: | 5.2 CE | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Error Starting Workbench Administrator | ||
[2 May 2013 16:55]
Admin Owner
[2 May 2013 17:34]
MySQL Verification Team
Are you using version 5.2.47? . Otherwise please upgrade. Thanks.
[3 Jun 2013 1:00]
Bugs System
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".
[3 Jun 2013 12:35]
Joel Dean
Yes I am running 5.2.47
[22 Jun 2013 3:27]
Alfredo Kojima
Please try 6.0.2 beta
[1 Jul 2013 9:24]
Kon Tiki
Same issue here, as of June 28th 2013. I'm on Workbench 5.2.47 CE. Immaterial whether I run mySQL as ordinary user or as admin, still get this error. Curiously, this error was not there when I first installed and started using mySQL. Am I to upgrade to the 6.x beta version or what ? I'm a bit reluctant to try a beta version when the alpha does not work right. Any advice from others who may've encountered this pesky bug ? KonTiki.
[1 Jul 2013 9:30]
Kon Tiki
I should add that I get this bug when I click on the "Server Administration" link after opening the Workbench. The error is thrown up immediately. And I'm thus prevented from switching on the mySQL server. A show-stopper.
[11 Jul 2013 23:48]
Alfredo Kojima
Please attach the wb.log file which can be located with Help -> Locate Log Files
[12 Jul 2013 12:11]
Kon Tiki
mySQL weblog
Attachment: wb.2.log (application/octet-stream, text), 28.13 KiB.
[12 Jul 2013 12:11]
Kon Tiki
mySQL weblog
Attachment: wb.1.log (application/octet-stream, text), 15.61 KiB.
[12 Jul 2013 12:12]
Kon Tiki
mySQL weblog
Attachment: wb.3.log (application/octet-stream, text), 12.71 KiB.
[12 Jul 2013 12:13]
Kon Tiki
mySQL weblog
Attachment: wb.1.log (application/octet-stream, text), 22.20 KiB.
[12 Jul 2013 12:13]
Kon Tiki
mySQL weblog
Attachment: wb.2.log (application/octet-stream, text), 16.59 KiB.
[12 Jul 2013 12:14]
Kon Tiki
mySQL weblog
Attachment: wb.3.log (application/octet-stream, text), 12.53 KiB.
[12 Jul 2013 12:14]
Kon Tiki
mySQL weblog
Attachment: wb.4.log (application/octet-stream, text), 12.48 KiB.
[12 Jul 2013 12:14]
Kon Tiki
mySQL weblog
Attachment: wb.5.log (application/octet-stream, text), 12.33 KiB.
[12 Jul 2013 12:15]
Kon Tiki
mySQL weblog
Attachment: wb.6.log (application/octet-stream, text), 12.50 KiB.
[12 Jul 2013 12:15]
Kon Tiki
mySQL weblog
Attachment: wb.7.log (application/octet-stream, text), 12.61 KiB.
[12 Jul 2013 12:15]
Kon Tiki
mySQL weblog
Attachment: wb.8.log (application/octet-stream, text), 16.71 KiB.
[12 Jul 2013 12:16]
Kon Tiki
mySQL weblog
Attachment: wb.9.log (application/octet-stream, text), 13.62 KiB.
[12 Jul 2013 12:16]
Kon Tiki
mySQL weblog
Attachment: wb.log (application/octet-stream, text), 16.23 KiB.
[12 Jul 2013 12:52]
Kon Tiki
I'm new to mySQL. So far I can't find any book or manual giving a proper explanation of the architecture of this software as opposed to how to create and populate databases, which is intuitive enough. By deleting old server connections and databases and making new ones I was able to get the mySQL process going again. But I'm none too clear on it.
[15 Jul 2013 12:34]
Rich Zeliff
I'm encountering the same problem with 5.2.47.
The traceback information shows up in the Help>System Information window rather than the logs:
WMIShell: Set filters for local windows cli
Traceback (most recent call last):
File "E:\Software\MySQL Server 5.6\MySQL Workbench CE 5.2.47\modules\wb_admin_grt.py", line 132, in do_open_administrator
adminTab = AdministratorTab(server_instance)
File "E:\Software\MySQL Server 5.6\MySQL Workbench CE 5.2.47\modules\wb_admin_grt.py", line 68, in __init__
self.ctrl_be.init()
File "E:\Software\MySQL Server 5.6\MySQL Workbench CE 5.2.47\modules\wb_admin_control.py", line 429, in init
self.connect_sql()
File "E:\Software\MySQL Server 5.6\MySQL Workbench CE 5.2.47\modules\wb_admin_control.py", line 634, in connect_sql
connection.connect()
File "E:\Software\MySQL Server 5.6\MySQL Workbench CE 5.2.47\workbench\db_utils.py", line 144, in connect
params = self.connect_info.parameterValues
AttributeError: 'NoneType' object has no attribute 'parameterValues'
MySQL Workbench CE for Windows version 5.2.47 revision 10398
Configuration Directory: C:\Users\Administrator\AppData\Roaming\MySQL\Workbench
Data Directory: E:\Software\MySQL Server 5.6\MySQL Workbench CE 5.2.47
Cairo Version: 1.8.8
OS: Microsoft Windows 7 Home Premium Edition Service Pack 1 (build 7601), 64-bit
CPU: 8x Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 8.0 GiB RAM
Active video adapter NVIDIA GeForce GTX 680
Installed video RAM: -2048 MB
Current video mode: 1920 x 1080 x 4294967296 colors
Used bit depth: 32
Driver version: 9.18.13.1106
Installed display drivers: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Current user language: English (United States)
[7 Aug 2013 0:11]
Alfredo Kojima
Thanks for the info, Rich, that's very helpful. For anyone having this problem, please try version 6.0.5 and if the problem still occurs, create a backup of the connection data files (Tools -> Configuration -> Backup Connections...) and after reviewing the contents for sensitive data, please attach to this bug report.
[7 Sep 2013 1:00]
Bugs System
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".
