Problem Migrate Plesk 11 to Plesk 11

[HectorS]

Updated the two servers with MU # 25 and still the same problem.

 

[Webroy]

I have MU25 installed on both resource and destination server..

the problems remains....

 

[MilesUK]

Same here...

 

[GavriilT]

The same here

MU26 installed on both servers.

Destination -> Plesk 11.0.9 ->Centos 6.3 MU #26
Source -> Plesk 11.0.9 ->Centos 6.2 MU #26
"-login incorrect parameter"

Please provide us a solution.

 

[Webroy]

@ plesk please respond problem is not solved......

 

[Will-NYESDigital]

We have gone to MU25 on both resource and destination server..

Still have the same issue

 

[AnibalB]

I have the same problem and it's quite urgent!

 

[hannes42]

CentOS 6.3 x86 => x64, both on 11.0.9 MU#26

still fails with empty -login parameter for some domains. Parallels, please help.

 

[AnibalB]

This problem is also in centos 5 x64

 

[AnibalB]

Most probably it is related to issue discussed in this thread - http://forum.parallels.com/showthread.php?t=260790

This does not solve anything

 

[GavriilT]

I think plaesk support team is busy right now :
we have to discuss our problem and sovle it alone.

Well in my opinion the problem seems to be begin from the source server.

Let's collect logs from database and post it to this thread.
I think for some reason, some sql fields not dumped correct.

let's give it a try. i'll post log ASAP

 

[ErwanG]

Same problem. I've search but no solution...

 

[GiuseppeV]

I have the same problem.
My source server is CentOs 5.5 64 bit with Plesk panel MU #26
My dest server is CentOS 6.3 64 bit with same Plesk Panel MU #26

Please Parallels Support this must be a bug! Resolve it please!

If I try also a single domain migration:
Execution of /usr/local/psa/admin/plib/api-cli/domain.php --update domain.com -guid a30bdaa2-cba5-49c3-8d6a-914229c9ef00 -vendor-guid 2993d605-f09c-4887-9a17-4eed6e3b498e -creation-date 2006-04-18 -hosting true -hst_type phys -do-not-apply-skeleton -ip 192.168.190.191 -www-root httpdocs -login '' -passwd '' -ignore-nonexistent-options failed with return code 1.

Stderr is

Wrong syntax for command's '-login' parameter.


Error: hosting "domain.com"

The password was generated for user 'sysuser'. New password is 'N57ry99'


thank you

 

[HoracioS]

Wrong syntax for command's '-login' parameter.

Hi Igor,

I´m trying to migrate one domain from VZ Debian x64 Plesk 11 MU#26 to exactly the same platform and got the result:

Error: domain "XXXXX.com"
Execution of /opt/psa/admin/plib/api-cli/domain.php --update XXXXX.com -guid f2fab748-d28a-4ac4-ac7c-d2ec49a60a14 -vendor-guid dc07e0a2-e9bf-4f42-a935-2352a01edf4e -creation-date 2011-08-04 -hosting true -hst_type phys -do-not-apply-skeleton -ip x.x.x.x -www-root httpdocs -login '' -passwd '' -ignore-nonexistent-options failed with return code 1.
Stderr is
Wrong syntax for command's '-login' parameter.


Error: hosting "XXXXX.com"
The password was generated for user 'sysuser'. New password is 'idYDQ0r'


PLEASE HELP!!!!

 

[GiuseppeV]

hi all,
verify that domains in source server have one service plan correctly configured (must NOT be 'none').
For me, after apply a service plan, the migration was done.

 

[ErwanG]

Thanks a lot !

It works for me.

 

[ParkerL]

Thank you GiuseppeV, assigning service plans on the source server did the trick.

 

[GrBeach]

Just thought I'd add my experience to the thread.

After I applied all the latest updates my servers are:

Source: CentOS 5.8, Plesk 11.0.9 Update #26
Target: CentOS 6.3, Plesk 11.0.9 Update #26

Thanks to the info here I was finally able to get everything migrated by changing the service plan but only after I did an unlock and sync. It was a bit tedious since there is no way, that I know of, to unlock and sync all domains so I had to go into each subscription one by one. Luckily I don't have too many sites or it would have been a real pain.

 

[TiagoLuz]

Guys,

After hard times cooking my brain, I got the problem. Very simple!

Go to source server, and Sync & Unblock the website you're trying to migrate.

That's it.

 

[Will-NYESDigital]

We can confirm that applying subscriptions to all our clients has indeed fixed this issue.