• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Class not registered (COM Error 80040154)

P

pazzo81

Guest
When i create a new subdomain I have this problem

Unable to update hosting preferences: SubDomain::update() failed: subdomainmng failed: Execute vhostmng --create-subdomain --vhost-name=xxxx --subdomain-name=emporio2 --user-name=xxxx failed: Class not registered (COM Error 80040154) at createSubdomainSecurity(pcommerce.it\subdomains\emporio2)

I have this problem after migrate Plesk 8.2 to 8.3
 
Most likely .Security file for domain is corrupted (it is located in %plesk_vhosts%\domain.com)
Backup it just in case (copy to .Security.bak), then delete it and use option "Check permissions" in Plesk to setup correct permissions for this domain. After that .Security will be recreated.

Then, try to create a subdomain once again.
 
I tried with Reconfigure Plesk ecc ecc but the problem is the same.... after I rebot the server and all is down, IIS in primis.

With

RUN
> regsvr32 Msxml3.dll

I reboot the server and I resolve all the problem... plesk go ok and IIS idem

I think the problem is caused by the Msxml3.dll because It's corrupt...
 
Back
Top