Cloudy with a Chance of InsightsReaching for the Cloud NewsletterSubscribe to NewsletterSubscribe via RSS
The Microsoft Cloud Blog

Expert insights on Microsoft Azure, Cloud Architecture, and Enterprise Technology

1 min read
PowerShellSearchSharePointSharePoint 2013

SharePoint 2013 Error: The filtering process has been terminated

ShareLinkedInXBlueskyThreadsFacebook

I had just completed a PowerShell scripted deployment of a SharePoint farm and was just performing the final checks when I noticed the following error in the crawl logs.

“The filtering process has been terminated”

This turned out that because in the PowerShell script I had specified that the SharePoint installation location should be different to the default location.  The SharePoint installation routine had not associated the correct permissions for the WSS_WPG group.

In my instance I had specified that SharePoint should be installed onto a non system disk and I had also specified different directories for indexes and logs.

To fix this I added the WSS_WPG with full control to the following directories.

%:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Applications
c:\Windows\Temp
%:\SharePoint\Index

Once the correct permissions had been applied I ran a full crawl and no longer received this error.

Want more cloud insights? Listen to Cloudy with a Chance of Insights podcast:

Spotify | YouTube | Apple Podcasts

Tags

CrawlErrors
Like this article?

Comments

Loading comments...

Richard Hogan - Global Chief Architect, Microsoft Practice

Richard Hogan

Global Chief Architect, Microsoft Practice | IBM

Global Chief Architect, Microsoft Practice at IBM. 20+ years experience working at the intersection of cloud architecture, security, and emerging AI capabilities across Azure and the wider Microsoft ecosystem. Host of the Cloudy with a Chance of Insights podcast. Regular speaker at tech conferences and active contributor to the Microsoft Tech Community.

LinkedInYouTubeMore About Me

You might also like

SharePoint 2013: PowerShell to update a term sets Submission Policy

The following PowerShell can be used to update a terms sets submission policy to open or closed. #Connect to Central Admin $Session = new-object Microsoft.SharePoint.Taxonomy.TaxonomySession(“Central Admin URL”) #Connect to Managed Metadata Service $Store = $Session.TermStores[“Managed Metadata Service Name”] #Get the group $Group = $Store.Groups[“Group Name”]; #Get the Term Set $TermSet = $Group.TermSets[“Term Set Name”]; #Update… Continue Reading →

SharePoint 2013: Get User Profile Properties via PowerShell

The following script will iterate through all the user profiles and return the account name. Add-PSSnapin microsoft.sharepoint.powershell; #Load SharePoint User Profile assemblies [System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SharePoint”) [System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.Office.Server.UserProfiles”) #Get Context $serviceContext = Get-SPServiceContext -Site “[Site Name]” #Instantiate User Profile Manager $userProfileConfigManager = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager($serviceContext); #Get All User Profiles $profiles = $userProfileConfigManager.GetEnumerator(); #Loop through all user profiles and display account name… Continue Reading →

Error: Specified value is not supported for the domainname parameter.

I came across the below error when trying to create a new web application via PowerShell against a 2013 farm. “Specified value is not supported for the domainname parameter error when creating web apps” This appears to have been caused by the machine loosing connectivity to the domain so even though my server was domain… Continue Reading →

Cloudy with a Chance of Insights

Practical discussions on cloud engineering, architecture, and the reality behind the diagrams.

Reaching for the Cloud

Bi-weekly reflections on cloud architecture, Azure, and the decisions teams wrestle with in practice.

Get the newsletter by email →Follow along on LinkedIn →
← View All Posts