Jouledoc Notes on Web

Thank
you for your suggestion. I did as you suggested, and stopped the
Windows SharePoint Services Search. When I did the standard search, it
worked normally. When I did the Search: This Site, I got a message I
had not gotten before…. It was

Your search cannot be completed because this site is not assigned to an indexer.

I
restarted the SharePoint Services Search, but still got the same
error. So I looked up what I needed to check to verify my Indexer
settings and found the following: “To start it, you have to visit your
content database in Central Admin Application Management. In the SharePoint Web Application Management section, click on Content Databases. This should expose your content database for the farm.”

So
I did just that. I went to Application Management on the Central
Administration site and clicked on Content Databases. I saw my
database; WSS_Content and clicked on it to view the settings. Sure
enough, the Search Server (Indexer) was not selected. I chose my index
server (my only SP server) and clicked OK. I retried the Search: This
Site, and got a message that there were no results to be found!!! Woo
Hoo!!! No error message!!!

I
stopped and restarted my Content Crawls by going to Shared Services
Admin>Shared Services>Search Settings (under Search)>Content
sources and crawl schedules. I have 3 sources; the SP server and
sites, a shared folders directory, and the Exchange Public Folders
directory. I stopped and started the crawl on all 3 and then tried the
Search: This Site once again…… Success!!!! I am getting search
results now.

Unfortunately,
I do not know if this was the actual root cause of the problem I was
experiencing with the Search: This Site function. I had not been
getting an Indexer error previously. This one is a head
scratcher….. I am glad it is working though.

Powered by ScribeFire.

Share This

taken from http://workerthread.wordpress.com/2008/01/03/configure-pdf-ifilter-in-wss-30/

There are various posts around on setting up MOSS 2007 to use the
PDF IFilter, and some stuff on Windows SharePoint Services 3.0 as
well. I’ve found a method which works for me, so I wanted to put this
together in one place - not least of all so I can find it when out on
site with a client.

Out of the box neither WSS 3 nor MOSS 2007 will index content
located in Acrobat PDF files, so you need to set up the IFilter. I’ve
also found that that PDF files loaded prior to the installation of the
filter won’t be re-crawled automatically, so to be on the safe side you
might want to kick off a full crawl.

Here is what I’ve found works for WSS 3.0:

1. First, you need to download the Adobe PDF IFilter 6.0, which you can find at this URL.
   You should also get hold of a suitable Icon to use with PDFs, so that
   when they are listed in a document library they are easily
   recognisable. There is a 17 x 17 one available on the Adobe web site here.
2. 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 927675.
   I’ve always found that providing 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 search
   service.
3. Now you need to set up the Icon file. If you downloaded the
   icon file in step 1 above, you will have a file called
   pdficon_small.gif. You need to copy this onto your WSS 3.0 server,
   into drive:\Program Files\Common FIles\Microsoft Shared\Web Server
   extensions\12\TEMPLATE\IMAGES.
4. 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 Files\Common FIles\Microsoft Shared\Web
   Server extensions\12\TEMPLATE\XML. 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 </ByExtension> closing tag. The new key
   will be <Mapping Key=”pdf” Value=”pdficon_small.gif” OpenControl=””/> (note that XML is case sensitive so make sure you use same case as previous entries). Then save the file.
5. That’s pretty much it, but if you already have PDFs uploaded
   to your WSS server I would recommend starting a full crawl. You can do
   the with STSAdm, the command syntax is Stsadm -o spsearch -action fullcrawlstart . More on this on TechNet here.

Powered by ScribeFire.

Share This