Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I am trying to scale out our search topology by adding a new Index Partition and Query Servers. The approach that is being taken is using PowerShell to build a new SharePoint Search Query Topology using New-SPEnterpriseSearchQueryTopology.

This topology has two index partitions which in turn have two query components that are pointing to the same property database.

When the topology is applied with Set-SPEnterpriseSearchQueryTopology the powershell command processes for about 12 minutes but fails with the following error:- ActivationError: Crawl Component 'GUID-crawl-0' on [ServerName] cannot be dismounted. Check that the server is available.

Looking at the ULS logs on the server we see that the 'Application Server Administration Job' failed for service instance Microsoft.Office.Server.Search.Administration.ServerServiceInstance. Reason: The Remote Procedure call failed. Exception 0x800706BE).

Prior to that we have an error from mssearch.exe which is location d:\office\source\search\libs\util\hangrecoverer.cxx161) condition !"Application dismount hangs".

It seems that the dismount is failing and timing out and that causes the topology changes to fail to be applied.

Has anyone had experiences like this?

share|improve this question

2 Answers 2

up vote 2 down vote accepted

The issue seemed to be down to the size of the Index Partition. We reduced the number of items in the index using crawl rules and were able to get it down to about 8 million items from 12 million.

We were able to then make changes to the search topology.

What was interesting was the SharePoint Search Service on the rogue Crawl server would take about 90 seconds to restart. Once the index was reduced down it took about 5-10 seconds.

I guess this is one of the reasons why the supported maximum number of items in an index partition is 10 million items.

share|improve this answer
    
You should mark this as the answer. –  shufler May 2 '13 at 0:21
    
Thought I had.. thanks for reminder –  Simon Doy May 10 '13 at 21:44

Run the configuration wizard once again, I assume your DB layout is not in sync.

share|improve this answer
    
Thanks for the comment, DB layout is not in sync? Do you mean Property Db or Crawl Db? –  Simon Doy Apr 30 '13 at 10:05
    
Cant tell which one blocks it - did you try it? See this blog post: sharepointed.com/2012/08/26/… –  Max Melcher Apr 30 '13 at 13:39
    
Thanks - this issue is different though the error that the blog post is referring to is that files cannot be found. –  Simon Doy May 1 '13 at 21:53
1  
Thanks for your help, we ended up getting Microsoft involved. I have added the answer below in case anyone else has the problem. –  Simon Doy May 1 '13 at 21:56

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.