Installing PDF support in WSS 3.0 and MOSS 2007 (icon and search)

Lots of info out there seems to differ, so this is what worked for me, for both scenarios (MOSS 2007 or WSS 3.0). One thing for sure, since about September 2007, there is a lot of FUD.

 

MOSS 2007 – PDF Support (icon and search)

Configure Search To Work

 

1. Stop the IIS Admin Service: Start->Run->Services.msc->Locate the IIS Admin Service and stop it

 

2. Don’t Download the Adobe PDF IFilter and install it on your indexing server (like most articles suggest). That’s right, don’t. Instead, download the latest Adobe Reader (at this writing, Adobe 9.0) and install on your Index Server.

 

3. Modify the following Registry keys by changing their “Default” value to the new

CLSID of the Adobe iFilter: {E8978DA6-047F-4E3D-9C78-CDBE46041603}

   1: HKEY_LOCAL_MACHINESOFTWAREMicrosoftOfficeserver12.0SearchSetupContentIndexCommonFiltersExtension.pdf
   2:  
   3:         set the Default value to {E8978DA6-047F-4E3D-9C78-CDBE46041603}
   4:  
   5:  
   6:  
   7: HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions12.0 SearchSetupContentIndexCommonFiltersExtension.pdf
   8:  
   9:         set the Default value to {E8978DA6-047F-4E3D-9C78-CDBE46041603}

 

4. Add the Installation directory of the Adobe Reader v.9.0 to the System Path.

NOTE: This is necessary because the Adobe filter .dll file (AcroRdIF.dll) depends on the AcroRd32.dlland AGM.dll files. These files are located in the C:Program FilesadobeReader 9.0reader folder. Because the path is not included in the system path on the computer that is running SharePoint Server 2007, the SharePoint Server 2007 Search service cannot properly scan the .pdf files.

    a. Click Start, click Control Panel, and then double-click System.

    b. In the System Properties dialog box, click the Advanced tab, and then click Environment Variables.

    c. In the Environment Variables dialog box, double-click Path in the System Variables area.

    d. In the Edit System Variable dialog box, put the cursor at the end of the text in the Variable value box, and then type ;Drive_Letter:Program FilesadobeReader 9.0reader

    e. Click OK three times.

 

5. Recycle the search service:

    a. net stop oSearch

    b. net start oSearch

 

Then Prep the Icon

 

3. Install this GIF ( ) or any icon of your choosing to “C:Program FilesCommon FilesMicrosoft Sharedweb server extensions12TEMPLATEIMAGES”

 

4. Edit the DocIcon.xml file at “C:Program FilesCommon FilesMicrosoft SharedWeb server extensions12TemplateXmlDOCICON.XML” and add the following text under the tag.


 

5. Perform an IISRESET 

 

6. Open the SSP Admin site (Central Administration->SharedServices1). Click on Search Settings->File Types->New File Type) and add the pdf file type.

 

7. Perform a full crawl on content sources. Search Settings->Content Sources and Crawl Schedules, click on the Content Source you want to perform a full crawl on. Check the Start Full Crawl check box at the bottom and then click OK. Wait for the crawl to finish.

 

 

 

————————————————————

 

 

 

WSS 3.0 – PDF Support (icon and search)

Here’s what I found works for me, for installing PDF support on WSS 3.0.

 

Configure Search To Work

 

1. Stop the IIS Admin Service: Start->Run->Services.msc->Locate the IIS Admin Service and stop it.

 

2. Don’t Download the Adobe PDF IFilter and install it on your indexing server (like most articles suggest). That’s right, don’t. Instead, download the latest Adobe Reader (at this writing, Adobe 9.0) and install on your Index Server.

 

3. Modify the following Registry key by changing their “Default” value to the new

CLSID of the Adobe iFilter: {E8978DA6-047F-4E3D-9C78-CDBE46041603}

   HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions12.0 SearchSetupContentIndexCommonFiltersExtension.pdf
    
           set the Default value to {E8978DA6-047F-4E3D-9C78-CDBE46041603}

4. Add the Installation directory of the Adobe Reader v.9.0 to the System Path.

NOTE: This is necessary because the Adobe filter .dll file (AcroRdIF.dll) depends on the AcroRd32.dlland AGM.dll files. These files are located in the C:Program FilesadobeReader 9.0reader folder. Because the path is not included in the system path on the computer that is running SharePoint Server 2007, the SharePoint Server 2007 Search service cannot properly scan the .pdf files.

    a. Click Start, click Control Panel, and then double-click System.

    b. In the System Properties dialog box, click the Advanced tab, and then click Environment Variables.

    c. In the Environment Variables dialog box, double-click Path in the System Variables area.

    d. In the Edit System Variable dialog box, put the cursor at the end of the text in the Variable value box, and then type ;Drive_Letter:Program FilesadobeReader 9.0reader

    e. Click OK three times.

 

5. Restart the WSS Search Service and an IISRESET for good measure

 

Then Prep the Icon

 

6. Copy this GIF ( ) or any icon of your choosing to System_driveProgram FilesCommon FIlesMicrosoft SharedWeb Server extensions12TEMPLATEIMAGES

 

7. Once you’ve downloaded the IFilter, install it on your WSS 3.0 server, and then follow the instructions on registry settings in Microsoft KB Article 927675Usually, if the Adobe IFilter installed properly, the only setting I need to add is the Search Extensions one listed in step 2.  Also note step 5 re stopping and re-starting the WSS search service.

 

image

 

8. Next you need to edit the XML file which WSS uses to link file extensions to icons.  This file is called DOCICON.XML and is located at drive:Program FilesCommon FIlesMicrosoft SharedWeb Server extensions12TEMPLATEXML.

Navigate to that folder and locate the file.  I would suggest making a backup copy first, then opening the file in NotePad.  You need to add a mapping key for PDFs at the bottom of the file, above the closing tag.  The new key will be:


 

Note: XML is case sensitive so make sure you use same case as previous entries and make sure the “” quotes, etc. are truly text.  Then save the file.

 

9. Finally, perform a full crawl.

STSADM -o spsearch -action fullcrawlstart

 

Reference: