• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Plesk Updates Failing

Courtney Brown

New Pleskian
For a few days now, I have been getting notices that Plesk updates are failing. This is the log:

Execution failed.
Command: ai.exe
Arguments: Array
(
[0] => --select-product-id
[1] => panel
[2] => --select-release-current
[3] => --upgrade-installed-components
)

Details: ERROR: Unexpected 'class boost::filesystem::filesystem_error' caught: boost::filesystem::rename: Access is denied: "C:\ParallelsInstaller\parallels\PANEL-WIN_12.0.18\examine_launcher.exe.tmp", "C:\ParallelsInstaller\parallels\PANEL-WIN_12.0.18\examine_launcher.exe"

Does anyone know what to do about this? Also, is there a way to do the updates manually when the automatic scheduled updates fail?
 
Also, is this the type of issue that would require a per incident service request from Odin? I don't mind creating a ticket if this is what should be done.
 
Hi Courtney Brown,

did you have a look at the very big Odin knowledge base? Or at


Details: ERROR: Unexpected 'class boost::filesystem::filesystem_error' caught: boost::filesystem::rename: Access is denied: "C:\ParallelsInstaller\parallels\PANEL-WIN_12.0.18\examine_launcher.exe.tmp", "C:\ParallelsInstaller\parallels\PANEL-WIN_12.0.18\examine_launcher.exe"

A search at the knowledge base leads to:


If the suggestion in the KB doesn't solve your issue, consider to open a support ticket, which might be refunded, if your issue was caused by a bug. :)
 
Back
Top