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

IIS 7 application pool

This is a new MS Sever 2008sp2 (x64)server that I am setting up, I had the web server working with WSS 3.0 sp2 (x64).  I installed IBM Client access v6r1 and the application pools stopped working.  I have tried uninstalling the IBM software, server roles and reinstalling the web role but no joy.  I am about to dump the OS and start over; but if anyone has a suggestion first I would appriciate it.
The following is one of four listeners that fail before WAS shuts the App pool down.
Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          4/20/2011 11:57:42 AM
Event ID:      5139
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      WD-FS1.wdc.local
Description:
A listener channel for protocol 'http' in worker process '4740' serving application pool 'DefaultAppPool' reported a listener channel failure.  The data field contains the error number.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />
    <EventID Qualifiers="32768">5139</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-04-20T15:57:42.000Z" />
    <EventRecordID>300069</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>WD-FS1.wdc.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="AppPoolID">DefaultAppPool</Data>
    <Data Name="ProcessID">4740</Data>
    <Data Name="param3">0</Data>
    <Data Name="ProtocolID">http</Data>
    <Binary>05000780</Binary>
  </EventData>
</Event>
0
MisterMitch
Asked:
MisterMitch
1 Solution
 
RovastarCommented:
We you get error it is often something is grabbing at the http listener process away from http.sys and the IIS.

As you have de-installed the likely cause of this problem and it is still doing it something has gone very wrong.

Even if you seem to get it working what else might be lurking there not the answer you want to here but I would reinstall it to be sure.

Also is this your staging box or production/live box?

Having multiple environments of your web infrastructure it is even more important to have the correct procedures and not replicate problem ups and a consistent across all environments. So build from scratch again.........
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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