Bobcares

Error during Plesk upgrade to Obsidian or Onyx

by | Jan 1, 2022

Stuck with error during Plesk upgrade to Obsidian or Onyx? We can help you.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team help a customer deal with this plesk error.

How to resolve error during Plesk upgrade to Obsidian or Onyx?

Plesk Obsidian proposes compelling UX which makes website management easier.

Plesk Onyx is the newest and smoothest upgrade of the traditional Plesk control panel

Typical error might look as shown below:

Upgrade to Onyx 17.8:

Installing packages
Upgrading Plesk URL protection module...
Failed to install 'C:\ParallelsInstaller\parallels\PANEL-WIN_17.8.11\dist-windows\plesk-urlprotection.msi': Fatal error during installation. (Error code 1603)
ERROR: The installation of the package 'plesk-urlprotection' failed with code 1603. (upgrade: Upgrading Plesk URL protection module...)

Upgrade to Obsidian:

Installing packages
Upgrading Plesk URL protection module...
Failed to install 'C:\ProgramData\Plesk\Installer\cache\pool\release\PLESK-WIN_18.0.21_1598\dist-windows\plesk-urlprotection.msi': Fatal error during installation. (Error code 1603)
Action '' failed with error 1603(0x00000643)
ERROR: The installation of the package 'plesk-urlprotection' failed with code 1603. (upgrade: Upgrading Plesk URL protection module...)

Today, let us see the steps followed by our Support Techs to resolve issue in each case.

Upgrade to Onyx 17.8:

1. Firstly, connect to the Plesk server via RDP

2. Then, download the plesk-urlprotection package.

3. Next, start a command prompt as Administrator.

4. Stop IIS service:

Warning: Plesk and websites will be offline while IIS is stopped.

iisreset /stop

5. Then, install the plesk-urlprotection package:

Note: Modify the path to the plesk-urlprotection package if it is different from the below.

msiexec /i "C:\Users\Administrator\Downloads\plesk-urlprotection.msi" /L*V "C:\plesk_urlprotection_installation_debug.txt" AUTOINSTALLER=1

6. Next, start IIS service:

iisreset /start

7. Finally, restart the Plesk upgrade

Upgrade to Obsidian 18

1. Firstly, connect to the Plesk server via RDP

2. Then, start a command prompt as Administrator

3. Next, stop IIS service:

Warning: Plesk and websites will be offline while IIS is stopped.

iisreset /stop

4. Then, install the plesk-urlprotection package:

Note: Modify the path to the plesk-urlprotection package if it is different from the below.

msiexec /i "C:\ProgramData\Plesk\Installer\cache\pool\release\PLESK-WIN_18.0.21_1598\dist-windows\plesk-urlprotection.msi" /L*V "C:\plesk_urlprotection_installation_debug_OBSIDIAN.txt" AUTOINSTALLER=1

5. Then, start IIS service:

iisreset /start

6. Finally, restart the Plesk upgrade

[Need a solution to another query? We are just a click away.]

Conclusion

Today, we saw steps followed by our Support Engineers to resolve error during Plesk upgrade to Obsidian or Onyx.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF