Executing the following commmand:Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa -Identity XPS -Enable $FALSEI get the following error message:"The processing of files of type 'xps' is already supported by the parsing system". I think, I found, inside the code, the cause of the problem:Is there a workaround?How can I report to Microsoft developers the issue?I done a report to Microsoft support but they tell me they support "Out of the box" product only. They tell me that I must have a "MSFT Premier contract" to have a support.

Hi @Steve ZhangAfter replacing the dll in the GAC: microsoft.ceres.coreservices.utils.dll ver. 16.0.14326.20450 (Sharepoint SE) with the oldest ver. 16.0.10337.12109 (Sharepoint 2019), the command:Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa -Identity XPS -Enable $FALSEand therefore the command:Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa PDF $TRUE $TRUE started working again.To replace the dll it is necessary to stop at least the following services:- SPCache (SharePoint Caching Service)- SPSearchHostController (SharePoint Search Host Controller)- OSearch16 (SharePoint Server Search 16)- SPTimerV4 (SharePoint Timer Service)You need to close any PowerShell, if already hooked to the search service. The problem appears to be due to the function:public static void CreateAssembly (AssemblyCreatorParameters assemblyInformation, bool dumpCode, bool createPdb, List <string> referencedNameSpaces, params string [] resources) ...which does not take into account the assemblyInformation.AssemblyName.Version parameter, dynamically generating dlls with version 0.0.0.0. Can we trust in a release as soon as possible of a new version of the dll that corrects the problem?

Hi Ignzo,Could you please tell us more about what are you going to achieve by running this PowerShell?SteveSteve

Steve ZhangWhat I was trying to do was install my own PDF IFilter, disabling Microsoft's.The company I work for has developed a PDF IFilter that also do OCRs of the images contained in a PDF, while Microsoft's IFilter does not.This is especially useful when obtaining PDFs from scans. We want to index these documents on Sharepoint SE so that we can search for them.All this works with other versions of Sharepoint.Attempting to set my IFilter with the Set-SPEnterpriseSearchFileFormatState command I got the indicated error.To eliminate any doubt that the error was due to my IFilter, I therefore looked for command execution contexts that had nothing to do with my software.I then came to reproduce the same error with the same command but trying to disable Microsoft's IFiter XLS, which has nothing to do with mine.I believe that command always gives that error whether you try to enable an IFilter or disable it It is very similar to an error reported years ago:https://social.technet.microsoft.com/Forums/ie/en-US/571b3aa7-9620-4b12-a44f-355d3a1cbfca/powershell-command-to-prevent-the-content-of-pdf-files-being-indexed-fails?forum=sharepointsearch If this powershell command makes any changes to the configuration file or in the registy I could work around with some manual changes, but I should know exactly where and what to do.

Any update on this? We're seeing the same behavior in SharePoint Server 2016. It returns the same error whether you're trying to enable/disable a 3rd party iFilter or just trying to disable the built-in PDF parsing filter. For example, the following commands fail:$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "Name of Search Service Application"Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa -Identity PDF -Enable $false -UseIFilter $trueSet-SPEnterpriseSearchFileFormatState -SearchApplication $ssa pdf -Enable $falseIt 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-parserThe 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")

Hi Steven and Ignazio,Thanks for the details. We will look at the problem. Steve

Set-SPEnterpriseSearchFileFormatState disabling built-in IFilter issue on Sharepoint SE

16 Replies

SJHBham
Copper Contributor
Apr 28, 2022
Any update on this? We're seeing the same behavior in SharePoint Server 2016. It returns the same error whether you're trying to enable/disable a 3rd party iFilter or just trying to disable the built-in PDF parsing filter. For example, the following commands fail:

$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")
- Ignzo
  Copper Contributor
  Apr 29, 2022
  SJHBham
  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
  - SJHBham
    Copper Contributor
    May 02, 2022
    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 $false
    
    Is 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.
- Steve Zhang
  Microsoft
  Apr 29, 2022
  Hi Steven and Ignazio,
  
  Thanks for the details. We will look at the problem.
  
  Steve
Steve Zhang
Microsoft
Apr 24, 2022
Hi Ignzo,

Could you please tell us more about what are you going to achieve by running this PowerShell?

Steve
Steve
- Ignzo
  Copper Contributor
  Apr 26, 2022
  Steve Zhang
  What I was trying to do was install my own PDF IFilter, disabling Microsoft's.
  The company I work for has developed a PDF IFilter that also do OCRs of the images contained in a PDF, while Microsoft's IFilter does not.
  This is especially useful when obtaining PDFs from scans.
  
  We want to index these documents on Sharepoint SE so that we can search for them.
  All this works with other versions of Sharepoint.
  
  Attempting to set my IFilter with the Set-SPEnterpriseSearchFileFormatState command I got the indicated error.
  To eliminate any doubt that the error was due to my IFilter, I therefore looked for command execution contexts that had nothing to do with my software.
  I then came to reproduce the same error with the same command but trying to disable Microsoft's IFiter XLS, which has nothing to do with mine.
  I believe that command always gives that error whether you try to enable an IFilter or disable it
  
  It is very similar to an error reported years ago:
  https://social.technet.microsoft.com/Forums/ie/en-US/571b3aa7-9620-4b12-a44f-355d3a1cbfca/powershell-command-to-prevent-the-content-of-pdf-files-being-indexed-fails?forum=sharepointsearch
  
  If this powershell command makes any changes to the configuration file or in the registy I could work around with some manual changes, but I should know exactly where and what to do.

Forum Discussion

Set-SPEnterpriseSearchFileFormatState disabling built-in IFilter issue on Sharepoint SE

16 Replies

Resources