what I know at this time.

Technologies involved

=====================

- Windows Server 2008 64 bit
- SharePoint 2007 (64 bit) configured as a dedicated indexing Server

Issue

=====================

After installing the 64bit version of Sharepoint 2007 on Windows 2008 Server we see the following behavior:

IIS crashing as soon as any request is made to the server and gives a 503 Server Unavailable error message

Symptoms

======================

In the event log you will see the following event entries:

Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          6/24/2008 2:43:16 PM
Event ID:      5139
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      <ComputerName>

Description:
A listener channel for protocol 'http' in worker process '5764' serving application pool 'DefaultAppPool' reported a listener channel failure.  The data field contains the error number.
Event Xml:
<Event xmlns="https://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="2008-06-24T18:43:16.000Z" />
    <EventRecordID>6798</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>computername</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="AppPoolID">DefaultAppPool</Data>
    <Data Name="ProcessID">5764</Data>
    <Data Name="param3">0</Data>
    <Data Name="ProtocolID">http</Data>
    <Binary>FC2A0780</Binary>
  </EventData>
</Event>

Also all sites when browsed return a 503 Service unavailable

Findings

=====================

It was found that after configuring a shared service provider for Sharepoint ipv6 entries are added to the hosts file that look similar to the following:

fe80::1451:3968:5b73:2978    ServerName # Added by Office SharePoint Server Search (6/23/2008 6:14 PM).

These entries are added for the dedicated crawler

We found that if we removed these entries, that the site starting working again, but once the WAS service is restarted they are added back

Workaround

=====================

It was found that if you use the setting "Use all web front end computers for crawling" then it does not add the IPv6 entries, if you use a dedicated host then Sharepoint adds these entires

Below are the steps to use all frontend servers for crawling:

Central Admin Website --> Operations --> Services on Server --> Go to the server that hasthe search installed --> Office Sharepoint Server Search --> enter all the information and change it from "Use a dedicated web front end computer for crawling" to "Use all web front end for crawling"

Workaround 2:

Disable IPv6 on the NIC
Removed the entry from the hosts file. The entries look like:

fe80::1451:3968:5b73:2978    ServerName # Added by Office SharePoint Server Search (6/23/2008 6:14 PM).

Restart the Windows SharePoint Services Search and Office SharePoint Services Search service

The entries are then added back using the IPv4 address

Broken again by enabling ipv6
Removing the ipv4 entry from the hosts file
Restarting the Windows SharePoint Services Search and Office SharePoint Services Search service

Now restart the application pools in IIS and you should be able to browse the sites.

More Info

=====================

So at this time using a dedicated crawler is not working. Once I have more information on how to get this working I will post it to the blog.

Best Regards,

Jeff MacLeod, MCAD.NET, MCSD.NET
IIS/ASP.NET Support Escalation Engineer ]]>