A master merge is the process of merging a group of indexes into a single index. This process occurs on index servers when you crawl content and on query servers when the index is propagated from the index server. If this alert occurs repeatedly, the Office SharePoint Server Search (OSearch) service will eventually be unable to index new documents.
A master merge is the process of merging a group of indexes into a single index. This process occurs on index servers when content is crawled and on query servers when the index is propagated from the index server. If this alert occurs repeatedly, the Office SharePoint Server Search (OSearch) service will eventually be unable to index new documents.
Possible causes include:
Inadequate disk space on the hard drive volume that contains the content index.
Hardware problems occurring on any server running the OSearch service.
Server is out of memory.
Content index is corrupt.
First check the Windows NT Event log to determine the cause of the problem.
If the problem is due to a hard drive volume that is full, either increase the size of the hard drive volume or move the content index to another hard drive volume that has adequate space.
If the problem is due to hardware errors, resolve the hardware errors accordingly.
If the problem is due to a server that is out of memory, stop and then restart the Office SharePoint Server Search (OSearch) service on the affected server as described in the Stop and restart the Office SharePoint Server Search service
Important: Do not use the Services on Server page in Central Administration to restart this service because doing so removes the service and deletes the index and associated configuration. Instead, use the following steps:
Stop and restart the Office SharePoint Server Search service
On the affected server, click Start, click Administrative Tools, and then click Services.
Scroll down the list, right-click the Office SharePoint Server Search service, and then click Properties. The properties page appears.
Click Stop. After the service is stopped, click Start
Ensure that the Startup Type is not set to Disabled.
If the problem is due to a corrupted index, the resolution varies depending upon whether the problem occurred on an index or query server.
If the problem occurred on an index server, use the procedures below to reset the content index and start a full update of the content index. Note that users will not be able to perform search queries during this process.
If the problem occurred on a query server, remove the query server from the farm and then add the query server back to the farm. This forces the index server to propagate the full index to the query server.
Reset the content index
Open the administration page for the Shared Services Provider (SSP). To open the administration page for the SSP, do the following in Central Administration:
On the top navigation bar, click Application Management.
On the Application Management page, in the Office SharePoint Server 2007 Shared Services section, click Create or Configure this Farm’s Shared Services.
On the Manage this Farm’s Shared Services page, click the SSP that you want to open.
On the Shared Services Provider Home page, in the Search section, click Search settings.
On the Configure Search Settings page, in the Crawl Settings section, click Reset all crawled content.
On the Reset Crawled Content page, click Reset Now.
Start a full update of the content index
Open the administration page for the Shared Services Provider (SSP). To open the administration page for the SSP, do the following in Central Administration:
On the top navigation bar, click Application Management.
On the Application Management page, in the Office SharePoint Server 2007 Shared Services section, click Create or Configure this Farm’s Shared Services.
On the Manage this Farm’s Shared Services page, click the SSP that you want to open.
On the Shared Services Provider Home page, in the Search section, click Search settings.
On the Configure Search Settings page, in the Crawl Settings section, click Content sources and crawl schedules.
On the Manage Content Sources page, on the drop-down menu for each content source, click Start Full Crawl.
© 2000-2007 Microsoft Corporation, all rights reserved.
Target | Microsoft.Office.Sharepoint.Server.2007.MOSS.Application | ||
Category | EventCollection | ||
Enabled | True | ||
Event Source | Office Server Search | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
| ||
Event Log | Application |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.EventProvider | Default |
CollectData | WriteAction | Microsoft.SystemCenter.CollectEvent | Default |
DataWarehousePublishData | WriteAction | Microsoft.SystemCenter.DataWarehouse.PublishEventData | Default |
MOSS.GenerateAlert | WriteAction | System.Health.GenerateAlert | Default |
<Rule ID="Microsoft.Office.Sharepoint.Server.2007.Master_merge_error" Enabled="onEssentialMonitoring" Target="Microsoft.Office.Sharepoint.Server.2007.MOSS.Application" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="MSWL!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="MSWL!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<Expression>
<And>
<Expression>
<Or>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="Integer">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>4105</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="Integer">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>4106</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</Or>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>Office Server Search</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="CollectData" TypeID="SystemCenter!Microsoft.SystemCenter.CollectEvent"/>
<WriteAction ID="DataWarehousePublishData" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>
<WriteAction ID="MOSS.GenerateAlert" TypeID="Health!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Office.Sharepoint.Server.2007.Master_merge_error.AlertMessageID"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDisplayNumber$</AlertParameter1>
<AlertParameter2>$Data/EventDescription$</AlertParameter2>
<AlertParameter3>$Data/PublisherName$</AlertParameter3>
<AlertParameter4>$Target/Host/Property[Type="MSWL!Microsoft.Windows.Computer"]/NetworkName$</AlertParameter4>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/EventDisplayNumber$</SuppressionValue>
<SuppressionValue>$Data/PublisherName$</SuppressionValue>
<SuppressionValue>$Data/LoggingComputer$</SuppressionValue>
<SuppressionValue>$Data/EventDescription$</SuppressionValue>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>