Failed setting of domain parameters in Plesk 8.3 to Plesk 8.3 migration

[RangerTX]

I am using the Migration Manager to try to migrate a single domain from one Plesk 8.3 (rhel3) server to another Plesk 8.3 (rhel5) server.

The first strange thing I noticed that during the process, I get a warning:

After IP mapping, you will not be able to use anonymous FTP service on the following IP address: x.x.x.x

Then it goes through the download progress and fails with:

Execution of /usr/local/psa/admin/plib/api-cli/domain.php --create domain.com -clogin clientname -notify false -guid 5e1e5d9c-bdf8-4663-9ac1-8a94fe1f7768 -creation-date 2006-12-29 failed with return code 1.
Stderr is
An error occured during domain creation: unable to update domain preferences: Unable to update domain data: Failed setting of domain parameters: There is a DNS record pointing to the host www.domain.com.

I have tried turning off DNS on the source Plesk, and got the same error, so deleted all of the DNS entries for the domain, and got the same error. So I tried stopping the DNS (bind) service on the source Plesk, but got the same error, so I tried suspending the domain but I still get the same error. Running the above command in the shell gives the same error with no extra information.

Any other ideas?

 

[Monica@]

Hello.

Seems the same domain or the same DNS record existsi already on the destination server. To troubleshoot the issue instead of the migration try to add the domain with the same name on the destination server. the possible error could spread the light on the issue.

 

[TXRanger]

This happens with any domain I try to migrate from the old Plesk 8.3 to the new Plesk 8.3. Adding the domain manually through Plesk works fine. I just tried it again after updating the Plesk Migration manager, but it still fails. Any other ideas?

 

[TXRanger]

This issue is finally resolved. It turned out to be a record in the DNS template on the destination server. There was a CNAME pointing to www.<domain>. which was causing the problem. We changed the CNAME to point to <domain>. instead and now migrations are working properly.