• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Specified column "status" is not in the row

Carsten Zaddach

New Pleskian
Hello,

after upgrade to 17.5.3 login is not possible. If I got ot the start page, the following message appears on screen.

Internal error:
Specified column "status" is not in the row
Message Specified column "status" is not in the row
File Abstract.php
Line 179
Type Zend_Db_Table_Row_Exception

Any idea?

System is Ubuntu 16.04.2 LTS and MySQL 5.7

Best regards
Carsten
 
Hi Carsten Zaddach,

did you consider to use the Plesk Repair utility?


This utility has several command options, like for example
Code:
plesk repair installation -y -v
and it is able to investigate and repair quite a lot possible issues. ;)


Pls. inspect as well your upgrade/install/repair - logs ( /var/log/plesk ), in order to investigate the root cause of your issue and make sure, that the Plesk upgrade didn't finish with errors/issues/problems/failures. Consider as well to use the command ( logged in as user "root" over SSH ):
Code:
plesk installer --select-product-id plesk --select-release-current --upgrade-installed-components
 
Hi Carsten Zaddach,

did you consider to use the Plesk Repair utility?


This utility has several command options, like for example
Code:
plesk repair installation -y -v
and it is able to investigate and repair quite a lot possible issues. ;)


Pls. inspect as well your upgrade/install/repair - logs ( /var/log/plesk ), in order to investigate the root cause of your issue and make sure, that the Plesk upgrade didn't finish with errors/issues/problems/failures. Consider as well to use the command ( logged in as user "root" over SSH ):
Code:
plesk installer --select-product-id plesk --select-release-current --upgrade-installed-components

Thank you.

plesk repair installation -y -v

and the problem is fixed. :)
 
Back
Top