In our uls logs , we are getting message :
Process : mssearch.exe (_x-_-_)
Thread ID : -x_-_-
Area : SharePoint Server Search
Category : IDXPIPlugin
Event ID : _-_-
Level : High
Message : [ad0-c-0 Po] A master merge was started because the catalog reached the maximum number of indexes on the last level (16). [merge.cxx:2709] d:\office\source\search\native\ytrip\tripoli\cindex\merge.cxx (0x0DBC) 0x2D50 SharePoint Server Search IDXPIPlugin e130 High [ad0-c-0 Po] A master merge was started because the catalog reached the maximum number of indexes on the last level (16). [merge.cxx:2709] d:\office\source\search\native\ytrip\tripoli\cindex\merge.cxx
Please help us identify the root cause and resolution for this .
You may also like:
SharePoint 2010 Enterprise Search | SharePoint Crawl Exceptional Behaviour
Search – One or more property databases have fragmented indices.
Search History in SharePoint 2010
Process : mssearch.exe (_x-_-_)
Thread ID : -x_-_-
Area : SharePoint Server Search
Category : IDXPIPlugin
Event ID : _-_-
Level : High
Message : [ad0-c-0 Po] A master merge was started because the catalog reached the maximum number of indexes on the last level (16). [merge.cxx:2709] d:\office\source\search\native\ytrip\tripoli\cindex\merge.cxx (0x0DBC) 0x2D50 SharePoint Server Search IDXPIPlugin e130 High [ad0-c-0 Po] A master merge was started because the catalog reached the maximum number of indexes on the last level (16). [merge.cxx:2709] d:\office\source\search\native\ytrip\tripoli\cindex\merge.cxx
Please help us identify the root cause and resolution for this .
You may also like:
SharePoint 2010 Enterprise Search | SharePoint Crawl Exceptional Behaviour
Search – One or more property databases have fragmented indices.
Search History in SharePoint 2010
No comments:
Post a Comment