When a content source on a file share is set to use change notifications and you copy a large number files into the content source, (for example, 2,500 or more documents) an event ID message similar to the following may be logged in the Event Viewer Application event log:
Event Type: Warning
Event Source: Microsoft Search
Event Category: Gatherer
Event ID: 3079
Date: 1/1/2002
Time: 12:00:00 PM
User: N/A
Computer: ServerName
Description:
Notifications for the scope \\ServerName\ShareName\ are not active.
Context: SharePointPortalServer Application, CatalogName Catalog
Details: Notifications have failed either because of a network failure or because the internal cache size was exceeded. If the condition persists, change the content source type to adaptive or crawl. (0x80040d9f)
After this event occurs, and in scenarios where this event is not logged, the Indexing service starts an incremental crawl of the whole content source, and then abandons notifications. This function may be indicated by the following informational event ID messages in the Event Viewer Application event log:
Event Type: Information
Event Source: Microsoft Search
Event Category: Gatherer
Event ID: 3081
Date: 1/1/2002
Time: 12:00:00 PM
User: N/A
Computer: ServerName
Description:
Notifications for the scope \\ServerName\ShareName\ have been reactivated.
Context: SharePointPortalServer Application, CatalogName Catalog
-and-
Event Type: Information
Event Source: Microsoft Search
Event Category: Gatherer
Event ID: 3019
Date: 1/1/2002
Time: 12:00:00 PM
User: N/A
Computer: ServerName
Description:
The crawl has started.
Context: SharePointPortalServer Application, CatalogName Catalog
This behavior can occur because there is a buffer size limit of approximately 2,500 change notifications for the operating system. When Microsoft SharePoint Portal Server 2001 or Microsoft Office SharePoint Portal Server 2003 uses remote notifications this limit may be exceeded, after which the cache error occurs.
To work around this behavior, use the following guidelines:
- If content is frequently changed, configure the content source for crawling instead of for notifications.
- If content is seldom changed, configure the content source for notifications instead of for crawling.
The latter method only functions well in scenarios where a buffer overflow is not occurring. After SharePoint Portal Server detects that notifications were missed, SharePoint Portal Server implements incremental crawls.
To view additional information about the types of crawls available in SharePoint Portal Server:
- Open the SharePoint Portal Server Administration tool.
- On the Help menu, click Help Topics, and then click the Search tab.
- In the Search box, type Adaptive, Incremental, or Full.
- Click List Topics.
- Click the topic that you want, and then click Display to view the topic.