Friday, August 19, 2011

Crawl Status with an ID of "5" (aka FORBID!)

I saw in the SharePoint Search database that one of my full crawl instances (#129) had a status of "5". A list of all crawls (current and previous) is in the MSSCrawlHistory table if you're curious...

(Yes! GASP! I look in the SharePoint databases - but I just look, I don't touch. Neither should you. Ever.)

I looked the status code up online (here: http://msdn.microsoft.com/en-us/library/dd957360(v=office.12).aspx) and found that meant "FORBID".

Now, luckily, the search service was returning expected results during this time, so there was no obvious user impact.

I looked in the table MSSCrawlURLLog in the search database and saw no items (success or fail) under that crawlid. Curious. Nothing was even tried - sounds like the forbid flag must have been thrown a little earlier than the item level - I definitely don't think this is a permissions issue now as [1] the permissions haven't changed in any way and [2] there are no permissions errors on individual items in the table (because there are no rows).

I went in to my WFE server's application log to the time when this crawl failed and sure enough, found these errors:

==============================================================
Event Type: ErrorEvent Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 10036
Date:  8/18/2011
Time:  6:00:01 PM
User:  N/A
Computer: myservername
Description:
A database error occurred.
Source: Microsoft OLE DB Provider for SQL Server
Code: 11 occurred 1 time(s)
Description: [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
==============================================================
Event Type: WarningEvent Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2423
Date:  8/18/2011
Time:  6:00:01 PM
User:  N/A
Computer: myservername
Description:
The update cannot be started because all of the content sources were excluded by crawl rules, or removed from the index configuration.
Context: Application 'Search index file on the search server', Catalog 'Search'
Details:
 Unspecified error
 (0x80004005)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
==============================================================

Turns out there was some sort of network error that prompted SharePoint search to fail, as reported in the warning shown just below it. I haven't been able to pin down the network error but I haven't had an issue since with search.

No comments:

Post a Comment