Plesk migration shows warnings

Applicable to:

Plesk for Windows

Plesk for Linux

Symptoms

Performing migration from older Plesk server the following warnings are shown:

Before starting the transfer process, Migration & Transfer Manager checks for the issues that can affect the transfer or even block it. This includes checking for available disk space, differences in installed software and configuration of services on the source and destination servers, and so on. You should resolve at least the blocking issues before proceeding with the transfer.

The managed_runtime_version 2.0.50727.0 is not available on the destination server. The default version will be used instead. 3 domain(s) will be affected.

The php_version 4 is not available on the destination server. The default version will be used instead. 1 domain(s) will be affected.

The component mssql is not installed on the destination server. mssql will be unavaiable for all restored objects. Please install mssql. Note that this may take a few minutes. 111 domain(s) will be affected. Install the component

The component Microsoft FrontPage is not installed on the destination server. Microsoft FrontPage will be unavaiable for all restored objects.

The minimum acceptable download speed is 1.25 MBps. The download speed between the source and destination servers is 0 MBps. This might be caused by the network connection issues. Transfer is not possible. Please check your network connection between the source and destination servers and resolve issues.

The component Domain Keys is turned off on the destination server. Please turn on Domain Keys on the destination server. 8 domain(s) will be affected. Mail server settings

Plesk extension 'extension_name' not installed on target Plesk, data of this extension will not be migrated Install Plesk extension 'plesk-mobile' on target Plesk.

Cause

Known cases that may cause migration failures were not fixed before starting a migration procedure.

Resolution

This is just an information message to let you know that source and destination servers has different
MySQL
version. If you have any issues after migration, you might have to edit code of websites to make sure Unicode functionality works fine in MySQL 5.1 platform.

During migration, Plesk backup will be created on
C:\\
drive of the source server and after that this backup will be transferred to
C:\ emp
folder on destination server. Change option
"Directory on the target host where Migration & Transfer Manager will transfer and store temporary migration files."
to another drive with sufficient space or free some space on
C:\\
drive.

During migration, Plesk backup will be created on
C:\\
drive of the source server and after that this backup will be transferred to
C:\ emp
folder on destination server. Free required amount of space on
C:\\
.

This kind of warning message normally occurs if the source server is using the
ASP.NET
version 2.0 and the destination server with any other version such as ASP.NET 4.0. In this case, when migration manager finds a different version of ASP.NET framework 'managed_runtime' than the one on source server, it will just show a warning message which means that for corresponding domain after migration a default version of application will be used instead of managed_runtime_version 2.0 and you can safely ignore this warning message and continue with the migration process. Later you can install ASP.NET 2.0 using Server Components .

"domain.tld uses PHP 4, but PHP 4 is not installed on destination server" - all domains will be switched to PHP 5.*

Network connection speed between the source and destination servers do not met Plesk requirements.

On your destination server go to: Tools & Settings > Mail Server Settings, and enable options under DomainKeys spam protection. If it was already checked, uncheck it press OK, and then check it again and press OK, so it will regenerate the DomainKeys data in the DNS zone.