SharePoint Search Errors

Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint
repository, verify that the account you are using has “Full Read” permissions on the SharePoint Web Application being crawled.( , and )


This error will occur, at the time of crawling the SharePoint application content. because, you may have provided a URL to access the SharePoint web application like (just an example). If you try from the server, you will find you cannot access it at all.

When the search engine tried to crawl the content using the URL, the server will reject the request. because, it will take the request as “LoopBackRequest”.

Work around:

So we need to disable the LoopBackRequest in registry.


1. Go to command window and type regedit.exe

2. Once opened the registry editor, just navigate to “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa”

3. Right click on “Lsa” and create a new 32bit DWORD value

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

5. Then again modify the value of “DisableLoopbackCheck” as “1”
6. Close the registry editor.
7. Now start to crawl the content.


This item could not be crawled because the crawler could not connect to the repository.

Suspecting this issue from the network firewall side, we need to make sure that all the required ports are opened.


The object was not found.( http://us-bos-vwb012 and sps3://us-bos-vwb012)

In our case the object is http://us-bos-vwb012/ and is not have the root site. i.e. reason we got the object was not found in the crawl error .
Observations from Dev Environment :

Configured the Search functionality for testing purpose in Dev and Is working for these sites :



In Dev Env also got the same error (Error1: Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository.)

Executed the above workaround (to disable the LoopBackRequest in registry) and ran the full crawl. after that the Access Denied error resolved in Dev Env.

And from the best practice and security reasons we need to go for a separate Search managed service account to read and crawl the content in our SharePoint Portal.



Author: "Sharepoint Thoughts"

I’m a Microsoft Certified IT Professional with 5+ Years Experience on SharePoint Technologies. Worked extensively on “SharePoint 2007”, “SharePoint 2010”, “SharePoint 2013” & “SharePoint 2016” on Implementation, Configuration & Troubleshooting several Projects.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s