Vista - Web Service Crashes

I'm running 2003 Standard and IIS 6.0 with ASPNet 2.0.50727.

I hava plaguing situation where this particular application keeps crashing
with the following, some times back to back, sometimes after an hour or so.

App Log:

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 12/30/2008
Time: 3:48:45 AM
User: N/A
Computer: WEB02
Description:
Faulting application w3wp.exe, version 6.0.3790.3959, stamp 45d6968e,
faulting module kernel32.dll, version 5.2.3790.4062, stamp 46264680, debug?
0, fault address 0x0000bee7.

System Log:
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1011
Date: 12/30/2008
Time: 3:48:50 AM
User: N/A
Computer: WEB02
Description:
A process serving application pool 'WEBAppXX' suffered a fatal communication
error with the World Wide Web Publishing Service. The process id was '2176'.
The data field contains the error number.

I have over 20 other webs on the same server that do not crash like this.
But this app crashes about every hour during heavy loads. My developers
can't find the cause. I've looked at the IIS logs but don't think the
failing event is even being registered. I've run Process Monitor, but there
is no clear pattern as to a calling event that shows during the crash.

I have 2 other app pools in the same webspace, seperating 2 other apps and
they do not fail, just this one.

Any suggestions or has someone else run into this before? I need to resolve
this.

Thanks.

I wish I could offer something more specific but I recently had the
same problem.

Heres the scenario.

This new application was using the .NET 3.5 framework. When we put it
on the server, we had to install the service pack. After installing
the service pack we ran into the same kinds of issues you described
above. The solution was to realize there was a service pack, and
another installer called a bootstrap. The bootstrap looks at only
what is required by the machine and installs only those features as
opposed to the service pack which installed everything.



On Dec 30, 5:39*am, "CQL User" <f...@xxxxxx> wrote:

Thanks.

But to make sure I understand, what fixed it? The Service pack or the
bootstrap? Can you be specific so I can give it a try?

This is a web farm, and is occuring on BOTH servers, so I can try on one
before the other.

Thanks.

"rhaazy" <rhaazy@xxxxxx> wrote in message
news:e15a4bca-3dd6-4138-abe1-ac10c6890c2c@xxxxxx
I wish I could offer something more specific but I recently had the
same problem.

Heres the scenario.

This new application was using the .NET 3.5 framework. When we put it
on the server, we had to install the service pack. After installing
the service pack we ran into the same kinds of issues you described
above. The solution was to realize there was a service pack, and
another installer called a bootstrap. The bootstrap looks at only
what is required by the machine and installs only those features as
opposed to the service pack which installed everything.



On Dec 30, 5:39 am, "CQL User" <f...@xxxxxx> wrote:

We uninstalled the servicepack and then ran the bootstrap instead of
the servicepack. So apparently installing the NECESSARY components
only was the fix to our problem. I have no details beyond that, good
luck.

On Dec 30, 10:50*am, "CQL User" <f...@xxxxxx> wrote: