none
64bit PDF iFilter on Windows 2008 Server with MOSS

    Question

  • We have MOSS 2007 on Windows 2008 server (64bit). Trying to get 64bit PDF iFilter from FoxIT Software working.

    Installed the PDF iFilter and are able to search the PDF documents but we see the following errors in our windows application logs. It is not just one entry, there are series of these entries from the time the indexer start till it is completed. And it continues whenever the indexer is run.

    Faulting application mssdmn.exe, version 12.0.6211.1000, time stamp 0x46cd5391, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791adec, exception code 0xc0000374, fault offset 0x00000000000a6e97, process id 0x1758, application start time 0x01c8edd3f5811ce6.

    If we remove/uninstall your PDF filter and re-index there are no errors. This leads us to believe that there is an issue with the 64bit PDF ifilter from FoxIT on Windows 2008 Server.

    Has anybody successfully installed and gotten t the 64bit PDF iFilter (FoxIT) working on Windows 2008 Server with MOSS without any issues? Any suggestion/ideas on the above error?

    Thanks for the help!


    http://www.agilesense.com
    Thursday, July 31, 2008 6:41 PM

All replies

  • Do you know what version of the Foxit iFilter you have?  Here's some more info:

    http://www.foxitsoft.com/bbs/showthread.php?s=e2224d4aebdbb7d014d424035b51ab27&t=7736


    John
    SharePoint911: SharePoint Consulting
    http://www.rossonmoss.com
    • Edited by John D. Ross Friday, August 01, 2008 1:03 PM updated signature
    Friday, August 01, 2008 1:01 PM
  • I have the latest version from FoxIT.... I contacted the FoxIT team and waiting to hear back from them.

    In the meantime, if anybody has any information on this, please give your inputs...

    Thanks!


    http://www.agilesense.com
    Friday, August 01, 2008 8:20 PM
  • I have one difference from your environment, Windows 2003 instead of 2008, and all works fine.
     
    If you've followed all instructions accurately, then I suggest you focus on "Windows 2008" side of operations regarding this, do FoxIt supports running on Windows 2008? I don't see any information regarding the OS versions on "FoxIt - pdf Ifilter" page. This should be a question directed to FoxIt software support!


    V Jonian
    • Proposed as answer by v jonian Tuesday, August 12, 2008 11:17 PM
    • Unproposed as answer by Mike Walsh FIN Friday, January 30, 2009 5:32 PM
    Friday, August 01, 2008 9:49 PM
  • Having the same problem here - 64bit FoxIT iFilter on Windows Server 2008 Enterprise running WSS 3.0/Project Server 2007 (all WSS, MOSS service packs applied including the Infrastructure Update). Did you ever get anything back from Fox regarding this?
    Tuesday, August 12, 2008 4:19 AM
  • Glenn,

    I submitted the errors to FoxIT and they responded saying that they are not able to replicate the error and will get back to me as soon as they have something on it.

    Any luck on your end?

    -WD

    http://www.agilesense.com
    Wednesday, September 03, 2008 5:40 PM
  • It appears I might have been a bit precipitate in thinking it was the FoxIT ifilter. After removing it, I found that errors were still being generated in the event log to do with the search crawl service. There was one other possible candidate for generating these errors - I had installed the Microsoft Office Filter Pack at the same time as the FoxIT pdf filter, but had ruled it out in my mind initially as the source of these errors because I had run the 32 bit version on another server for many months and it had performed flawlessly.

    I found that this was indeed the source of the errors when I did some deeper investigation using procmon to try and get to the root cause (the eventlog messages were completely devoid of any useful detail which was extremely un-helpful). I watched the indexing process on the server as it ran and collected the errors.

    The errors are actually being generated by the ifilter for .VSD files, which was included as part of the 64bit version of the Microsoft Office Filter Pack. I Googled the error with my new information included and found that a few other users were experiencing similar issues and posted about it on another thread here: http://forums.technet.microsoft.com/en-US/sharepointsearch/thread/ec655524-131d-4117-8155-8848efc2dc9f/. Here is another (unresolved) post by a different user about the same issue: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3006674&SiteID=17

    I did re-install the FoxIT PDf iFilter and kick of another full crawl while investigating the errors. It indexed PDF files without a problem (NONE or the errors in the event log were generated by the FoxIT ifilter). Sorry FoxIT - no bad press here. Still no resolution to the other error though.
    • Edited by Glenn Laugesen Wednesday, September 03, 2008 9:52 PM More grammar errors. I must learn to proof read more thoroughly!
    Wednesday, September 03, 2008 9:47 PM
  • I am having the same issue and I am running Windows 2003.    We had a user complain that pdf's were not being searched.     After SP1 we reinstalled Foxit iFilter but for some reason it didn't index them.    After I reinstalled on August 28 and got it to work we started seeing the exact errors.     I am going to uninstall if I don't hear bach from Foxit.   Sometimes the crawl is successful and others there are tons of popups and then when I look in the log it shows over 2000 errors in the log.   Once I recrawl they seem to go away.
    EmilyBen
    Friday, September 12, 2008 2:44 PM
  • We have identified a bug in the Visio IFilter on x64 systems that causes memory corruption. In the case I worked the problem was often reflected in the Fox-it PDF IFilter even though at this time I have no evidence they were contributing the to the corruption and they appear to simply be a victim.

    A hotfix is currently scheduled to be released in December 2008. In the interim the only workaround is to disable the IFilter. This will not cause you to lose existing the existing Visio content / properties in your index but it will cause you to only get basic info on files that get re-crawled via an incremental and of course any new files won't have full Visio content either.
    Tuesday, November 11, 2008 7:10 PM
  • Thanks for that reply Steve, this confirms my and others findings. Interesting that the memory corruption appears to have affected the FoxIT PDF iFilter as well - explains the red herrings that casue a few users (including me initially) to blame it for the errors. Are the errors specific to .VSD files generated by Visio 2000 and older? I ask this because of a post that I came across, by another user who narrowed the errors down even further to specific files generated by older versions of visio. I can't back this up myself however as I haven't tried to replicate the problem.

    Good to see a hotfix will be made available. I'd be keen to know as soon as it is out as I have clients who I host for who use Visio extensively on their SharePoint site.
    Tuesday, November 11, 2008 8:44 PM
  • Has this fix been release yet?  We are experiencing it on a new 64-bit Index server we have just installed.
    Thursday, December 04, 2008 7:21 PM
  • Steve,

    Any movement on this issue? We are seeing it on x64 2008 servers.

    Matt


    Matthew McDermott, MVP MOSS
    Friday, January 30, 2009 4:57 PM
  • We are in the process of installing Adobe pdf ifilter.    They just released a 64bit version.
    EmilyBen
    Tuesday, February 24, 2009 3:28 PM
  • As you are testing the Adobe product you may want to consider performance...

    http://blogs.msdn.com/opal/archive/2008/12/10/pdf-ifilter-battle-foxit-vs-adobe-64bit-version.aspx

    Matthew
    Matthew McDermott, MVP MOSS
    Tuesday, February 24, 2009 8:29 PM
  • We are just in the process of installing it.   This is a great post. Thanks for sharing.   But does the iFilter work.    We had to uninstall it because it was causing so many issues.
    EmilyBen
    Wednesday, February 25, 2009 2:45 PM
  • Which iFilter? Adobe or Foxit? Both work just fine, though my preference is for Foxit as the performance, support and multithreading are superior to Adobe. It also concerns me that Adobe is so late producing this much needed addition. I don't think it is a priority for them. My $0.02.

    Bear in mind that the issue that started this thread has nothing to do with the PDF iFilter, it is a flaw in the Microsoft Visio IFilter.

    Matthew
    Matthew McDermott, MVP MOSS
    Wednesday, February 25, 2009 5:40 PM
  •  I haven't be able to get the 64bit PDF iFilter
     to work on my Windows 2003 SP2 for almost week now.
    I have tried almost all i could read.
    Can someone just tell me does it need WDS installed
    Thursday, March 26, 2009 2:45 AM
  • Patrick,

    We need more detail. Is MOSS filtering other document types? Are you attempting the Foxit or Adobe iFilter?

    You do NOT need WDS, I have seen cases where it causes problems.

    For MOSS to work with the Foxit iFilter you just need to walk through the Foxit installation. If it still does not work. You should confirm:
    1. You added PDF as a crawled type.
    2. You have the right registry setting for the Foxit filter (this setting gets corrupted with one of the SharePoint service packs) There is a KB article, but the easiest thing is to just reinstall.
    3. If all else fails install the IFilter Explorer and ensure that the server is registering the DLL correctly.

    HTH,

    Matthew


    Matthew McDermott, MVP MOSS
    Thursday, March 26, 2009 12:37 PM
  • Thanks Matthew for the reply.
    We need more detail. Is MOSS filtering other document types? Are you attempting the Foxit or Adobe iFilter?
    I'm on WSS v3 and yes i can filter other document types.I'm attempting Adobe Filter v9.1


    You do NOT need WDS, I have seen cases where it causes problems.
    I have removed it.its all confusing with resources not enough :(

    For MOSS to work with the Foxit iFilter you just need to walk through the Foxit installation. If it still does not work. You should confirm:
    1. You added PDF as a crawled type.
    2. You have the right registry setting for the Foxit filter (this setting gets corrupted with one of the SharePoint service packs) There is a KB article, but the easiest thing is to just reinstall.
    3. If all else fails install the IFilter Explorer and ensure that the server is registering the DLL correctly.
      I have tried using the Ifilter Explorer and i can see the pdffilter registered but it ALSO SHOWS INVALID
    HTH,

    I hope you can help
    Patrick

    Friday, March 27, 2009 1:19 AM
  • Not sure if this will help, but this is the install methodology I've been using.  It can probably be adapted to 64bit just fine:

    http://msmvps.com/blogs/sundar_narasiman/archive/2008/02/06/configuring-moss-2007-to-search-pdf-documents-install-and-configure-pdf-ifilters.aspx

    It goes into a little bit more detail with respect to some things that don't get updated.
    John
    SharePoint911: SharePoint Consulting
    Blog: http://www.rossonmoss.com
    Twitter: JohnRossJr

    MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007
    Friday, March 27, 2009 12:22 PM
  • Patrick,

    If IFilter Explorere is reporting Invalid I would uninstall the Filter and try to reinstall it. I have never used the 64bit version of Adobe because the Foxit version is so superior. Maybe someone else has info for the Adobe installation.

    Matthew
    Matthew McDermott, MVP MOSS
    Friday, March 27, 2009 12:36 PM
  • To reiterate what Matthew said -- I've had several clients try the Adobe 64 bit iFilter and never had a single one get it to work.  This was several months back and I understand they have recently released a new version, so you might want to make sure you have the latest bits.  However, at one point there were a number of comments on the page annoucing the 64bit version on Adobe's own site of people saying they couldn't get it working.

    I agree with Matthew 100% -- I recommend the FoxIt iFilter over the Adobe one.  Better installation and far better performance.
    John
    SharePoint911: SharePoint Consulting
    Blog: http://www.rossonmoss.com
    Twitter: JohnRossJr

    MOSS Explained: An Information Workers Deep Dive into Microsoft Office SharePoint Server 2007
    Friday, March 27, 2009 12:52 PM
  • We have identified a bug in the Visio IFilter on x64 systems that causes memory corruption. In the case I worked the problem was often reflected in the Fox-it PDF IFilter even though at this time I have no evidence they were contributing the to the corruption and they appear to simply be a victim.

    A hotfix is currently scheduled to be released in December 2008. In the interim the only workaround is to disable the IFilter. This will not cause you to lose existing the existing Visio content / properties in your index but it will cause you to only get basic info on files that get re-crawled via an incremental and of course any new files won't have full Visio content either.
    The Visio iFilter for x64 is in this fix.  http://support.microsoft.com/kb/960502

    Forget Adobe.  After trying it for quite a while we got FoxIT and are very happy with it. 

    Thursday, April 09, 2009 6:40 PM
  • The default adobe 9 ifilter is available for x64, and the best part is thats its free.,

    http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025

      

    The following files priovide support

    http://www.adobe.com/special/acrobat/configuring_pdf_ifilter_for_ms_sharepoint_2007.pdf

    http://support.microsoft.com/?id=555209

    http://blogs.msdn.com/ifilter/archive/2007/03/29/indexing-pdf-documents-with-adobe-reader-v-8-and-moss-2007.aspx

     

    Dont forget to start a full crawl after you have completed the installation........

     

    Cheers,

     

    Ivan Sanders

    SharePoint Architect

    Dimension Solutions, Inc.

    http://dimension-si.com/blog

    http://linkedin.com/in/iasanders

    http://twitter.com/iasanders

    http://delicious.com/iasanders

     


    Ivan Sanders http://linkedin.com/in/iasanders http://dimension-si.com/blog
    • Proposed as answer by Ivan Sanders Sunday, May 03, 2009 8:34 AM
    • Unproposed as answer by Mike Walsh FIN Monday, May 04, 2009 10:32 AM
    Saturday, April 18, 2009 10:40 PM