Archive for the ‘Search Service’ Category

In some of the more recent builds of MOSS, the “contains” and “does not contain” options for advanced searches have been removed. This was done because of query performance concerns expressed by a significant number of customers.These options were removed from the default Advanced Search page with hotfix 950280 (and all other cumulative MOSS 2007 updates released since) due to potential performance issues – Expensive Transact-SQL queries are generated in the back-end instance of SQL Server when you perform a search in SharePoint Server 2007. If you are not worried about the query perfomance hit, you can make this option available to users with a small amount of work. Take the following steps to do so.

1.       From your search center, go to the Advanced Search Page
2.       Click Site Actions->Edit Page
3.       On the “Advanced Search Box” web part, click edit -> Modify Shared Web Part
4.       Expand the Properties tab
5.       In the “Properties” textbox, find <Option Name=”AllowOpContains” Value=”False”/> under root the node. If it does not exist, create it.
6.       Change value from “False” to “True” and click OK
7.       Click “Publish” to publish the page

Resources :


I was configuring SharePoint search service. when I started full crawl , it started and 1 second later ( after refresh ) it stoped and gives me this error in error log :

Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (The item was deleted because it was either not found or the crawler was denied access to it.)

I searched and found the solution is : Disable the loopback check

How ?  Follow these steps:

  1. Click Start, click Run, type regedit, and then click OK.
  2. In Registry Editor, locate and then click the following registry key:
  3. Right-click Lsa, point to New, and then click DWORD Value.
  4. Type DisableLoopbackCheck, and then press ENTER.
  5. Right-click DisableLoopbackCheck, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Quit Registry Editor, and then restart your computer.

After doing this and restarting the server, nothing happened !!

So I stoped both Windows SharePoint Services Search & Office SharePoint Server Search and then restart them again.

after I started the again, I started full crawling and it didn’t stop soon … and no error happened .


I was usually creating the web applications with Application pool identity Network Service . I found that you should use a Service Account to solve this problem. So after doing the above workaround , if your problem already exists you can delete your web application and recreate it by using a Service Account application pool.


A very simple post ! A simple Note ! 😉

If you were starting the Office Sharepoint server Search and you see this error :

“An unhandled exception occurred in the user interface.Exception Information: D:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Config”

Don’t be afraid ! just go to the directory that you keep your indexes . In my case this is D:\Program Files …. and then maybe you will see that there’s an extra Office server folder in it. So you can cut it’s sub directories and paste them in the previous folder. after that your search servive will be started ! 🙂