I have been working with a company who have installed SharePoint 2013 SP1 using AutoSPInstaller.
We have got issues switching PDF and Word parsing off and on.
After 5 months Microsoft have come back saying it is an autospinstaller issue and are closing the call and I quote
“So we request you to go ahead and make a clean windows install and install Sharepoint from binaries and not from auto-installer scripts.”
Regards
Nigel
Comments: ** Comment from web user: brianlala **
To clarify on your original title for this issue, is the issue really with "PDF parsing", or with turning PDF file parsing off?
So Microsoft haven't actually given you any technical details as to why they think AutoSPInstaller is to blame? Sounds like a cop-out...
Besides, with SharePoint 2013 AutoSPInstaller doesn't actually _do_ anything with respect to PDF files anymore, except for adding the PDF MIME type to the web applications (to enable direct opening without having to save the file first). But this has nothing to do with Search.
What happens if you run the commands as follows, by explicitly requesting the first SSA (in case you happen to have more than one), and calling the parameters by name?
$ssa = (Get-SPEnterpriseSearchServiceApplication)[0]
Set-SPEnterpriseSearchFileFormatState -SearchApplication $ssa -Identity pdf -Enable $false
Is your SSA in good health otherwise? Have you installed the PDF iFilter on your own (shouldn't need to in SP2013)?
Brian