Microsoft SharePoint (WSS 3.0) search is probably one of the most common points of failure and source of support tickets for our customers.
Here are some of the major points to check when troubleshooting this service.
1. Make sure the content database is assigned an indexer.
Open SharePoint Central Administration > Application Management > Content Databases
Select your web application if it is not already selected.
Click on the content database.
Make sure that the Search Server dropdown has the servername selected which is running the WSS Search Service.
2. Make sure you have implemented the DisableLoopbackCheck registry entry.
Check out this blog post.
3. Make sure your search service is running as a domain account and that the account credentials were entered correctly (with DOMAIN\serviceaccount) in Central Administration.
4. Make sure your alternate access mappings in the default zone are accessible from the server.
5. If using forms authentication, use windows authentication in the default zone, and then extend the web application to the internet zone which uses forms.
6. If pdf files are not being indexed correctly on 64bit systems, there may be a registry entry that you are missing.
Note there is an extra registry GUID change for the 64bit Adobe I filter. Here'a a link to a well written post : Here
7. After all these are verified and\or changed to the correct configurations, run an stsadm full crawl.
This is performed by opening a command promt on the server running the Windows SharePoint Services Search Service then:
Type cd C:\program files\common files\microsoft shared\web server extensions\12\bin
Hit Enter
Type stsadm -o spsearch -action fullcrawlstart
Hit Enter
Your content should begin the indexing process
Check the event lot to see if the 401 unauthorized messages have gone away.
I hope this helps you guys out there in the field.
Tags: sharepoint, wss 3.0, sharepoint search