Originally posted by eugenevdm
Be carefull vesterman. I did the same modification and yes sure now my Plesk is accessible. But I did a field comparison on a healthy Plesk upgrade and I found that 'ownership' is:
ENUM field, not VARCHAR, which takes 'true' and 'false' values. The default is 'true' and it is NOT NULL.
I'm not sure if you will ever experience a problem with this, unless you maybe start using Expand or some other integration product. Who Knows.
Well, your hypothesis may be correct. It was probably the root of my problem when I tried to update to Plesk to version 2 from 8.1
It rendered my plesk inaccessible, and then login page not even found when I tried to update via ssh.
Well $79 to swsoft later, the problem was fixed. Hre is the findings so maybe someone else can save the $79. Feel free to donate a small token of appreciation via paypal

lol.
"I found that Plesk upgrade was failed and the database had some mix of 8.1 and 8.2 data structures. Unfortunately there was no mysql dumps. To be more exact the latest dump had "Jul 12" date. So I was forced to downgrade the database manually such way:
mysql> ALTER TABLE clients DROP COLUMN uid;
Query OK, 3 rows affected (0.04 sec)
Records: 3 Duplicates: 0 Warnings: 0
mysql>
mysql> ALTER TABLE clients DROP COLUMN ownership;
Query OK, 3 rows affected (0.23 sec)
Records: 3 Duplicates: 0 Warnings: 0
mysql> ALTER TABLE clients DROP COLUMN server_version;
Query OK, 3 rows affected (0.05 sec)
Records: 3 Duplicates: 0 Warnings: 0
mysql>
etc
Then I updated Plesk to 8.2.0 version fine.
Now if you with you can update it to 8.2.1 version."