none
SharePoint 2013 Search Crawl Issue with https web application and local DNS

    Question

  • We have a Multiple server SharePoint farm with 2 Wfes and 3 App servers.

    We have configured SharePoint search and have a web application under 443 port https enabled. and we are accessing the root site of the web application using a local DNS that is added an entry in the host file with the one of the WFE's IP,

    and can access the site successfully from crawler App server and when trying to run the Search Full Crawl it fails with the below error message.

    An unrecognized HTTP response was received from the server when attempting to crawl this item, verify whether the item can be accessed using your browser ("Error from SharePoint site: WebExceptionStatus: SendFailure The underlying connection was closed: An unexpected error occurred on a send." Search ID = "")

    and I'm getting the below msgs logged in verbose level ULS log of the search components.


    CHttpAccessorHelper::InitRequestInternal - unexpected status (404) on request for 'https://siteintra/robots.txt' Authentication 1.  [httpacchelper.cxx:746]  search\native\gather\protocols\http\httpacchelper.cxx

    SetSTSErrorInfo ErrorMessage = Error from SharePoint site: WebExceptionStatus: SendFailure The underlying connection was closed: An unexpected error occurred on a send. hr = 80041204  [sts3util.cxx:6994]  search\native\gather\protocols\sts3\sts3util.cxx



    Couldn't retrieve server https://siteintra policy, hr = 80041204            [sts3util.cxx:1871]  search\native\gather\protocols\sts3\sts3util.cxx



    STS3::StoreCachedError: Object initialization failed.  Message:  "Error from SharePoint site: WebExceptionStatus: SendFailure The underlying connection was closed: An unexpected error occurred on a send." HR: 80041204  [sts3util.cxx:7089]  search\native\gather\protocols\sts3\sts3util.cxx



    Server siteintra security initialization failed, hr = 80041204 error Message Error from SharePoint site: WebExceptionStatus: SendFailure The underlying connection was closed: An unexpected error occurred on a send.  [sts3util.cxx:1597]  search\native\gather\protocols\sts3\sts3util.cxx



    CSTS3Accessor::InitURLType fails, Url https://siteintra, hr=80041204        [sts3acc.cxx:297]  search\native\gather\protocols\sts3\sts3acc.cxx



    FLTRDMN: URL https://siteintra Errorinfo is "Error from SharePoint site: WebExceptionStatus: SendFailure The underlying connection was closed: An unexpected error occurred on a send."  [fltrsink.cxx:566]  search\native\mssdmn\fltrsink.cxx
    and when I tried to crawl the Central administration site the full crawl is successfully done and the crawled items appear in the search, which makes sure that the search is configured correctly.

    here I have tried solutions suggested related to this issues:

    1.disable loopback check 2.checking all the permission level of the Default Content Access Account in Search Service Application, User Profile Service Application, and Web Application User Policy level 3.Accessing the site pages with the Search Account

    nothing helps here as still the full crawl fails in this situation.

    here I suspect whether the local DNS which is not in our DNS server will make any issues in the crawling.

    Your inputs are highly appreciated here.
    Sunday, May 13, 2018 10:41 AM

All replies

  • Hi Esakiappan Perumal,

    Did you configure the AAM for the https web application?

    If you configure the AAM of the https web application, we should crawl the default zone of the https web application.

    To troubleshoot the issue, check things below:

    1. Check if you crawl the default zone of the web application in search content source.

    2. Set the default zone to HTTPS web application in AAM settings. Then crawl again.

    More reference:

    Crawl the default zone of SharePoint Server web applications.

    https://docs.microsoft.com/en-us/SharePoint/search/best-practices-for-crawling#BKMK_CrawlDefaultZone

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, May 14, 2018 8:34 AM
    Moderator
  • can the same site be crawled via http?

    Blog - http://sadomovalex.blogspot.com
    Dynamic CAML queries via C# - https://github.com/sadomovalex/camlex

    Monday, May 14, 2018 6:24 PM
  • Hi Esakiappan Perumal,

    How is everything going?

    Is there anything update about this issue?

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, May 16, 2018 1:38 AM
    Moderator
  • Hi Sara Fan,

    Thank you for your input on this and sorry for the delayed response , 

    Did you configure the AAM for the https web application? - Yes we have tow different zones here Default and Intranet and we have configured AAM and we have different Authentication enabled like default zone we have ADFS authentication enabled and Intranet we have Windows Authentication enabled .

    as per your suggestion i tried to crawl the default zone url with windows authentication enabled , but still I'm getting the same error.



    Monday, May 21, 2018 7:46 AM
  • Hi Esakiappan Perumal,

    To troubleshoot the issue, check things below:

    1. Check if you have added the certificate of the https site in SharePoint Trust store in Central Administration. If not, you could follow the steps in the article below.

    SharePoint 2010 and Cert Trust – Could not establish trust relationship for the SSL/TLS secure channel.

    http://itgroove.net/brainlitter/2012/03/13/sharepoint-2010-and-cert-trust-could-not-establish-trust-relationship-for-the-ssltls-secure-channel/

    2. Reset IIS and run a full crawl again to check if the same issue will occur.

    3. Create a new search service application to check if the same issue will occur.

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, May 23, 2018 9:20 AM
    Moderator
  • Hi Esakiappan Perumal,

    I am checking to see how things are going there on this issue. Please let us know if you would like further assistance.

    If the issue was resolved, you can mark the helpful post as answer to help other community members find the helpful information quickly.

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, June 5, 2018 1:36 AM
    Moderator