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
LVL 3
TingathewingaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
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?
0
TingathewingaAuthor Commented:
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.
0
JohnBusiness Consultant (Owner)Commented:
If the same error , then yes, delete the AD user and re-create
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

TingathewingaAuthor Commented:
Ok, it turned out to be a faulty legacyDN entry.
The new user even after I made him new again, had a previous users legacyDN, once I corrected this all is working fine.
Now I will find out why this happened.  :)
Thanks for your time on this issue.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JohnBusiness Consultant (Owner)Commented:
Thank you and I was happy to help.
0
TingathewingaAuthor Commented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.