When i move an active database with "Move-ActiveMailboxDatabase -MountDialOverride:None" in my Exchange 2013 CU1 DAG the source servers ContentIndex gets "AutoSuspended"

If i try to "update-mailboxdatabasecopy -catalogonly" i get:
WARNING: Seeding of content index catalog for database 'DB02' 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-ABF80EC7-D4D5-4D12-93D8-6B13D8996EC712/Single that could accept the
message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more
details..

Restarting services does not help.
Nor did: http://support.microsoft.com/kb/2807668

The only thing making the ContentIndex Healty is rebooting the server...

Any clues?

Hi

Perhaps There is something wrong with database copy

Please to the original database 'DB02', then Deleted the database copy, So Content index state now is at failed

Run command "Update-mailboxdatabasecopy -catalogonly" again

Cheers

There is something wrong with database copy

Please to the original database 'DB02', then Deleted the database copy, So Content index state now is at failed

Hi, i don't understand you, "please to the original" ?

HI

Cause I saw in your post

"Seeding of content index catalog for database 'DB02' failed"

So I mean go to 'DB02' to Delete the database copy

Cheers

I wonder if a solution to this was ever found? I am having the same issue and yes I have deleted the copy and recreated it.

Hi, i have no solution for this problem.

They are still "AutoSuspended"

Im waiting to se if CU2 fixes this..

So I installed CU2 on all my servers and the autosuspended no longer is an issue.

• Proposed as answer by Jared Van Leeuwen Thursday, July 18, 2013 9:21 PM

Installing Exchange 2013 CU2 v2 fixes the problem!

• Marked as answer by Mikael.Hagberg Thursday, August 15, 2013 8:04 AM

Good to know. Thanks for the update guys.

So what

now I got Exchange 2013 SP1 CU5

WARNING: Seeding of content index catalog for database '2013-DB-1' 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-BE3466A6-1DF5-424B-A26C-9E6E4C73121E12/Single that could accept the message. This is often caused
by an incorrect address or SOAP action. See InnerException, if present, for more details..

Even on CU7 it exists. I don't know when Microsoft will stop push updates that causes their own product to not function properly. 

If you're going to Install Exchange 2013. don't install CU7. CU6 will work but not CU7. It's full of Fastfeeder and indexing issues.