Hello! I'am experiencing some troubles with Search Service at my Sharepoint 2013 Enterprise Farm.

When i've started troubleshooting, i suddenly found a lot of warnings and errors in parsing component, such as:
Error parsing document 'https://<filename>.xlsx'. There is no format handler able to parse documents of the format 'encoffmetro'.

I have no idea what is encoffmetro, and firstly checked my parsing options with Get-SPEnterpriseSearchFileFormat -SearchApplication $ssa
And I found that almost all of my crawled file types have UseIFilter option enabled. Though i've never set this manually and never install third party Ifilters! 
Get-SPEnterpriseSearchFileFormat -SearchApplication $ssa | ? {$_.UseIFilter -eq $True} returns me a lot of results, almost all of my file types.
According to https://technet.microsoft.com/en-us/library/jj730455.aspx, UseIFilter are False by default. But I have "True", though i don't have any third-party Ifilters installed!

But what is real trouble, I can't disable this IFilter and return to built-in Ifilter!
I've tried to use: Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa xlsx -Enable:$True -UseIFilter:$False (or shortly: Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa xlsx $True $False)
That gives me a reminder to restart Search Host Controller Service. But when i use Get-SPEnterpriseSearchFileFormat anew, got UseIFilter=True again. Even after restarting service.

How can change this? Or how can i reset all file types options to Sharepoint defaults?

SharePoint includes iFilters for the Office 2007 file formats (xlsx, docx, pptx, etc).

Third party iFilters would be things like PDF.

so you shouldn't need to disable iFilters for xlsx

"According to https://technet.microsoft.com/en-us/library/jj730455.aspx" to parse the specified file format with a third-party iFilter, set UseIFilter to $TRUE.

UseIFilter = True = Third-party ifilter enabled

UseIFilter = False = Third-party ifilter disabled, native ifilter used

, right?

And i want to know, why now i have enabled third-party ifilter, i don't have them installed.

P.S. Why pdf needs third-party, since 2013 sharepoint has native parser, isn't?

• Edited by Lehus 27 minutes ago

"According to https://technet.microsoft.com/en-us/library/jj730455.aspx" to parse the specified file format with a third-party iFilter, set UseIFilter to $TRUE.

UseIFilter = True = Third-party ifilter enabled

UseIFilter = False = Third-party ifilter disabled, native ifilter used

, right?

And i want to know, why now i have enabled third-party ifilter, i don't have them installed.

P.S. Why pdf needs third-party, since 2013 sharepoint has native parser, isn't?

• Edited by Lehus Wednesday, March 25, 2015 7:06 AM

"According to https://technet.microsoft.com/en-us/library/jj730455.aspx" to parse the specified file format with a third-party iFilter, set UseIFilter to $TRUE.

UseIFilter = True = Third-party ifilter enabled

UseIFilter = False = Third-party ifilter disabled, native ifilter used

, right?

And i want to know, why now i have enabled third-party ifilter, i don't have them installed.

P.S. Why pdf needs third-party, since 2013 sharepoint has native parser, isn't?

• Edited by Lehus Wednesday, March 25, 2015 7:06 AM

PDF was just my go-to reference... yes, it's been fixed in 2013.

admittedly, it does seem that your error sorta matches what that link suggests will happen if no third party iFilter is found ("If you dont install the third-party iFilter, the content processing component cant parse the file format. Failure to parse a file format is logged in the crawl log")

Yep, i have a lot of parse errors in my crawl log. And i just want to revert my parsing settings to defaults, i.e to use only built-in filters.

But when i manually setting UseIFilter parameter to False via powershell, nothing changes and search app as usual tries to load third-party filter.

Hi Lehus,

After you run the PowerShell command, whether you try to reset Index, then do a full crawl. If not, please do it and compare the result.

In addition, you said there are a lot of parse errors in your crawl log, please provide morw detailed information about these errors to troubleshoot this issue.

Best Regards,

Wendy