We have been setting up SharePoint 2013 Search and crawling SharePoint 2010 content sources (SP2010 web apps in another farm). We have done the configuration and setup and are able to do a crawl of SP2010 content sources. However, the crawl logs shows many errors and warnings, and we found that only 30% of the overall data was crawled. One of the major issues in the logs that we are targeting to resolve is as under:

Crawler:Content Plugin High CSSFeedersManager::session_CallbackReceived: Document processing returned a warning. Error messages: Error parsing document 'http://sp2010webapp/sites/Document Library/3.pptx'. There is no format handler able to parse documents of the format 'encoffmetro'.

The above error is shown for a .pptx however the same error occurs for other file formats (xlsx, docx, etc) too.

I have no idea what is encoffmetro and trying to search for the same came across the following post.

https://social.technet.microsoft.com/Forums/office/en-US/0b525aad-50d5-47f4-a38e-646754aa0ee6/unable-to-disable-ifilter?forum=sharepointsearch

As mentioned, I checked the UseIFilter setting for the various file types and found that it was set to true for almost all the file types. I am not sure how this was set to true as the default value should have been false as per MSDN, while we did not modify this setting earlier. Also, we do not have any third party Ifilters installed.

So, as suggested in the post tried updating the UseIFilter = False for errored file types, did a Search Host Service restart, index reset and did a full crawl. However, it still resulted in the same exact errors. While checking the setting for UseIFilter for the changed file types we noticed that it still shows UseIFilter = True.

The setting for UseIFilter is not getting applied while we are not sure if this resolve our issue.

Anyone faced similar issues? Thanks in advance.

• Edited by Devendra Singh Tuesday, August 18, 2015 8:26 AM

Hi Wendy,

I have checked the files in error, those are not password protected while these same files were crawled in SP2010 search.

However, one thing I noticed is that some of the documents are part of information right management (IRM) but not all of them. There are some which are not but still have the same error.

Anyway, have checked the IRM settings in SP2010 and the same was already in place for SP2013 as well i.e. "Use the default RMS server specified in Active Directory" in Central Admin -> Information Rights Management

While also the SP2010 farm and SP2013 farm use the same active directory.

Regards,

DEven

• Edited by Devendra Singh 23 hours 37 minutes ago

Hi Wendy,

I have checked the files in error, those are not password protected while these same files were crawled in SP2010 search.

However, one thing I noticed is that some of the documents are part of information right management (IRM) but not all of them. There are some which are not but still have the same error.

Anyway, have checked the IRM settings in SP2010 and the same was already in place for SP2013 as well i.e. "Use the default RMS server specified in Active Directory" in Central Admin -> Information Rights Management

While also the SP2010 farm and SP2013 farm use the same active directory.

Regards,

DEven

• Edited by Devendra Singh Wednesday, August 19, 2015 8:02 AM

Hi,

We are currently looking into this issue and will give you an update as soon as possible.
 
Thank you for your understanding and support.

Best Regards,

Wendy

Hi Devendra,

Please try to re-save the problematic file with newer Office version, and try to crawl again, and see if this document can be crawled or not.

Best Regards,

Wendy

Hi Wendy,

Do you mean to use Office 2013?

Office 2013 is not yet installed and used in our client organization. So cannot get Office 2013 installed as this will require an enterprise wide rollout. While even if I get some documents crawled by managing to install Office 2013 just for me, we would not have solved the problem. As users will still be using Office 2010 and keep adding new documents to the different libraries with Office 2010.

Regards,

Deven

Hi Deven,

What CU did you install for SharePoint 2013?

Please try to install the latest CU for SharePoint 2013, then test again, compare the result.

Best Regards,

Wendy

Hi Wendy,

I have checked the CUs and the following are installed currently on the server.

• Update for Microsoft SharePoint Enterprise Server 2013 (KB2965266) 64-Bit Edition  - version 15.0.4711.1000 Installed
• Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552) 64-Bit Edition - version 15.0.4571.1502 Installed

The above installed CU KB2965266 was made available as part of CU for April 2015.

Do you feel any other or any specific CU that needs to be installed?

Regards,

DEven

Hi Deven,

You can try to install August CU 2015. After installing, test again, compare the result.

http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=346

Best Regards,

Wendy