Can't start PleskSQLServer service: System error 1058 has occurred. The service cannot be started

Symptoms

• Plesk upgrade failed with an error

  Info 1923.Service 'Plesk SQL Server' (PleskSQLServer) could not be installed. Verify that you have sufficient privileges to install system services MSI (04): ExecServiceConfig: Error 0x80070430: Cannot change service configuration. Error: The specified service has been marked for deletion. Failed to install 'C:\ParallelsInstaller\parallels\PANEL-WIN_17.8.11\dist-windows\mysql-admin_mu067.msi': Fatal error Action '' failed with error 1603(0x00000643) Error: The installation of the package 'mysql' failed with code 1603. (upgrade: Upgrading Plesk SQL server...)

• The Plesk SQL service fails to start

  System error 1058 has occurred. The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

• There are no specific errors in the PleskSQL error log

Cause

The Plesk SQL service configuration has been corrupted during the update.

Resolution

Remove the corrupted service and recreate it.

1. Connect to the server over RDP

2. Open a Command Prompt as Administrator

3. Stop PleskSQLServer

   net stop PleskSQLServer

4. Delete the service

   sc delete PleskSQLServer

   If the error below appears, restart the service with net start PleskSQLServer and run the previous command again

   [SC] DeleteService FAILED 1072:
   The specified service has been marked for deletion.

5. Recreate PleskSQLServer

   sc create PleskSQLServer start= auto DisplayName= "Plesk SQL Server" binPath= "\"%plesk_dir%MySQL\bin\mysqld.exe\" --defaults-file=\"%plesk_dir%MySQL\my.ini\" PleskSQLServer"

6. Configure the Log on user in the PleskSQLServer service

   sc config "PleskSQLServer" obj= "NT Service\PleskSQLServer"

7. Start the service

   net start PleskSQLServer

8. Continue with the Plesk upgrade using the following command and selecting the forward options

   plesk installer --console --debug

Note: The following warning may appear during the upgrade; it can be safely ignored:

Continuing with the upgrade without having an appropriate product license key will result in the installation of a default license key with limited functionality. Administrators are advised to first acquire the appropriate license key before continuing with the product upgrade.