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. 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.( http://samcommunity.qxl.int , http://bpsmerfwwf.qxl.int
and http://marketing.qxl.int:8080 )
Reason:
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 http://portal.com.au(just an example). If
you try http://portal.com.au from the
server, you will find you cannot access it at all.
When the search engine tried to
crawl the content using the kenportal.com.au 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.
Steps:
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.
Error2:
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.
Error3:
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.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.