Search Error issue in SharePoint Server 2016

Question

Search Error issue in SharePoint Server 2016

Sajith Gopalakrishnan Hema 1,056

When we search with Server Name, the search is working. However with Alternative Access Mapping name, showing the below error and there is no log info in the correlation ID

Full crawl is configured using Server Name and not with the AAM.

trevorseward 11,711 Reputation points

2021-01-15T16:53:32.59+00:00

This is too little information to assist you. You need to get the ULS logs from the SharePoint server to find out what the underlying error of that correlation ID is.

Accepted answer

0 additional answers

Your answer

trevorseward 11,711 Reputation points

2021-01-15T16:53:32.59+00:00

This is too little information to assist you. You need to get the ULS logs from the SharePoint server to find out what the underlying error of that correlation ID is.

Answer 1

Chelsea Wu 6,341 Moderator

Is AAM recently configured in your farm? Has search been working in AAM sites before?

Please make sure you put only the URLs of Default Zones in the Content Source, even if it is the AAM that is set to Default.
If the issue persists, perform an Index Reset and then run a full crawl again.

Reference: Beware crawling the non-Default zone for a SharePoint 2013 Web Application.
Another post with same issue for your reference: SharePoint 2013 search stopped working on the alternate access mapping after latest update KB3191886.

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. **

Sajith Gopalakrishnan Hema 1,056 Reputation points

2021-01-13T07:02:28.637+00:00

AAM was configured initially and It was working fine before.

The below URL Comment section, there is a suggestion of running the configuration wizard. Please advise.

https://community.spiceworks.com/topic/1915551-sharepoint-2013-search-not-working-for-dns-redirect
Chelsea Wu 6,341 Reputation points Moderator

2021-01-13T08:31:13.61+00:00

You can run the configuration wizard to check the farm status, it will not cause any issue.
Have you installed any patch recently? If yes, do run the configuration wizard again to configure the farm properly.
Sajith Gopalakrishnan Hema 1,056 Reputation points

2021-01-15T12:44:11.187+00:00

After running the configuration wizard in the production farm, the issue is fixed. Also configured loopback check for the DNS name.
The previous version was April 2019 Patch (16.0.4834.1000). The updated version is May 2020 Patch (16.0.5005.1000).

The DR Farm (different farm) is located in different country and replication is performed using double take. The DR SharePoint is not online and only database replication is performed.

Can we run the configuration wizard in the DR for updating the patch version to May 2020 Patch ? Otherwise, replication may have issue right.
trevorseward 11,711 Reputation points

2021-01-15T16:54:25.68+00:00

DR farms should be patched and updated before production farms. This does mean that service application databases/content databases should not be connected to the DR SharePoint farm prior to updating production to prevent a schema mis-match.
Chelsea Wu 6,341 Reputation points Moderator

2021-01-18T00:44:29.693+00:00

As Trevor suggests, do not patch the DR farm by running the configuration wizard directly in this situation, patch it before production farms and run the configuration wizard right after.

You can post your solution as a separate Answer and accept it If you confirm the issue is solved.
Of you can accept this Answer if you find it helpful. Thank you for your understanding.
Chelsea Wu 6,341 Reputation points Moderator

2021-01-21T23:57:25.65+00:00

Hi @Sajith Gopalakrishnan Hema , do you have any progress on this thread? Please feel free to let us know if you need further assistance.
Sajith Gopalakrishnan Hema 1,056 Reputation points

2021-01-22T18:25:28.56+00:00

The DR is in passive state. (not active). The DR is configured in such a way that it will be active only when production farm is down.

1) Can I run the configuration wizard in DR Farm in passive state ?
2) Double Take replication needs to be stopped right from prod to DR ?
trevorseward 11,711 Reputation points

2021-01-22T19:25:53.573+00:00

I suppose you need to clarify exactly how you're replicating. If you're replicating VMs, which wouldn't be supported, no you can't bring up the DR farm. If you're replicating databases (i.e. where you could otherwise use SQL AlwaysOn or SQL Mirroring (legacy)), you just need to make sure any replicated Content or Service Application database is not mounted to the DR farm before you update the DR farm.
Sajith Gopalakrishnan Hema 1,056 Reputation points

2021-01-22T19:51:19.723+00:00

The database replication is done by the Double Take Tool. Thanks for the info.

Share via

Search Error issue in SharePoint Server 2016

0 additional answers

Your answer