• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2751
  • Last Modified:

W3SVC 1009 with "exit code was '0x80'"

I guess I did it the wrong way...  I upgraded the array on two of my web servers (W2003 SE, SP1) and copied the whole web-sites (wwwroot, etc) directory to the new drive.  To do this, I copied everything once (a lot of files on our site that get ftp'd) and once I had copied everything, stopped everything (disabled), did a last update and renamed the drives in case anything was hard coded.  Two reboots later, I have the new array as F: and the old as E: (what I wanted).  Brougt everything back on line and all sites were up, happy and no errors.  29 hours later (Application pool recycle time), I start getting ""W3SVC 1009 with "exit code was '0x80'" errors and the final W3SVC 1002 with exit code "Application pool 'XXX' is being automatically disabled due to a series of failures in the process(es) serving..."

Help - I have done all of the right assignments again (.Net, IWUSR, etc.) and this two boxes continue with the weird random stops
  • 3
  • 2
1 Solution
Check Event Viewer logs and Dr Watson for possible details.
NLathropAuthor Commented:
Event viewer is pretty non specific:
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1009
Date:  4/14/2010
Time:  05:29:21
User:  N/A
Computer: CTIA13108
A process serving application pool 'CPO' terminated unexpectedly. The process id was '5020'. The process exit code was '0x80'.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
and for Dr. Watson, nothing yet...
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

NLathropAuthor Commented:
Thanks.  Tried all of the related security / membership / etc. from this great blog, but still have the error...
First off i'd probably disable rapid fail protection if you have it on with your application pool so it will keep recycling when it crashes. Prevents you from having to keep starting it when it fails.

If you have w3wp processes crashing and you have no idea why it would be a good idea to gather some dump information for diagnostics. Download DebugDiag and have it start monitoring your live w3wp processes at the time. This will allow you to capture the threads and heap of the process when it crashes to help determine whats happening. You may also want to start a ProcMon on the w3wp process just in case its failing due to some sort of access violation or ntfs issue. As long as you setup both tools to monitor the particular PID of the w3wp process at the time when it crashes they should both stop logging and a new process will be spawned to start taking new requests. At that time you can review your logs and determine what likely caused the issue.

David Wang from the IIS team has a really good blog posting that discusses how/why crashes could be happening and how to capture enough data to determine what's going on:


I hope this helps. If you need assistance interpreting some of the logs send them along i'll try to help best I can. I realize how frustrating this type of issue is and i'm honestly sympathetic.
NLathropAuthor Commented:
Issue was not really resolved, but solution helped

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now