## Synchronizing the Plesk Subscription on a Node and in Parallels Business Automation - Standard Database

There are two types of Plesk-related conflicts:

- A Plesk client or domain exists on a Hardware Node being registered, but there is no information about it in the Parallels Business Automation - Standard database.
- A Plesk client or domain is still registered in the Parallels Business Automation - Standard database, but it was actually deleted from a Hardware Node. This can happen in case a Hardware Node was registered if (for example, manually,

When you register the Plesk Hardware Node that already hosts Plesk clients/domains, it may occur that the information about Plesk clients/domains hosted on this Hardware Node either is absent in Parallels Business Automation - Standard database or does not correspond to the data containing in the database. You can resolve such a conflict by registering

Secondly, Plesk conflicts can occur with already registered node, if a subscription is recorded in the Parallels Business Automation - Standard database, but is actually deleted on a node, or conversely. You can resolve such a conflict either by re-creating a Plesk domain/client or deleting it.

Note: To register a Plesk domain or a client in Parallels Business Automation - Standard, it is necessary that this Plesk domain/client must be in the Active state on the corresponding node. Otherwise, the Parallels Business Automation - Standard will be unable to fetch the Plesk domain configuration, and you will see the system message telling that Parallels Business Automation - Standard is not able to read the domain configuration. In this case, please check the Plesk domain status, activate it if needed, and then try to import it again.

To resolve the Plesk domains or clients conflicts, go to the Migration Director Conflicts Resolver - Plesk Domains or - Plesk Clients respectively.

In This Section Resolving Plesk Subscriptions Registration Conflicts

Please send us your feedback on this help page