I just changed over from a Linux/CPanel solution to a Windows 2003 server with IIS 6 and Plesk 7.5 and I'm having some trouble. Namely after only one full day on the server, the Plesk control panel is inaccessible. Everything was working fine however after my first reboot for a security patch Plesk croaked. It doesn't respond at all via https.
The problem seems to be tied to the Apache HTTP Server (188.8.131.52) dying immediately upon reboot. It gives some cryptic message regarding the ntdll.dll and goes into an endless relaunch cycle.
szAppName : Apache.exe szAppVer : 184.108.40.206 szModName : ntdll.dll
szModVer : 5.2.3790.1830 offset : 000396d0
Since I'm fairly sure Plesk runs on at least one copy of Apache (though there appears to be two) it would seem that the Plesk control panel can't launch since it requires Apache to run. Knowing very little about this, I've tried the Plesk Reconfigurator, then tried repairing and upgrading the Plesk install, changing the settings on various services, configuring a variety of permissions and so on but nothing seems to work.
Two days in and I'm dead in the water. Anyone have any ideas? I'm in an unmanaged dc so not much support I can get there (though thus far they have been very helpful) and the kind folks at SWSoft want $75 just to initiate a conversation.