Event details
Having errors while installing a custom PDF IFilter, I investigated and traced the problem to a simpler one, the following:
Running the following powershell command fails on Sharepoint SE:
Set-SPEnterpriseSearchFileFormatState -SearchApplication $ ssa -Identity XPS -Enable $ FALSE
I get the following error:
Set-SPEnterpriseSearchFileFormatState : The processing of files of type 'xps' is already supported by the parsing system.
With VisualStudio I found that:
I believe the problem is related to the contents of the Default-manifest.txt file which on Sharepoint 2019, where everything works correctly, contains the following text:
...
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
...
While 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 versions shown seem to me to be incorrect.
I would like guidance on how to fix this.
If the solution to the problem is not simple, I would like to have some information that could allow me to continue with my investigations such as:
1) How can I regenerate it;
2) Which executable / dll creates this file;
3) At what moment it is created;
4) How and where the information that is inserted in the file is retrieved;
5) How can I officially report this issue to Microsoft. I done a report to Microsoft support but they tell me they support "Out of the box" product only.
I have already submitted the question to the community but to date we have not found any solution, indeed it seems that it is not always reproduced.
On the internet I saw that this problem has also manifested itself in the past with Sharepoint 2013.
Thanks in advance
- Steve ZhangMay 10, 2022
Microsoft
Hi Ignazio, Thank you for emphasizing this issue to us. Our engineer is actively looking at this issue now. We will get back to you when we have some update on it. Steve