Various errors from VHCS2 to ispCP Omega

[fabio.mazzarino]

I tried to migrate from VHCS2 to ispCP Omega on a Debian server.

The webserver seems to be ok, but I found various errors:

1. Can't login to ispCP. The log table contains the following entry
admin logged in.<br /><small>User IP: xxx.xx.xx.xxx</small>

But the administration interfaces simply does not appears. I'm always redirect to login page.

2. domains table is empty.
domain, domain_dns, ftp_group, ftp_users, sql_database, sql_user, among others tables, are all empty. No data was migrated from VHCS2, which is very important not only to me, but to my clients.

3. No email accounts were migrated.
No email is checked or received. Although imap and smtp is working, no username is recognized.

Could anybody please help?

[RatS]

Looks like the migration was not done correctly.
Did you followed all the steps in the wiki?

Your only chance is a rollback to VHCS2 and restart the installation with ispCP Omega 1.0.0. After you installed 1.0.0 you can update to 1.0.7.

[fabio.mazzarino]

I followed all steps from this tutorial
http://isp-control.net/documentation/dok...grade:vhcs

Found no problems during migration process.

(04-10-2011 05:01 PM)RatS Wrote:  Looks like the migration was not done correctly.
Did you followed all the steps in the wiki?

Your only chance is a rollback to VHCS2 and restart the installation with ispCP Omega 1.0.0. After you installed 1.0.0 you can update to 1.0.7.

[RatS]

You can try to copy the content of the VHCS2 tables to the ispCP table and set all domains, subdomains, emails, etc to status "toadd". Good luck

[fabio.mazzarino]

Too risky for now.

I'll try to install 1.0.0 if not successful I will try this one.

Thanks in advance.

(04-11-2011 12:13 AM)RatS Wrote:  You can try to copy the content of the VHCS2 tables to the ispCP table and set all domains, subdomains, emails, etc to status "toadd". Good luck

[kilburn]

Here is the correct guide to migrade from VHCS/ispcp pre-1.0.0 to 1.0.0.

Once you have ispcp 1.0.0 you can follow the normal upgrade procedures (see docs/upgrading) to get to 1.0.7.