• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Urgent IIS problem

D

Dat

Guest
Hi,

I have installed Plesk for Windows 9.5.1 twice yesterday and today. And after updating Windows Server 2003 64 bit, Plesk does not start because of IIS and the following error is given:

Application pool 'PleskControlPanel' is being automatically disabled due to a series of failures in the process(es) serving that application pool.


and a couple of warning messages show in event logs also:

A process serving application pool 'PleskControlPanel' terminated unexpectedly. The process id was '2752'. The process exit code was '0xffffffff'.

This is really a great problem as I have already formatted and installed Windows Server 2003 64 bit from scratch but the same problem exists.

Please help its urgent.
 
In that case you can revise IIS log files and detect what exactly call was performed in that time. Such errors very often related with web-sites application, those applications treid to perform call which terminate IIS. In that case you can switch sites into different pools and detect what exactly site was terminated IIS.

Also you may try to reinstall IIS, for further details you may try to check the following Microsoft site:
http://www.microsoft.com/technet/pr...485-d74c-4647-87a5-f9d0f9aae51e.mspx?mfr=true

Investigation of this problem require access to server, therefore I can suggest you contact support team. If it is really bug - request to developers will be submitted after support team investigation and you will be refunded for ticket.
 
This is a fresh install. There are no sites yet. The log files are all emtpy. The latest update causes such an error. I'll try to uninstall and install IIS back but I don't think it will help.
 
Back
Top