• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

After upgrade to Plesk8.3.0, desktop fails with MySQL errors

N

net24

Guest
ERROR: PleskMainDBException
DB query failed: Incorrect information in file: '.\psa\newsarticles.frm'

Additionally, an exception has occurred while trying to report this error: PleskMainDBException
DB query failed: Incorrect information in file: '.\psa\newsarticles.frm'

0: D:\plesk\admin\plib\common_func.php3:213
db_query(string 'select id, class, data from NewsArticles where id > 0 order by id')
1: D:\plesk\admin\plib\news\NewsManager.php:52
NewsManager->getArticles(integer '0')
2: D:\plesk\admin\plib\news\NewsManager.php:30
NewsManager->getNewArticles()
3: D:\plesk\admin\plib\class.Form.php:320
Form->assign()
4: D:\plesk\admin\plib\dashboard\DashboardForm.php:96
DashboardForm->assign(array, object of type UserAdmin)
5: D:\plesk\admin\plib\dashboard\DashboardLocation.php:51
DashboardLocation->accessItem(string 'GET', NULL null)
6: D:\plesk\admin\plib\UIPointer.php:529
UIPointer->access(string 'GET')
7: D:\plesk\admin\htdocs\plesk.php:13
 
'.\psa\newsarticles.frm'

this is because newsarticles table is corrupted in Plesk database.

it is necessary to login to Plesk MySQL database which is running on 8306 port typically, delete and recreate the table.

but it is necessary to create it with proper Plesk Default structure

probably, switching Plesk database provider to JET or MSSQL type will create the table
 
Back
Top