Quantcast
Channel: Exchange Server 2013 - General Discussion forum
Viewing all articles
Browse latest Browse all 4521

Following mailbox migration from 2010 to 2013, Outlook 2013 Users displayed as connected, Send/Receive does not work: Error 0x80040115

$
0
0

Hi all,

I have been battling an issue following the migration of mailboxes from Exchange Server 2010 to Exchange Server 2013.

When I created test accounts for migration on 2010 they connect to the 2013 server fine after migration using Outlook 2013.

I am running Exchange 2013 Enterprise CU6.

I then chose several users for a secondary migration test for live accounts. All of these users are running Outlook 2013 with the Latest updates.

Following the migration the users are asked to restart as normal.

Once they restart their clients they are prompted again to restart, "The Microsoft Administrator has made a change that requires you to quit and restart outlook".

Outlook continues to load and show as "connected". However, the users cannot send or receive.

They are presented with error: "Task "emailaccount@domain.com" - Sending reported error (0x80040115): We can't complete this because we can't contact the server right now.

Please try again."

If I do a "repair" of the mail account, everything passes successfully, however, they still cannot send or receive. If I then remove the mail profile and attempt to add it again, I receive the error: "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected complete this action."

If I select okay, I am presented with the correct Microsoft Exchange server and Mailbox details of the user, (GUID of the mailbox@domain and =SMTP:emailaccount@domain.com). I can check name, and it fails with “The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.”

If I log onto a different machine on the same network as the same user who has been migrated, the mailbox will load successfully without issue. The autodiscover .xml is returning all of the correct addresses.

There is no ACL on the network.

Has anyone had any similar issue with Exchange 2010 to 2013 migration?

The select users I have migrated are now using OWA as a workaround.

Any assistance would be appreciated. 

Thanks.


Viewing all articles
Browse latest Browse all 4521

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>