Forum Discussion
SharePoint 2013 search stopped working on the alternate access mapping after latest update KB3191886
Same issue here, did you find an answer?
Unfortunately I did not. I was going to open a paid support with Microsoft.
What I ended up doing was changing the AAM that the users are used to using to the Default zone and changing the server name that was rarely used to the Intranet zone.
I would like to get this figured out.
- Dieter HaspeslaghJun 15, 2017Copper Contributor
Finaly I found somebody with the same problem as I am facing for a few weeks now...
Tried various things but nothing seems to help.
Did any of you find a solution?
What are the consequences changing the AAM to Default zone?
Can I still leave the current default zone as "default"?
Kind regards
Dieter
- Robbie PayneJul 01, 2017Copper ContributorI installed latest SharePoint CU and once restarted all was working fine. SharePoint was behind a few months on CU's.
- Scott ChristensenJul 17, 2017Brass Contributor
One of my clients recently experienced the same issue but was able to get Search returning results simply by reseting the index and allowing a full crawl to run. They are in the process of getting to the lastest CU, but were able to resolve this exact error message without applying the update.