Unable to migrate a MSSQL Database to Plesk: Unexpected EOF from the server (localhost:1433) DB-Lib error message 20002, severity 9

Symptoms

• Migration of a subscription fails with the following error:

  PLESK_ERROR: Failed to deploy databases of subscription ‘example.com’
  Migration tools tried to perform operation in 3 attempts: Failed to execute SQL query: DB-Lib error message 20017, severity 9:
  Unexpected EOF from the server (localhost:1433)
  DB-Lib error message 20002, severity 9:
  Adaptive Server connection failed (localhost:1433)

• In migration log %plesk_dir%varmodulespanel-migratorsessionsYYYMMDDhhmmssdebug.log there are errors about failed connection via particular TLS versions:

  URLError: <urlopen error [Errno 10054] An existing connection was forcibly closed by the remote host>
  Connecting using TLSv1.1

  ---

  URLError: <urlopen error [Errno 10054] An existing connection was forcibly closed by the remote host>
  Connecting using TLSv1.2

Cause

Due to Plesk MIgrator bug PMT-4793, TLSv1.0 support is required, but it is disabled in the registry. The bug will be fixed in future extension updates.

Resolution

As a workaround:

1. Connect to the destination server via RDP;

2. Go to Start > Run > type regedit to open Windows Registry;

3. Enable TLSv1.0 by updating (or creating) the following registry entry:

   • Name with full path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.0ServerEnabled
   • Type: REG_DWORD
   • Value data: 1

4. Restart the MSSQL server service at Start > Run > type services.msc > right click SQL Server > Restart.

   Note: TLSv1.0 can be disabled again by reverting/setting the Value data to 0 and restarting the SQL Server.

5. Log into Plesk;

6. Resync the subscription Tools & Settings > Migration & Transfer Manager > 203.0.113.2 > example.com > Re-sync.