• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

ERROR: PleskFatalException Client cant own other client.

D

davisjl

Guest
Hello,

We are getting the following error after upgrading to plesk 9.0.1 on a Windows 2003 Server. This error occurs when clicking on any client from the client accounts list. I have not been able to identify any other experiences with this problem. Any help would be appreciated. There is nothing in Plesk event log.

Thanks,
Joseph

ERROR: PleskFatalException
Client cant own other client.

Additionally, an exception has occurred while trying to report this error: PleskFatalException
Client cant own other client.

0: plib\Navigation.php:311
Navigation->getActualLocation(object of type plesk__client)
1: plib\Navigation.php:329
Navigation->detectContext(object of type UserAdmin, object of type plesk__client)
2: htdocs\plesk.php:28
 
dbupgrade.exe cannot update base from 8.6.5 to 9.0.0 (or 9.0.1) and dashboards in domains, clients (and other) does not work (

C:\Program Files (x86)\Parallels\Plesk\admin\bin>dbupgrade.exe --upgrade --from-
version=8.6.5 --to-version=9.0.0
Invalid column name 'parent_id'.
at (ContentHandlerWrapper::parseURL line 31)
at Updating clients scheme(UpdateDatabaseOver_9_0_0 line 1705)
Invalid column name 'overuse'.
at (ContentHandlerWrapper::parseURL line 31)
at Updating domains scheme(UpdateDatabaseOver_9_0_0 line 1719)
Table `ip_pool` hasn't known schema
at (recreateTable line 29)
at Add ip_pool table(UpdateDatabaseOver_9_0_0 line 1725)
Invalid column name 'send2reseller'.
at (ContentHandlerWrapper::parseURL line 31)
at Add new notifications.(UpdateDatabaseOver_9_0_0 line 1767)
Invalid column name 'type'.
at (VADORecordSet::eek:pen line 118)
at APS pool upgrade(UpdateDatabaseOver_9_0_0 line 1796)
Table `APSCatalogUpdates` hasn't known schema
at (recreateTable line 29)
at Add APSCatalogUpdates table.(UpdateDatabaseOver_9_0_0 line 1802)
Table `BillingCache` hasn't known schema
at (recreateTable line 29)
at Creating BillingCache table(UpdateDatabaseOver_9_0_0 line 1960)
Table `suspend_handler_history` hasn't known schema
at (recreateTable line 29)
at Creating suspend_handler_history table(UpdateDatabaseOver_9_0_0 line 1966)

Table `BackupsScheduled` hasn't known schema
at (recreateTable line 29)
at Upgrade BackupsScheduled(UpdateDatabaseOver_9_0_0 line 1978)
Table `PersistentCache` hasn't known schema
at (recreateTable line 29)
at Create PersistentCache table.(UpdateDatabaseOver_9_0_0 line 1992)
Table `BackendCache` hasn't known schema
at (recreateTable line 29)
at Create BackendCache table.(UpdateDatabaseOver_9_0_0 line 1998)
 
Manual to all clients set parent_id = parent_id where type of client = admin and no errors, but dashboard is empty...
 
I install Plesk 9.0.1 on a clean server and with adeptsql compare tables Dashboard* and misc.
 
Has anyone found a solution to this error ? We are experiencing the same issue after upgrading to Plesk 9
 
Back
Top