Outlook does not connect to Exchange 2013 after name change due to marriage

When launching Outlook and clicking through the setup wizard to create a new profile, Outlook auto-discovers the correct email alias. When establishing a connection it successfully checks network connectivity and successfully searches the email settings. When it attempts to logon to the mail server the error comes up.

"The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."

Clicking "Check Name" gives the error:

"The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."

The same result occurs with a manual setup.

We are running Exchange Server 2013. User workstations are running Outlook 2013 on Windows 7 Pro. All updates have been applied as of March 31, 2015.

All name changes have been made in AD and Exchange. Old aliases and new aliases are set in Exchange. Offline Address books are updated daily. The local profile and registry settings have been updated on the workstation and the user is successfully logging into the profile. The issue is only with Outlook 2013. User can access mail through OWA and ActiveSync on their mobile device.

Logging the user into another workstation and running the wizard returns the same results, which rules out the possible problem being with the workstation.

March 31st, 2015 2:32pm

Can the user sign on through OWA?
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2015 4:17pm

Can the user sign on th
March 31st, 2015 5:12pm

Hi,

According to your description, I understand that failed auto-configure Outlook with error The name cannot be resolved. The connection to Microsoft Exchange is unavailable, however OWA works fine.
If I misunderstand your concern, please do not hesitate to let me know.

Are all account or any special user experience this question?

If OWA works fine, it indicate that the mailbox database is mounted, and mailbox works well.
I notice that you have changed the account name before issue arise, because external access, the client locates the Autodiscover service on the Internet by using the primary SMTP domain address from the user's email address.
More details about Autodiscover service, for your reference: https://technet.microsoft.com/en-us/library/bb124251.aspx?f=255&MSPPError=-2147217396

Please try below command to force update address list, GAL, OAB, then test again:
Get-AddressList | update-AddressList
Get-GlobalAddressList | update-GlobalAdressList
Get-OfflineAddressBook | Update-OfflineAddressBook

If the issue persists, please wait for some time to complete configuration.

Thanks

Free Windows Admin Tool Kit Click here and download it now
April 1st, 2015 3:53am

These commands have been run in Powershell on the Exchange server and the address list, GAL, and OAB was updated.

I've attempted to run the Outlook wizard again after about 30 minutes and receive the same results.

This is the only user experiencing this issue.

April 1st, 2015 12:48pm

It would seem the only solution is to not do it in the first place.

The last resort is to export the user's mailbox from Exchange to .pst file, delete the user's mailbox and Active Directory object, then create a new account (which will generate a new SID), and import the .pst file back into the mailbox.

I'd prefer not to do this.

Free Windows Admin Tool Kit Click here and download it now
April 7th, 2015 4:42pm

Hi,

Any updates about this issue?
Please try to disable mailbox in Exchange server, then force update address list. Final, re-enable it for testing.

Best Regard,
Allen Wang

April 28th, 2015 9:50am

This solution was resolved.

We ended up calling Microsoft and paying a bunch of money mere hours before the problem would have resolved itself.

The cause was from Exchange Auto-Discover. Auto-Discover, by default, uses the oldest Exchange server in the domain. At the time, all the mailboxes had previously been migrated off a 2007 Exchange server and onto a new 2013 server, but the old Exchange server had not yet been decommissioned. As a result, Outlook was trying to go to an old Exchange 2007 server even though that's not the location of the users mailbox.

The Microsoft Tech had to manually alter some configurations on the new Exchange server. As it turns out, the old Exchange server was being decommissioned that evening.



  • Marked as answer by Grey VLAN 16 hours 17 minutes ago
  • Edited by Grey VLAN 16 hours 16 minutes ago
Free Windows Admin Tool Kit Click here and download it now
April 29th, 2015 11:10am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics