Facebook
Twitter-
Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
ERR [panel] Specified column "isAllowed" is not in the row
- Thread starter Akos
- Start date
It is database inconsistency - https://talk.plesk.com/threads/unknown-error.328850/
Contact Odin Support Team if this thread not help.
Contact Odin Support Team if this thread not help.
Here is instruction how to backup Plesk psa database - http://kb.odin.com/en/881
Contact Odin Support Team if you are not familiar with SQL and Windows administration.
Contact Odin Support Team if you are not familiar with SQL and Windows administration.
Hi,
The smb_roleGeneralPermissions is is identical to yours.
My Plesk is clean install, without any upgrades.
mysql> desc smb_roleGeneralPermissions;
+-------------------------+---------+------+-----+---------+---------------------+
| Field | Type | Null | Key | Default | Extra |
+-------------------------+---------+------+-----+---------+---------------------+
| id | int(11) | NO | PRI | NULL | auto_increment |
| roleId | int(11) | NO | MUL | NULL | |
| generalPermissionId | int(11) | NO | | NULL | |
| isAllowed | int(11) | YES | | NULL | |
+-------------------------+---------+------+-----+---------+---------------------+
4 rows in set (0.00 sec)
The smb_roleGeneralPermissions is is identical to yours.
My Plesk is clean install, without any upgrades.
mysql> desc smb_roleGeneralPermissions;
+-------------------------+---------+------+-----+---------+---------------------+
| Field | Type | Null | Key | Default | Extra |
+-------------------------+---------+------+-----+---------+---------------------+
| id | int(11) | NO | PRI | NULL | auto_increment |
| roleId | int(11) | NO | MUL | NULL | |
| generalPermissionId | int(11) | NO | | NULL | |
| isAllowed | int(11) | YES | | NULL | |
+-------------------------+---------+------+-----+---------+---------------------+
4 rows in set (0.00 sec)
I have checked this issue in our support ticket tracker and found that this issue caused by different types of complex database inconsistencies.
I can only recommend to create a request to support team to do in-depth investigation to find the reason and to fix it. Please create a ticket to support at https://www.odin.com/support/request/ .
You may have free support, please check what kind of Plesk license you use for available support options at http://kb.odin.com/en/121580 .
If there’s no free support in your case, you can order Plesk per-incident support at http://www.odin.com/support/buy-support/ Support team will contact you as soon as purchase is processed, and they will do the best to resolve it.
I can only recommend to create a request to support team to do in-depth investigation to find the reason and to fix it. Please create a ticket to support at https://www.odin.com/support/request/ .
You may have free support, please check what kind of Plesk license you use for available support options at http://kb.odin.com/en/121580 .
If there’s no free support in your case, you can order Plesk per-incident support at http://www.odin.com/support/buy-support/ Support team will contact you as soon as purchase is processed, and they will do the best to resolve it.
Similar threads
