Migration Agent for Exchange (MAgE) logs the following error when connecting to source or target mailbox:
There might be several causes for this:
1) The service account, defined in the Mailbox (or Calendar) Synchronization job Properties for source or target, does not have Impersonation permissions to source or target mailboxes.
2) The Autodiscover URL the MAGE connects to resturns incorrect external EWS URL (in the Problem Description section it is shown in the following trace:
M706 Trace Get user settings results : (UserDeploymentId) : 4b88b8cc-70fb-4b0d-839f-529bbddf7ea1; (InternalEwsUrl) : https://<target_EWS>/EWS/Exchange.asmx; (ExternalEwsUrl) : https://<souce_EWS>/ews/exchange.asmx; )
where the internal URL points to the target Exchange and the external URL points to the source or any other wrong server.
Since MAGE uses the external EWS URL (if exists) it appears that it is unable to connect to a mailbox.
Resolution 1:
Ensure the service account defined in the Mailbox (or Calendar) Synchronization job Properties for source or target Exchange, meets the following requirements:
Resolution 2:
Run Get-WebServicesVirtualDirectory |fl in your source or target depending on where the issue occurs and check what the internal and external URLs of the Virtual Directory are pointing to. If you see the external URL is pointing to the wrong server and internal one is ponting to the right one, you can just remove the external URL. If both are pointing to the wrong servers, reconfigure the Exchange virtual directories to point to the right exchange servers.
For Exchange 2013 or later you can use the TechNet Article below to configure both the Internal and External URI's to the same place.
http://technet.microsoft.com/library/jj218640(EXCHG.150)
To configure the external URI's follow the steps below.
You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "<Service> virtual directory settings" entry in the Clients and Mobile Devices Permissions topic.
Before clients can connect to your new server from the Internet, you need to configure the external domains, or URLs, on the Client Access server's virtual directories and then configure your public domain name service (DNS) records. The steps below configure the same external domain on the external URL of each virtual directory. If you want to configure different external domains on one or more virtual directory external URLs, you need to configure the external URLs manually. For more information, see Virtual Directory Management.
For Exchange 2010 run the following cmdlet:
Set-WebServicesVirtualDirectory -Identity Contoso\EWS(Default Web Site)-ExternalUrl https://www.contoso.com/EWS/exchange.asmx -BasicAuthentication $true -InternalUrl https://contoso.internal.com/EWS/exchange.asmx
Error thread similar to: Microsoft.Exchange.WebServices.Data.ServiceResponseException: Unable to access an account or mailbox.
Exchange Server 2010 does not allow external accounts to be given impersonation rights, so in a scenario where single service account is in use for source and target organizations and that account is a member of the target domain, you may need to fall back to using MAPI to connect to source Exchange 2010 server. You can do this by setting the migration project option using powershell command Set-MMExProjectOptions -UseEwsProtocolForSourceIfAvailable $false
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center