Upgrade from 7.5.6 to 8.2

[qcomm]

Whats the best way to upgrade to 8.2 from 7.5.6, with as little hassles as possible?

Downloading the installer and running it gives an error 1920 and the Application Log shows the error is a missing php module in httpd.conf. And re-running the installer after gives a another error which the App Log says is SpamAssassin.

Should I upgrade to 8.1 first? then upgrade to 8.2?

I have looked through other posts and tried the suggestions posted, with no luck.

Now I'm looking for more answers, can anyone help?

 

[JackL]

1. Remove Perl, Spam assassin,awstats also remove folders
2. Start Plesk upgare
3. Ignore all errors but cannot start Plesk CP- while on that stage invoke commannd
reconfigurator --switch-plesk-web-server --new-provider=iis

However, I highly recomend to contact support they to perform upgrade

John S.G.

 

[qcomm]

Thanks for the reply.

Unfortunately your suggestion did not work for me, but I was able to complete the upgrade. What I did was upgrade to Plesk 8.1, with no problems BTW. I then made this registry change (I found in another forum post):

Copy registry key and values and subkeys from
HKEY_CLASSES_ROOT\Installer\Products\62CD591E4B6A3
1E48B9E6DB13499D7DD\SourceList

to
HKEY_CLASSES_ROOT\Installer\Products\E8DC367B72BFB
714DB24746C6A074784\SourceList

And then change value

HKEY_CLASSES_ROOT\Installer\Products\E8DC367B72BFB
714DB24746C6A074784\SourceList|PackageName := Apache.msi

Then I ran the Plesk 8.2 installer, and it completed with no errors.

Now I am looking for any errors within the Plesk installation, and I seem to have found one. When I attempt to view the databases under servers I receive an error. One thing I think I should mention is that I am testing the upgrade process on a restored image of my live server on a test server with different hardware. By doing this the network connection is changed, I was forced to move the IP addresses to a new network connection. Would this change of network connections cause the DB errors. I was able to create a new domain but was unable to remove it. Also those sites that are using DB's are not generating errors.

 

[JackL]

Perhaps situation is as follows:
You have changed sa password since backup was made and you are receiving error at server level, when connecting using sa or root(admin) but at domain level it is more rarely password change occurs , so error can be reproduced only on server

John S.G.