I have a two node Exchange 2013 (CU15) DAG. The mailbox servers are performing well except that you cannot search in Outlook client or OWA. Most articles I find are from 2013 and discuss a ContentSubmitters group in AD. I'm not certain, but I don't think that is relevant to CU15. I just migrated from Exchange 2010 in March-April.
The services, Exchange Search and Exchange Search Host Controller start. I have stopped these services, deleted the GUID.Single folders and restarted the services, but no new GUID folders were created. I rebooted the server and problem persists.
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus Name Status CopyQueue ReplayQueue LastInspectedLogTime ContentIndex Length Length State ---- ------ --------- ----------- -------------------- ------------ DB05\MBX01 Healthy 0 1 6/22/2017 9:54:53 AM Failed DB04\MBX01 Healthy 0 0 6/22/2017 9:53:50 AM Failed DB03\MBX01 Healthy 0 0 6/22/2017 9:53:45 AM Failed DB02\MBX01 Healthy 0 0 6/22/2017 9:53:44 AM Failed DB01\MBX01 Healthy 0 0 6/22/2017 9:52:15 AM Failed [PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus | FL conte* ContentIndexState : Failed ContentIndexErrorMessage : The database has been dismounted. ContentIndexErrorCode : 4 ContentIndexVersion : ContentIndexBacklog : ContentIndexRetryQueueSize : ContentIndexMailboxesToCrawl : ContentIndexSeedingPercent : ContentIndexSeedingSource : ContentIndexServerSource : [PS] C:\Windows\system32>Update-MailboxDatabaseCopy -identity db01\mbx01 -CatalogOnly Confirm Are you sure you want to perform this action? Seeding database copy "DB01\MBX01". [Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): y WARNING: Seeding of content index catalog for database 'DB01' failed. Please verify that the Microsoft Search (Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: There was no endpoint listening at net.tcp://localhost:3863/Management/SeedingAgent-4FEA91B2-FD60-4743-B03A-08B319F04DB312/Single that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details..
And finally, in CMD I checked the tcp port status.
netstat -ano Active Connections Proto Local Address Foreign Address State PID TCP 0.0.0.0:3863 0.0.0.0:0 LISTENING 3076