• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Plesk 7.5.6 Installer Fatal error

C

ckissack

Guest
Hi

Yesterday I updated my plesk installation and via Add/Remove changed the config to add MSDE which seemed to go on fine.

Then I installed EMS MSSQL Manager on the server to help manage the DB's and everything appeared to be working fine.

Today I thought I'd look at the other components that could be installed but I received "Fatal Error" when I click next on the Modify/Repair or Remove screen.

Thinking it was the EMS app, I removed that without a problem but its stil the same.

Can I force it to remove/uninstall or do we know what it cant find thats causing it to error and the install to crash?

Colin
 
Cant tell log is now corrupt - Made Progress

HI

Unfortunately I must have some other issues as the app log is now saying its corrupt. I have saved it though.

I did make some progress, the server stopped serving ASP pages and also reported resource in use, so I thought I'd better solve this first.

I worked through this article.

http://msmvps.com/blogs/bernard/archive/2005/05/24/48690.aspx

JSCRIPT registered ok but not VBSCRIPT, upon further investigation I found the VBSCRIPT dll was missing! Its a new VPS and I dont go around deleteing DLLs at the best of times so I dont know where it went. I ftp'd a copy form my server at home and registered it.

This fixed the ASP error so I though I'd check the installer again and bingo its now working. However first time round 2/3rds of the way through a repair it now stops stating Error 2 couldnt connect to pipe.

I've just ran it again and the Repair completed. I dont think its completely fixed all the problesm as I still have some DCOM Local Launch permission errors in the syslog and occasional memory errors via RDC.

Cheers

Colin
 
Back
Top