The content below is from a great post at Learning SharePoint

Here is a little comparison chart for describing Search capabilities in Search Foundation 2010 Vs  SharePoint Server 2010 Vs FAST Search Server 2010

Feature	SharePoint Foundation 2010	SharePoint Server 2010	FAST Search Server 2010
Basic Search	Yes	Yes	Yes
Document preview	N	No	Yes
Indexing sites	Yes	Yes	Yes
Indexing external content	No	Yes	Yes
People search	No	Yes	Yes
Query federation	No	Yes	Yes
UI-based administration	Limited	Yes	Yes
Visual best bets	No	Limited	Yes

I ran across an issue this morning that had the Sharepoint WSS Search Server in a “Pausing” state.  I had to restart the Office SharePoint Server Search service in order to resolve the issue.

Now to see if it will complete successfully.

From time-to-time we have incremental deployments fail because of issues with checked out pages or other objects.  So, I searched for a way to find all the checked out files and came across Ryan Steeno’s blog.

Here is an overview of the process:

1. Create a new managed property in the Shared Service Provider (SSP)
2. Perform a full crawl on the SharePoint content source
3. Use the new managed property by searching something like: checkoutuser:<author_name>

Go to Ryan’s blog post for details: Find checked out files using MOSS Enterprise Search

One day, we noticed that our search was not working.   Well really, one of the applications managers noticed that it wasn’t working.  Anyway, we found the following errors in the event viewer on our SharePoint 2007 Server:

Event Type:      Warning
Event Source:      Windows SharePoint Services 3 Search
Event Category:      Gatherer
Event ID:      2436
Date:            4/11/2009
Time:            11:45:02 PM
User:            N/A
Computer:      <servername>
Description:
The start address <{somesite}> cannot be crawled.

Context: Application ‘Search index file on the search server’, Catalog ‘Search’

Details:
Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content.   (0×80041205)

Apparently, this error was caused by a recent Microsoft Windows Update that was installed that affected the "Loopback Check" in order to make the system more secure.

In order for the SharePoint Search Services to work we needed to add the following registry entry with a REG_DWORD value of 0×00000001 (1):

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsaDisableLoopbackCheck

Have you ran into this issue or one like it?