Banging your head against your screen because you get the following error message...?
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 the following to fix this:
Disable the loopback check
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: 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
After applying the following SharePoint Server 2007 patches:
ReplyDelete1. KB 953397: Excel Server Security Update x86 x64
2. KB 955586: Document Lifecycle Workflow Update
3. August Cumulative Update for Windows SharePoint Services 3.0 (Global)
4. August Cumulative Update for Windows SharePoint Services 3.0 (Local)
5. August Cumulative Update for Microsoft Office Servers
was getting access denied when search ran. did the following fix
BAMG fixed the issue!!!!!!!!!
THANKS!!!!!!!
After installing .Net Framework on my Moss servers, I received some remarks that the Search didn't do its job...
ReplyDeleteI've tried your solution, and BAM! Fixed the problem.
Thanks,
Same as above ... installed latest .net 3.5 sp1 ... applied the reg fix and all sorted!
ReplyDeleteThank you very much !!!
Saved my butt, thanks! My issue was also .net 3.5sp1 related.
ReplyDeleteGreat fix....and I didn't even have to reboot to get results. The next time the search service ran, it just worked. Thanks Again!!
ReplyDeleteAwesome! This registry change fixed our search problems.
ReplyDeleteThanks!
It worked perfectly!
ReplyDeleteThe problem is fixed :D
Thanks a lot:)
Have been pulling hair out. Other SSP on the same farm indexing a site works. But not our main one. This fixed it. Thanks. No reboot necessary.
ReplyDeleteThanks for the info... fixed the problem for me! Have to say, this fix isn't an obvious one.
ReplyDeleteSuperb !!!!!!!!!.
ReplyDeleteI was banging my head on the wall for this
Search works now
Thank you very much for this!
ReplyDeleteDang!! worked like a charm
ReplyDeleteWorked like a charm for me
ReplyDeleteTHANKS!!!!!
PS: didnt have to reboot
Thought I had broken my site after modifying the search bar on the master page. Searched a week for the answer. This worked like a charm. Thanks a mil.
ReplyDeleteError every five minutes for weeks. 5 Minutes RegEdit - fixed. Thanks a mill - I didn't need to re-boot either (W2008)
ReplyDeleteDitto.... Problems occurred after .NET Framework 3.5 Sp1 update. This fix worked liked a dream.
ReplyDeleteThanks for keep my stress levels down.
I have been tearing my hair out (literally) for about three days now. The problem I was having was with the people search. The rest of the search service was working was just fine.
ReplyDeleteThank you for this post. I can now go back to my life and work on a comb-over!
My Problem is still not fixed. I still got the same access denied error. I have made the registry entry and many other things, but didnt work for me.
ReplyDeleteAny other thoughts?
Same problem after .net 3.5 sp1 update.
ReplyDeleteApplied the fix and it works!
Thanks,
Kees
Had the same problem after .NET Framework 3.5 SP1 update + Feb 24th WSS & MOSS Cumulative updates. This solution worked!!! Thank you!!!
ReplyDeleteThanks! this works for me.
ReplyDeleteThanks for posting this!
ReplyDeleteIt worked like a charm!!!
Many thanks for posting this. It fixed the problem for me too.
ReplyDeleteThe fix works like a dream - no reboot required.
ReplyDeleteI had actually come across the MS KB article but did not think that was related in any way to my MOSS search issue.
Thank you so much!
TM
This was the solutions. Indeed weeks of errors and one little registery hack fixed it...
ReplyDeleteThanks!
I was going around, checking the user permissions...nothing could make it work.
ReplyDeleteThis solution worked. Thanks a lot.
Thanks!
ReplyDeleteThis was a great post and quick fix. Wish I found this sooner.
THANK YOU!!! This saved me many headaches after the tedious installation process only to have my crawl log tell me access was denied to the content account.
ReplyDeleteHi.
ReplyDeleteI faced the same problem on MOSS 2007 Server running on Windows Server 2008 OS. I managed to fix this problem by disabling look backup check, which is enabled by default on Windows Server 2008 Operating Systems.
Complete detail can be found at: http://www.mossgurus.com/adnan/Lists/Posts/Post.aspx?ID=22
Thanks
Adnan Ahmed
http://www.mossgurus.com
Great instruction - works like a champ!.. thanks for an awesome post!
ReplyDeleteThanks, this really helped!
ReplyDeleteThis saved my day, thank you!
ReplyDeleteRobert, Norway
This worked fabulously. I stopped started services instead of a reboot.
ReplyDeleteYou are Awesome!. Your recommended fix worked for me too!
ReplyDelete-Ben
Hi,
ReplyDeleteOn which server need to edit registry: front-end srever, sql data server or application server? thanks! Viv
Hi,
ReplyDeleteOn which server need to edit registry: front-end srever, data server or application server? thanks!
Viv
I used your process and it worked. I was working with Moss 2007 R2 on windows server 2008 R2 and for some reason the search didn't work. Thanks anyway.
ReplyDeleteThank you thank you thank you. I bucked it all afternoon, being a registry edit and all, but it worked and my default content access account now has all the acess its little heart desires.
ReplyDeleteNow I can stop saying bad words and will have a better weekend...
Thanks. Works perfectly. Can't believe, that you have to modify the registry to have the search running.
ReplyDeleteGreat fix! Thanks - just had to apply this to my SP2010 cluster, and it fixed my search.
ReplyDeletethank you! your post is very helpful to me
ReplyDeleteThank you, had to do this on our moss 2010 and it did the trick
ReplyDeleteGreat post. Wonderful. :-)
ReplyDeleteMany people were benifited from this solution. My only question is which server should I apply this regedit changes? I change it on the SharePoint 2010 server, and still have the same problem. Should I change it on the MOSS2007 instead?
ReplyDeleteThank you.
Bang on!!!! We were experiencing the same problem in our QAT environment with new sites only, old site were crawling fine. I was scratching my head. I didn't even have to reboot the server, because would have to wait till after hours, raise a plog etc., but put the key in the registery and I am getting results! YEAH
ReplyDeleteTHANK YOU.. i was literally banging my head as you said :o). this simple solution solved my problem.
ReplyDeleteBrand new Sharepoint Server 2010 installation and this is still very relevent.
ReplyDeleteGreat fix!!!
Folks, in my case I was crawling file shares, not moss content. MOSS content crawling was working fine.
ReplyDeleteAnyways, the fix for my environment was to change default content access account from
domain\username
to
username@domain.local
Hope this helps someone out there.
It fixed the search error.
ReplyDeleteThanks
Thanks ..Help me a lot..
ReplyDelete