Todd Klindt's SharePoint Admin Blog

Shane and I were preparing some demos for our sessions at TechEd EMEA and we were working with the new Search infrastructure. The changes to Search in SharePoint 2010 are pretty impressive so we were starting from scratch trying things out. One of our first tests was indexing PDFs with Foxit's iFilter. The iFilter installed fine and it makes the necessary Registry changes for SharePoint to use it. I added PDF to the crawled file types and kicked off a full crawl. After the crawl was finished it looked like PDFs were still not being indexed. We double-checked everything and it still wasn't working. After much research and after bothering some folks at Microsoft we found the issue. The Search Service had not been restarted, so it hadn't read the new settings. After running a "net stop osearch14 && net start osearch14" and running a full crawl, our PDF files were indexed correctly. It's been a while since I've installed the Foxit iFilter but my memory is telling me this wasn't necessary before. I'm guessing the Foxit installer bounces the old service name, "osearch", which is why it's not working now, since the service name is "osearch14."

Whether that's what it does or not, if you install an iFilter on SharePoint 2010 and it doesn't appear to work, trying bouncing OSearch14 and running a full crawl. It might work. Or you could reboot the machine, which works too. J

*Note: this was done with pre-release software. That comes with all kinds of craziness. Your mileage may vary*

tk