How to Fix MapiExceptionNoAccess Error when Migrating to Office 365?

Let’s take a scenario. An Exchange Server 2010 is installed on a legacy Windows Server 2008 R2 server and updated to the latest security and cumulative updates. Since this is old, there is a need to migrate Exchange Server 2010 to Office 365. An additional Exchange Server 2016 (which can coexist with Exchange Server 2010) is added, along with Windows Server 2016.

An Azure AD Connect is installed to allow to synchronize the users and passwords with Office 365 and to ensure that the same users are on the Exchange Online tenant. After this is complete, the Hybrid Configuration Wizard is installed and configured. The setup is successful with no issues. During the setting up of the wizard, the Exchange Server 2010 was chosen as the data source as this is still the main server to receive emails and is accessible from outside, with all the certificates and Outlook Anywhere configured.

The first migration batch is created and the synchronization is started with a test mailbox. After it started, the following error message appeared:

User status
Data migrated:
Migration rate:
Last successful sync date:
Error: MapiExceptionNoAccess: MapiExceptionNoAccess: Unable to open message store. ‎(hr=0x80070005, ec=-2147024891)‎ Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=223] Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=288][latency=2] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropLogon [254] Lid: 17082 ROP Error: 0x80070005 Lid: 26937 Lid: 21921 StoreEc: 0x80070005 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 45112 StoreEc: 0x80070005 Lid: 56872 dwParam: 0xFE Lid: 42712 StoreEc: 0x80070005 Lid: 45434 Unknown record layout: 00000008 Lid: 10786 dwParam: 0x0 Msg: 15.01.2242.004:VM--MFEXCH01:0b5371fd-241d-49a5-86a0-64d60a9f90b0 Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid: 21817 ROP Failure: 0x80070005 Lid: 26297 Lid: 16585 StoreEc: 0x80070005 Lid: 32441 Lid: 1706 StoreEc: 0x80070005 Lid: 24761 Lid: 20665 StoreEc: 0x80070005 Lid: 25785 Lid: 29881 StoreEc: 0x80070005

Possible Solutions to Fix the MapiExceptionNoAccess Error

There could be issues on the Exchange Server 2010 or the Exchange Server 2016. The first thing to do is to create a new mailbox on the Exchange Server 2010 (hosted on the same server) and another mailbox on the Exchange Server 2016 (hosted on the same server). Now, create two separate migration batches – one with the 2010 mailbox and the other with 2016. This will help you to determine if the problem resides on the legacy server or the new server.

There could also be problems with the legacy server. Although both Exchange Server 2010 and 2016 can coexist in the same forest, there could be situations where the MRS Proxy requests are being addressed to one server and not the other. To ensure that nothing is blocked, start the migration batch and run an analysis on the network, along with the network team, to see if there are any ports or traffic being blocked from and to the Exchange Server 2010 or the Exchange Server 2016. In most cases, the reason is that a router or firewall is dropping the requests to the Exchange Server. Running a packet trace from external to the Exchange Server 2010 helps to identify the ports or services, which are being blocked by these permitter devices.

Although Exchange Server 2010 would work with the Hybrid Migration Wizard, for compatibility and safety (since you already have a newer version of Exchange Server installed), you can first migrate to it and then migrate mailboxes from Exchange to Office 365. Apart from that, the Exchange Admin Center is better and easier to use than its predecessor.

Another option is to eliminate the Exchange Server 2016 from the scenario. This will not affect the Hybrid configuration that was set up. However, re-running the Hybrid Migration Wizard right after uninstall is strongly suggested.

To Conclude

As mentioned above, there could be issues with the permitter devices or the Exchange Server configuration. In addition, there could be other configurations issues and limitations that might be restricting you from starting the migration. In such cases, you can look for alternative solutions. You can use a third-party application, such as Stellar Converter for EDB for migration and to avoid the above-mentioned error.

With Stellar Converter for EDB, you can open multiple EDB files without MS Exchange Server, with no size limit and from any version of Exchange Server, without having an Exchange Server running. You can browse the data store and granularly export the EDB data to PST and other file formats. You can also directly export the data to another Exchange Server database or Office 365 tenant.

Was this article helpful?

YES0

NO

About The Author

Shelly Bhardwaj

I am a Product Consultant and is associated with Stellar Data Recovery from last 8 years. I write about the latest technology tips and provide custom solutions related to Exchange Server, Office 365, MS Outlook, and many other Email Clients & different flavors of OS Servers. Read More