SharePoint search only crawling default alternate access mappings

Question

question

ellier2021-9518 asked Dec 21, '21 ellier2021-9518 commented Mar 25, '22

SharePoint search only crawling default alternate access mappings

Hi, I have a single server farm where I tried to set up https to work alongside http plus some new urls. I have 4 different urls I want to be able to access the solution with:

url1
url1.domain
url2
url2.domain

Along with both http and https, this makes 8 urls in total. I have set up IIS bindings for the https urls and alternate access mappings as follows:

internal: https://url1- default - public: https://url1 (this is the web app url but with https. Content source links have been updated to this)
internal: http://url1- intranet - public: http://url1
internal: https://url2.domain - internet - public: https://url2.domain
internal: http://url2.domain - custom - public: http://url2.domain

and have set links in content sources to https with the web app url (same as default zone aam). I have not set any redirecting up as I wanted both http and https accessible.

Accessing the solution works without issues, however, search does not really work. If you access the solution with the web app url in https (default in alternate access mappings, same as links in content sources) then it works, if you have accessed the solution with any other url, search returns 0 results or sometimes even an error "SqlError: procedure or function proc_MSS_GetUrlMapping has too many arguments specified". I have tried a full crawl and it made no difference.

Does somebody have experience with a setup like this? What have I missed? Any tips would be appreciated.

office-sharepoint-server-administration office-sharepoint-server-search-itpro

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 1 · 2021-12-22T01:52:08.017Z

JoyZ answered Dec 22, '21 ellier2021-9518 commented Mar 25, '22

@ellier2021-9518,

For best practices, make sure you crawl the default zone of a SharePoint Server web application,the query processor automatically maps and returns search-result URLs so that they are relative to the alternate access mapping (AAM) zone from which queries are performed.

This setting makes it possible for users to readily view and open search results.

For your issue, please run the SharePoint Configuration wizard in search server to check the result.

Similar issue for your reference:

https://social.technet.microsoft.com/Forums/en-US/53945486-c44d-4aaf-8cc4-960f012acf69/sharepoint-2016-search-issue-searchserviceapplicationproxyisurlmappingcachedwithhasherror?forum=SP2016

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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.

· 5

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JoyZ · Dec 27, 2021 at 07:11 AM

@ellier2021-9518,

Do you have any progress on this issue?

Please remember to update this thread if you need further assistance.

0 ·

ellier2021-9518 JoyZ · Jan 03 at 08:12 AM

Hi Julie,

Thank you. I just tried running PSConfig in the test environment where we use 1 url with both http and https and it has resolved the issue with search.
I will update the thread again when I try this in production where we use the 4 urls as described in the original post.

0 ·

JoyZ ellier2021-9518 · Jan 07 at 01:30 AM

@ellier2021-9518,

Did you test it in production?

Would you please provide us with an update on the status of your issue?

0 ·

Show more comments

question