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

Occasional Contributor

Executing the following commmand:

Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa -Identity XPS -Enable $FALSE

I get the following error message:

"The processing of files of type 'xps' is already supported by the parsing system".

2022_04_06_ScreenShot_SetSPEnterpriseSearchFileFormatState _XPS.jpg

 

 

 

 

 

I think, I found, inside the code, the cause of the problem:

2022_04_08_Microsoft_Ceres_HostController_Repository_dll_Stack_Exception_Evi.png

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.

 

 

 

 

 

 

 

 

 

 

 

14 Replies
Hi Ignzo,

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

Steve
Steve

@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...

 

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 $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 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

@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

@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. 

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.

Thanks Ignzo,

We have this bug created and assigned to engineer to take a look at.

Hi @Steve Zhang 

 

I have done clean installation of Sharepoint SE on the following system.

SharePoint

SharePoint Build Number:

Ignzo_0-1652958133643.png

 

Configuration database version: 16.0.14326.20450

 

Windows

Windows Server Version:

Ignzo_1-1652958133645.png

 

 

SQL Server

Version: 15.0.4198.2

 

I have installed and reinstalled Search service application multiple time.

The last time the file Default-manifest.txt isn’t generated, but we continue to have the same errors.

I don’t understand why someone don’t reproduce the issue.

 

The Sharepoint log I have is the following:

 

05/19/2022 01:14:54.29        PowerShell.exe (0x0174)                           0x0B34    SharePoint Foundation                   PowerShell                              6tf0      Medium   

  Entering BeginProcessing Method of Set-SPEnterpriseSearchFileFormatState.     f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:54.29        PowerShell.exe (0x0174)                           0x0B34    SharePoint Foundation                   PowerShell                              6tf0      Medium   

  Leaving BeginProcessing Method of Set-SPEnterpriseSearchFileFormatState.      f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:54.29        PowerShell.exe (0x0174)                           0x0B34    SharePoint Foundation                   PowerShell                              6tf0      Medium   

  Entering ProcessRecord Method of Set-SPEnterpriseSearchFileFormatState.       f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:54.29        PowerShell.exe (0x0174)                           0x0B34    SharePoint Foundation                   Config DB                               a99o1     Medium   

  Cloning object 0a273f54-d944-44c4-9ce2-4bc1d6ebb8eb       f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:54.29        PowerShell.exe (0x0174)                           0x0B34    SharePoint Foundation                   Config Cache                            a0ic2     Medium   

  Refreshed SPPersistedObject with Name AppSearch1, Id 0a273f54-d944-44c4-9ce2-4bc1d6ebb8eb, Parent fec113d5-e9a2-43e2-8102-5bf18a38e2be, Version 40208.

  Last update info: [User: ITCONSULT\spseservice Process:OWSTIMER (2264) Machine:SPSETEST Time:May 18, 2022 07:00:55.0000

  Stack trace (Thread [20] CorrelationId [589a3ea0-dc31-80a7-bc67-fdf0fe288f80]): ]       f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:54.29        PowerShell.exe (0x0174)                           0x0B34    Search                                  Search Platform Services             barqy     High     

  GetValue : object not found for (valueName = ServiceUser ProductKeyName = HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\16.0\Search)          f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:54.33        PowerShell.exe (0x0174)                           0x0B34    Search                                  Search Platform Services             barqy     High     

  GetValue : object not found for (valueName = ServiceUser ProductKeyName = HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\16.0\Search)          f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:54.35        PowerShell.exe (0x0174)                           0x0B34    Search                                  Search Platform Services             barqy     High     

  GetValue : object not found for (valueName = ServiceUser ProductKeyName = HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\16.0\Search)          f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:54.39        PowerShell.exe (0x0174)                           0x0B34    Search                                  Search Platform Services             barqy     High     

  GetValue : object not found for (valueName = ServiceUser ProductKeyName = HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\16.0\Search)          f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:55.12        NodeRunnerAdmin1-0a273f54-d944- (0x2C3C)          0x21CC    Search                                  Search Platform Services             aiyx3     Medium   

  HostControllerClient : Connecting to host controller at address: URI[s=net.tcp,h=spsetest,p=808,r=ceres_hostcontroller_nettcp]  f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:55.15        NodeRunnerAdmin1-0a273f54-d944- (0x2C3C)          0x21CC    Search                                  Search Platform Services             aiyx3     Medium   

  HostControllerClient : Connecting to host controller at address: URI[s=net.tcp,h=spsetest,p=808,r=ceres_hostcontroller_nettcp]  f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:55.21        hostcontrollerservice.exe (0x1038)                0x3288    Search                                  Search HostController                ad5eq     Monitorable        

  RepositoryManager: Module Microsoft.DocParsing, Version=0.0.0.0, Culture=neutral, PublicKeyToken=0fbbedb750799a68 from Microsoft.DocParsing.dll is already installed - threadId: 22         

 

05/19/2022 01:14:55.21        hostcontrollerservice.exe (0x1038)                0x3288    Search                                  Search HostController                ad5eq     Monitorable        

  RepositoryManager: Install of C:\Users\spseservice\AppData\Local\Temp\HostController\Downloads\1603184814\Microsoft.DocParsing.dll failed.

  [Cause: Module Microsoft.DocParsing, Version=0.0.0.0, Culture=neutral, PublicKeyToken=0fbbedb750799a68 from Microsoft.DocParsing.dll is already installed] - threadId: 22      

 

05/19/2022 01:14:55.21        hostcontrollerservice.exe (0x1038)                0x3288    Search                                  Search Platform Services             agw7x     Critical 

  Repository installation failed. File: C:\Users\spseservice\AppData\Local\Temp\HostController\Downloads\1603184814\Microsoft.DocParsing.dll

    Error: Microsoft.Ceres.HostController.Repository.RepositoryException: Module Microsoft.DocParsing, Version=0.0.0.0, Culture=neutral, PublicKeyToken=0fbbedb750799a68

          from Microsoft.DocParsing.dll is already installed

          at Microsoft.Ceres.HostController.Repository.RepositoryManager.Install(String moduleFileName, Boolean validateDependencies)

          at Microsoft.Ceres.HostController.Repository.RepositoryManager.Install(String moduleFileName)      

         

05/19/2022 01:14:55.22        hostcontrollerservice.exe (0x1038)                0x3288    Search                                  Search HostController                ad5eq     Monitorable        

  WcfHostController: Failed to install module Microsoft.DocParsing.dll.

   [Cause: Module Microsoft.DocParsing, Version=0.0.0.0, Culture=neutral, PublicKeyToken=0fbbedb750799a68 from Microsoft.DocParsing.dll is already installed] - threadId: 22

  

05/19/2022 01:14:55.22        NodeRunnerAdmin1-0a273f54-d944- (0x2C3C)          0x21CC    Search                                  Search Platform Services             aiyx4     Medium   

  HostControllerClient : Reconnecting to host controller after exception.

   System.ServiceModel.FaultException: Module Microsoft.DocParsing, Version=0.0.0.0, Culture=neutral, PublicKeyToken=0fbbedb750799a68 from Microsoft.DocParsing.dll is already installed

   Server stack trace:

     at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)

     at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

     at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

     at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

           Exception rethrown at [0]:

           at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

     at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

     at Microsoft.Ceres.CoreServices.HostController.IHostController.InstallModule(RemoteFileInfo request)

     at Microsoft.Ceres.CoreServices.HostController.AbstractHostControllerWrapper.WrapCall[T](Func`1 original)          f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

           

05/19/2022 01:14:55.23        hostcontrollerservice.exe (0x1038)                0x23C8    Search                                  Search HostController                ad5eq     Monitorable        

  RepositoryManager: Install of C:\Users\spseservice\AppData\Local\Temp\HostController\Downloads\645385132\Microsoft.DocParsing.dll failed.

    [Cause: Module contents does not conform to detected module type: System.BadImageFormatException: Could not load file or assembly 'Microsoft.DocParsing.dll' or one of its dependencies.

          An attempt was made to load a program with an incorrect format.

          File name: 'Microsoft.DocParsing.dll'

          ---> System.BadImageFormatException: Could not load file or assembly 'Microsoft.DocParsing.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

          File name: 'Microsoft.DocParsing.dll'

            at System.Reflection.AssemblyName.nGetFileInformation(String s)

            at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)

            at Microsoft.Ceres.HostController.Repository.RepositoryManager.LoadAssemblyModuleInfo(String moduleFileName)    ] - threadId: 24         

 

05/19/2022 01:14:55.23        hostcontrollerservice.exe (0x1038)                0x23C8    Search                                  Search Platform Services             agw7x     Critical 

  Repository installation failed.

  File: C:\Users\spseservice\AppData\Local\Temp\HostController\Downloads\645385132\Microsoft.DocParsing.dll

  Error: Microsoft.Ceres.HostController.Repository.RepositoryException:

    Module contents does not conform to detected module type:

            System.BadImageFormatException: Could not load file or assembly 'Microsoft.DocParsing.dll' or one of its dependencies.

            An attempt was made to load a program with an incorrect format.

            File name: 'Microsoft.DocParsing.dll'

            ---> System.BadImageFormatException: Could not load file or assembly 'Microsoft.DocParsing.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

            File name: 'Microsoft.DocParsing.dll'

              at System.Reflection.AssemblyName.nGetFileInformation(String s)

                   at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)

                   at Microsoft.Ceres.HostController.Repository.RepositoryManager.LoadAssemblyModuleInfo(String moduleFileName)

                   at Microsoft.Ceres.HostController.Repository.RepositoryManager.LoadAssemblyModuleInfo(String moduleFileName)

                   at Microsoft.Ceres.HostController.Repository.RepositoryManager.Install(String moduleFileName, Boolean validateDependencies)

                   at Microsoft.Ceres.HostController.Repository.RepositoryManager.Install(String moduleFileName)      

 

05/19/2022 01:14:55.23        hostcontrollerservice.exe (0x1038)                0x23C8    Search                                  Search HostController                ad5eq     Monitorable        

  WcfHostController: Failed to install module Microsoft.DocParsing.dll.

  [Cause: Module contents does not conform to detected module type: System.BadImageFormatException: Could not load file or assembly 'Microsoft.DocParsing.dll' or one of its dependencies.

  An attempt was made to load a program with an incorrect format.

  File name: 'Microsoft.DocParsing.dll'

  ---> System.BadImageFormatException: Could not load file or assembly 'Microsoft.DocParsing.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

  File name: 'Microsoft.DocParsing.dll'

    at System.Reflection.AssemblyName.nGetFileInformation(String s)

          at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)

          at Microsoft.Ceres.HostController.Repository.RepositoryManager.LoadAssemblyModuleInfo(String moduleFileName)    ] - threadId: 24 

 

05/19/2022 01:14:55.23        NodeRunnerAdmin1-0a273f54-d944- (0x2C3C)          0x21CC    Search                                  Document Parsing                       898f4     Unexpected         

  ParsingAdminService - Failed to save parsing configuration.

  Will reload configuration.

  System.ArgumentException: Exception while communicating with Host Controller at spsetest:

    Module contents does not conform to detected module type: System.BadImageFormatException:

            Could not load file or assembly 'Microsoft.DocParsing.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

            File name: 'Microsoft.DocParsing.dll'

            ---> System.BadImageFormatException: Could not load file or assembly 'Microsoft.DocParsing.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

            File name: 'Microsoft.DocParsing.dll'

              at System.Reflection.AssemblyName.nGetFileInformation(String s)

                   at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)

                   at Microsoft.Ceres.HostController.Repository.RepositoryManager.LoadAssemblyModuleInfo(String moduleFileName)

                   at Microsoft.Ceres.CoreServices.HostController.AbstractHostControllerWrapper.HandleException(Exception e)

                   at Microsoft.Ceres.CoreServices.HostController.AbstractHostControllerWrapper.WrapCall[T](Func`1 original)

                   at Microsoft.Ceres.ContentEngine.Parsing.Component.ParsingAdminService.CreateConfigurationPackage(String keyFile)

                   at Microsoft.Ceres.ContentEngine.Parsing.Component.ParsingAdminService.Save()   f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:55.25        NodeRunnerAdmin1-0a273f54-d944- (0x2C3C)          0x21CC    Search                                  Document Parsing                       898f7     High     

  ParsingAdminService - Loading format registry. View '16.0.0.0'. Format registry package '16.0.0.0'.         f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:55.33        NodeRunnerAdmin1-0a273f54-d944- (0x2C3C)          0x21CC    Search                                  Document Parsing                       ajp9a     Unexpected         

  ParsingManagementAgent - Failed to disable parsing of format xps.

  System.ArgumentException: Exception while communicating with Host Controller at spsetest: Module contents does not conform to detected module type:

    System.BadImageFormatException: Could not load file or assembly 'Microsoft.DocParsing.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

          File name: 'Microsoft.DocParsing.dll'

          ---> System.BadImageFormatException: Could not load file or assembly 'Microsoft.DocParsing.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

          File name: 'Microsoft.DocParsing.dll'

            at System.Reflection.AssemblyName.nGetFileInformation(String s)

            at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)

            at Microsoft.Ceres.HostController.Repository.RepositoryManager.LoadAssemblyModuleInfo(String moduleFileName)

            at Microsoft.Ceres.CoreServices.HostController.AbstractHostControllerWrapper.HandleException(Exception e)

            at Microsoft.Ceres.CoreServices.HostController.AbstractHostControllerWrapper.WrapCall[T](Func`1 original)

            at Microsoft.Ceres.ContentEngine.Parsing.Component.ParsingAdminService.CreateConfigurationPackage(String keyFile)

            at Microsoft.Ceres.ContentEngine.Parsing.Component.ParsingAdminService.Save()

            at Microsoft.Ceres.ContentEngine.Parsing.Component.ParsingAdminService.EnableParsing(String formatId, Boolean enable)

            at Microsoft.Ceres.ContentEngine.Parsing.Component.ParsingManagementAgent.EnableParsing(String formatId, Boolean enable)          f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:55.33        NodeRunnerAdmin1-0a273f54-d944- (0x2C3C)          0x21CC    Search                                  Search Platform Services             ak8y1     Medium   

  Exception in remote service invocation (service=Admin92, method=http://schemas.microsoft.com/ceres/Parsing/2011/08/agents/IParsingManagementAgent/EnableParsing, user=ITCONSULT\nlbadmin):

    System.ArgumentException: Exception while communicating with Host Controller at spsetest:

            Module contents does not conform to detected module type:

              System.BadImageFormatException: Could not load file or assembly 'Microsoft.DocParsing.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

                   File name: 'Microsoft.DocParsing.dll'

                   ---> System.BadImageFormatException: Could not load file or assembly 'Microsoft.DocParsing.dll' or one of its dependencies.

                   An attempt was made to load a program with an incorrect format.

                   File name: 'Microsoft.DocParsing.dll'

                     at System.Reflection.AssemblyName.nGetFileInformation(String s)

                     at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)

                     at Microsoft.Ceres.HostController.Repository.RepositoryManager.LoadAssemblyModuleInfo(String moduleFileName)

                     at Microsoft.Ceres.CoreServices.HostController.AbstractHostControllerWrapper.HandleException(Exception e)

                     at Microsoft.Ceres.CoreServices.HostController.AbstractHostControllerWrapper.WrapCall[T](Func`1 original)

                     at Microsoft.Ceres.ContentEngine.Parsing.Component.ParsingAdminService.CreateConfigurationPackage(String keyFile)

                     at Microsoft.Ceres.ContentEngine.Parsing.Component.ParsingAdminService.Save()

                     at Microsoft.Ceres.ContentEngine.Parsing.Component.ParsingAdminService.EnableParsing(String formatId, Boolean enable)

                     at Microsoft.Ceres.ContentEngine.Parsing.Component.ParsingManagementAgent.EnableParsing(String formatId, Boolean enable)

                     at SyncInvokeEnableParsing(Object , Object[] , Object[] )

                     at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

                     at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

                     at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

                     at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)

                     at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)    

 

05/19/2022 01:14:55.34        PowerShell.exe (0x0174)                           0x0B34    SharePoint Foundation                   PowerShell                              6tf2      High     

  System.InvalidOperationException: The processing of files of type 'xps' is already supported by the parsing system.

  at Microsoft.Office.Server.Search.Administration.DocumentParserAdmin.EnableParsing(String formatId, Boolean enable)

  at Microsoft.Office.Server.Search.Cmdlet.SetDocumentParserFileFormatState.UpdateDataObject()

  at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord()         f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:55.34        PowerShell.exe (0x0174)                           0x0B34    SharePoint Foundation                   PowerShell                              91ux      High     

  Error Category: InvalidData    Target Object  Microsoft.Office.Server.Search.Cmdlet.SetDocumentParserFileFormatState  Details  NULL  RecommendedAction NULL        f2d83ea0-3c55-80a7-bc67-f07ffc36cf53

 

05/19/2022 01:14:55.39        PowerShell.exe (0x0174)                           0x0B34    SharePoint Foundation                   PowerShell                              6tf0      Medium   

  Leaving ProcessRecord Method of Set-SPEnterpriseSearchFileFormatState.        6d63e9fe-692f-0000-c0ba-846d2f69d801

 

05/19/2022 01:14:55.39        PowerShell.exe (0x0174)                           0x0B34    SharePoint Foundation                   PowerShell                              6tf0      Medium   

  Entering EndProcessing Method of Set-SPEnterpriseSearchFileFormatState.       6d63e9fe-692f-0000-c0ba-846d2f69d801

 

05/19/2022 01:14:55.39        PowerShell.exe (0x0174)                           0x0B34    SharePoint Foundation                   PowerShell                              6tf0      Medium   

  Leaving EndProcessing Method of Set-SPEnterpriseSearchFileFormatState.        6d63e9fe-692f-0000-c0ba-846d2f69d801

 

 

I add the registry key “ServiceUser”. The relative warning has disappeared, but the logs remain basically the same.

 

 

Hi @Steve Zhang

After 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 $FALSE

and 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?

Thank you for doing more testing. We are actively looking at problem and investigate what's going wrong. Hopefully we will get it solved soon.
We've found the root cause. Now we are in the progress of fixing.