Article ID: 113608, created on Apr 5, 2012, last review on Aug 12, 2014

  • Applies to:
  • Plesk for Windows


The symptoms vary:
-          Updates/upgrades fail
-          Services refuse to start
-          Services malfunction
-          Errors in control panel
-          Migrations/backups fail


The Parallels Plesk Panel (PP) installation may have suffered a failed upgrade.
Disclaimer: This is only one possible cause, but it is important to identify it at an early troubleshooting stage before you have made any major changes to the server. Otherwise, it may be difficult to restore the installation to a working condition.


Note: If multiple services malfunction or refuse to start, check if there is enough free space on all disk partitions.
We need to verify that all PP components are of the same version, so let us check them, one-by-one.
The installation itself:

Open this file with Notepad:

C:\Program Files (x86)\Parallels\Plesk\version

Example content:
10.2.0 Windows 2003/2008 20110407.20

Note: For 32-bit systems, it will be located in "C:\Program Files\Parallels\Plesk\version."

PSA database:
Go to Start -> Run
Type "cmd" and hit Enter.
In the opened command prompt window, type and run the following commands (do not copy the ">" sign):
>cd %plesk_bin%
>dbclient.exe --direct-sql --sql="select * from upgrade_history order by upgrade_date desc limit 1"
upgrade_date    version_info    db_version

Note: If you see no output (as in the above example), it means that your database has never been upgraded.

For PP 10: You will not find Parallels Plesk Panel in the list of installed programs, so there is nothing to compare.
For earlier PP versions:

On Windows Server 2008: Go to Start -> Control Panel -> Programs -> Programs and Features
On Windows Server 2003: Go to Start -> Control Panel -> Add or Remove Programs

Windows registry:
Go to Start -> Run, type regedit, and hit Enter.
Open this branch:
64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Plesk\PSA Config\Config
... and look for the value of this key: PRODUCT_FULLVERSION

Analyzing the results:
If the above returned versions do not match, it means that your PP installation has suffered a failed upgrade in the past. Proceed to the Resolution section below.
If all three versions match, and you were in the process of upgrading to version 10 from an earlier PP version, you may proceed with further troubleshooting using Parallels Plesk Panel Post-Upgrade Checker.


Try to find the reason for the upgrade failure in the autoinstaller3.log file, which is located on drive C in this directory or a similarly-named directory: a9f588c2d45cba549bb91b9b7de86ab2
Then search for the found error message in our knowledgebase.

Try checking Event Viewer for errors as well.

If you did not find any useful information in the logs, you may need to enable debug logging as described here:

112125 How to enable debug log

If the above actions do not help, feel free to use available support options in our Support portal (in the menu on the left).

a914db3fdc7a53ddcfd1b2db8f5a1b9c 85a92ca67f2200d36506862eaa6ed6b8 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF