How to fix InnoDB corruption cases for the MySQL/MariaDB databases on Plesk for Windows?

Symptoms

• Plesk SQL server cannot be started with the following error:

  Incorrect function (Error code 1) at Start service PleskSQLServer at (service::startStopService line 997)

  ---

  Error 1067: The process terminated unexpectedly, Exception code: 0xc0000005

• MySQL.MariaDB on Windows is crashing with the following error:

  Faulting application name: mysqld.exe, version: 5.6.36.0, time stamp: 0x58ccdb65
  Faulting module name: mysqld.exe, version: 5.6.36.0, time stamp: 0x58ccdb65
  Exception code: 0x80000003
  Fault offset: 0x00000000002bb162
  Faulting process id: 0x1764
  Faulting application start time: 0x01d4639065120bae
  Faulting application path: C:Program FilesMySQLMySQL Server 5.6binmysqld.exe
  Faulting module path: C:Program FilesMySQLMySQL Server 5.6binmysqld.exe
  Report Id: f33b3065-14ac-4735-b77c-3653d732bef3

• The following can be observed in the %plesk_dir%databasesmysqldata*.err file:

  InnoDB: Page directory corruption: infimum not pointed to
  InnoDB: Page dump in ascii and hex (16384 bytes):
  len 16384; hex 00.....000; asc ;
  InnoDB: End of page dump

  ---

  [ERROR] InnoDB: Page [page id: space=0, page number=237] log sequence number 1737623713 is in the future! Current system log sequence number 1704662866.
  [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.

  ---

  [ERROR] InnoDB: Cannot create log files because data files are corrupt or the database was not shut down cleanly after creating the data files.

• In case it is PleskSQL service, Plesk is inaccessible with:

  ERROR 500
  Zend_Db_Adapter_Exception
  SQLSTATE[HY000] [2002] No connection could be made because the target machine actively refused it.

• The following messages can be found in Event Viewer > Windows Logs > Application:

  InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 252683671 and the end 252687827.For more information, see Help and Support Center at http://www.mysql.com.
  InnoDB: Plugin initialization aborted with error Generic errorFor more information, see Help and Support Center at http://www.mysql.com.
  Plugin 'InnoDB' init function returned error.For more information, see Help and Support Center at http://www.mysql.com.
  Plugin 'InnoDB' registration as a STORAGE ENGINE failed.For more information, see Help and Support Center at http://www.mysql.com.

  ---

  Faulting application name: mysqld.exe, version: 5.5.52.0, time stamp: 0x57c0337c
  Faulting module name: mysqld.exe, version: 5.5.52.0, time stamp: 0x57c0337c
  <..>
  Faulting application path: C:Program Files (x86)ParallelsPleskMySQLbinmysqld.exe
  Faulting module path: C:Program Files (x86)ParallelsPleskMySQLbinmysqld.exe
  Report Id: 3ec05b88-c439-11e8-8102-005056b17492
  Faulting package full name:
  Faulting package-relative application ID:

• Plesk upgrade fails with the next error:

  ERROR 2013 (HY000) at line 275: Lost connection to MySQL server during query

• The following information is found in the %plesk_dir%MySQLData*.err file:

  InnoDB: Completed initialization of buffer pool
  InnoDB: Error: checksum mismatch in data file .ibdata1
  InnoDB: Could not open or create data files.
  InnoDB: If you tried to add new data files, and it failed here,
  InnoDB: you should now edit innodb_data_file_path in my.cnf back
  InnoDB: to what it was, and remove the new…