Forum Discussion
Set-SPEnterpriseSearchFileFormatState disabling built-in IFilter issue on Sharepoint SE
$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "Name of Search Service Application"
Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa -Identity PDF -Enable $false -UseIFilter $true
Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa pdf -Enable $false
It seems SharePoint 2013 had KB2883000 released to address an issue with enabling iFilters. But we're not seeing anything similar mentioned about a 2016 or SE hotfix.
The official MS docs say this should be possible in SharePoint 2016. Perhaps it's a similar issue affecting SharePoint SE:
https://docs.microsoft.com/en-us/sharepoint/troubleshoot/lists-and-libraries/ifilter-alternative-to-the-native-pdf-parser
The reason we're trying to get this to work is we want to enable Adobe's PDF ifilter 11 to see if it will resolve some issues we're having with the SharePoint built-in PDF parser successfully parsing certain types of PDFs. The error we get is:
"This item was partially parsed. ( Error parsing document ssic://50184. Document was partially processed. The parser was not able to parse the entire document")
My system administrator tell me we have installed our IFilter by our customers without any problems with Sharepoint 2016/2019 environments.
I think the problem is related to the file ...\Office Server\Applications\Search\Repository\Default-manifest.txt.
In Sharepoint 2019 environment where I can execute successfully the following command:
Add-PSSnapin Microsoft.SharePoint.PowerShell
$ssa = Get-SPEnterpriseSearchServiceApplication
Get-SPEnterpriseSearchFileFormat -SearchApplication $ssa -Identity XPS
Identity : xps
Name : Microsoft XML Paper Specification
MimeType : application/vnd.ms-xpsdocument
Extension : .xps
BuiltIn : True
Enabled : True
UseIFilter : True
Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa -Identity XPS -Enable $FALSE
Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa -Identity XPS -Enable $TRUE
The file Default-manifest.txt contains rows as the same:
E:\SharePoint\Office Server\Applications\Search\Repository\Journal\33fdd438-c057-4391-b20a-57f203c05d88\Microsoft.DocParsing.dll
Microsoft.DocParsing, Version=16.0.0.1, Culture=neutral, PublicKeyToken=0fbbedb750799a68
On Sharepoint SE it contains:
E:\SharePointData\Index\Office Server\Applications\Search\Repository\Journal\e9ac9b13-f7e2-48c3-99b1-9fc8c8a8dcc4\Microsoft.DocParsing.dll
Microsoft.DocParsing, Version=0.0.0.0, Culture=neutral, PublicKeyToken=0fbbedb750799a68
E:\SharePointData\Index\Office Server\Applications\Search\Repository\Journal\ec0d23eb-7e8b-4d88-a2a3-e83c8cad9678\Microsoft.UserDictionaries.EntityExtraction.Companies.Inclusions.dll
Microsoft.UserDictionaries.EntityExtraction.Companies.Inclusions, Version=15.0.8082.15928, Culture=neutral, PublicKeyToken=0fbbedb750799a68
The version numbers give me a lot of doubts.
Ignazio
Ignzo - not sure what to do if we can't even run the following successfully:
$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "Search Service Application" Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa -Identity PDF -Enable $falseIs there a way to "repair" the search service without rebuilding the whole search service application and its configuration?
Our default-manifest.txt doesn't have any references to parsing DLLs. All of our entries reference *dictionary/dictionaries*.dll is some fashion or other.
Hi SJHBham Steve Zhang,
When I contacted Microsoft support, they told me they have reproduced the problem.
I would like to know if anyone on Sharepoint SE can execute this commands without errors.
This is to understand if the problem always occurs or only with some customization of the installation.
Steve ZhangMicrosoft
Thanks Ignzo,
We have this bug created and assigned to engineer to take a look at.