MAgE Mailbox Migration fails with "internal error occurred." (4219673)

MAgE Mailbox Migration fails with "internal error occurred."

Several errors may occur in either the MAgE logs or be displayed within the QMM Console status column when trying to migrate mailboxes. 

1. In the QMM console you may see:  "Internal Error Occured. Try again later" 

In the logs:  "EWS:  EWS Connect. Url: https://mail.cphs.org/EWS/Exchange.asmx Username:  Mailbox: LAnselmo@cphs.org Error   An internal server error occurred. Try again later.   at Microsoft.Exchange.WebServices.Data.ServiceResponse.InternalThrowIfNecessary()"

2. "The mailbox with GUID "<mailbox guid>" caused crash or resource outage on database (GUID="<database guid>")"

This problem may occur when the 8.10 QMM console and MAgE agent have not been properly patched. QMM 8.10. may require the latest patch to resolve these errors effectively.

Patch both the QMM 8.10 console AND any server with the MAgE agent installed to resolve this issue.  These require different files as outlined below.  Follow instructions carefully.

You can login and download patches from our site: http://www.quest.com

NOTE:  Remember that the MAgE agent must be updated with a separate patch file.  server itself. following files. msp.    When the console itself it updated.

On the computer where the Migration Manager console is installed, complete the following steps:

1. Close the Migration Manager console if it is running.
2. Open the Services MMC snap-in and stop all services provided by Quest.
3. Run the QuestMigrationManager_8.10_Update20130829EX.exe file and complete the update setup wizard.
4. If you stopped any services on step 2, start them again.
5. Run the Migration Manager console, then right-click Exchange Migration Project on the Exchange Data tab and select the Hotfix Installation Wizard from the shortcut menu.
6. Follow the wizard steps to install the hotfix on all computers with the components that need to be updated. The list of updated components is different depending on the updates that are already installed in your environment. Refer to this readme file and the readme files from the previous updates in order to define the list of the updated components in your particular situation.

If you use Native Move or migrate to Office 365 or Exchange Server 2013, update all Migration Agents for Exchange (MAgE) agents:

1. Stop MAgE agents on all agent hosts.
2. Stop all COM+ applications that are used by MAgE agents. For that, go to Start | Administrative Tools | Component Services to open the Component Services console. In the console treeview, go to Component Services | Computers | My Computer | COM+ Applications, then right-click the Quest Migration Agent for Exchange MAPI Assistant node and select Shut down.
3. Run the MAgE_Update20130829EX.msp file on all hosts where the MAgE agents are installed (including Migration Manager console host). This file resides on the computer where the Migration Manager Console is installed in the following folder: %ProgramFiles%\Quest Software\Migration Manager\Exchange Data\Hotfixes. (Get this file and take it to the MAgE server location)
4. Start all MAgE agents that were stopped.

The installation does not affect existing settings. All your projects remain intact and can be continued after installation.

NOTE: You will need to apply the fresh MSP patch file even after you install a new MAgE on a host from an updated QMM console. In the next 8.10 update, after applying that update, all new installations of MAgE will be pushed to host with latest patches already included. This functionality does not exist as of update: QuestMigrationManager_8.10_Update20130829EX.exe But not now, sorry.