The Stack Overflow podcast is back! Listen to an interview with our new CEO.
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) ...


5

This can be achieved by Extending each of the web applications instead of specifying AAMs only. The steps from where you are now would be: On each web app, remove the AAMs leaving the default one only On ISS Remove IIS bindings for the deleted AAMs on each of the SharePoint servers for the respective web sites On Central Administration => Manage Web ...


5

Try the following steps using PowerShell to remove the search service application: Get-SPServiceApplication Identify the GUID for the search service application and take a copy of it. $SSA = Get-SPServiceApplication -identity "GUIDRetrievedAbove" Remove-SPServiceApplication $SSA If that doesn't work, try the following instead: $SSA = Get-...


5

Most of your incremental crawls do have a massive amount of Security Updates (last column). If the number of Security-Updates decreases, your crawls finish much faster. Question: Why do security only crawls take so long? Answer: The time difference in crawl can be attributed to expansion of the SharePoint Group and also that the group is at the site ...


4

I ended up contacting MS support of to assist with resolution. The root cause was the timer service "instance" was offline on the server. Since there was only one server in farm, timer jobs no longer ran. The timer service (windows service) itself was running, but the service instance (Farm level on server) was not. This was found by running the following ...


4

Stop the crawl for all content sources Get-SPEnterpriseSearchCrawlContentSource -SearchApplication "Search Service Application" | ForEach-Object { If($_.CrawlStatus -ne "Idle") { Write-Host "Stopping crawl on Content source $($_.Name)..." $_.StopCrawl() While ($_.CrawlStatus -ne "Idle") { Write-Host "Waiting to crawl to be stopped......


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

Try using PowerShell commend Stop-SPServiceInstance -Identity Example Stop-SPServiceInstance 67877d63-bff4-4521-867a-ef4979ba07ce Where is the GUID of the service. If you do not know the service GUID, you can retrieve a list of all services in the farm together with their GUIDs by using the Get-SPServiceInstance cmdlet. Or if this not works then ...


2

Interesting question, you can find the better explanation in technet "*In SharePoint 2013, individual services can be configured independently and third-party companies can add services. The services infrastructure gives you control over which services are deployed and how services are shared. Services that are deployed are named service applications. A ...


2

No, it does not. The continuous crawl has a delay of 15-20 minutes before it starts and will add items that has been added since the full crawl was started. http://social.technet.microsoft.com/wiki/contents/articles/15571.sharepoint-2013-continuous-crawl-and-the-difference-between-incremental-and-continuous-crawl.aspx


2

I would recommend everything except the Query Component should go on your app server, so as not to overload the web front end. Creating a secondary backup copy of the Search Index (i.e. the one stored on disk) on the WFE is also a good idea, if you can, to increase fault tolerance. Remember to have both servers configured via HOSTS to point all your web ...


2

Try restarting the search service. go to services restart "SharePoint Server Search 14" service If you got multiple servers with search service you need to do this on each server.


2

You need to disable certificate revocation list (CRL check) on your SharePoint Servers. Here is shown how you can achieve this.


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's no direct way to do this, but here's what you could do. $ssa = Get-SPEnterpriseSearchServiceApplication $cs = Get-SPEnterpriseSearchCrawlContentSource -SearchApplication $ssa -Identity 'Local SharePoint Sites' $dt = Get-Date #value in minutes if($dt.Subtract($cs.CrawlStarted).TotalMinutes -gt '60') { Send-MailMessage [...] }


1

Is the issue existing in every file or a few files? Try to troubleshoot this issue as following: Make sure the search service application is actively crawling the content, and the files are crawled. Please check if the following timer jobs is running, then re-run them and check again: Microsoft SharePoint Foundation Usage Data Import Microsoft SharePoint ...


1

The iFilter Shop sells and supports a variety of iFilters. If I recall correctly you will need to perform the installation and registration of the iFilter and then manually ensure that the Foundation SSA correctly registers the iFilter. In Server this is well documented, in Foundation, less so, though the folks at iFilterShop should be able to assist.


1

EDIT See this solutions Access is denied. Verify that either the Default Content Access Account has access 'Retrieve People Data for Search Crawlers' rights disable the LoopBackRequest


1

Check the following settings in your SharePoint central administration site: Check the search service application->crawl rule, if there is any custom rule which exclude the teams site. Make sure the root site collection has been created in the web application. Type the default zone Web application URL in the start address in content source, then reset index ...


1

This is implemented by default if your users are on the same domain in both SharePoint and the FileShare. If it doesn't work, my guess is that your search service application is miss-configured.


1

You need read article: SharePoint 2013: Service Accounts SP Search Service Search Service Account Used for: Windows user credentials for the SharePoint Search service Domain account SP Search Crawl Default Content Access Account Used for: For Search service application to crawl content. Domain account This account must have read access to external or ...


1

Managed account details are stored in the Configuration Database. You can use below powershell to remove Remove-SPManagedAccount -Identity DOMAIN\ServiceAcct


1

try this code Get-SPEnterpriseSearchCrawlContentSource -SearchApplication "Search Service Application" | ForEach-Object { If($_.CrawlStatus -ne "Idle") { Write-Host "Stopping crawl on Content source $($_.Name)..." $_.StopCrawl() While ($_.CrawlStatus -ne "Idle") { Write-Host "Waiting to crawl to be stopped..." -f DarkYellow sleep 3 } write-host "Crawl ...


1

Editing my answer because apparently i missunderstood: The new default search is the 2010 FAST search, when you upload a file or files in bulk then the event receiver should send those files into a queue which will then be handled by the Continuous crawler. So in effect my previous answer has been wrong/errornous (sorry just human here :D) You can and ...


1

I had a similar problem with full crawl on SP2013 (it was running for several days) and the solution was to reset the search index and run the full crawl again - after that the crawls were taking normal times like before. This blog post describes all the necessary steps for reseting the search index (it is written for SP2013 but it also applies for SP2010). ...


1

Why would I need to create a search service application? You can't use search feature within your farm , If you are not configured the search service application. so the search service application is required to enable search feature To configure the search service application check Create and configure a Search service application in SharePoint Server ...


1

You dont to reset the index if you just want new content coming to this component. But if you want to divide the content equally then Reset the Index and perform a Full Crawl. Or if you see any issue after adding new crawl DB i.e crawling on content source not completed etc.then you need a index reset followed by full crawl.


1

Before you create the service components you have to start the service instance on your server(s). $hostA = Get-SPEnterpriseSearchServiceInstance -Identity “server-name” Start-SPEnterpriseSearchServiceInstance -Identity $hostA then go on with your code. example below $ssa = Get-SPEnterpriseSearchServiceApplication $newTopology = New-...


1

A Full Crawl can be triggered from a few things. Stopping an incremental crawl restoring or adding databases crawl account is changed Change log does not contain URL's being crawled full crawl never completed You have to complete a full crawl before any incremental can run again.


1

You can get more information about the degradation with this powershell: Get-SPEnterpriseSearchStatus -SearchApplication $ssa -Text or more detailed for an index component with name IndexComponent1 Get-SPEnterpriseSearchStatus -HealthReport -Component IndexComponent1 -Text It could be a networking or storage problem. Relocating the index could be an ...


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