locked
[SharePoint 2007 SP3] - Full Crawl after deploying SP3? RRS feed

  • Question

  • I applied SP3 in my environment and users complained that they are not able to search.

    The issue got resovled after a full crawl was run.

    If i read teh following article it says 

    http://technet.microsoft.com/en-us/library/cc262926(office.12).aspx

    that a full crawl may be required after a service pack.

    So is there anyone else who had to run a full crawl after applying SP3?


    MSDNStudent Knows not much!


    Monday, May 28, 2012 11:43 AM

Answers

  • You're right, the KB article for SP3 does not mention anything about performing a full crawl. The KB article also does not mention anything else about anything except for a minor known issue. I say this in reference to the KB articles for SP1 and SP2 which contain lots of information. I don't know why this is, but to guess I would attribute it to the approaching end of live of a previous version of the product.

    That all said, as you point out from the TechNet article you posted (which is official documentation):

    Reasons for a search services administrator to do a full crawl include:

    One or more hotfix or service pack was installed on servers in the farm. See the instructions for the hotfix or service pack for more information.

    While the SP3 KB articles provides no further insight, this document does say that you may need to do a full crawl after a SP. Not only is this good advice, but it resolved your issue. ;)


    Jason Warren
    Infrastructure Specialist




    Tuesday, May 29, 2012 2:37 PM

All replies

  • Well, probably everyone who applied SP3. The Service Pack updates files on the servers and database schemas. While I don't know specifically what these changes may amount to (because I'm not the developer that made these changes, nor do I know which previous version you upgraded from), it's safe to assume that if the documentation says you may need to perform a full crawl there were changes to search components and performing a full crawl will ensure your index is still working.

    Note that it's common in a farm for a full crawl to be scheduled on a regular basis (once a week). Depending on the size of the content it's also common for SharePoint Administrators to kick off a full crawl after any maintenance that affects the Search Service (such as the installation of service packs) to ensure that Search is working after the work.


    Jason Warren
    Infrastructure Specialist

    Monday, May 28, 2012 3:52 PM
  • But I read the KB articles... and there was nothing which said do full crawl.

    MSDNStudent Knows not much!

    Tuesday, May 29, 2012 11:54 AM
  • You're right, the KB article for SP3 does not mention anything about performing a full crawl. The KB article also does not mention anything else about anything except for a minor known issue. I say this in reference to the KB articles for SP1 and SP2 which contain lots of information. I don't know why this is, but to guess I would attribute it to the approaching end of live of a previous version of the product.

    That all said, as you point out from the TechNet article you posted (which is official documentation):

    Reasons for a search services administrator to do a full crawl include:

    One or more hotfix or service pack was installed on servers in the farm. See the instructions for the hotfix or service pack for more information.

    While the SP3 KB articles provides no further insight, this document does say that you may need to do a full crawl after a SP. Not only is this good advice, but it resolved your issue. ;)


    Jason Warren
    Infrastructure Specialist




    Tuesday, May 29, 2012 2:37 PM