Access Denied with Windows Server 2008 and MOSS when Crawling

Comments

# Access Denied with Windows Server 2008 and MOSS when Crawling : EasyCoded said on September 18, 2008 1:25 PM:

PingBack from http://www.easycoded.com/access-denied-with-windows-server-2008-and-moss-when-crawling/

# Matthew Chestnut said on October 14, 2008 10:38 AM:

Thank you so much for this timely post!

I ran into this exact issue after switching to using host headers in my MOSS farm (SP1, Infrastructure Updates, August Cumulative Updates).

All was fine while I used different ports for the web sites, but as soon as I configured the farm with host headers, I kept getting the errors mentioned above.

Thanks again!

# Jason M said on October 16, 2008 4:34 PM:

Dude, thanks!  3 days of looking for an answer and this was it!

# wsspectacular said on November 10, 2008 12:57 AM:

There is one more issue you will probably encounter (and I think this will apply to any version of SharePoint

# Andy Ball said on December 2, 2008 10:04 PM:

love your work , hair is growing back now, although i have a bit of a bald patch because of this

# Richard Threlkeld said on February 17, 2009 12:57 AM:

I've just spent a couple of days looking for this problem. Unfortunately, this solution does not seem to help. I love the new Sharepoint 2007, but this one element is killing me.

Any other ideas? I've created a new logon and attached it to the search service so I could give it a variety of groups, but none appear to help.

Richard

# Richard Threlkeld said on February 17, 2009 1:48 AM:

Never mind. I finally got it working. Went to the Central Administration site, Operations, Services on Servers. Set it to ALL Services, then clicked on the Search Server. Set the parameters correctly for my new ID. First time it failed because I had added the intrinsic Administrator. I went back and removed all the administrator groups from the ID, then updated it again. It took and everything was wonderful.

# Kipp said on March 5, 2009 5:17 PM:

Did you apply this change to all WFEs or just the indexing server?

# shawnfel said on March 5, 2009 5:31 PM:

i would think that all wfe servers need this update if they are being crawled.  Personally i only ran a single server setup.  

# Alex said on March 19, 2009 4:49 PM:

Great job, shawnfel! Thanks a lot - we were pulling our hair for 3 days now. Don't know how you figured that out but that was right on target - didn't even require any other action like search service restart or anything else. The search just picked up after the registry change has been made.

# René said on May 19, 2009 4:49 AM:

Thanks, Shawnfel!

Works like a charm.

Finally we have an index to search ...

Keep up the good work!

# Patrick said on August 6, 2009 11:45 AM:

Thank you for the posting.  Method 1 worked for me!

# Daniel said on November 10, 2009 7:26 PM:

OMG thank you, its been driving me nuts, i was soon going to start rebuilding things! Dam reg entry, would have never found it!

# Benjamin Gemperle said on December 3, 2009 6:56 AM:

Search Server 2008 shows this error for a SharePoint Site (Windows SharePoint Services 3 SP2):

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.)

I solved it by adding the crawler account to: Central Administration > Application Management > Policy for Web Application. Permissions: Full Read.

Leave a Comment

Name (required) 

Your URL (optional)

Comments (required) 

  

Enter Code Here: Required

Remember Me?

About shawnfel