SharePoint 2016 Crawl error

Er Bo Guan 461 Reputation points
2021-03-05T20:59:10.857+00:00

I go this error when I tried to crawl a web application (2013 upgrade to 2016):
"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."

I already did
(1) The "Default content access account" has full access to the site collection. It also in permission to the web application.
(2) The account has access (administrator & full accesses) to "User Profile Service Application" and "Search Service Application".
(3) "DisableLoopbackCheck" and "BackConnectionHostNames" already added to the server register.

Please let me know if something else I should look for. Many thanks.

SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,811 questions
0 comments
Accepted answer
  1. Er Bo Guan 461 Reputation points
    2021-03-10T21:29:29.14+00:00

    Issue solved.

    The content database was linked to a test site. We switched over the content database to the current site and turn off the test site. After I deleted the test web application. I can crawl now. Thanks to everyone.

    0 comments

5 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Trevor Seward 11,681 Reputation points
    2021-03-06T18:58:43.58+00:00

    Verify you're crawling the URL you believe you're crawling. Taking a look at your Content Source, validate that name resolution points to your new SharePoint front end or try accessing the new front end from your Search server with Internet Explorer on that server. This will tell you if you have a name resolution issue or not.

    0 comments
  2. Er Bo Guan 461 Reputation points
    2021-03-08T00:02:53.807+00:00

    I will double check tomorrow when I back to work. Thanks for your response.

    0 comments
  3. Echo Du_MSFT 17,116 Reputation points
    2021-03-08T01:49:06.903+00:00

    After verifying that the account did indeed have the correct permission I did a little digging and found that this was caused by a very common SharePoint headache.

    Here’s how to disable the LoopBackCheck:

    Manually:

    • Go to command window and type regedit.exe
    • Open the registry editor, navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa"
    • Right click on "Lsa" and create a new 32bit DWORD value
    • Rename it as "DisableLoopbackCheck" (Note: you cannot rename it actually. so, once created the DWORD value, directly paste/type as "DisableLoopbackCheck".)
    • Then again modify the value of "DisableLoopbackCheck" as "1"
    • Close the registry editor and now start to crawl the content.

    Powershell:

    New-ItemProperty HKLM:SystemCurrentControlSetControlLsa -Name “DisableLoopbackCheck” -Value “1″ -PropertyType dword

    Thanks,

    Echo Du

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  4. Er Bo Guan 461 Reputation points
    2021-03-08T18:44:09.123+00:00

    As I mentioned on my original post. I already had "DisableLoopbackCheck" entry in my server.

    0 comments