Services events used in Windows SharePoint Services 3.0
Applies To: Windows SharePoint Services 3.0
Topic Last Modified: 2008-07-10
In this article:
Search service rules
Windows Services rules
Search service rules
Windows SharePoint Services 3.0 uses the same search technology used by Enterprise Search in Microsoft Office SharePoint Server 2007, rather than relying on Microsoft SQL Server full-text search, as previous versions of Windows SharePoint Services did.
The Search service in Windows SharePoint Services addresses a single site collection, and it is automatically scoped to the current context and limited to a site and subsites, list, library, or folder. If you are looking at a subsite, you cannot search the entire site collection, but you can search all subsites of the current site.
The following table describes the rules pertaining to the events that occur while using the Search service.
Rule name | Rule properties |
---|---|
Crawler cannot read from registry |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Crawler_cannot_read_from_registry Description: This alert indicates that the crawler was unable to read from the registry in order to load configuration information needed by the Windows SharePoint Services Search service. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Warning Event ID: 2438 Event Source: Windows SharePoint Services 3.0 Search |
Crawler exception |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Crawler_exception Description: The crawler component of Search uses the Windows SharePoint Services Search service to read its settings in the Windows registry of the search server. This alert indicates that an unexpected error has occurred in the crawler. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Warning Event ID: 2414 Event Source: Windows SharePoint Services 3.0 Search |
Failed to load index |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Failed_to_load_index Description: This alert indicates that the Windows SharePoint Services Search service could not load the index. This can happen when the service is paused or stopped, or the index is corrupt or missing. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Error Event ID: 7043 Event Source: Windows SharePoint Services 3.0 Search |
Failed to load word breaker |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Failed_to_load_word_breaker Description: This alert indicates that a particular word breaker could not be loaded and, therefore, documents that require this word breaker will be crawled using a language-neutral word breaker. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Warning Event ID: 2462 Event Source: Windows SharePoint Services 3.0 Search |
Index is corrupt |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Index_is_corrupt Description: The Windows SharePoint Services Search service has detected that the content index is corrupt. This can occur on either an index server or a query server. When this error occurs on an index server, the Search service automatically attempts to reset and start a full update of the content index. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Error Event ID:4138 Event Source: Windows SharePoint Services 3.0 Search |
Instance of search could not be initialized |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Instance_of_search_could_not_be_initialized Description: This alert indicates that the configuration information for Search could not be loaded from the SQL Server database, which prevented an instance of the Windows SharePoint Services Search service from initializing. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Warning Event ID: 2458 Event Source: Windows SharePoint Services 3.0 Search |
Internal plug-in error |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Internal_plug_in_error Description: This error indicates that the search server is out of memory or that there is an unexpected problem with the search server plug-in. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Warning Event ID: 9502 Event Source: Windows SharePoint Services 3.0 Search |
Master merge error |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Master_merge_error Description: This alert indicates that an error has occurred during a master merge, which is the process of merging a group of indexes into a single index. If this alert occurs repeatedly, the Windows SharePoint Services Search service will eventually be unable to index new documents. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Warning Event ID: 4105, 4106 Event Source: Windows SharePoint Services 3.0 Search |
Plug-in failed to connect to SQL Server |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Plug_in_failed_to_connect_to_SQL_Server Description: This alert indicates that an error occurred in the Windows SharePoint Services Search service. The plug-in did not connect to the SQL Server instance listed in the Event log and the update of the content source cannot continue. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Warning Event ID: 9503, 9510 Event Source: Windows SharePoint Services 3.0 Search |
Windows Services rules
Windows Services are applications that are launched automatically, when the computer is starting up. They operate in the background, while the Windows operating system is running. Windows Services are useful as long-running and independent applications that do not involve user interaction, because they require a significant part of the physical resources of the servers. SharePoint sometimes requires Windows Services to run SharePoint processes. Windows Services ensure these tasks function in periods of low-user load. Windows Services can also manage SharePoint activities because they run independently of Windows SharePoint Services (and Office SharePoint Server), depending exclusively on the Windows operating system infrastructure.
The following table describes the rules pertaining to the events that occur while using Windows Services.
Rule name | Rule properties |
---|---|
Alternate access mapping update failed |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Alternate_access_mapping_update_failed Description: This error occurs when the timer job used to update alternate access mappings failed on the specified server. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Warning Event ID: 6397 Event Source: Windows SharePoint Services 3.0 |
The Windows SharePoint Services Search service is not running |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.The_Windows_SharePoint_Services_Search_service_state Description: This alert indicates that the Windows SharePoint Services Search service is not running. This can happen when the administrator stopped the service or the Startup Type of the service was set to manual and the computer was restarted. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Information Event ID: 21207 Event Source: Microsoft Operations Manager (SPSearch) |
The Windows SharePoint Services Timer service is not running |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.The_Windows_SharePoint_Services_Timer_service_state Description: This alert indicates that the Windows SharePoint Services Timer service is not running. This can happen when the administrator stopped the Windows SharePoint Services Timer service or the Startup Type of the service was set to manual and the computer was restarted. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Information Event ID: 21207 Event Source: Microsoft Operations Manager (SPTimer) |
The Windows SharePoint Services Tracing service is not running |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.The_Windows_SharePoint_Services_Tracing_service_state Description: This alert indicates that the Windows SharePoint Services Tracing service is not running. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Warning Event ID: 21207 Event Source: Microsoft Operations Manager (SPTracer) |
Unable to create a log file |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Unable_to_create_a_log_file Description: This alert indicates that the Windows SharePoint Services Tracing service could not create a log file. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Warning Event ID: 3250 Event Source: Windows SharePoint Services 3.0 |
Unable to load authentication provider |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Unable_to_load_authentication_provider Description: This error indicates that the Role Manager or membership Provider that is specified for a particular Web application is incorrectly configured. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Warning Event ID: 6143 Event Source: Windows SharePoint Services 3.0 |
Unable to write to trace log |
Rule ID: Microsoft.Windows.SharePoint.Services.3.0.Unable_to_write_to_trace_log Description: This alert indicates that Windows SharePoint Services cannot write to the Windows Trace log. This can happen when the hard drive on which the Trace log is located is full or the permissions on the trace logging directory are not set correctly. Rule Category: Event Collection Rule Target: Microsoft.Windows.SharePoint.Services.3.0.WSS.Application Alert Type: Warning Event ID: 5401 Event Source: Windows SharePoint Services 3.0 |