Wednesday, June 17, 2009

Access denied when crawling MOSS Content in crawl Log.

Hi All,
when you try to crawl the site content from central admin in MOSS and look into crawl log the site is not crawled properly and showing you following error.

"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. (The item was deleted because it was either not found or the crawler was denied access to it.)"

try following steps to get rid of this kind of error:

1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
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.

Source: http://support.microsoft.com/kb/896861



10 comments:

Chandresh pansuriya said...

Good Article....

Thanks !

Anonymous said...

That saved my ass!

Anonymous said...

Thanks a lot, man !! Worked for me!

Anonymous said...

Thank you. This article saved me from a nightmare. My search was broken and the project was held up for several weeks.

Thanks a MILLION

Samuel

SharePoint Web Log said...

In SharePoint 2010 my error is coming is
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. ( HttpStatusCode Unauthorized The request failed with HTTP status 401: Unauthorized. )

And this cannot be resolved by your above solution.

Any idea ?

SharePoint Kings said...

Our solution is for Sharepoint 2007,
we not tried this for 2010.
this should work actually but as search is changed in 2010 (fast search) so may be some thing else need to be done.

we had not faced this error in 2010 yet so no idea what can be the work around.
sorry for that.

Greg said...

Yo SP King, NTLM reflection reg hack was specifically needed to get search to work. I saw it first hand. We were unable to crawl ... and I did the NTLM reflection adjustment ... rebooted ... and the search started working like a charm. So, it does appear that this is still something that needs to be done in SP 2010

SharePoint Kings said...

Greg,

Thanks for find and share solution in SP 2010.

your trick will help a ton.

Thanks a lot again.

Thanks,
Sharepointkings Team

Anonymous said...

Thank you Very much for this!!

Confirmed this issue & solution in SP 2010.

X

SharePoint Kings said...

Hay X (Anonymous),

Thanks




Share your SharePoint Experiences with us...
As good as the SharePointKings is, we want to make it even better. One of our most valuable sources of input for our Blog Posts comes from ever enthusiastic Visitors/Readers. We welcome every Visitor/Reader to contribute their experiences with SharePoint. It may be in the form of a code stub, snippet, any tips and trick or any crazy thing you have tried with SharePoint.
Send your Articles to sharepointkings@gmail.com with your Profile Summary. We will Post them. The idea is to act as a bridge between you Readers!!!

If anyone would like to have their advertisement posted on this blog, please send us the requirement details to sharepointkings@gmail.com