Forum Discussion

Anthony Monda's avatar
Anthony Monda
Copper Contributor
May 25, 2017

SharePoint 2013 search stopped working on the alternate access mapping after latest update KB3191886

I have had a SharePoint 2013 foundation up and running well for some time.  After the latest update KB3191886 search no longer works on any of the sites when it is accessed with the the alternate access mapping ( http://intranet) , search works fine when accessed from the server name (http://servername) .  When using the AAM name it returns: "Sorry, something went wrong"  - "There was an exception in the Database. Please retry your operation and if the problem presists, contact an administrator." - "Correlation ID: c626f59d-af33-e01b-f39c-93ca43cb319f"

 

The server name is set in the defaut zone and search is set to index it and it appears to be working.  The AAM name - Intranet is set to the intranet zone.

 

I have tried everything I can think of short of uninstalling KB3191886.

 

Any insight would be greatly appreciated!

sharepoint server

7 Replies

    • Anthony Monda's avatar
      Anthony Monda
      Copper Contributor
      Jun 13, 2017

      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 Haspeslagh's avatar
        Dieter Haspeslagh
        Copper Contributor
        Jun 15, 2017

        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

Resources