Exchange 2013 CU2

3 Mailbox Servers(MBX#), 1 DAG, 3 Databases and 2 copies for each database.

On my MBX3 server, the passive copy of DB01 has an Unknown content index state. All other active or passive copies have Healthy content index states on all servers.

1. Already have ContentSubmitters group with the permissions. "Netstat -a" shows the ports 3800, 3801, 3803, 3863... 

2. When I look at the folder "...\Mailbox\DB01\", I could not see any content index catalog folder with GUID.

3. When I run the command "Update-MailboxDatabaseCopy -Identity DB01\MBX3 -CatalogOnly", I get the error:

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-6F2FD4DC-54FF-40B7-9A2A-4F40785E4CAA12/Single that could accept the
message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more
details..

4. Stopping the search services and starting them did not solve the problem.

5. I removed the copy and deleted the folder. Then I added the database copy again. But the same issue continues.

Any help?

Best Regards.

Hi

Try this, snippet from another thread:

Basically, the replication is looking for a group named ContentSubmitters.  Once the group is created in AD, the issue was resolved.  Sounds like MS forget to update the /PrepareAD process because this group is not created when running it.

Because of this item and at least two other items identified upon installation of the product I have decided not to try and put Exchagne 2013 into production until there are some patches released for the product. 

Manually updating AD with attribute permissions found below and manually adding a group after the appropriate preparation scripts are run without error screams incomplete product release to me. 

Ref: http://social.technet.microsoft.com/Forums/exchange/en-US/bc5f9666-6b33-47af-bf88-98917b3fe894/exchange-2013-content-index-state-failed?forum=exchangesvrdeploy

Hi DareDevil57,

ContentSubmitters group has already been created as I mentioned on 1st item of my question. (I think the issue is not related with it because content index states of other active and passive copies are in healthy state.) Anyway thank you for your response.

Still waiting for a solution...

Hello Tanil;

Here are the two suggestions to try, let me know if this helps

1. Set the correct Nic order.
Then restart the Microsoft Exchange Search and the Microsoft Exchange Search Host Controller services
You content index will be healthy, Until context index is healthy you may get the error.

2. Create a new AD group named ContentSubmitters and grant Admistrators and NetworkService full access to it
Thereafter restart Microsoft Exchange Search & Microsoft Exchange Search Host Controller services