DocParser error in SharePoint 2013 Search RRS feed

  • Question

  • I am using SharePoint Server 2013 (February 2015 CU installed) to index a couple of document libraries on the local SharePoint server.

    For some small Word documents (docx, less then 400 kB, less than 30.000 words and less than 2.000.000 characters) I get the following error message:

    This item was partially parsed. The item has been truncated in the index because it exceeds the maximum size. ( Document 'http://demo2/....docx' was partially processed. The parser was not able to parse the entire document.; ; SearchID = 178285BA-3D51-4054-8C4F-6FBA54D078A2 )

    Digging in the ULS log I found this entry:

    DocParser - A parsing failure caused the partial processing of the document. The original error code was 309003 and the error message was...

    The only thing that these documents have in common is that they have embedded contents such as pictures or small text files.

    The logs (ULS, set to verbose for everything) give me absolutely no clue why the document was truncated. I could not find any reference to the error code. How can I find out what the issue with these documents is?

    Saturday, March 14, 2015 2:01 PM


  • Hi Bernd,

    Firstly, I recommend to increase the value of MaxCharactersInPropertyStoreForRetrieval for body managed property with PowerShell command below:

    $prop = Get-SPEnterpriseSearchMetadataManagedProperty -Identity body -SearchApplication (Get-SPEnterpriseSearchServiceApplication)
    $prop.MaxCharactersInPropertyStoreForRetrieval = “2097152”

    Secondly, to narrow down the issue scope, I recommend to test the things below:

    1. Copy the files with issue without the embedded objects and upload them to SharePoint, and then check if the files can be searched.
    2. Create new files which will only contain the embedded objects and upload them to SharePoint, and then check if the files can be searched.

    More reference:

    Best regards.


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact

    Monday, March 16, 2015 8:34 AM