Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
Tried several mailboxes. Same result.
Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
Ex 2013 is SP1 aka CU4.
How to proceed???
john11

After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
What did work:
1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
of the four mailboxes. The other 3 failed.
2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
3. Then on the Exchange 2013 box, use this Exchange shell command:
New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
Get-MoveRequest
The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
Thanks for the suggestions. I had to get this done and the MS Tech made that happen.
john11

Similar Messages

Move mailbox from exchange 2010 2003 , Transient error MapiExceptionLogonFailed has occurred.

We are currently migrating from Exchange 2003 to Exchange 2010, same domain.
We have successfully moved some mailboxes from exchange 2003 to exchange 2010 without any problems.
Now we need to move 1 mailbox back from exchange 2010 to exchange 2003.
After creating the moverequest it stucks on 0% and the log shows the error below.
After using Bing I found this post -> http://social.technet.microsoft.com/Forums/exchange/en-US/ef41ae05-8816-4c0c-968a-c48f0e3d50b5/move-mailbox-back-from-exchange-2010-to-exchange-2003-failure?forum=exchangesvrdeploylegacy
This suggest ->
After I give FULL permissions to each Mailbox Stores on Exchange 2003 server, I was able to move my mailbox back onto the Exchange 2003 server. In details:
Simply right click Storage Group\Mailbox Store and go to Security, in there you may see Exchange Servers group already there, if no add it in, then give it FULL permissions! and thats it!
Create a new move request but still stuck on 0% and error as below
20-3-2014 16:32:10 [ex2010p11] 'contoso.com/Users/exadmin' created move request.
20-3-2014 16:32:11 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'exchangep21.contoso.com' (14.3.151.0 caps:07) is examining the request.
20-3-2014 16:32:11 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
20-3-2014 16:32:11 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
20-3-2014 16:32:11 [ex2010p21] Request processing started.
20-3-2014 16:32:11 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (1/60).
Error details: MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=1010)
Diagnostic context:
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: ex2003
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -545057711
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662
Lid: 45169 StoreEc: 0x824
Lid: 44273
Lid: 59431 EMSMDB.EcDoConnectEx called [length=163]
Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
Lid: 56945
Lid: 59431 EMSMDB.EcDoConnectEx called [length=163]
Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
Lid: 59505 StoreEc: 0x3F2
Lid: 52465 StoreEc: 0x3F2
Lid: 60065
Lid: 33777 StoreEc: 0x3F2
Lid: 59805
Lid: 52209 StoreEc: 0x3F2
Lid: 56583
Lid: 52487 StoreEc: 0x3F2
Lid: 19778
Lid: 27970 StoreEc: 0x3F2
Lid: 17730
Lid: 25922 StoreEc: 0x3F2
at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
at Microsoft.Mapi.ExRpcConnection.Create(ConnectionCache connectionCache, ExRpcConnectionCreateFlag createFlags, ConnectFlag connectFlags, String serverDn, String userDn, String user, String domain, String password, String httpProxyServerName,
Int32 ulConMod, Int32 lcidString, Int32 lcidSort, Int32 cpid, Int32 cReconnectIntervalInMins, Int32 cbRpcBufferSize, Int32 cbAuxBufferSize, Client xropClient, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, String mailboxDn, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo,
WindowsIdentity windowsIdentity, String applicationId)
at Microsoft.Exchange.MailboxReplicationService.MapiUtils.OpenSystemMailbox(Guid mdbGuid, String serverDN, String dcName, NetworkCredential cred, String& systemMailboxDn)
at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.OpenSystemMailbox()
at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncStateStr)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass57.<Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState>b__56()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncState)
at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.ClearSyncState()
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass23.<CleanupOrphanedDestinationMailbox>b__22(MailboxMover mbxCtx)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CleanupOrphanedDestinationMailbox(Object[] wiParams)
at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: IMailbox.SaveSyncState
OperationSide: Target
Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)
Key: F2FA63B0116C564EA4C598D69786443D9E4FB582FF27D2449142F949D567E1E7E0CA914F6695624C98892FA527AAA91E
SyncStateLength: 0
20-3-2014 16:32:41 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'ex2010p21.contoso.com' (14.3.151.0 caps:07) is examining the request.
20-3-2014 16:32:41 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
20-3-2014 16:32:41 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
20-3-2014 16:32:41 [ex2010p21] Request processing started.
20-3-2014 16:32:41 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (2/60).

Hello，
When you move mailbox from exchange 2010 to exchange 2003, please check if the following situations exist:
http://technet.microsoft.com/en-us/library/dd638157(v=exchg.141).aspx
Before you move mailbox again, please clear the previous move request.
I recommend you use EXBPA to check your exchange server 2003 and exchange 2010.
Please check if inheritable permission is missing on the mailbox store on Exchange Server 2003.
Cara Chen
TechNet Community Support

Move mailbox from Exchange 2010 SP3

Hi all. I implemented Exchange 2013 in my current Exchnage 2010 environment, update this server to version 15.0 build 847.32. Build Exch2010 - 14.3 (build 123.4). Then i move mailbox from exch2010 to exch2013 this request all time "queued" and
not migrate to exch2013:
PS C:\Windows\system32> Get-MoveRequestStatistics Scom
DisplayName StatusDetail TotalMailboxSize TotalArchiveSize
PercentComplete
scom Queued 575.3 KB (589,056 bytes)
0
I restart services Microsoft Exchange Replication, Microsoft Exchange Search, Microsoft Exchange Search Host Controller, but no result(

PS C:\Windows\system32> Get-MoveRequestStatistics Scom | FL
RunspaceId : 64b764aa-8b7c-435e-8bb7-2b5fbe3692ba
MailboxIdentity : polikomm.local/Users/scom
DistinguishedName : CN=scom,CN=Users,DC=polikomm,DC=local
DisplayName : scom
Alias : scom
ExchangeGuid : ed423e14-5c3b-42a8-910d-48fa6e7c4335
ArchiveGuid :
Status : Queued
StatusDetail : Queued
SyncStage : None
Flags : IntraOrg, Pull
RequestStyle : IntraOrg
Direction : Pull
IsOffline : False
Protect : False
DoNotPreserveMailboxSignature : False
Priority : Normal
WorkloadType : Local
Suspend : False
SuspendWhenReadyToComplete : False
IgnoreRuleLimitErrors : False
RecipientTypeDetails : UserMailbox
SourceVersion : Version 14.3 (Build 210.0)
SourceDatabase : Mailbox Database
SourceServer : pc-mail.polikomm.local
TargetVersion : Version 15.0 (Build 847.0)
TargetDatabase : Mailbox Database 0506035495
TargetServer : EXCHANGE2013.polikomm.local
SourceArchiveDatabase :
SourceArchiveVersion :
SourceArchiveServer :
TargetArchiveDatabase :
TargetArchiveVersion :
TargetArchiveServer :
RemoteHostName :
RemoteGlobalCatalog :
BatchName : MigrationService:MoveSCOM
StartAfter :
CompleteAfter :
RemoteCredentialUsername :
RemoteDatabaseName :
RemoteDatabaseGuid :
RemoteArchiveDatabaseName :
RemoteArchiveDatabaseGuid :
TargetDeliveryDomain :
ArchiveDomain :
BadItemLimit : 1000
BadItemsEncountered : 0
LargeItemLimit : 0
LargeItemsEncountered : 0
AllowLargeItems : True
QueuedTimestamp : 15.01.2015 14:46:18
StartTimestamp :
LastUpdateTimestamp : 15.01.2015 14:46:18
InitialSeedingCompletedTimestamp :
FinalSyncTimestamp :
CompletionTimestamp :
SuspendedTimestamp :
OverallDuration : 07:20:29
TotalFinalizationDuration :
TotalDataReplicationWaitDuration :
TotalSuspendedDuration :
TotalFailedDuration :
TotalQueuedDuration : 07:20:29
TotalInProgressDuration :
TotalStalledDueToCIDuration :
TotalStalledDueToHADuration :
TotalStalledDueToMailboxLockedDuration :
TotalStalledDueToReadThrottle :
TotalStalledDueToWriteThrottle :
TotalStalledDueToReadCpu :
TotalStalledDueToWriteCpu :
TotalStalledDueToReadUnknown :
TotalStalledDueToWriteUnknown :
TotalTransientFailureDuration :
TotalProxyBackoffDuration :
TotalIdleDuration :
MRSServerName :
TotalMailboxSize : 575.3 KB (589,056 bytes)
TotalMailboxItemCount : 122
TotalArchiveSize :
TotalArchiveItemCount :
BytesTransferred :
BytesTransferredPerMinute :
ItemsTransferred :
PercentComplete : 0
CompletedRequestAgeLimit : 7.00:00:00
PositionInQueue : 1/1 (Position/Queue Length)
InternalFlags : SkipFolderPromotedProperties, WordBreak
FailureCode :
FailureType :
FailureSide :
Message :
FailureTimestamp :
IsValid : True
ValidationMessage :
RequestGuid : 1b2dc64c-685d-4a60-be75-6c09efdbd1da
RequestQueue : Mailbox Database 0506035495
Identity : polikomm.local/Users/scom
DiagnosticInfo :
Report :
ObjectState : New
statusDetail "Queued"

Move Mailboxes from Exchange 2007 to Exchange 2013 (Could not find a valid mailbox migration for esta organization)

Hi all, I am in full migration from Exchange 2007 to Exchange 2013 and everything went correctly.
I have migrated several mailboxes and are working well. But a few days ago, when I try to migrate a mailbox I get the following error and can not migrate:
"Could not find a valid mailbox migration for this organization"
Do you know that you can be?
regards
Microsoft Certified IT Professional Server Administrator

Hi,
From your description, the issue should be related to the migration mailbox. I recommend you check if the following account is existed in ADUC.
Migration.8f3e7716-2011-43e4-96b1-aba62d229136
If this account does not exist, you need to run setup /prepareAD and then enable this migration mailbox to check the result.
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

Move Mailbox from Exchange 2007 to 2013 creates additional Contacts and Junk E-mail folders in Outlook Clients

I have moved a handful of mailboxes from my Exchange 2007 server to my new Exchange 2013 server. When the users logon to Outlook, usually Outlook 2007 Pro, they have a new default Contacts folder and Junk Email folder that are empty. I
have to copy all the user's contacts into the new default folder and delete the old one. Not sure why this is happening. Any information would be appreciated. Thanks.

Are you sure your Outlook 2007 is compatible with Exchange 2013?
http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
http://support.microsoft.com/default.aspx?kbid=2687404
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Can no longer send mail from exchange account

My send mail icon is now greyed out and I can no longer send mail. The only thing that I have done that I never do is I selected the "synchronize" option on the mailbox name after right clicking on it last night.
As far as Mail goes, I attempted to set up a MediaCom email box several days ago that never worked correctly, but I changed no settings on the exchange account and it was working great 24 hours ago. I've deleted the MediaCom email box.
Tried the usual quitting, rebooting but nothing is working, any ideas why this started and how to fix.
Mark

It is possible the Evil Starbucks empire has blocked SMTP sending as an antispam measure. You would need to log in to your email server using the smtpauth protocol. For example, Earthlink has an smtpauth.earthlink.net server for secure sending, which I was able to use sending from any public AP. Possibly T-Mobile has a similar authorized server.
But nowadays I just use Gmail, they make it easy and reliable to send from anywhere because they use a custom smtp port. Yeah, Gmail solved a multitude of problems with mobile sending.
Aluminum PowerBook Mac OS X (10.4.7)

Cannot Move Mailbox from Exchange 2003 to Exchange 2007

Hello,
I am migrating exchange 2003 to Exchange 2007 and have moved almost all the mailboxes without any issue, but there are some mailboxes which are not being moved since they are giving me the below error.
Error:
Error was found for John Doe ([email protected]) because: Error occurred in the step: Opening source mailbox. Failed to open mailbox with error: ClassFactory cannot supply requested class, error code: -1056749262
Initially I found that the account was disabled from Active
Directory so enabled it but and also replicated the active Directory but still the problem is there, its not hidden in the GAL aswell.
http://www.arabitpro.com

Thanks everybody .. I have solved the problem myself.
To resolve this issue I had to give the account "SELF" permissions for "Associated external account". If the user does not have these
permissions to its own account it is unable to set the msExchMasterAccountSID attribute for the disabled account causing the error. By setting this permission on the disabled account, it allows it to mark the msExchMasterAccountSID attribute.
To do this follow this procedure:
1. In the Active Directory Users and Computers snap-in, on the View menu, click Advanced Features.
2. In the Exchange Advanced properties of the disabled user object that owns the mailbox, click Mailbox Rights, and then search the list of accounts for one
that has the Associated External Account permission.
4. If no account has this permission, grant the SELF account Associated External Account and Full Mailbox Access permissions.
https://support.microsoft.com/kb/278966?wa=wsignin1.0
http://www.arabitpro.com

Migrate mailboxes from Exchange 2013 to Exchange 2010

Hello,
We have a merger and would like to know if it is possible to migrate mailboxes from Exchange 2013 to Exchange 2010 in a cross-forest scenario.
Or should we first upgrade destination Exchange 2010 to 2013?
Peteris

Hi Peteris,
Based on my tests, we can move mailboxes from Exchange Server 2013 to Exchange server 2010. You can use the Prepare-MoveRequest.ps1 script in the EMS to prepare mailboxes for cross forest moves.
For more information about it, here is a helpful article for your reference.
Prepare mailboxes for cross-forest moves using the Prepare-MoveRequest.ps1 script in the Shell
http://technet.microsoft.com/en-us/library/ee861103(v=exchg.150).aspx
Hope my clarification can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

OST corrupt when moving Mailbox from Exchange 2010 to Exchange 2010

Anyone come across this?
Moving a mailbox on Exchange 2010 to Exchange 2013 - the outlook client wont connect, if you remove the OST and allow outlook to recreate it comes good again.
outlook client knows the mailbox has moved as it connects to the new server
Not happening to every mailbox
thak=nks

Hi,
After you move mailbox from Exchange 2010 to Exchange 2013, Outlook should still work.
Is there any error message when these affected users try to connect? If there is, please post here for further analysis.
I saw someone failed to connect to the new Exchange server after they moved mailbox, then they restarted the Microsoft Exchange Information Store service and restarted Outlook, it worked.
If you haven't tried this, you can restart the Microsoft Exchange Information Store service to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Move from HIS 2010 to HIS 2013

We are in a process of upgrading our servers to Windows Server 2012. This is done by installing new servers. We will install HIS 2013 on Windows 2012 Server . We have a lot of HIS 2010 objects (both WIP and HIP) which we want to move over. WIP objects
are currently hosted as ASP.NET Worker process on HIS 2010. Is it possible to move these objects to HIS 2013 just using generated dll's from VS 2010/HIS 2010 ? I know that it is possible to upgrade 2010 to 2013, but we have installed an empty HIS 2013, and
want to do a "move" from HIS 2010 and run 2010/2013 in parallel. I am also looking for docs how to "Connect" HIS 2013 to IIS using TICT to IIS as we did in TI in HIS 2010 when we deployed Objects hosted as ASP.NET Worker process.
Jan Terje

Hello Jan,
I've done this kind of migration last year with more than 1500 TI Objects :-)
Yes, it's possible to move easy from HIS 2010 to HIS 2013 by converting the TI Objects using the TIConversionTool (C:\Program Files\Microsoft Host Integration Server 2013\SysWow64).
The Problem with the TIConversionTool is that it doesn't replace directly the assemblies but it creates a folder structure with the converter TI Object. It's also possible to Open the HIS 2010 TI Objects in Visual Studio 2010/2012 with HIS 2013. The Objects
will be converted after you are saving again the Assemblies.
In addition you have to change your web.config files because the HIS Assembly Version has changed from 7.0 to 9.0.
Please let me know if you need more information or help !
Best Regards,
Steve Melan - BCEE My Blog : http://stevemelan.wordpress.com

I have accidentally deleted the trash bin in my mailbox and can no longer move any deleted mail into the trash. I thought I was removing all the emails from the trash but somehow managed to delete the bin instead. Does anyone know who to reinstate it?

I have accidentally deleted the trash bin in my mailbox and can no longer move any deleted mail into the trash. I thought I was removing all the emails from the trash bin but somehow managed to delete the bin instead. Does anyone know who to reinstate the bin?

You are running 10.6.8? If yes, I assume you have your install disks? As the trash bin is part of Mail app and that is an integral part of the OS, the only way I know to get it back is to reinstall the OS. You won't lose any files, just reinstall the OS over the top of the current system.

Cannot move more than 2 mailboxes from exchange 2007 to Exchange 2013

I have been trying to move mailboxes from ex2007 to ex2013with the new-migrationbatch and the new-moverequest command.
I have a DAG-cluster with two servers with all roles.
What happens is that I cannot get more than two concurrent mailbox moves. If I restart the MRS-service nothing happens. I have changed the config-file for the mailbox replication service and currently have these settings:
MaxMoveHistoryLength="5"
MaxActiveMovesPerSourceMDB="20"
MaxActiveMovesPerTargetMDB="20"
MaxActiveMovesPerSourceServer="100"
MaxActiveMovesPerTargetServer="100"
MaxTotalRequestsPerMRS="100"
What is funny is that when I start a new batch with autocomplete off, only two mailboxes goes to 95% and the rest of them is not even started.
The command I use is New-Migrationbatch -local -Name TestNew -csvdata ([System.IO.File]::ReadAllBytes("c:\temp\exchange\migration\testmigration.txt")) -targetdatabases mdb001,mdb002 -autostart
Here is the output of Get-MigrationConfig | fl
RunspaceId : d382f8a7-924a-4f0e-812e-f18970b632e2
Identity :
MaxNumberOfBatches : 100
MaxConcurrentMigrations : Unlimited
Features : MultiBatch
CanSubmitNewBatch : True
SupportsCutover : False
I have off course restarted both servers and services.

Just out of curiosity, on which server you made these changes? Mailbox or CAS? And on Target or Source Server?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Cannot transfer mailbox from Exchange 2007 to Exchange 2013

Error message I get is below:
Any one got the same issue?
It was working fine a few days ago,suddenly cannot move mailboxes.
-Tried to create another database in case it has a limit: same issue
-tried to move from GUI and shell same issue.
MigrationTransientException: The call to ‎'net.tcp://domain.local/Microsoft.Exchange.MailboxReplicationService.ProxyService domain.local ‎(15.0.995.28 caps:017FFFFFCB07FFFF)‎‎' timed out.
Error details: This request operation sent to net.tcp://domain.local/Microsoft.Exchange.MailboxReplicationService.ProxyService did not receive a reply within the configured timeout ‎(00:00:50)‎.
The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message.
Please consider increasing the operation timeout ‎(by casting the channel/proxy to IContextChannel and setting the OperationTimeout property)‎ and ensure that the service is able to connect to the client. -->
The call to ‎'net.tcp://lnp-exch2013.loopartners.local/Microsoft.Exchange.MailboxReplicationService.ProxyService domain.local ‎(15.0.995.28 caps:017FFFFFCB07FFFF)‎‎' timed out. Error details:

Hi,
I recommend you refer to the following article:
http://blogs.technet.com/b/asiasupp/archive/2011/06/23/when-you-attempt-to-move-mailbox-from-to-exchange-online-you-receive-the-error-quot-the-call-to-microsoft-exchange-mailboxreplicationservice-timed-out-quot.aspx
Cause:
The DataImportTimeout property may be set too low.
Resolution:
To isolate the issue, you may check how it works if you increase the timeout with the following steps:
On the Client Access server, open the following file with a text editor such as Notepad:
\ExchWeb\EWS\web.config
Locate the following section in the web.config file:

<MRSProxyConfiguration
IsEnabled="true"
MaxMRSConnections="100"
DataImportTimeout="00:01:00" />
Make sure value of the IsEnabled property is set to true.
Check the value of the DataImportTimeout property. The minimum value is one minute (00:01:00), and the maximum value is 30 minutes (00:30:00).
Set a higher value, but make sure the value is less than 30 minutes.
The recommended value for this field should be 00:20:00 (20 minutes).
After the values are configured correctly, save and close the web.config file.
Niko Cheng
TechNet Community Support

Moving mailbox from exchange 2013 back to exchange 2007 ..

Hi Guys,
I recently configured configured co-existence between exchange 2007 and exchange 2013. I moved a pilot user from exchange 2007 to exchange 2013 and now the user has issues receiving mails.
I am trying to move the user back to 2007 pending the resolution of the issue. The move status says completed but the mailbox remains in the exchange 2013 environment.
I need to return the user to an exchange 2007 mailbox database ..any ideas on what I am missing.
Thanx guys ..
~Richard
..forever is just a minute away*

Hi Richard,
Please move your mailbox from Exchange 2013 to 2007 from the Exchange 2013 admin center (EAC) and the Exchange Management Shell instead of EMC in Exchange 2007.
Then check whether the issue persists. If possible, please provide more error logs for further analysis.
Regards,
Winnie Liang
TechNet Community Support

Getting error when I try to remove eum secondary email address from the Mailbox from Exchange 2013 server

Getting error when I try to remove eum secondary email address from the Mailbox from Exchange 2013 server. The command works if you issue directly from the server exchange shell.
I open the remote power shell to the exchange server 2013.
Issue the following commands and getting the following error.
$mailbox = Get-Mailbox -Identity testuser$mailbox.EmailAddresses -= "eum:50004;phone-context=telExt5digits.lync5.com"Then getting the following error:Method invocation failed because [System.Collections.ArrayList] doesn't contain a method named 'op_Subtraction'.
At line:1 char:27
+ $mailbox.EmailAddresses -= <<<< "eum:50004;phone-context=telExt5digits.lync5.com"
+ CategoryInfo : InvalidOperation: (op_Subtraction:String) [], RuntimeException
+ FullyQualifiedErrorId : MethodNotFoundHelp!

Now for an answer - your remote session doesn't have the same object you have on the server itself. Notice it says this is an array list, not a ProxyAddressCollection. If you need to work around this, you'll need to massage the addresses another
way that the system will accept. I'd try the following:
$NewAddresses = $mailboxEmailAddresses | ? { $_ -notlike "eum:50004;phone-context=telExt5digits.lync5.com" }
See what you get in the $NewAddresses variable when you do this.

Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

Similar Messages

Maybe you are looking for