Facebook
Twitter
J
jrhe
Guest
During install of update 7.5.6 060502.17, the following error is received:
"Error 1920. Service 'PleskControlPanel' failed to start. Verify that you have sufficient privileges to start system services."
The options "Retry" and "Cancel" are offered. If we select retry, the error message reappears. If we select cancel, the installation is rolled back to 7.5.6 pre-update, and SmarterMail Enterprise Edition 3.3.x is de-registered back to "Free Edition". Fixing the SmarterMail again is a snap, but we can't seem to install the update, nor can we now start the Plesk control panel.
This is obviously a permissions error on a file or directory that the update install program is trying to access.
We have verified that PSAADM and PSASERV both have read/write permissions, and that PSACLN has read.
Anyone else have a better handle on the required permissions needed for starting up the Plesk Control Panel service, and for installing the update?
Other than the routine admin issues, the only anomaly we encountered was that DrWeb Cureit discovered a file infected with BackDoor.BitFrost lurking in one virtual FTP server's anonymous inbound file directory last week.
"Error 1920. Service 'PleskControlPanel' failed to start. Verify that you have sufficient privileges to start system services."
The options "Retry" and "Cancel" are offered. If we select retry, the error message reappears. If we select cancel, the installation is rolled back to 7.5.6 pre-update, and SmarterMail Enterprise Edition 3.3.x is de-registered back to "Free Edition". Fixing the SmarterMail again is a snap, but we can't seem to install the update, nor can we now start the Plesk control panel.
This is obviously a permissions error on a file or directory that the update install program is trying to access.
We have verified that PSAADM and PSASERV both have read/write permissions, and that PSACLN has read.
Anyone else have a better handle on the required permissions needed for starting up the Plesk Control Panel service, and for installing the update?
Other than the routine admin issues, the only anomaly we encountered was that DrWeb Cureit discovered a file infected with BackDoor.BitFrost lurking in one virtual FTP server's anonymous inbound file directory last week.
