You cannot crawl or index SharePoint sites in FAST Search Server 2010

Article ID: 2570111 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

When you feed content to a multi-node FAST environment in FAST Search Server 2010, the content is not indexed correctly, and the crawl process seems to stop responding.

Additionally, communication errors that resemble the following may be logged on the FAST system:
WARNING systemmsg Module (Search Dispatcher) at fast.contoso.com:15102 is not responding

VERBOSE systemmsg The ping call resulted in the following exception: socket.error: [Errno 10061] Connection refused.

WARNING systemmsg Module (NodeControl) at fast.contoso.com:16015 is not responding

VERBOSE systemmsg The ping call resulted in the following exception: Timeout
Back to the top | Give Feedback

Cause

This problem can occur if the TCP/IP Offload Engine (TOE) is enabled on the FAST Search system. This is because IPSEC does not work correctly with this feature.
Collapse this tableExpand this table
Program or serviceWorks together with TCP Chimney OffloadExpected behavior when both the service and TCP Chimney Offload are enabled
Internet Protocol security (IPsec) policyNoIf the system has an IPsec policy applied, the TCP/IP stack does not try to offload any TCP connections. This lets the IPsec layer inspect every packet to provide the desired security.
Network Adapter teaming service (This service is also known as the Load Balancing and Failover service. It is usually provided by an OEM.)Implementation-specificSome OEMs implement their network adapter teaming solutions so that they coexist with TCP Chimney Offload. See the network adapter teaming service documentation to determine whether you can use TCP Chimney Offload together with this service.
In Fast Search for SharePoint, the non-administrator nodes try to communicate with the administrator node via port 13390, which is secured through IPSEC.

If the Kerberos session encounters a failure, the IPSEC connection is never established, and the socket is not opened. Therefore, connectivity is affected, and the crawling and indexing process fails.
Back to the top | Give Feedback

Resolution

To resolve this issue, disable TOE.

The following procedure is an example of how to determine whether TOE is enabled on the FAST server. If TOE is enabled, you can use the information that is generated in these steps to disable the TOE features.

Step 1: Disable TCP Chimney Offload by using Netsh.exe

To determine the current status of the TCP Chimney Offload feature, follow these steps:
  1. Open an administrator-level Command Prompt window.
  2. At the command prompt, type netsh int tcp show global.
  3. Press Enter.
To disable TCP Chimney Offload, follow these steps:
  1. Open an administrator-level Command Prompt window.
  2. At the command prompt, type netsh int tcp set global chimney=disabled.
  3. Press Enter.
  4. Run the netsh int tcp show global command again to verify that the options are disabled.

Step 2: Disable IP Task Offload by using Netsh.exe

To determine the current status of the IP Task Offload feature, follow these steps:
  1. Open an administrator-level Command Prompt window.
  2. At the command prompt, type: netsh int ip show global.
  3. Press Enter.
To disable the IP Task Offload feature, follow these steps:
  1. Open an administrator-level Command Prompt window.
  2. At the command prompt, type netsh int ip set global taskoffload=disabled.
  3. Press Enter.
  4. Run the netsh int ip show global command again to verify that the options are disabled.

Step 3: Disable offloading at the Teaming level

If a network team is available, Specify the following option settings in Advanced settings for the teaming software:
  • IPv4 Checksum Offload: None
  • IPv4 Large Send Offload: Disabled
Note Depending on your Network Card and driver capabilities, additional offloading options may be listed. In this case, make sure that all options are disabled.

Step 4: Disable offloading at the network card layer (all network cards)

In the advanced configuration for each network adapter that is used, specify the following option settings :
  • IPv4 Checksum Offload: None
  • IPv4 Large Send Offload: Disabled
Note Depending on your Network Card and driver capabilities, additional offloading options may be listed. In this case, make sure that all options are disabled.

Step 5: Disable TCP Offload in the registry (Applicable to Windows 2003)

You can also disable TCP Chimney Offload in the registry. To do this, follow these steps:
  1. In the Start Search box, type regedit, and then click Regedit.exe.
  2. Locate the following subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
  3. Make sure that the following parameters and values are configured:
    • Parameter: EnableTCPChimney
    • Type: REG_DWORD
    • Value: 0
    • Parameter: DisableTaskOffload
    • Type: REG_DWORD
    • Values: 1

Step 6: Verify settings across servers

Make sure that the settings that you have made in the previous steps are consistent across all FAST nodes and SharePoint crawl components servers. Then, restart every server.
Back to the top | Give Feedback

References

Windows Network Task Offload
http://msdn.microsoft.com/en-us/windows/hardware/gg463469.aspx
(http://msdn.microsoft.com/en-us/windows/hardware/gg463469.aspx)


Information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory Access features in Windows Server 2008
http://support.microsoft.com/kb/951037
(http://support.microsoft.com/kb/951037)


The Microsoft Windows Server 2003 Scalable Networking Pack release
http://support.microsoft.com/kb/912222
(http://support.microsoft.com/kb/912222)
Back to the top | Give Feedback

Properties

Article ID: 2570111 - Last Review: September 21, 2012 - Revision: 9.0
Applies to
  • Microsoft FAST Search Server 2010 for SharePoint
  • Microsoft SharePoint Server 2010
Keywords: 
KB2570111
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top