IIS6 and SP1 - Application Pools crashing

IIS6 and SP1 - Application Pools crashing

am 02.04.2005 05:12:41 von Colin Bowern

I went to deploy Windows Server 2003 Service Pack 1 to our main mail server.
This server has Exchange Server 2003 Service Pack 1, Windows SharePoint
Services Service Pack 1, and is a domain controller (we run a small
environment).

After the service pack was deployed to that server the IIS application pools
continuously crashed logging errors to the System event log:
---
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1009
Date: 4/1/2005
Time: 9:35:13 PM
User: N/A
Computer: MAIL
Description:
A process serving application pool 'DefaultAppPool' terminated unexpectedly.
The process id was '6136'. The process exit code was '0x80'.

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


Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1011
Date: 4/1/2005
Time: 9:35:12 PM
User: N/A
Computer: MAIL
Description:
A process serving application pool 'DefaultAppPool' suffered a fatal
communication error with the World Wide Web Publishing Service. The process
id was '2816'. The data field contains the error number.

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

Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1011
Date: 4/1/2005
Time: 9:17:41 PM
User: N/A
Computer: HOMER
Description:
A process serving application pool 'SharePointAppPool' suffered a fatal
communication error with the World Wide Web Publishing Service. The process
id was '3468'. The data field contains the error number.

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

I ran a FILEMON and REGMON trace to find out if there was some sort of
permissions issue. Nothing came up. The application pools run the default
configuration (identity = NETWORK SERVICE) with exception of the
SharePointAppPool which runs as a domain user account so it can access the
SQL Server via Windows Authentication. Everything worked great prior to
Windows Server 2003 Service Pack 1 deployment. Has anyone else encountered
this problem?

I haven't opened a case with PSS yet as I was able to uninstall Windows
Server 2003 Service Pack 1 and it returned to normal operating conditions.

Thanks,
Colin

Re: IIS6 and SP1 - Application Pools crashing

am 02.04.2005 05:28:31 von someone

Right now, we only know that something is trying to load in the Application
Pool and it is crashing. Without attaching debuggers, it is hard to
determine what is crashing and why. You can use IIS State for this.

http://www.iisfaq.com/default.aspx?view=P197

Are you running SBS2003 or ???

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Colin Bowern" wrote in message
news:uaZXXHzNFHA.3336@TK2MSFTNGP09.phx.gbl...
I went to deploy Windows Server 2003 Service Pack 1 to our main mail server.
This server has Exchange Server 2003 Service Pack 1, Windows SharePoint
Services Service Pack 1, and is a domain controller (we run a small
environment).

After the service pack was deployed to that server the IIS application pools
continuously crashed logging errors to the System event log:
---
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1009
Date: 4/1/2005
Time: 9:35:13 PM
User: N/A
Computer: MAIL
Description:
A process serving application pool 'DefaultAppPool' terminated unexpectedly.
The process id was '6136'. The process exit code was '0x80'.

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


Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1011
Date: 4/1/2005
Time: 9:35:12 PM
User: N/A
Computer: MAIL
Description:
A process serving application pool 'DefaultAppPool' suffered a fatal
communication error with the World Wide Web Publishing Service. The process
id was '2816'. The data field contains the error number.

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

Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1011
Date: 4/1/2005
Time: 9:17:41 PM
User: N/A
Computer: HOMER
Description:
A process serving application pool 'SharePointAppPool' suffered a fatal
communication error with the World Wide Web Publishing Service. The process
id was '3468'. The data field contains the error number.

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

I ran a FILEMON and REGMON trace to find out if there was some sort of
permissions issue. Nothing came up. The application pools run the default
configuration (identity = NETWORK SERVICE) with exception of the
SharePointAppPool which runs as a domain user account so it can access the
SQL Server via Windows Authentication. Everything worked great prior to
Windows Server 2003 Service Pack 1 deployment. Has anyone else encountered
this problem?

I haven't opened a case with PSS yet as I was able to uninstall Windows
Server 2003 Service Pack 1 and it returned to normal operating conditions.

Thanks,
Colin

Re: IIS6 and SP1 - Application Pools crashing

am 02.04.2005 06:38:36 von Colin Bowern

Hi David,

It's a Windows Server 2003 Standard box, not SBS. I'll try the upgrade
again on the weekend and run IISState to see what I can find out.

Thanks,
Colin

"David Wang [Msft]" wrote in message
news:%23oz3SSzNFHA.2144@TK2MSFTNGP09.phx.gbl...
> Right now, we only know that something is trying to load in the
> Application
> Pool and it is crashing. Without attaching debuggers, it is hard to
> determine what is crashing and why. You can use IIS State for this.
>
> http://www.iisfaq.com/default.aspx?view=P197
>
> Are you running SBS2003 or ???
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "Colin Bowern" wrote in
> message
> news:uaZXXHzNFHA.3336@TK2MSFTNGP09.phx.gbl...
> I went to deploy Windows Server 2003 Service Pack 1 to our main mail
> server.
> This server has Exchange Server 2003 Service Pack 1, Windows SharePoint
> Services Service Pack 1, and is a domain controller (we run a small
> environment).
>
> After the service pack was deployed to that server the IIS application
> pools
> continuously crashed logging errors to the System event log:
> ---
> Event Type: Warning
> Event Source: W3SVC
> Event Category: None
> Event ID: 1009
> Date: 4/1/2005
> Time: 9:35:13 PM
> User: N/A
> Computer: MAIL
> Description:
> A process serving application pool 'DefaultAppPool' terminated
> unexpectedly.
> The process id was '6136'. The process exit code was '0x80'.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> Event Type: Warning
> Event Source: W3SVC
> Event Category: None
> Event ID: 1011
> Date: 4/1/2005
> Time: 9:35:12 PM
> User: N/A
> Computer: MAIL
> Description:
> A process serving application pool 'DefaultAppPool' suffered a fatal
> communication error with the World Wide Web Publishing Service. The
> process
> id was '2816'. The data field contains the error number.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 8007006d
>
> Event Type: Warning
> Event Source: W3SVC
> Event Category: None
> Event ID: 1011
> Date: 4/1/2005
> Time: 9:17:41 PM
> User: N/A
> Computer: HOMER
> Description:
> A process serving application pool 'SharePointAppPool' suffered a fatal
> communication error with the World Wide Web Publishing Service. The
> process
> id was '3468'. The data field contains the error number.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 8007006d
> ---
>
> I ran a FILEMON and REGMON trace to find out if there was some sort of
> permissions issue. Nothing came up. The application pools run the
> default
> configuration (identity = NETWORK SERVICE) with exception of the
> SharePointAppPool which runs as a domain user account so it can access the
> SQL Server via Windows Authentication. Everything worked great prior to
> Windows Server 2003 Service Pack 1 deployment. Has anyone else
> encountered
> this problem?
>
> I haven't opened a case with PSS yet as I was able to uninstall Windows
> Server 2003 Service Pack 1 and it returned to normal operating conditions.
>
> Thanks,
> Colin
>
>
>

Re: IIS6 and SP1 - Application Pools crashing

am 02.04.2005 06:56:21 von Steve Schofield

Hi Colin,

I was seeing this behavior on an internal site and wasn't sure if it was SP
1 or not. The one thing I did differently on some app pools I use an Active
Directory domain user instead of the built-in network service. I wasn't
sure if it was related to that or not. Things were working fine before
upgrading to SP1. I verified the AD user is in the IIS_WPG group and the
correct has folder permissions.

I verified the permissions for app pools in this KB article
http://support.microsoft.com/default.aspx?scid=kb;en-us;8424 93 I spent a
few hours and even temporarily put the AD user in the local machine admin
group to rule out folder permissions were the cause. I un-installed SP 1
and things returned to normal. I'm curious if others are seeing this too.

--
Thank you,

Steve Schofield
Microsoft MVP - ASP/ASP.NET
ASPInsider Member - MCP

http://www.orcsweb.com/
Powerful Web Hosting Solutions
#1 in Service and Support

"Colin Bowern" wrote in message
news:uaZXXHzNFHA.3336@TK2MSFTNGP09.phx.gbl...
> I went to deploy Windows Server 2003 Service Pack 1 to our main mail
server.
> This server has Exchange Server 2003 Service Pack 1, Windows SharePoint
> Services Service Pack 1, and is a domain controller (we run a small
> environment).
>
> After the service pack was deployed to that server the IIS application
pools
> continuously crashed logging errors to the System event log:
> ---
> Event Type: Warning
> Event Source: W3SVC
> Event Category: None
> Event ID: 1009
> Date: 4/1/2005
> Time: 9:35:13 PM
> User: N/A
> Computer: MAIL
> Description:
> A process serving application pool 'DefaultAppPool' terminated
unexpectedly.
> The process id was '6136'. The process exit code was '0x80'.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
> Event Type: Warning
> Event Source: W3SVC
> Event Category: None
> Event ID: 1011
> Date: 4/1/2005
> Time: 9:35:12 PM
> User: N/A
> Computer: MAIL
> Description:
> A process serving application pool 'DefaultAppPool' suffered a fatal
> communication error with the World Wide Web Publishing Service. The
process
> id was '2816'. The data field contains the error number.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 8007006d
>
> Event Type: Warning
> Event Source: W3SVC
> Event Category: None
> Event ID: 1011
> Date: 4/1/2005
> Time: 9:17:41 PM
> User: N/A
> Computer: HOMER
> Description:
> A process serving application pool 'SharePointAppPool' suffered a fatal
> communication error with the World Wide Web Publishing Service. The
process
> id was '3468'. The data field contains the error number.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 8007006d
> ---
>
> I ran a FILEMON and REGMON trace to find out if there was some sort of
> permissions issue. Nothing came up. The application pools run the
default
> configuration (identity = NETWORK SERVICE) with exception of the
> SharePointAppPool which runs as a domain user account so it can access the
> SQL Server via Windows Authentication. Everything worked great prior to
> Windows Server 2003 Service Pack 1 deployment. Has anyone else
encountered
> this problem?
>
> I haven't opened a case with PSS yet as I was able to uninstall Windows
> Server 2003 Service Pack 1 and it returned to normal operating conditions.
>
> Thanks,
> Colin
>
>

Re: IIS6 and SP1 - Application Pools crashing

am 04.04.2005 18:14:34 von Colin Bowern

Hi Steve,

We're starting to see another error pop up with an ASP.NET identity as well:
---
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: 4/4/2005
Time: 12:09:16 PM
User: NT AUTHORITY\SYSTEM
Computer: WEBSERV
Description:
Logon Failure:
Reason: An error occurred during logon
User Name: aspnetservice
Domain: MYDOMAIN
Logon Type: 3
Logon Process: Ðù»
Authentication Package: NTLM
Workstation Name: WEBSERV
Status code: 0xC000006D
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: 192.168.1.11
Source Port: 1957
---

Notice the garbage in the logon process field.

The troubleshooting continues..

Cheers,
Colin

"Steve Schofield" wrote in message
news:OYNqWB0NFHA.244@TK2MSFTNGP12.phx.gbl...
> Hi Colin,
>
> I was seeing this behavior on an internal site and wasn't sure if it was
> SP
> 1 or not. The one thing I did differently on some app pools I use an
> Active
> Directory domain user instead of the built-in network service. I wasn't
> sure if it was related to that or not. Things were working fine before
> upgrading to SP1. I verified the AD user is in the IIS_WPG group and the
> correct has folder permissions.
>
> I verified the permissions for app pools in this KB article
> http://support.microsoft.com/default.aspx?scid=kb;en-us;8424 93 I spent a
> few hours and even temporarily put the AD user in the local machine admin
> group to rule out folder permissions were the cause. I un-installed SP 1
> and things returned to normal. I'm curious if others are seeing this too.
>
> --
> Thank you,
>
> Steve Schofield
> Microsoft MVP - ASP/ASP.NET
> ASPInsider Member - MCP
>
> http://www.orcsweb.com/
> Powerful Web Hosting Solutions
> #1 in Service and Support
>
> "Colin Bowern" wrote in
> message
> news:uaZXXHzNFHA.3336@TK2MSFTNGP09.phx.gbl...
>> I went to deploy Windows Server 2003 Service Pack 1 to our main mail
> server.
>> This server has Exchange Server 2003 Service Pack 1, Windows SharePoint
>> Services Service Pack 1, and is a domain controller (we run a small
>> environment).
>>
>> After the service pack was deployed to that server the IIS application
> pools
>> continuously crashed logging errors to the System event log:
>> ---
>> Event Type: Warning
>> Event Source: W3SVC
>> Event Category: None
>> Event ID: 1009
>> Date: 4/1/2005
>> Time: 9:35:13 PM
>> User: N/A
>> Computer: MAIL
>> Description:
>> A process serving application pool 'DefaultAppPool' terminated
> unexpectedly.
>> The process id was '6136'. The process exit code was '0x80'.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>>
>> Event Type: Warning
>> Event Source: W3SVC
>> Event Category: None
>> Event ID: 1011
>> Date: 4/1/2005
>> Time: 9:35:12 PM
>> User: N/A
>> Computer: MAIL
>> Description:
>> A process serving application pool 'DefaultAppPool' suffered a fatal
>> communication error with the World Wide Web Publishing Service. The
> process
>> id was '2816'. The data field contains the error number.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 8007006d
>>
>> Event Type: Warning
>> Event Source: W3SVC
>> Event Category: None
>> Event ID: 1011
>> Date: 4/1/2005
>> Time: 9:17:41 PM
>> User: N/A
>> Computer: HOMER
>> Description:
>> A process serving application pool 'SharePointAppPool' suffered a fatal
>> communication error with the World Wide Web Publishing Service. The
> process
>> id was '3468'. The data field contains the error number.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 8007006d
>> ---
>>
>> I ran a FILEMON and REGMON trace to find out if there was some sort of
>> permissions issue. Nothing came up. The application pools run the
> default
>> configuration (identity = NETWORK SERVICE) with exception of the
>> SharePointAppPool which runs as a domain user account so it can access
>> the
>> SQL Server via Windows Authentication. Everything worked great prior to
>> Windows Server 2003 Service Pack 1 deployment. Has anyone else
> encountered
>> this problem?
>>
>> I haven't opened a case with PSS yet as I was able to uninstall Windows
>> Server 2003 Service Pack 1 and it returned to normal operating
>> conditions.
>>
>> Thanks,
>> Colin
>>
>>
>
>

Re: IIS6 and SP1 - Application Pools crashing

am 04.04.2005 18:49:43 von Colin Bowern

Hi David,

This looks like it's the cause of the application pool crashes. One of the
ISAPI filters (ISAPI_Rewrite from Helicon) we use is affected by the Service
Pack 1 upgrade:

http://www.helicontech.com/forum/display_topic_threads~Forum ID~2~TopicID~2525~PagePosition~1.asp

Cheers,
Colin

"Colin Bowern" wrote in message
news:u9rEY3zNFHA.1392@TK2MSFTNGP10.phx.gbl...
> Hi David,
>
> It's a Windows Server 2003 Standard box, not SBS. I'll try the upgrade
> again on the weekend and run IISState to see what I can find out.
>
> Thanks,
> Colin
>
> "David Wang [Msft]" wrote in message
> news:%23oz3SSzNFHA.2144@TK2MSFTNGP09.phx.gbl...
>> Right now, we only know that something is trying to load in the
>> Application
>> Pool and it is crashing. Without attaching debuggers, it is hard to
>> determine what is crashing and why. You can use IIS State for this.
>>
>> http://www.iisfaq.com/default.aspx?view=P197
>>
>> Are you running SBS2003 or ???
>>
>> --
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>> "Colin Bowern" wrote in
>> message
>> news:uaZXXHzNFHA.3336@TK2MSFTNGP09.phx.gbl...
>> I went to deploy Windows Server 2003 Service Pack 1 to our main mail
>> server.
>> This server has Exchange Server 2003 Service Pack 1, Windows SharePoint
>> Services Service Pack 1, and is a domain controller (we run a small
>> environment).
>>
>> After the service pack was deployed to that server the IIS application
>> pools
>> continuously crashed logging errors to the System event log:
>> ---
>> Event Type: Warning
>> Event Source: W3SVC
>> Event Category: None
>> Event ID: 1009
>> Date: 4/1/2005
>> Time: 9:35:13 PM
>> User: N/A
>> Computer: MAIL
>> Description:
>> A process serving application pool 'DefaultAppPool' terminated
>> unexpectedly.
>> The process id was '6136'. The process exit code was '0x80'.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>>
>> Event Type: Warning
>> Event Source: W3SVC
>> Event Category: None
>> Event ID: 1011
>> Date: 4/1/2005
>> Time: 9:35:12 PM
>> User: N/A
>> Computer: MAIL
>> Description:
>> A process serving application pool 'DefaultAppPool' suffered a fatal
>> communication error with the World Wide Web Publishing Service. The
>> process
>> id was '2816'. The data field contains the error number.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 8007006d
>>
>> Event Type: Warning
>> Event Source: W3SVC
>> Event Category: None
>> Event ID: 1011
>> Date: 4/1/2005
>> Time: 9:17:41 PM
>> User: N/A
>> Computer: HOMER
>> Description:
>> A process serving application pool 'SharePointAppPool' suffered a fatal
>> communication error with the World Wide Web Publishing Service. The
>> process
>> id was '3468'. The data field contains the error number.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 8007006d
>> ---
>>
>> I ran a FILEMON and REGMON trace to find out if there was some sort of
>> permissions issue. Nothing came up. The application pools run the
>> default
>> configuration (identity = NETWORK SERVICE) with exception of the
>> SharePointAppPool which runs as a domain user account so it can access
>> the
>> SQL Server via Windows Authentication. Everything worked great prior to
>> Windows Server 2003 Service Pack 1 deployment. Has anyone else
>> encountered
>> this problem?
>>
>> I haven't opened a case with PSS yet as I was able to uninstall Windows
>> Server 2003 Service Pack 1 and it returned to normal operating
>> conditions.
>>
>> Thanks,
>> Colin
>>
>>
>>
>
>

Re: IIS6 and SP1 - Application Pools crashing

am 04.04.2005 21:09:46 von kbrown

I'm working with PSS on this issue right now. The problem is with
Helicon Tech's ISAPI_Rewrite ISAPI filter. There are two ways you can
handle the issue:

1) If you want to continue using ISAPI_Rewrite, add the
%WINDIR%\System32\inetsrv\w3wp.exe to the Data Execution Prevention
exclusions list

OR

2) Remove ISAPI_Rewrite from the list of ISAPI filters on the master
web service properties in the Internet Information Services snap-in

Microsoft actually wants to continue working the case even though I've
reported the details of what is apparently the cause of the issue, so
perhaps Helicon Tech is not completely at fault. In any case, I've
shot an e-mail to Helicon Tech informing them of the DEP
incompatibility.

Kevan Brown

Re: IIS6 and SP1 - Application Pools crashing

am 05.04.2005 20:58:10 von zippo76

We had the same problem. Helicon v50 fixed the problem and our server
has been back in production w/o incident for 48 hrs.

http://www.isapirewrite.com/download/isapi_rwf_0050.msi


Colin Bowern wrote:
> Hi Steve,
>
> We're starting to see another error pop up with an ASP.NET identity
as well:
> ---
> Event Type: Failure Audit
> Event Source: Security
> Event Category: Logon/Logoff
> Event ID: 537
> Date: 4/4/2005
> Time: 12:09:16 PM
> User: NT AUTHORITY\SYSTEM
> Computer: WEBSERV
> Description:
> Logon Failure:
> Reason: An error occurred during logon
> User Name: aspnetservice
> Domain: MYDOMAIN
> Logon Type: 3
> Logon Process: Ðù=BB
> Authentication Package: NTLM
> Workstation Name: WEBSERV
> Status code: 0xC000006D
> Substatus code: 0x0
> Caller User Name: -
> Caller Domain: -
> Caller Logon ID: -
> Caller Process ID: -
> Transited Services: -
> Source Network Address: 192.168.1.11
> Source Port: 1957
> ---
>
> Notice the garbage in the logon process field.
>
> The troubleshooting continues..
>
> Cheers,
> Colin
>
> "Steve Schofield" wrote in message
> news:OYNqWB0NFHA.244@TK2MSFTNGP12.phx.gbl...
> > Hi Colin,
> >
> > I was seeing this behavior on an internal site and wasn't sure if
it was
> > SP
> > 1 or not. The one thing I did differently on some app pools I use
an
> > Active
> > Directory domain user instead of the built-in network service. I
wasn't
> > sure if it was related to that or not. Things were working fine
before
> > upgrading to SP1. I verified the AD user is in the IIS_WPG group
and the
> > correct has folder permissions.
> >
> > I verified the permissions for app pools in this KB article
> > http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;84 2493 I
spent a
> > few hours and even temporarily put the AD user in the local machine
admin
> > group to rule out folder permissions were the cause. I
un-installed SP 1
> > and things returned to normal. I'm curious if others are seeing
this too.
> >
> > --
> > Thank you,
> >
> > Steve Schofield
> > Microsoft MVP - ASP/ASP.NET
> > ASPInsider Member - MCP
> >
> > http://www.orcsweb.com/
> > Powerful Web Hosting Solutions
> > #1 in Service and Support
> >
> > "Colin Bowern" wrote in

> > message
> > news:uaZXXHzNFHA.3336@TK2MSFTNGP09.phx.gbl...
> >> I went to deploy Windows Server 2003 Service Pack 1 to our main
mail
> > server.
> >> This server has Exchange Server 2003 Service Pack 1, Windows
SharePoint
> >> Services Service Pack 1, and is a domain controller (we run a
small
> >> environment).
> >>
> >> After the service pack was deployed to that server the IIS
application
> > pools
> >> continuously crashed logging errors to the System event log:
> >> ---
> >> Event Type: Warning
> >> Event Source: W3SVC
> >> Event Category: None
> >> Event ID: 1009
> >> Date: 4/1/2005
> >> Time: 9:35:13 PM
> >> User: N/A
> >> Computer: MAIL
> >> Description:
> >> A process serving application pool 'DefaultAppPool' terminated
> > unexpectedly.
> >> The process id was '6136'. The process exit code was '0x80'.
> >>
> >> For more information, see Help and Support Center at
> >> http://go.microsoft.com/fwlink/events.asp.
> >>
> >>
> >> Event Type: Warning
> >> Event Source: W3SVC
> >> Event Category: None
> >> Event ID: 1011
> >> Date: 4/1/2005
> >> Time: 9:35:12 PM
> >> User: N/A
> >> Computer: MAIL
> >> Description:
> >> A process serving application pool 'DefaultAppPool' suffered a
fatal
> >> communication error with the World Wide Web Publishing Service.
The
> > process
> >> id was '2816'. The data field contains the error number.
> >>
> >> For more information, see Help and Support Center at
> >> http://go.microsoft.com/fwlink/events.asp.
> >> Data:
> >> 0000: 8007006d
> >>
> >> Event Type: Warning
> >> Event Source: W3SVC
> >> Event Category: None
> >> Event ID: 1011
> >> Date: 4/1/2005
> >> Time: 9:17:41 PM
> >> User: N/A
> >> Computer: HOMER
> >> Description:
> >> A process serving application pool 'SharePointAppPool' suffered a
fatal
> >> communication error with the World Wide Web Publishing Service.
The
> > process
> >> id was '3468'. The data field contains the error number.
> >>
> >> For more information, see Help and Support Center at
> >> http://go.microsoft.com/fwlink/events.asp.
> >> Data:
> >> 0000: 8007006d
> >> ---
> >>
> >> I ran a FILEMON and REGMON trace to find out if there was some
sort of
> >> permissions issue. Nothing came up. The application pools run
the
> > default
> >> configuration (identity =3D NETWORK SERVICE) with exception of the
> >> SharePointAppPool which runs as a domain user account so it can
access
> >> the
> >> SQL Server via Windows Authentication. Everything worked great
prior to
> >> Windows Server 2003 Service Pack 1 deployment. Has anyone else
> > encountered
> >> this problem?
> >>
> >> I haven't opened a case with PSS yet as I was able to uninstall
Windows
> >> Server 2003 Service Pack 1 and it returned to normal operating
> >> conditions.
> >>
> >> Thanks,
> >> Colin
> >>
> >>
> >
> >

Re: IIS6 and SP1 - Application Pools crashing

am 21.04.2005 00:43:56 von Eric Frost

zippo76 wrote:
> We had the same problem. Helicon v50 fixed the problem and our
server
> has been back in production w/o incident for 48 hrs.
>
> http://www.isapirewrite.com/download/isapi_rwf_0050.msi

THanks for sharing zippo.. now if Helicon's server ever comes back up,
I can get mine working.

Eric

http://www.mp2kmag.com

Re: IIS6 and SP1 - Application Pools crashing

am 21.04.2005 13:48:20 von Eric Frost

Their web site finally came up... they are at v53 now --
http://www.helicontech.com/download/#isapi_rewrite

Eric
http://www.ericfrost.com

RE: IIS6 and SP1 - Application Pools crashing

am 24.10.2007 16:55:24 von bmk

In one of our production server running with ASP.NET with .NET 1.1.4322 crashes and hangs very often.

We are having crystal report 10 for reports

From http://www.google.co.in/search?q=+what+is+this+error+code+80 07006d+&hl=en&start=40&sa=N

Posted via DevelopmentNow.com Groups
http://www.developmentnow.com