distal-attribute
distal-attribute
distal-attribute
distal-attribute

Can't list tables in tree view

User, date Message
Written by Pyton
5 months ago
Category: General
5 posts since Tue, 25 Feb 14
Hello.

I have big problem. After update Heidid i lost tree view of tables. When i connect to DB after clicking (+) on database name i've got an error:

/* Błąd SQL (1044): Access denied for user 'exeevol19'@'%' to database 'exeevol19' */


This error appears in all connections, event i'm root with full grants.

Full stack:

SHOW STATUS;
SHOW VARIABLES;
/* Ładowanie sesji "Test\Test - IP" */
SELECT `DEFAULT_COLLATION_NAME` FROM `information_schema`.`SCHEMATA` WHERE `SCHEMA_NAME`='exexxx';
SHOW TABLE STATUS FROM `exexxx`;
SHOW FUNCTION STATUS WHERE `Db`='exexxx';
SHOW PROCEDURE STATUS WHERE `Db`='exexxx';
SHOW TRIGGERS FROM `exexxx`;
SHOW EVENTS FROM `exexxx`;
/* Błąd SQL (1044): Access denied for user 'exexxx'@'%' to database 'exexxx' */



In prev. version everything works fine.
Written by ansgar
5 months ago
4936 posts since Fri, 07 Apr 06
Please post the same SQL queries from a version which works fine.

You are not "root" by the way, as the error shows a username "exexxx@%", so... probably just a wrong username.
Written by Pyton
5 months ago
5 posts since Tue, 25 Feb 14
No, it's database which works fine on same username and pass.
When I'm connecting to localhost as 'root' it's same problem.

Btw. Everything works fine, just tree view don't.

I'm thinking that "SHOW EVENT" could do crash.
8.1.0.4545 Works fine, next dont't.
I'm working on Wine
Written by ansgar
5 months ago
4936 posts since Fri, 07 Apr 06
4545 is not the latest build, but version 8.1. You should use the newest installer or build when reporting stuff.
Written by Pyton
5 months ago
5 posts since Tue, 25 Feb 14
I'm using the newst version which won't work.
Temporally I installed 4545.
4545 is build which works for me (tree is visible).

Queries are same, with same error (Acces denied) but tree appears.
Written by ansgar
5 months ago
4936 posts since Fri, 07 Apr 06
What's the server version? Must be a bit out-dated, as it does not support events. HeidiSQL probably needs a slightly modified exception handling here.
Written by Pyton
5 months ago
5 posts since Tue, 25 Feb 14
MySQL 5.5.35 on localhost and same on remote
Written by Pyton
4 weeks ago
5 posts since Tue, 25 Feb 14
After few months and manu updates still can't list table in tree view.

I can sent you more data if you need.
Written by longtermheidi
3 weeks ago
1 posts since Fri, 04 Jul 14
Hi.
I am have being battling exactly the same problem trying to remotely access 2 databases housed at Pair Networks. One, databaseA is a new database so I had never tried remote access before. The other, databaseB, has been set up for a while. I was previously able to access it but now I am not. Pair Networks has confirmed they have been able to replicate the problem.

I have tried the following versions:

8.3.0.4792
8.3.0.4741
8.2.0.4675
7.0.0.4053
6.0.0.3603

Versions 6 and 7 successfully connect to databaseA but not databaseB. The key difference seems to be that databaseA is on a system with MySQL 5.5.35 whereas databaseB is on a system with MySQL 5.1.56.

Pair's investigations suggest the issue revolves around event_schedule which is now disabled on their servers. Evidently this should return a null result but HeidiSQL seems to disconnect at this point.

Below are some HeidiSQL console logs.

8.3.0.4741 console:

databaseA:
/* Delimiter changed to ; */
/* Connecting to db150a.pair.com via MySQL (TCP/IP), username keena_7, using password: Yes ... */
/* Connected. Thread-ID: 1657086 */
SHOW STATUS;
SHOW VARIABLES;
/* Entering session "reeannekeena.info" */
SHOW DATABASES;
/* Access is denied */

databaseB:
/* Connection to db150a.pair.com closed at 2014-07-04 10:53:38 */
/* Connecting to db142e.pair.com via MySQL (TCP/IP), username keena_4_r, using password: Yes ... */
/* Connected. Thread-ID: 354382 */
SHOW STATUS;
SHOW VARIABLES;
/* Entering session "hibiscusorg-pair" */
SHOW DATABASES;
/* Access is denied */

By contrast here are console logs for HeidiSQL 7.0.0.4053 to the point of connecting to a table:

databaseA:
/* Connection to db150a.pair.com closed at 2014-07-04 11:03:09 */
/* Connecting to db150a.pair.com via MySQL (TCP/IP), username keena_7, using password: Yes ... */
/* Connected. Thread-ID: 1662669 */
SHOW STATUS;
SHOW VARIABLES;
/* Entering session "reeannekeena.info" */
SHOW DATABASES;
USE `keena_reeannekeenaj`;
SELECT `DEFAULT_COLLATION_NAME` FROM `information_schema`.`SCHEMATA` WHERE `SCHEMA_NAME`='keena_reeannekeenaj';
SHOW TABLE STATUS FROM `keena_reeannekeenaj`;
SHOW FUNCTION STATUS WHERE `Db`='keena_reeannekeenaj';
SHOW PROCEDURE STATUS WHERE `Db`='keena_reeannekeenaj';
SHOW TRIGGERS FROM `keena_reeannekeenaj`;
SHOW EVENTS FROM `keena_reeannekeenaj`;
/* SQL Error (1044): Access denied for user 'keena_7'@'%' to database 'keena_reeannekeenaj' */
SHOW CREATE TABLE `keena_reeannekeenaj`.`subscription`;
SHOW COLLATION;
SHOW ENGINES;
SELECT `id`, `name`, `lastname`, `email`, `phonenumber`, `signupip`, `signupxforward`, `signupdatetime`, `confirmationkey`, `confirmationxforward`, `confirmationdatetime`, `confirmationip` FROM `keena_reeannekeenaj`.`subscription` LIMIT 1000;
SHOW CREATE TABLE `keena_reeannekeenaj`.`subscription`;

databaseB:
/* Connection to db150a.pair.com closed at 2014-07-04 11:04:48 */
/* Connecting to db142e.pair.com via MySQL (TCP/IP), username keena_4_r, using password: Yes ... */
/* Connected. Thread-ID: 359179 */
SHOW STATUS;
SHOW VARIABLES;
/* Entering session "hibiscusorg-pair" */
SHOW DATABASES;
USE `keena_hibiscusorg`;
SELECT `DEFAULT_COLLATION_NAME` FROM `information_schema`.`SCHEMATA` WHERE `SCHEMA_NAME`='keena_hibiscusorg';
SHOW TABLE STATUS FROM `keena_hibiscusorg`;
SHOW FUNCTION STATUS WHERE `Db`='keena_hibiscusorg';
SHOW PROCEDURE STATUS WHERE `Db`='keena_hibiscusorg';
SHOW TRIGGERS FROM `keena_hibiscusorg`;
SHOW EVENTS FROM `keena_hibiscusorg`;
/* SQL Error (1044): Access denied for user 'keena_4_r'@'%' to database 'keena_hibiscusorg' */

From my discussions with Pair I don't believe the issue had being previously reported, much to my surprise. Whatever the cause, there seem to be some quirks somewhere here. Any help and suggestions would be appreciated!

Thanks.


 

Please login to leave a reply, or register at first.