KB ID 0001228
Problem
I usually follow my own documented process for migrating public folders to Exchange 2016. I did that this week, and this happened;
Error;
[box]
MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=-2147221231) Diagnostic context: Lid: 49064 dwParam: 0x1 Lid: 37288 StoreEc: 0x6AB Lid: 49064 dwParam: 0x2 Lid: 49191 EMSMDBMT.EcDoConnectEx called [length=178] Lid: 48679 EMSMDBMT.EcDoConnectEx returned [ec=0x80040111][length=56][latency=0] Lid: 45169 StoreEc: 0x80040111 Lid: 50544 ClientVersion: 15.1.225.42 Lid: 52080 StoreEc: 0x80040111 Lid: 1494 ---- Remote Context Beg ---- Lid: 22086 Lid: 27206 Lid: 39869 Lid: 56893 StoreEc: 0x8004010F Lid: 44989 Lid: 24684 Lid: 20076 StoreEc: 0x80040111 Lid: 29100 Lid: 20396 StoreEc: 0x80040111 Lid: 9486 StoreEc: 0x80040111 Lid: 24492 Lid: 18348 StoreEc: 0x80040111 Lid: 26540 dwParam: 0xE0003 Lid: 22444 dwParam: 0xC30001 Lid: 1750 ---- Remote Context End ---- Lid: 51152 Lid: 52465 StoreEc: 0x80040111 Lid: 60065 Lid: 33777 StoreEc: 0x80040111 Lid: 59805 Lid: 52487 StoreEc: 0x80040111 Lid: 19778 Lid: 27970 StoreEc: 0x80040111 Lid: 17730 Lid: 25922 StoreEc: 0x80040111 + CategoryInfo : NotSpecified: (:) [New-PublicFolderMigrationRequest], RemoteTransientException + FullyQualifiedErrorId : [Server={New-Server},RequestId=6cbefa76-98ad-4a2e-bb33-237d7fd795fd,TimeStamp=03/08/2016 7:1 7:17 PM] [FailureCategory=Cmdlet-MapiExceptionLogonFailed] 42728F13,Microsoft.Exchange.Management.Migraion.NewMgrationBatch + PSComputerName : {new-server}
[/box]
Solution
Although it looks a pretty scary error, it’s quite straightforward to rectify. I was doing a migration and I’d moved all the mailboxes already, so I had dismounted and removed the mailbox database on the source Exchange server. (Exchange 2010). All I had to to was mount a mailbox database (I just created a new empty one, and mounted it.)
If I then tried to do the migration, it queued up properly!
Related Articles, References, Credits, or External Links
NA