Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals > Forums Home > Microsoft Enterprise Search Forums > SharePoint - Search (pre-SharePoint 2010) > Filtering Process Terminated for crawling VSD files

Answered Filtering Process Terminated for crawling VSD files

    •  
      Wednesday, May 14, 2008 4:18 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I am having issues crawling .VSD files in a 64 bit MOSS environment.  I set up crawling VSD’s with the Microsoft Filter Pack on a 32 bit indexer and everything works perfectly.  When I set it up on our 64 bit indexer (different environment) I get the following error on the majority of VSD’s, but not all.

       

      The filtering process has been terminated

       

      This is happening in both my Test 64 bit environment and Pre-production environment, so it seems to be consistent on the 64 bit side. 

       

      Any ideas out there?

       

    Answers

    • Wednesday, December 31, 2008 2:50 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      Microsoft has released a hotfix for the 64 bit issue when crawling .VSD's.  We submitted this as a bug and worked with them on getting it fixed.  Although the hotfix says it is an x86 package, this is for both 64 bit and 32 bit.

      http://support.microsoft.com/kb/960502

      • Marked As Answer by mcwoods Wednesday, December 31, 2008 2:51 PM
      •  
       

    All Replies

    • Tuesday, August 05, 2008 5:51 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      I encountered the same problem. The environment is Windows 2008 X64 with 64bit Office SharePoint Server 2007 installed. I picked up the files failed to create indexes and created a new contents source via file share. The issue was reproduced against the new content source.

      What I did is trying several times to perform incremental crawl, the surprising thing is after 2-3 times all files can be indexed successfully. I believe this is a bug of MOSS 2007. Mostly importantly, even I can use the workaround the error does impact the crawling performance - the full crawl performance is very slow.
       
    • Sunday, August 17, 2008 12:22 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Identical problem here - WSS 3.0 with Project Server 2007 being served on Windows Server 2008 Enterprise Edition, 64bit/IIS7.0. After downloading and installing the Filter pack from Microsoft (64bit verion) and kicking off a full crawl, I noticed that the Application Event Log was filling with errors to do with the mssdmn.exe application. After downloading and using Process Monitor, I found that it was faulting on one type of file only - Microsoft Visio Drawings (*.vsd extension). The SharePoint Search gather Temp folder on the Web Font End server contains copies of the failed files (Path is C:\Users\<SearchCrawlServiceAccountName>\AppData\Local\Temp\gthrsvc). They are eventually automatically cleaned up by SharePoint, but you can at least see which files are giving it grief by looking in here.

      As you have noted - the error is not consistent in that some Visio drawings appear to cause no trouble and are indexed. This is evidenced by the fact that a search in the containing site will return Visio drawing content in the results no problem. Even supposedly faulting files appear to be getting indexed eventually?

      These very same files were indexed fine under a 32bit WSS3.0 (plain - no Project Server 2007) environment - the containing site collection was identical - it was moved onto the new 64 bit server a week ago from the original 32bit server. Everything else works fine. Other file types are indexed no problem by the filterpack iFilter, as well as PDF files by the FoxIT 64bit ifilter.

      It is causing problems on the Web front end - slow crawl poerformance, resource usage spikes and choking the server's hard drive with error reports - which means I've had to disable the Microsoft Error reporting function, which is not very helpful for Microsoft - albeit after sending of a few for them to chew on (at least I hope they are getting looked at...).

      Have you made any further progess in identifying the error source? It may well be file specific with certain files appearing to not cause trouble. Feel free to e-mail me directly on glenn at centric dot co dot nz.
       
    • Tuesday, August 19, 2008 7:23 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      A workaround for this issue is to get rid of the .VSD file from Full Crawl. You may either do that via removing the file type though search settings, or removing the following registry keys.

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.Vsd]

      @="{FAEA5B46-761B-400E-B53E-E805A97A543E}"

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.Vdx]

              @="{FAEA5B46-761B-400E-B53E-E805A97A543E}"

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.Vss]

              @="{FAEA5B46-761B-400E-B53E-E805A97A543E}"

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.Vst]

              @="{FAEA5B46-761B-400E-B53E-E805A97A543E}"

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.Vsx]

              @="{FAEA5B46-761B-400E-B53E-E805A97A543E}"

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.Vtx]

                      @="{FAEA5B46-761B-400E-B53E-E805A97A543E}"

      If you really need the .VSD files to be crawled, I think you can create a unc file share, put the .VSD to the folder then repeat full crawl again the file share path. If there are too many .VSD files I believe you will be in trouble:-). My testing result revealed that it is the SPS 2007's defect - on some conditions the full crawl filter process will crush when processing the .VSD file on 64bit environment even the content of .VSD does not change, but several times crawling will successfully crawl all files, although it really impacts the performance. You can say that is not the solution to this issue, but we might only use the workaround before MS provides the hotfix.

       
    • Monday, October 13, 2008 9:19 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      I am getting the same error message on my 64bit Farm even after I moved my .vsd files in a File Share and installed the Microsoft Filter pack using the following KB (http://support.microsoft.com/?id=946336, but I am able to crawl these visio files on my 32bit Farm without any issues. I am also unable to crawl .pdf files after installing the pdf iFilter from (http://labs.adobe.com/wiki/index.php/PDF_iFilter_8_-_64-bit_Support). I have tested this with both Adobe Reader 8.1.0 and 9.x with no luck on 64bit Farm, but on 32bit I can index .pdf without any issues. All these signs are point to 64bit platform and I am unable to find the solution yet (Microsoft please advice!!!!!!!!!!!)
      MA
       
    • Friday, October 17, 2008 3:34 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
       

      "mcwoods" did you guys receive any feedback from Microsoft regarding your .vsd crawl issues? I was getting the same error message on my 64bit MOSS FARM "The filtering process has been terminate" and I was unable to crawl visio files, but after further troublshotting/testing I've noticed that the error is isolation to visio .vsd files/docs that were created using older Visio 2000 version. So here is what I did, on my file_share I copied two visio docs one was created using Visio 2000 and one with Visio 2003, reseted my crawl, ran a FULL crawl against my File_Share and this time MOSS search was able to crawl and find visio doc that was created using visio 2003 pro, but I got the same error message on the files that was created using Visio 2000.

       Please, see if you can perform the same test on your end to verify what I am experiancing. Hope this helps

       (Microsoft, Please Pimp my Search")

      Murad Akram

      MA
       
    • Friday, October 17, 2008 3:41 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I was able to fix my problem by installing "Windows Desktop Search 3 for Windows Server 2003 x64 Edition" (as recommend in the adobe article) on my index server and re registering the pdffilter64.dll (regsvr32.exe). Initially I ignore the fact that we need Windows desktop search on the server, but since everything else failed I end up installing it on my server which apparently fixed my issue.

      I am building my production MOSS next month, will let you know if this work there as well.
      Good luck

      Murad Akram

      MA
       
    • Wednesday, December 31, 2008 2:50 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      Microsoft has released a hotfix for the 64 bit issue when crawling .VSD's.  We submitted this as a bug and worked with them on getting it fixed.  Although the hotfix says it is an x86 package, this is for both 64 bit and 32 bit.

      http://support.microsoft.com/kb/960502

      • Marked As Answer by mcwoods Wednesday, December 31, 2008 2:51 PM
      •  
       
    • Friday, September 18, 2009 2:30 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      I'm encountering this same problem and am patched up through SP2 and the June Cumulative Update (so presumably I already have the code in the hotfix)? Anybody come up with another solution for this?
       
    • Friday, September 18, 2009 9:40 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      What is your current configuration, what have you done so far to enable/install .pdf iFilter? Take a look at these instructions http://sharepointsolutions.blogspot.com/2009/01/installing-adobes-64-bit-pdf-ifilter-9.html

      MA
       
    • Monday, November 23, 2009 6:15 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I too had the following errors in my SharePoint MOSS 2007 crawl log that were associated with .vsd (Visio) files:

      - The filtering process has been terminated
      - The requested operation cannot be performed on a file with a user-mapped section open

      Environment:
      - WIN2K3 R2 x64 SP2,
      - MOSS 07 patched fully to date with all Service Packs and Infrastructure Updates through July 2009 (12.0.0.6510)
      - SQL 2008

      I checked all the normal things like the iFilter registration GUID in the registry for the Microsoft files etc... , but still had the error. Despite the fact that I had all the SP's and updates in place, I had to install the hot fix you have mentioned to clear up the crawl errors. http://support.microsoft.com/kb/960502

      I now have no errors within my crawl log.
      Thanks for posting.
      Kenny