Article ID: 126113, created on Jul 9, 2015, last review on Jul 9, 2015

  • Applies to:
  • Plesk Automation

After "ppa-transfer check config.ini" you may see a list of errors and warnings. In this article I'm going to explain some of them.

└ Subscription '<subscription_name>'
│ │ 
│ └ error: Subscription is assigned to PPA service template '<Service_template_name>' that has no Web Apache service
│   Assign this subscription to a service template which offers Web apache service.
├ Subscription '<subscription_name>'
│ │ │ │ 
│ │ │ ├ error: Subscription is assigned to PPA service template '<Service_template_name>' that has no Microsoft SQL database service
│ │ │ │ Assign this subscription to a service template which offers Microsoft sql database service.
│ │ │ │ 
│ │ │ └ error: Subscription is assigned to PPA service template '<Service_template_name>' that has no Web IIS service
│ │ │   Assign this subscription to a service template which offers Web iis service.

Most likely that means that subscription based on Apache (or IIS) were assigned to Service plan based on IIS (or Apache). If not, then you need to check that selected Service template has IIS, Apache, Mysql or MSSQL resource (depends on error message).

│ ├ Client '<client_name>'
│ │ │ 
│ │ ├ Auxiliary user '<user_name>'
│ │ │ │ 
│ │ │ └ info: Auxiliary user won't be migrated as subscription '<subscription_name>' it is restricted to does not exist in PPA and won't be created.
│ │ │   
│ │ │ 
│ │ └ Subscription '<subscription_name>'
│ │   │ 
│ │   └ error: Subscription is assigned to PPA service template '<Service_template_name>' that has no Web IIS service
│ │     Assign this subscription to a service template which offers Web iis service.

This 'info' message means that as the subscription will not be transferred due to an error, that is why auxiliary user will not be created too.

│ ├ Client '<client_name>'
│ │ │ 
│ │ └ warning: A client with the same username already exists on another Plesk server
│ │   Subscriptions of both clients will be transferred to PPA under the same customer account. If you want migration tool to create separate PPA accounts for each client, change the username for the one of them.

Client exists on both your source servers. After the transfer in PPA it will be one client with two subscriptions. If you need to have two separate clients then you need to rename one of them.

│ │ │ └ DNS zone '<domain_name>'
│ │ │   │ 
│ │ │   └ warning: The DNS zone '<domain_name>' of this subscription is managed by an external server.
│ │ │     Once the transfer is finished, manually change DNS records on the external DNS server(s).

Client uses an external DNS server for this domain and after the transfer DNS records should be changed manually.

│ ├ Client '<client_name>'
│ │ │ 
│ │ ├ warning: Domain 'rhemo-stb.de' belongs to client '<client_name>' in centralized mail server '<mail_server_name>', but no such client found in Plesk servers
│ │ │ Domain administrator '<user_name>' will not be transferred to PPA. You can create corresponding additional user in PPA hosting panel after transfer.

Client exists on mail server node, but does not exist in Plesk. If you need to transfer it anyway, create such a client in PPA first.

Client '<client_name>' 
warning: Domain 'rhemo-stb.de' belongs to client '<client_name>' in centralized mail server '<mail_server_name>', but no such client found in Plesk servers 
Domain administrator '<user_name>' (and the other <client_name> users) will not be transferred to PPA. You can create corresponding additional user in PPA hosting panel after transfer. 

This means that domain is present on centralized mail server, but client is not present in Plesk. The reasons may be the following:

  • This domain were created manually
  • Domain were deleted from Plesk, but due to some error were not deleted from centralized mail.
  • Check that in the migration-list file this domain is assigned to correct user.

If mailboxes for this domain are used, then it may be migrated as usual. In this case in PPA the client with mailboxes will be created. If domain is not used, then you may decide not to migrate it.

Search Words

error

warning

Migration

precheck

e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF