Crawling a New WebApplication – Exception in the Crawl Log


Sathish Nadarajan
SharePoint MVP
Published On :   03 Nov 2014
Visit Count
Today :  3    Total :   10675



I faced a problem like, when I search for some content, the result is not bringing me the content from one specific web application. The result fetches from all other web applications. But not from one web application. On the process of debugging, I found some interesting stuff. Thought of sharing with the sharepoint community.

First thing, verify the Crawl Log. On the crawl Log, I found some exception like, there is no access for the SPSearch Service Account to the Web Application.

At that time, we need to give access to the SPSearch Service Account on the Web Application.

Go to Central Administration

clip_image002

Click on the Manage Web Applications

Select the web application and Click on User Policy.

clip_image004

The below screen will be appearing.

clip_image006

On that, Add Users. Select the Zone as Default.

Add the user SPSearch with full Control.

clip_image008

That’s it. Now we gave permission for the SPSearch Account to the WebApplication.

Then come back to the Registry. There we need to do a small modification.

1. Once opened the registry editor, just navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa"

2. Right click on "Lsa" and create a new 32bit DWORD value

3. Rename it as "DisableLoopbackCheck" (Note: you cannot rename it actually. so, once created the DWORD value, directly paste/type as "DisableLoopbackCheck".

4. Then again modify the value of "DisableLoopbackCheck" as "1"

Close the registry editor.

Do an IISRESET.

Now start to crawl the content.

Now, the content from that WebApplication should appear on your Search Results. This will be really helpful, when trying to implement the Cross Site Publishing Concept in SharePoint 2013.

Happy Coding.

Sathish Nadarajan.

Categories