MySQL Community Server instance is stopped and set as Manual Startup during Updates

Symptoms

• During the update process MySQL57 is stopped and set as Manual Startup at Win+R > services.msc

• The following can be found at autoinstaller3.log

  [2019-07-17 01:57:46.612119] MSI (04): Execute "C:Program Files (x86)ParallelsPleskadminbindefpackagemng.exe" --get --force
  ...
  <type name="mysqlserver" nonestate="false" default="mysql51">
  <package name="mysql57" description="MySQL 5.7 Server " state="not_installed" configured="true" version="" timecost="0">
  <service name="MySQL57" display="MySQL57" status="is stopped" startupType="manual"/>
  </package>
  <package name="mysql56" description="MySQL 5.6 Server " state="not_installed" configured="true" version="" timecost="0"/>
  <package name="mysql51" description="MySQL 5.1 Server 5.1.73" state="" configured="true" version="5.1.73" timecost="16">
  <service name="MySQL" display="MySQL Server" status="is running" startupType="auto"/>
  </package>
  </type>

• The following can be found at the Event Viewer

  The start type of the MySQL57 service was changed from auto start to demand start.
  7/17/2019 1:57:46 AM

• MySQL 5.7 was installed manually on the server and the Service has the default name.

• The same behavior happens when accessing to Tools & Settings > Server Components and clicking at Refresh.

Cause

This is caused by Plesk bug with ID #PPPM-10768 which will be fixed in future product updates.

Note: Please, consider subscribing to this article to receive updates for this bug or check periodically the Plesk Changelog

Resolution

As a workaround, modify the registry value for the affected MySQL Community Server version.

1. Connect to the server via RDP

2. Open Windows Registry Win+R > regedit

3. Navigate to the following key based on the MySQL version affected

   HKEY_LOCAL_MACHINESOFTWAREWow6432NodePLESKPSA ConfigConfigPackagesmysqlservermysql57servicesMySQL57

4. Update the DWORD value as follows:

   AutoStop = 0