|
Question : Default Application Pool keeps stopping.
|
|
I have a web server which host multiple web sites. Most of the web sites use the default application pool. The pool will stop occasionally and the following error will appear in the event viewer.
Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 0
Date: 1/10/2008
Time: 5:31:11 AM
User: N/A
Computer: ADSWEBSERVER1
Description:
The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: .NET Runtime version 1.1.4322.2407- w3wp.exe - Common Language Runtime Debugging Services: Application has generated an exception that could not be handled.
Process id=0x660 (1632), Thread id=0x111c (4380).
Click OK to terminate the application.
Click CANCEL to debug the application..
To help Isolate this problem a little more I was wondering if I should go ahead a created a seperate application pool for each web site. This way only the pool for that web site will need to be restarted plus it would identify the site causing all the problems. Are there any issues with IIS 6.0 in having multiple applicaitions pools in IIS 6.0
|
|
|
Answer : Default Application Pool keeps stopping.
|
|
|
|
|
|
|
