• 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.

Error 1009 in W3SVC (0xC0000354)

M

marcussmit

Guest
Hi there,

After upgrading Plesk 7.5.6 to 7.6.1, the main worker process for Plesk's IIS-processes kept failing. I moved my primary customer's domain to a worker process of their own and it appears that the problem is with their domain. In Plesk 7.5.6 there was never a problem with this domain.

The error message says:
--------------------------------------------------------
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1009
Date: 11/9/2006
Time: 11:20:46 AM
User: N/A
Computer: WEB01
Description:
A process serving application pool 'xtreemradio.nl(domain)(pool)' terminated unexpectedly. The process id was '4388'. The process exit code was '0xc0000354'.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
--------------------------------------------------------

After a number of messages (5 in 5 minutes by default) the application pool shuts down completely. I've set the numbers higher to allow IIS to keep on hosting this domain, but this is not a situation that my client will allow for long.

Is there someone that knows how to solve this problem? I know that at least one other person had this problem, but he managed to arrange a full dedicated server as he experienced the problem while using Virtuozzo. I don't use Virtuozzo.

Please help !

Kind regards,
Marcs Smit
 
I'm having the exact same problem since purchasing a new VPS running Plesk 7.6 where as all of the domains hosted run/ran without problems on 7.5.6 with my old host.
 
Back
Top