Link to home
Start Free TrialLog in
Avatar of IT
IT

asked on

Outlook 2013 You must connect to MS exchange with current profile before you can sync folders

New AD user, replacing staff member, mail disabled old user, reconnected mailbox to new AD user.
New AD user can log into windows fine, but outlook on first and all subsequent openings throws this error.
Cannot Start Microsoft Outlook. Cannot Open the Outlook window. The set of folders cannot be opened. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost).

If I remove cached mode it throws this error.
Cannot Start Microsoft Outlook. Cannot Open the Outlook window. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance.

This issue only occurs for this user with the reconnected mailbox.
This user can use OWA without any issues.
I made another new AD user and gave fresh mailbox, no issues on this same PC.

Exchange 2016 on premise, Outlook 2013, Windows 7 Pro.

Any help would be appreciated.

Craig
Avatar of John
John
Flag of Canada image

That would suggest the user Windows User Account has been corrupted. No amount of Office repair or reinstall will fix this.

Can you delete the users local profile, then restart and setup Outlook again?
Avatar of IT
IT

ASKER

Hi John,

Tried this but same error sorry, I am going to delete the AD user, clean traces of old user of PC and server, and create new user.
Then connect existing mailbox to this one and see if it works.
SOLUTION
Avatar of John
John
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thank you and I was happy to help.
Avatar of IT

ASKER

Johns post pointed me in the direction of it being a user issue, and indeed it was, but took some digging to eventually find the legacyDN at fault.