Exchange 2013 Mailbox Move FailedOther

I am attempting to move 600 Mailboxes from my Exchange 2010 SP3 environment over to my Exchange 2013 environment all in all everything is going smooth Exchange is functioning properly.
I have successfully moved half of my users in which I found a problem with 2 accounts. The move status shows "FailedOther" at 95% complete. I have been searching the google for 2 days now and I have not found a solution to this problem. The user
account still shows that is on our old Exchange 2010 server. I have attempted to force restart the move but that fails and it says at FailedOther.
Has anyone seen this problem before? My Environment is as follows
1 Server Mailbox server EMS - Mail box roles - Specs 8 Procs, 14 GB of RAM running on a VM Server 2012 DC
1 Server Cas server - Client access server - 4 Procs, 12 GB Ram running on a VM Server 2012 DC
Exchange 2013 CU1 and all accumulative updates since CU1 release.
I read some where this was because I didn't have enough resources for the move which I then bumped up the server to the current specs and rebooted the VM. I restarted the move with
Get-MoveRequest | where{$_.Status -eq "FailedOther"} | Resume-MoveRequest
Do I need to remove this move request and start from the beginning or should this command work?

I actually figured out this problem on my own.
I did this to resolve problem.
Remove-MoveRequest -Identity username
New-MoveRequest -Identity "username" -TargetDatabase "MAILDatabase" -BatchName "Username" -BadItemLimit "200"
My research shows that our EMS server lost connection to our 2010 Exchange server during the finalization of the move which caused the move to fail. As the last 5% of the move is the clean up process of removing the mailbox and all items off of the old mail
server.
I hope this information is useful to someone else.
Incredible, that worked a treat. Many thanks for taking the time out to post this solution as about 10 of my 50mailboxes got to 95% and failed with this message and now they're working :)

Similar Messages

Exchange 2007 to exchange 2013 Mailbox Move problem

Data migrated:
Migration rate:
Error:MigrationPermanentException: Active Directory property ‎'homeMDB‎' is not writeable on recipient ‎'domain.org/ICT_Dept/Abu Bakar Siddikuzzaman‎(ICT-Mirpur)‎‎'. --> Active Directory property ‎'homeMDB‎' is not writeable on recipient
‎'domain.org/ICT_Dept/Abu Bakar Siddikuzzaman‎(ICT-Mirpur)‎‎'.
Md. Ramin Hossain

[PS] C:\Windows\system32>Get-Mailbox arahaman | New-MoveRequest -TargetDatabase "Head-Office"
Active Directory property 'homeMDB' is not writeable on recipient 'domain.org/ICT_Dept/Atikur Rahaman'.
+ CategoryInfo : NotSpecified: (:) [New-MoveRequest], RemotePermanentException
+ FullyQualifiedErrorId : [Server=HYPER-SUNMAIL,RequestId=fbb3dcab-54a3-423f-81b5-9c5c397b34b4,TimeStamp=7/2/2014
5:46:07 AM] [FailureCategory=Cmdlet-RemotePermanentException] 63F06918,Microsoft.Exchange.Management.RecipientTask
s.NewMoveRequest
+ PSComputerName : hyper-sunmail.domain.org
Md. Ramin Hossain

OWA Error after Exchange 2010 Mailbox move to 2013

Hello,
We have been experiencing an issue when we move a users mailbox from Exchange 2010 on-prem to Exchange 2013 on-prem. As a domain admin I was able to access the users mailbox via OWA 2010 with out issues. However, now that they have been
moved over to 2013 I am getting the following error message:
X-OWA-Error: SDServerErr;Microsoft.Exchange.Data.Storage.AccessDeniedException
X-OWA-Version: 15.0.995.28
X-FEServer: CASServer
X-BEServer: Mailboxserver.domain.com
Date: 1/29/2015 5:27:38 PM
Full Access permissions appear on the mailbox still via the 2013 ECP console for my account. I have tried running the
Set-Mailbox UserName -ApplyMandatoryProperties command but receive a message that no settings have been modified.
I have also tried to remove/re-add inheritable permissions on the users AD account to no avail.
I have a large group of mailboxes to move over to 2013 and hoping their is a decent solution out there to prevent this from happening.
Greatly appreciate any feedback on this request.
Cheers

Hi,
Please re-add the full access permission for the administrator:
Get-Exchange Server "servername" | Get-Mailbox | Add-MailboxPermission -User Administrator -AccessRights FullAccess
If Administrator is still located in Exchange 2010 and has the full access permission to an Exchange 2013 mailbox ([email protected]) which is moved from Exchange 2010, please use the following URL to open the mailbox:
https://Exch13.domain.com/owa/[email protected]/
Then check whether the issue persists.
Regards,
Winnie Liang
TechNet Community Support

Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence?

Hi Team,
I am in the phase of upgrading Exchange 2010 to 2013, and introduced 4 MBX and 2 CAS of 2013 servers in co-existence.
Only one production mailbox of 2010 moved to 2013. The owa of the mailbox moved to 2013, is working OK internally coz only internally configured, but when I configure outlook using 2010 settings, it got configured but when I open outlook it doesn't
open and throws an error of some "cannot open set of folders".
Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence? because I havnt configured 2013 CAS servers yet.
Kindly share some KB or tip. Any help is appreciated. Thank You.
Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

I'll change Adam's wording slightly - you *MUST* install a CAS 13 server into every site where there is a MBX 13 server.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
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.

Exchange 2010 mailbox prompts for authentication to Exchange 2013 mailbox

I am in the process of a 2010 to 2013 migration. The only issue I can't seem to manage is an authentication issue with Outlook 2010. My Outlook profile consists of my Exchange 2013 mailbox and a shared mailbox on Exchange 2010. Initially, Outlook was prompting
for authentication to the Exchange 2010 mailbox. Regardless of whether I entered the correct credentials or simply cancelled the prompt, I still had full access to both mailboxes (including Public Folders on 2010). The authentication prompt was removed with
the following command:
Get-OutlookAnywhere -Server my2013exchserver | Set-OutlookAnywhere -InternalClientsRequireSsl $true
The second issue I now have is the reverse of the above: an Exchange 2010 user is prompted for authentication to an Exchange 2013 mailbox. How do I begin to troubleshoot this problem - should I run the same command (above) on 2010? I don't quite understand
how Outlook communicates with Exchange but I am thinking there is an incorrect setting on one of the Virtual Directories(?).
Many thanks.

Hi Dennis,
Please open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar –Connection Status to check the connection for your Exchange 2010 mailbox with shared 2013 mailbox. The following example in my test results:
Please check your connection authentication. We can run the following command to set your Outlook Anywhere for Exchange 2013:
Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $True -InternalClientsRequireSsl $true
In Outlook side, please ensure the following settings in Account Settings:
In Security tab, make sure Always prompt for logon credentials is unchecked and Logon network security is set to Negotiate Authentication.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 Mailbox Role Installation Error

Hi All,
I am getting the below error when installing Exchange 2013 Mailbox Role. This is a Windows Server 2012. Previous Exchange 2013 setup was removed since it had issues with CAS. Now we have removed all previous Exchange software and attributes.
Error:
The following error was generated when "$error.Clear();
          Install-ExchangeCertificate -services IIS -DomainController $RoleDomainController
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
            Install-AuthCertificate -DomainController $RoleDomainController
        " was run: "Microsoft.Exchange.Management.Metabase.IISGeneralCOMException: An IIS directory entry couldn't be created. The error message is The system cannot find the path specified.
. HResult = -2147024893 ---> System.Runtime.InteropServices.COMException: The system cannot find the path specified.
   at System.DirectoryServices.DirectoryEntry
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.RefreshCache()
   at System.DirectoryServices.DirectoryEntry.FillCache(String propertyName)
   at System.DirectoryServices.PropertyCollection.KeysCollection.GetEnumerator()
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetWebSiteSslCertificate(String webObjectPath)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.FindIisCertificate()
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Any views on this is appreciated.
Regards
Boniface
Senior Systems Administrator

Hi,
After uninstalling the IIS, please run the following command to install prerequisites.
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45,
Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service,
Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
Then remove the “water mark” key and “action” key under the following registry and initiate the setup again.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15.0\HubTransportRole
In addition, please disable any third-part software for troublwshooting.
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]
Lynn-Li
TechNet Community Support

Exchange 2013 mailbox name resolving vs. exchange server name (mailbox rule)

Hello guys,
I am running exchange 2007 and exchange 2013 CU7 in hybrid mode, while internal autodiscover a record is pointing to exchange 2007 client rule server.
When I configure outlook mailbox located on exchange 2007- I can use autodiscover using mail address ore resolve mailbox name vs. exchange server name.
When I configure outlook mailbox located on exchange 2013- I can configure it only using autodiscover mechanism ( email address - next- next etc.).
We are using EMC backup software which works with MAPI. Since I wasn't able to restore granular mailboxes, I contacted EMC and they claimed that it's very important to configure mailboxes resolving.
What should I check and configure to make it work?

Hi,
I think if we want to browse single mailbox by backup software, it will be regard to resolve mailbox name using server name, I suggest you contact EMC supplier to improve it.
By the way, they I type mailbox name which located on exchange 2013 server database and typing exchange 2007 cluster name, server name of exchange 2007 cluster changes automatically to exchange 2013 server on which this mailbox located.
A: first, we should make sure cluster was worked without any problem. Then make sure Exchange 2013 mailbox server was included in cluster.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

How to introduce exchange 2013 mailbox server in an existing Exchange 2010 Environment

Hi All,
we are planning to install exchange 2013 mailbox server in an Exchange 2010 environment. we have 3 MB servers, 1 CAS 1 HUB which is installed with Exchange 2010 SP3 Enterprise Edition. how to install new exchange server 2013 and i have to add the 2013
servers in to existing DAG and migrate all mailboxes in to 2013 server. Please advise me from the scratch. also will it be create any impact in my existing setup.
Thanks, Venkatesh. "Hardwork Never Fails"

For a step by step follow the deployment assistant
http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-AAAAAAAAQAAAAAEAAAAAAAA%7e
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 mailbox moves get stalled

I am Experiencing an issue with Exchange 2010 SP3 UR2 two node DAG environment (server01 and server02). While moving mailboxes from old Exchange 2007 environment I get following errors.
Move for mailbox xxxxxxxxxxxx is stalled because DataMoveReplicationConstraint is not satisfied for the database 'MDB01' (agent MailboxDatabaseReplication). Failure Reason: Database does not satisfy constraint SecondCopy. Throttling completion as database copies
are falling behind.
Get-MailboxDatabaseCopyStatus informs me that server02 Copy and ReplayQueue length on the passive copy are getting big (from 10-500) while moving and the throttling will always pause the move for a while and then start again until it stops again because the
second copy is falling behind. This only happens when I move mailboxes to databases that have active copy of the database on my server01 and passive on server 02. If the active copy is moved to server02 and server01 is the passive copy this does not happen.
So this leads to a conclusion that there is something wrong with server02 replication from server01.
I've traced the replication network and there are no issues. What could be the reason that only the second node suffers from falling back during moves? I would not like to se the datamovereplicationconstraint value to none since this is the only Exhchange
2010 DAG environment where I am facing this issue and the replication should keep up while mailbox moves.

Hello,
" I would not like to see the datamovereplicationconstraint value to none". Do you mean you set
DataMoveReplicationConstraint to SecondCopy? If so, I recommend you use test-replicationhealth cmdlet to check all aspects of the replication and replay status.
Please check if you
configure a lagged database copy.
Please check if there is a witness server, and whether the witness is online.
If not, please set DataMoveReplicationConstraint to SecondCopy.
Besides, please check if there is any error in application log.
Here are some articles for your reference.
http://technet.microsoft.com/en-us/library/dd335158(v=exchg.150).aspx
http://blogs.technet.com/b/exchange/archive/2011/05/06/exchange-2010-mailbox-moves-and-mailbox-resiliency.aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Performance counters for exchange 2013 mailbox & cas servers?

what are the Performance counters for exchange 2013 mailbox & cas servers?
similar to rpc request for troubleshooting exchange slowness, I haven't found any technet article for exchange 2013.

Hi,
Please see this:
Ask the Perf Guy: Sizing Exchange 2013 Deployments
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
Hope it is what you need.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 mailbox added to the CAS array

We are upgrading to Exchange 2013 from Exchange 2010. Following the development guide, we have
installed the first mailbox server in the Exchange 2010 environment which has 3 Exchange 2010 CAS server
in the array. When installing the mailbox role, we did not choose the client access role but after
the installation we can see that the Exchange 2013 Mailbox server is added to the CAS array and yet
we did not choose the client access role. How does this happen, and to proceed ?

I see the same thing in my lab:
Get-ClientAccessArray | FL
RunspaceId        : 16b992b3-270f-4ae1-a3c3-fa9e2ea73d69
ExchangeLegacyDN : /o=Wingtiptoys/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Ou
                    tlook.wingtiptoys.ca
Fqdn              : Outlook.wingtiptoys.ca
Site              : wingtiptoys.ca/Configuration/Sites/Default-First-Site-Name
SiteName          : Default-First-Site-Name
Members           : {EXCH-2010, EXCH-2013}
AdminDisplayName :
ExchangeVersion   : 0.1 (8.0.535.0)
Name              : Outlook.wingtiptoys.ca
DistinguishedName : CN=Outlook.wingtiptoys.ca,CN=Arrays,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administr
                    ative Groups,CN=Wingtiptoys,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=wingtiptoys,DC=ca
Identity          : Outlook.wingtiptoys.ca
Guid              : 27968af1-1624-4ff3-85c8-e38e68183afe
ObjectCategory    : wingtiptoys.ca/Configuration/Schema/ms-Exch-Client-Access-Array-2
ObjectClass       : {top, server, msExchExchangeServer, msExchClientAccessArray}
WhenChanged       : 4/12/2014 12:51:18 PM
WhenCreated       : 4/12/2014 12:51:18 PM
WhenChangedUTC    : 4/12/2014 7:51:18 PM
WhenCreatedUTC    : 4/12/2014 7:51:18 PM
OrganizationId    :
OriginatingServer : DC-1.wingtiptoys.ca
IsValid           : True
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
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.

Exchange 2010 - 2013 Mailbox move - Syncing with no progress (Stalled?)

I'm in the process of moving mailboxes from Exchange 2010 to Exchange 2013, the major of the mailboxes have moved successfully, however I did not anticipate the additional space required by Exchange 2013 and ran out of disk space during the mailbox move,
and some mailboxes did not move successfully.
I have since added additional space but can't seem to get the remaining mailboxes to sync.
I have tried :
Rebooting
Clearing out migration batches and recreating
Stopping and resuming batches.
I see nothing helpful in the Migration log files.
2013-05-20T23:59:57.904Z,14,MigrationServicelet,Information,",827890ff-522d-4c13-9f42-96fbfefb57f4,,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.2724593, job :827890ff-522d-4c13-9f42-96fbfefb57f4:ExchangeLocalMove:Staged:4::SyncStarting:2013-05-17
2:59:12 PM::"
When I download the report for one of the users I see this, but don't know what it means :
The job is currently stalled due to 'Content Indexing' lagging behind on resource 'CiAgeOfLastNotification(Mailbox Database 2065686096)'
For one of the other users the downloaded report only shows :
2013-05-16
2:11:18 PM '' created move request.
DWW
Additional Info: I followed the info located here in regards to creating the ContentSubmitters group:
http://www.bullspit.co.uk/2013/04/08/exchange-2013-content-indexing-during-migration/
My mailbox database currently has Content index state: FailedAndSuspended
I only have one database, I am not using DAG

I had already created the contentsubmitters and it helped with the speed of the mailbox moves. We have a SMB with >100 users and everything was working great, migrating from 2007 to 2013. If I had it to do over, maybe it would have been better
to go to 2010 on a 2008 R2 box but decided to jsut go straight to 2013 on a 2012 R2 server. But the one thing I REALLY wish I had to do over again is to allocate about 3 times more space to the drive that was to hold the mailbox database. Everything
was working so well until a mailbox was being moved - a batch of several, I was doing maybe 5 at a time for the larger mailboxes - the disk filled up. Also, before I realized what was going on, I ran some cmdlets thinking my receive connectors weren't
right. I recovered the database - at first it would not mount at all... but after eseutil /r and /p (and allocating more disk space) I could mount the database and open the mailboxes. But from then on, nothing is being received and if you send,
it goes to sent items - doesn't hang in outbox, but never goes anyhere except into a queue. I have MS support working on it and it's been escalated to the top. If they fix it I will try to post any helpful information I can learn from it. But one
lesson - I will read the planning and preparations documentation thoroughly from now on.
Oh, and also, I keep getting this message in the ECP when navigating to the Recipients>migration applet:
Cannot open mailbox /o=<Organization>/ou=Exchange Asministrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/CN=<yourExchangeserver>/cn=Microsoft System Attendant.
If you did the same thing, (and didn't hang yourself or jump in front of a speeding locomotive), you are stronger than I. Not that I have taken the path of the Samurai network admin or anything....
And if you were able to fix it, I am impressed and would love to know how you fixed this.
Thanks and best,
Sam

Migrate mailbox from Exchange 2007 to Exchange 2013, mailbox stay in queue

Hi,
I'm trying to migrate a mailbox but the request is staying in queue, according to : Get-moverequest | Get-Moverequeststatistics
Configuration server Exchange 2007 SP3 :
Domain : test.com
OS : Windows 2008 server SP2 (not R2)
Firewall : OFF
Exchange roles are on separate three servers : CAS - MAILBOX - HUB.
Configuration Server Exchange 2013 :
Domain : new.com
OS: Windows 2012 R2
Firewall : OFF
This environment is on a closed network unable to reach internet.
I have try to restart the Replication service, but it didn't worked.
I've searched a lot but i can't find any information to help me. The mailbox stays in queue....
Anyone ever had this issue?
Thanks you and have a nice day.

Hi ,
Based on my knowledge below things need to checked.
1.Please check the content index state of the target database is healthy and ensure the entire mailbox database status was in healthy state.
2.If your exchange 2013 is an single server and target database copy doesn't have the second copy then we need to set the below parameter value to none.
DataMoveReplicationConstraint : None
Note : After the above change ,Microsoft exchange mailbox replication service needs to be restarted.
3.Restart the Microsoft exchange mailbox replication service and check the results.
4. Have you tried moving the same mailboxes to the different databases.
5.If the move request is in the failed state then we can export the details of the move request to find out the exact cause for the failure.
Get-MoveRequestStatistics -Identity "nithya" -IncludeReport | fl >c:\nithya.txt
Please feel free to reply me if you have any queries.
Thanks & Regards S.Nithyanandham

Exchange 2013 Mailbox Using 2010 Public Folders

Firstly, we will not be migrating completely to Exchange 2013 public folders for quite a while. Our first Ex2013 server is in a small branch office and won't be appropriate to hose the PF's for the entire company. Our environment consists of
8 Ex2010 servers and now the one Ex2013. I setup a test mailbox on the 2013 server and it access a 2010 PF database on another server just fine. How is that server discovered, and can we specify which one it uses? I understand the way 2013
public folders are moving but is there a downside to leaving our configuration this way for a long period of time?

Yes, the procedure should be followed to move mailbox first. Once you have successfully moved all the mailbox to new exchange server, you can migrate public folder after that.
You can also checekout this thread related to public folder migration from exchange 2010 to 2013 :
http://social.technet.microsoft.com/Forums/exchange/en-US/b7a35a45-9b74-4910-9dc3-c997bc71f03f/migration-form-exchange2010-to-exchange2013?forum=exchangesvrdeploy
Further, for a better convenience, you can also take a look at this application (http://www.exchangemailboxmigration.com/) which would be a good approach while migrating mailboxes and public folders
between two exchange server. It ensures about the data security and email contents during the completion of entire migration process.

Exchange 2007 to Exchange 2013 Mailbox Migration (moved twice)

I have an Exchange 2007 mailbox that I migrated to Exchange 2013 and works fine. I migrated it back to Exchange 2007 and still works fine during coexistence with Exchange 2013. I try to migrate the mailbox back to Exchange 2013 and now it won't open in
Outlook 2007. It says disconnected when it's trying to connect. I can't figure out what's causing this.

Hi,
According to your description, I understand that all mail client works fine after migrate mailbox form Exchange 2007 to Exchange 2013, however Outlook 2007 cannot connect to Exchange server when mailbox moved to Exchange 2007 then move back to Exchange 2013
If I misunderstand your concern, please do not hesitate to let me know.
Basis on previous steps testing, the mailbox and mailbox database is available in Exchange server. How about another computer with same Outlook version and problematic account?
If it works in another client, please open Control Panel\User Accounts\Credential Manager in problematic computer, then clear the remains credential and try again.
This issue may be related to the connection between Outlook and Exchange server, please click “Send/Receive All Folders” or “Update Folder” to update data. Also, run Test E-mail AutoConfiguration and Outlook Connection Status with problematic account to
narrow down issue. Please post relevant error message, it’s more helpful for further troubleshooting.
Thanks
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]
Allen Wang
TechNet Community Support

Exchange 2013 Mailbox Move FailedOther

Similar Messages

Maybe you are looking for