7

As it turned out, this was not an easy task. Clone Search Topology At fisrt I tried clone the search topology, replace the failing Index Component, and activate the clone topology - like this following the technet guide Manage the index component in SharePoint Server 2013: if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) ...


4

Null root directory is OK, it designates the default index location. Once you for example relocate the index, it will be assigned the new directory name. Logically, to restore the default index location, you can run New-SPEnterpriseSearchIndexComponent commandlet without having to specify -RootDirectory property.


4

We had this exact same problem. This post is what worked for us, without having to recreate components like some will tell you to do. http://blogs.msdn.com/b/kristopherloranger/archive/2014/09/26/sharepoint-2013-on-prem-reset-index-stuck-resolution.aspx Hope it works for you!


2

I had the exact same issue as you described where the index component was broken after an Index Reset. I was ready to roll my sleeves up and work through your detailed steps (thank you by the way) when I resolved it by using the Pause/Resume option. Why did I try Pause/Resume? Well after I did an IISRESET I found that the Content Sources were stuck on "...


2

You must have Distributed Cache in the farm; a farm without that service is unsupported. It sounds like you may want to use the Custom role instead so you can start what you need + Distributed Cache on the two servers.


2

policy right - Run As Service - for windows service of search add this account as Admininstartor - Go to CA > Service Applications > Select Search Service Application > in ribbon Permission > add account with full control Hope it helps!


2

There is an issue going on with SharePoint online because of which .aspx pages are not getting indexed. Expected time for a fix is tomorrow. It is visible in the Admin center. You need Admin credentials to check it. Go to Admin Center > Service Health and check the SharePoint online advisory The URL for that is : https://admin.microsoft.com/...


1

A Full Crawl should not be running with any regularity. It should run when you've performed an Index Reset, a rebuild of the SSA, or find a catastrophic failure to index items. A Full Crawl generally won't have any more success than an Incremental with regards to indexing errors (after all, it runs the same process). Full Crawls decrease the freshness of ...


1

I would try couple of things. fill the drive space on the your index location.Try to run the indexer Fill the disk space on the Index Database Server. While index is propagation try to reboot the index server. stop the crawler while it is running, do couple of times.


1

In sharepoint 2010, you have to install the pdf Ifilter in order to search the pdf documents. If you already had that install but after CU it is not working then check the settings if any piece is missing. Check this blog for complete settings. https://blogs.msdn.microsoft.com/sharepoint_bar__grill/2012/01/30/sharepoint-2010-configuring-adobe-pdf-ifilter-...


1

I think that you won't be able to avoid an index reset or a re-crawl. I'm not a search expert and have only cloned a search topology once but it seem's that all the search components need to be in a healthy state to be able to clone them, otherwise you would only clone a topology that is still broken and would be stuck with the same problem. SharePoint ...


1

To find the exact location of the search index, I suggest to use this script instead of the version you tried: $essi = Get-SPEnterpriseSearchServiceInstance $cc = $essi.Components | ? { $_.GetType().Name -eq 'CrawlComponent' } $cc.IndexLocation You might have an empty RootDirectory and having your index files at other (not default) location, for example, ...


1

Try this through Powershell: $hostA = Get-SPEnterpriseSearchServiceInstance -Identity "myserver1" $ssa = Get-SPEnterpriseSearchServiceApplication $topology = Get-SPEnterpriseSearchTopology -SearchApplication $ssa New-SPEnterpriseSearchIndexComponent -SearchTopology $topology -SearchServiceInstance $hostA -IndexPartition 1 Here is more about managed Index ...


1

Adding the disc space to index server solves this issue. Affected files will be indexed in the next/incremental crawl.


1

I struggled with this error for over a week trying everything I could find out on the internet and no luck. I did expand disk space and reset the index and it still did not work, so I rebooted the crawl server and everything worked fine. I hope this helps.


1

The first thing to do is click on the link to the document and see if it can be loaded. If the document is not corrupt, start up Excel (or whatever client app is involved) as your search account i.e. runas...sp-crawling-account-whateverthatmaybe and see if that account can still open the file and read it. If these two things are OK then I would expect that ...


Only top voted, non community-wiki answers of a minimum length are eligible