Archive Mailbox Duplicated - Exchange 2010/Outlook 2013

Hi,
I have enabled archive mailboxes for a number of users in an Exchange 2010 environment no problem.
There is one user though,  that is seeing two online archives:
Online Archive - <Firstname> <Surname>
Online Archive - <email address>
Both are replicas of the other.
Any ideas how to get rid of the duplicate?

I just encountered the same issue.  This has been going on for months with my mailbox and no one else's.
I can't tell you how many outlook profiles I created in attempt to fix this.
Originally I was running Outlook 2010 when the issue happened.  In my case I had one archived named "Online Archive."  The second one was named "Personal Archive."  If I expanded either one, I could see the contents in it without issue, but
I couldn't expand the other.  I didn't save the error message, but something about being unable to access it.
Once I started using 2013, both archives changed to be called "Online Archive," and were able to be expanded simultaneously. Any changes made in one were immediately reflected in the other.  But it still left me with the duplicate archives.
I had reset my password using AD Users and Computers a number of times, but it was always set to the same password.  This went on for probably 4 months.  Finally I reset my password via ctrl+alt+del.  I closed outlook, made sure outlook.exe
wasn't running, opened it back up, and the duplicate archive is GONE!
I even reset the password back to the original one via AD Users and Computers and the duplicate archive has not come back.
Excellent detective skills walshyno_1.  But I really want to know why this happens.  How is it even possible that creating a different password would remove the duplicate Exchange archive view in Outlook?

Similar Messages

  • "Resend" option is not working for specific user. "The Operation Failed" Exchange 2010 Outlook 2013

    Hi Everybody. I have a weird one for you.
    I have a user that gets an "operation failed" message whenever trying to use the "resend" option on any email (It's the one right under recall). I had tested up and down on her machine. Exchange 2010 Outlook 2013
    Ran in safe mode, recreated her profile, disabled virus scanning, repaired office. (weird, the font just changed sizes on me)
    After all of this I tested on other computers, other users seem to be able to "resend" just fine. However her account does not work on any computer I try, internal or external to the network.
    It looks more like a profile issue.
    She's a very active archivist, so she only has 486MB of space used by her mailbox.
    It's well under quota.
    It's been really puzzling me.
    MCSE 2003, Exchange. MCTS Vista, 7. Administrator of awful, neglected website http://timssims.net

    Hi Timssims,
    Since there is only one user in the org has this issue, it seems an issue on the Outlook client side.
    I suggest asking Outlook Forum for help so that we can get more professional suggestions.
    For your convenience:
    https://social.technet.microsoft.com/Forums/office/en-US/home?forum=outlook
    However I also have some suggestions for your reference:
    1. If this issue occur on Cached Mode, I suggest turning to Online Mode for testing.
    2. Please also paste the detailed error message if "operation failed" is not the
    complete information.
    3. If still not works after perform operations above (including suggestions from Outlook Forum), I suggest re-creating a new mailbox for the specific user just as Martin suggested.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Send As Permissions - Exchange 2010 - Outlook 2013

    I am currently having an issue with an account. 2 people share an Admin Account inbox, while having their own inbox, Although the Admin mailbox only works in Online
    mode or the folders will not update and emails will not come through.
    This is not the problem though.
    Before today both people were working fine for the last few months. Now User 1 (only user to send as Admin mailbox) can not send as the mailbox, while
    in online mode. In cached mode it works fine, however the folders do not work.
    When in online mode, i can remove the address from the From: drop down and re-add, however this only works for that email. Sending another email reaches
    the same error "you do not have the permission to send as blah blah blah". This is a popup error.
    Removing the address and re-adding works every time, however as you can imagine, this is not ideal for the user. In testing I have removed permissions
    for send as in EMC but removing the address from the from field and re-adding is still allowing it to send. It seems outlook/exchange is not recognizing the permissions. Does anyone have any ideas on what could be causing this?
    Exchange version is 2011
    Outlook version is 2013

    In testing I have removed permissions for send as in EMC but removing the address from the from field and re-adding is still allowing it to send. It seems outlook/exchange is not recognizing the
    permissions. Does anyone have any ideas on what could be causing this?
    Hi,
    After removing the permissions in EMC, I suspect it still takes some time to take effect. We can verify this by sending as the Admin mailbox on OWA to check the result. Then wait for some time, send the test email in Outlook again.
    This issue is actually opposite to these issues I've seen before: Most other issues are that the user is not able to send as another user in Cached mode, but able to send in Online Mode. Your description kind of implies there's something interfering
    with the connection between Outlook and Exchange when Outlook is in Online Mode, please disable all suspicious add-ins in Outlook, especially the anti-spam add-ins provided by the anti-virus program. Then disable the anti-virus program and the firewall temporarily
    to check the result.
    As mentioned in your post, this issue is also related to the Auto-Complete List in Outlook, the list may have been corrupted. We can try clearing the list to check if the problem persists:
    In Outlook 2013, click FILE -> Options -> Mail -> Send messages -> Click "Empty Auto-Complete List" button -> Yes -> OK.
    Regards,
    Melon Chen
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs. 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]

  • No calendar connection for Exchange 2010 + Outlook 2013

    My environment is this:
    Running Outlook 2013 (as part of Office 2013 Suite) connecting to Exchange Server 2010
    Both cached and non-cached modes
    Connecting using RPC
    With both existing profile for last 1yr+ and with a new profile
    Outlook v 15.0.4649.1001
    The issue I'm having is a room/resource calendar that I was once able to see I can't anymore.
    Running Outlook 2010 as the same user from a different computer works fine.
    OWA works as well.
    Other calendars work
    Running Outlook 2013 vs 15.0.4420.1017 also works on a different computer!!!
    So this seems to be an issue with my particular version of Outlook, and I did read where a security update seems to have gotten in the way (regression test lately?) but a December patch of 2013 was supposed to fix that. I didn't specifically install the
    patch, rather I downloaded from my vendor the latest available version they had.
    So is there a patch that will work for me. The only one I've come across tells me it isn't for my machine.
    Thanks,
    Joe

    Hi,
    According to your description and test, I understand that the room/resource calendar is invisible in Outlook.
    How about changing another user to log on your Outlook?
    How about the same version of Outlook on another computer?
    Please try to run Outlook under safe mode to avoid some AVs and add-ins.
    Please try to re-create profile for testing.
    If all method above doesn’t work, please re-install Outlook.
    Best Regards,
    Allen Wang

  • Exchange 2010 + Outlook 2013 = Items deleted from inbox, Keep Re-Appearing. (Cached mode outlook only)

    Hey Team,
    We have a single user who when she deletes items from the Inbox they re-appear (in the inbox), if she is running in cached exchange mode. The items do not re-appear in OWA.
    She is not experiencing any network connectivity issues
    We have rebuilt her MAPI profile including deleting all existing OST files
    We have removed and reinstalled outlook / office 2013
    She is the only user with the issue
    There are no Sync issues
    As soon as we disable cached exchange mode this issue immediately goes away, she is running Office 2013 RTM.
    Any Ideas,
    Thanks,
    Robert
    Robert

    Hi Robert,
    If change another PC to configure her mailbox within outlook 2013, is there the same issue?
    In addition, you can try to move her mailbox to another database and check if any helps.
    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]
    Niko Cheng
    TechNet Community Support

  • Exchange 2010 / Outlook 2013 - Mailflow Issues

    Hi everybody,
    Some time ago I've configured a SBS2011 server for one of my customers.
    The SBS2011 has exchange and sharepoint, these services work fine.
    The exchange server is only being used for the calendars, no e-mail flow.
    The company uses IMAP through an external hosting-server.
    So in Outlook 2013 we configure 2 accounts, one exchange account and one IMAP account.
    Configuring the clients isn't a problem, and all seems fine, the calendar works.
    But when the e-mail flow starts, users wil receive the same email multiple times and it seems the system is in a loop. E-mail flow will stop or the users get the same e-mails multiple times.
    I've checked multiple solution regarding Win8+Outlook 2013 and IMAP, (issue about an update and setting the right root folder), but nothing seems to help.
    We installed Outlook 2007 on the clients and configured them with both of the accounts and the system works like a charm! E-mail and the calendar are working like it should.
    But the company bought about 20 Office 2013 licenses, so we need to get this to work on the new Outlook.
    I don't think there is a problem in the Exchange Server, but in Outlook 2013, possible because both of the accounts share the same OST file.
    Does anyone know how to solve this problem? Been running my mind for months.
    With kind regards,
    Tim Grave

    Hi,
    This doc may help you a lot.
    http://office.microsoft.com/en-in/outlook-help/introduction-to-outlook-data-files-pst-and-ost-HA102749465.aspx
    Install Only one Outlook Ex :- Outlook 2007 / 2010 / 2013
    And if you want to create a *.pst file you need to go to
    1. File > Account Settings > Account Settings.. > Data Files > Add > Create a new PST as you want.
    Regards, Koustov Choudhury

  • SBS2011/Exchange 2010 + Outlook 2013 Flow Issues

    Hi everybody,
    Some time ago I've configured a SBS2011 server for one of my customers.
    The SBS2011 has exchange and sharepoint, these services work fine.
    The exchange server is only being used for the calendars, no e-mail flow.
    The company uses IMAP through an external hosting-server.
    So in Outlook 2013 we configure 2 accounts, one exchange account and one IMAP account.
    Configuring the clients isn't a problem, and all seems fine, the calendar works.
    But when the e-mail flow starts, users wil receive the same email multiple times and it seems the system is in a loop. E-mail flow will stop or the users get the same e-mails multiple times.
    I've checked multiple solution regarding Win8+Outlook 2013 and IMAP, (issue about an update and setting the right root folder), but nothing seems to help.
    We installed Outlook 2007 on the clients and configured them with both of the accounts and the system works like a charm! E-mail and the calendar are working like it should.
    But the company bought about 20 Office 2013 licenses, so we need to get this to work on the new Outlook.
    I don't think there is a problem in the Exchange Server, but in Outlook 2013, possible because both of the accounts share the same OST file.
    Does anyone know how to solve this problem? Been running my mind for months.
    With kind regards,
    Tim Grave

    Hi,
    Based on the description, I understand Outlook uses the calendar via Exchange and email via IMAP, so there are two accounts setup in Outlook 2013, correct? Then how come they share the same .ost file? Please try to configure an individual .ost file
    for both accounts, check whether the issue persists.
    Regards,
    Melon Chen
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Outlook 2010 clients cannot access their Online Archive mailbox in Exchange 2013??

    Hello,
    I have an issue where my Outlook 2010user cannot see/access their Archive mailbox when they are migrated from Exchange 2010 to Exchange 2013.
    Both the live and archive mailbox is in Exchange 2013, the user can launch Outlook but if they click on their Archive mailbox it is unavailable.
    Once the user is upgraded to SP2 or Outlook 2013 they have no issues accessing their archive mailbox.
    These users have the minimum required Outlook version (14.0.6126.5000),
    they are running 14.0.6129.5000.
    Is there a different requirement on the Outlook client if the user has an archive mailbox in Exchange 2013 as well?
    Thank you.

    Hi,
    Is there any update on this thread?
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If
    you have feedback for TechNet Subscriber Support, contact [email protected]
    Simon Wu
    TechNet Community Support

  • Primary mailbox (on Exchange 2010) and Personal Archive (on Exchange 2013), possible?

    Current environment is Exchange 2010 SP3 RU5 supporting 4,000 Users. Client estate is Outlook 2010 SP1 going on SP2.
    We're pulling our Archiving solution away from 3rd party and back into Exchange. Implementing a new set of Exchange 2010 Servers (old DAG or in a new Archive DAG) would be easy. But is there Exchange 2013 stepping stone potential?
    Can the Archive DAG / Archive mailboxes be on 2013? i.e. for any given User, leave their primary mailbox on Exchange 2010 and create new Archive mailbox on 2013.
    I want to avoid implementing 2010 Archive Servers and then go 2013 Archive 6 months or a year later.
    This article suggests 'no':
    http://technet.microsoft.com/en-gb/library/dd979800(v=exchg.150).aspx
    "Locating a user’s mailbox and archive on different versions of Exchange Server is not supported."
    I've found little info but the odd statement here / there.
    Is this the latest position? Is it that cut & dry? Anyone tried it? Why won't it work (or will it but it's not supported)?
    Thanks!

    <I had a response from MS>
    Below is a summary of the case for your records:
    Symptom:
    =============
    Is it possible to implement a 2013 environment to host the Archive mailboxes? i.e. for any given User, their primary mailbox is on Exchange 2010 and their Archive
    mailbox is on 2013. 
    Resolution:
    =============
    It’s not supported to have a user’s primary mailbox reside on an older Exchange version than the user’s archive. If the user’s primary mailbox is still on Exchange
    2010, you must move it to Exchange 2013 before or at the same time when you move the archive to Exchange 2013.
    http://technet.microsoft.com/en-us/library/jj651146(v=exchg.150).aspx
    as per the repro in our lab, having the archive mailbox in higher version of exchange would fail with the error above
    <the scenario isn't completely relevant, looks like he's trying to put the Primary on 2013 and not the Archive, no matter, we've established there are problems, question is whether they are looking into this area / to patch, they go on...>
    At this point in time we don’t have a conformation from the product team, if the above would change in the future exchange versions.
    <MS did say on the call that they were not looking at fixing it, naturally this isn't a "never", as per previous statement - they can't commit 100% to the future, but they've provided me the answer - they are not currently looking at resolving/providing
    this as a migration scenario, end.>

  • 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 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

  • Exchange 2010 to 2013 migration: Mailbox move requests are journaled.

    Hello,
    I've installed Exchange 2013 into Exchange 2010 infrastructure
    [ single Exchange 2010 server; single AD site; AD = 2003 ],
    Exchange 2010 has 2 databases:
    1. Database with users mailboxes;    Journaling YES: Journal account.
    2. Database with 1 mailbox for Journal user mentioned above:     Journaling NO.
    Exchange 2013 has 1 database:
    1. Database with moved users mailboxes;    Journaling YES: Journal account.
    I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !
    I logged into Journal mailbox by OWA and didn't see any duplicate messages concerned with this mailbox user...
    I'd like:
    * to understand technically what happened,
    * to avoid unnecessary growth of Journal Database.
    I'd like not to switch off journaling for all users during mailbox move.
    best regards Janusz Such

    Hello Winnie,
    your understanding is not correct:
    I move mailboxes from first DATABASE which is journaled;
    second database is dedicated solely for Journal user's mailbox and is not touched now.
    Thank you for PS commands; I'll use them...
    best regards Janusz Such
    Hi Janusz,
    Sorry for my delay. In your original posting, "I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !"
    My understanding is that when you move mailbox from Exchange 2010 Database 1 to Exchange 2013 database, the journal mailbox in Exchange 2010 Database 2 is incleased. Is it right?
    Generally, the mailbox move would not be journaled unless there is any new email bening sent to the mailbox during the migration. Please run the commands in my original posting to check the statistics about it, and refer to Ed Crowdly's suggestion to use
    Journal rule instead of database journal as a workaround.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Users with mailboxes on exchange 2010 cant proxy to OWA on exchange 2013

    We are in the process of migrating from 2010 to 2013.  Users with mailboxes on exchange 2010 can't proxy to the owa on Exchange 2013 - there is no error - just receiving a message "Still working on it"
    alex serdyukov

    Hi Alex,
    As the above suggestion mentioned, you can try to upgrade the Exchange 2013 to CU8 and check if any helps:
    Cumulative Update 8 for Exchange Server 2013
    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]
    Niko Cheng
    TechNet Community Support

  • Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

    I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
    as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
    Symptoms:
    Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
    from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
    URL to connect to my proxy server for Exchange: webmail.domain.com
    Connect using SSL only: Checked
    Only connect to proxy servers that have this principal name in their certificates: Unchecked
    On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
    On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
    After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
    first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
    Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
    Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
    domain: blank
    username: their AD username
    server: webmail.domain.com
    After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
    begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
    for mobile users in the same way that it's been working for us with Exchange 2010?
    Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

    Hi,
    Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
    Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
    fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
    Please restart the following Exchange service to have a try:
    Microsoft Exchange RPC Client Access
    Microsoft Exchange Mailbox Replication
    Restart IIS service by running IISReset in a Command Prompt window.
    Then check whether the Outlook client can connect to Exchange 2013 or not.
    As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
    https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
    Regards,
    Winnie Liang
    TechNet Community Support

  • Mailbox Move from 2010 to 2013 Completed with Warning and Stuck

    I have been moving mailboxes from Exchange 2010 to Exchange 2013 and was on my last batch when all the mailboxes Completed except for one which Completed With Warning.  It shows 0 bad items.
    In Exchange 2010, all the mailboxes that are part of this failed batch show they are still in the Move Request state.
    On the mailbox in Exchange 2013 Migration that shows Completed with Warning, the following details are provided:
    Error:                        
    MigrationPermanentException: Warning: Target mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible. Error details: The process failed to get the correct
    properties. --> MapiExceptionTimeout: Unable to get properties on object. ‎(hr=0x80040401, ec=-2147220479)‎ Diagnostic context:    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=342]    Lid: 43559  
    EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x80040401][length=178][latency=60009]    Lid: 32881   StoreEc: 0x80040401    Lid: 50035      Lid: 64625   StoreEc: 0x80040401   
    Lid: 52176   ClientVersion: 15.0.847.32    Lid: 50032   ServerVersion: 15.0.847.6032    Lid: 50128      Lid: 1494    ---- Remote Context Beg ----    
    Lid: 43632   StoreEc: 0x80040401    Lid: 42272   StoreEc: 0x80040401    Lid: 36392   dwParam: 0x1    Lid: 50904   StoreEc: 0x80040401    Lid: 35992  
    StoreEc: 0x80040401    Lid: 1750    ---- Remote Context End ----     Lid: 1494    ---- Remote Context Beg ----     Lid: 43632   StoreEc: 0x80040401   
    Lid: 42272   StoreEc: 0x80040401    Lid: 36392   dwParam: 0x1    Lid: 50904   StoreEc: 0x80040401    Lid: 35992   StoreEc: 0x80040401    Lid: 1750   
    ---- Remote Context End ----     Lid: 50288      Lid: 23354   StoreEc: 0x80040401    Lid: 25913      Lid: 21817   ROP Failure: 0x80040401   
    Lid: 20385      Lid: 28577   StoreEc: 0x80040401    Lid: 32001      Lid: 29953   StoreEc: 0x80040401    Lid: 62128      Lid: 38144  
    StoreEc: 0x80040401
    Report:                        
    [email protected]
    Any idea what steps to take to complete this move from here?
    Thanks,
    Brett Gibson
    Brett Gibson

    From the EMC on the Exchange 2013 (destination) I get:
    DisplayName               StatusDetail              TotalMailboxSize         
    TotalArchiveSize         PercentComple
    Jason Osborne             Completed                 6.029 GB (6,474,008,69...                         
    100
    Brent R. Holl             Completed                 4.102 GB (4,403,992,89...                         
    100
    Nathan Harsin             Completed                 3.321 GB (3,565,830,88...                         
    100
    Don Barrett               Completed                 11.1 GB (11,916,695,17...                         
    100
    Larry Michael             Completed                 3.705 GB (3,978,717,79...                         
    100
    Danyl Gonterman           Completed                 4.165 GB (4,471,791,08...                         
    100
    Jason Mullanix            Completed                 1.569 GB (1,684,906,68...                         
    100
    Eric Brown                Completed                 5.662 GB (6,079,329,50...                         
    100
    Nick Cacciola             Completed                 1.992 GB (2,139,080,78...                         
    100
    Dorothy M. Jones          Completed                 11.34 GB (12,181,530,1...                         
    100
    orders                    Completed                 3.632 GB (3,899,673,39...                         
    100
    Terrie Bumpus             Completed                 14.2 GB (15,249,956,21...                         
    100
    Sean Stepp                Completed                 2.55 GB (2,738,494,989...                         
    100
    Joshua Stolberg           Completed                 3.055 GB (3,280,581,92...                         
    100
    Josh Stremme              Completed                 2.571 GB (2,761,019,42...                         
    100
    Casey Jones               Completed                 1.614 GB (1,732,737,86...                         
    100
    Larry Gray                Completed                 2.545 GB (2,732,725,42...                         
    100
    Kelly Gray                Completed                 1.91 GB (2,050,883,915...                         
    100
    Bill Daugherty            Completed                 5.993 GB (6,434,784,87...                         
    100
    Laura Billstrom           Completed                 1.343 GB (1,442,466,39...                         
    100
    Adam Yates                Completed                 1.14 GB (1,224,119,328...                         
    100
    Eli Malooley              Completed                 606.8 MB (636,282,187 ...                         
    100
    Chad Ayers                Completed                 1.213 GB (1,302,645,29...                         
    100
    Nick Galvin               Completed                 815.9 MB (855,568,875 ...                         
    100
    Stephane Martin           Completed                 556.4 MB (583,443,766 ...                         
    100
    Todd Neal                 Completed                 222.5 MB (233,256,684 ...                         
    100
    Eric Botsford             Completed                 17.13 MB (17,962,734 b...                         
    100
    Archiving                 CompletedWithWarnings     138.6 GB (148,830,505,...                         
    100
    Running the same command on the source Exchange 2010 Server I get the following:
    [PS] C:\Windows\system32>Get-MoveRequest |Get-MoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (0:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (1:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (2:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : F4AB2B5B,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (3:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (4:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (5:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 903CB5C9,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (6:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 903CB5C9,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (7:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (8:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (9:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (10:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (11:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (12:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 903CB5C9,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (13:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (14:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (15:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (16:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (17:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (18:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (19:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (20:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (21:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (22:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (23:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (24:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (25:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 903CB5C9,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (26:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Failed to communicate with the mailbox database.
        + CategoryInfo          : ResourceUnavailable: (27:Int32) [Get-MoveRequestStatistics], AccessDeniedException
        + FullyQualifiedErrorId : 8E8584BB,Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics
    Thanks,
    Brett
    Brett Gibson

Maybe you are looking for