• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

MU37 phpMyAdmin errors

M-Ruiter

New Pleskian
Hello,

After MU37 the phpmyadmin is broken. It shows some info but Always comes with an error like :

SELECT `tables`
FROM `phpmyadmin_Co30qaqEc7d5`.`@@PMA_RECENT@@`
WHERE `username` = 'admin'

#1146 - Table 'phpmyadmin_Co30qaqEc7d5.@@PMA_RECENT@@' doesn't exist

When i hit the more info button i get :

$cfg['Servers'][$i]['recent'] ... Not OK
Persistente recent used tables: Turned Off

$cfg['Servers'][$i]['table_uiprefs'] ... Niet goed [ Documentatie ]
Persistente interfacevoorkeuren for tables: Turned Off



Anybody got the same problem with MU37 and found a sollution ?
 
same issue

using Plesk 11.0.9 and getting this issue once opening phpmyadmin

SELECT `tables`
FROM `phpmyadmin_************`.`@@PMA_RECENT@@`
WHERE `username` = 'admin'
 
Solution

Parallells support fixed the problem for me.
They mentioned the kb article they used.

See here the response after it was fixed:

I am glad to inform you that the issue is fixed. Now "phpMyAdmin" is loading fine.

In order to fix the issue, I performed the steps mentioned in the KB link given below:

++++
http://kb.parallels.com/114393
++++
 
Yes, there was problem when bootstrapper brokes phpmyadmin. This behaviour will be fixed in MU#38.
 
Back
Top