Exchange 2013: mailbox migration stays in "synchronizing"
Posted on 2016-11-08
I'm cleaning up the mess at a new customers site. They are running a single Exchange 2013 with about 30 mailboxes. The server has a second database named "archive" that is located on an iSCSI volume which resides on a QNAP NAS across a 100Mbit link.
I created a new virtual disk on this VMware VM, unmounted the database, transferred all files to the new disk, unmounted the iSCSI link and gave the new disk the drive letter of the iSCSI disk. Mounted the database, all is well.
The database is a mere 12GB. I now started the migration of a first user with a mailbox of 75MB. One single user only, moving him to the "real" database. I get no errors, but over the course of 12 hours and more, the migration job stays at "synchronizing".
In the event log of the server I am seeing the following events:
1006 Critical: Performance counter lists the free space for each drive, which is 26GB for the root drive, 166GB for the real database drive, 38GB for the temp drive and 178GB for the temporary db drive. I see no problem in this, but the event is "Critical". It does not say that there isn't enough space.
1009 Warning: Database indexing on both databases. The message is in German, but it continues in English:
Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Core.Abstraction.CatalogReseedException: Some of the notifications for database '00d572c8-442a-47c2-ae0d-f618a75758a6 (archiv)' are missing. Requesting a reseed.
bei Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object state)
--- Ende der internen Ausnahmestapelüberwachung ---
bei Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)
bei Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult asyncResult)
6002: Ping of mdb 'ID' timed out after '00:00:00' minutes. Last successful ping was at 08.11.2016 07:35:31 UTC
Also some 12014 events saying that self-signed certificates are missing so that STARTTLS-SMTP cannot be used.
What can be the reason?