One thing I notice is that will start to sync his e-mail, and he can actually close and open Outlook normally for a while. I even blew away his Windows profile and recreated it. I have tried the other fixes you can find. He has been using Teams Exploratory for about a year now. The user has been working form home for years with this setup.
We have Outlook 2016 and on-prem Exchange 2010 (yes we are working on that). I tried theĮxcludeScpLookup registry entry, but then the user could not log into Outlook at all after rebooting and trying to reconnect. I'm having the same problem with a remote user. The user's old computer is running Office 2013 and has no problems with Outlook. I've already setup other user's new computers and didn't have this problem. Repair Outlook Data File - No data file to repair as Outlook never opened to create one. Disable Exchange cached mode - No differenceĥ. Run the resetnavpane command - did not fix the problemĤ. Create new Outlook Profile - Tried several times and still won't openģ. Start Outlook in Safe Mode - Still won't openĢ. Now, I've googled this extensively and have come up with several solutions that still won't fix my problemġ. The attempt to log on to Microsoft Exchange has failed." Cannot open the Outlook Window.The set of folders cannot be opened. When I attempt to open Outlook, I get a message: We have our own on-premise Exchange 2013 server and not using Exchange Online. This is a Windows 10 Pro box, and the version of Office we use is 2019 Office 365 (Microsoft 365 Apps for Enterprise) I am preparing to give a user a new desktop computer and in the process of setting everything up on the new machine. I could then adjust some settings for PST files – and everything worked again! Thanks so much for the valuable advice.I have a strange and unusual situation with Outlook today. It seems the only one that was useful in my situation was the last one: “try to create and configure a new Outlook profile (Control Panel -> Mail item -> Add) and reconnect your PST files.” After creating a new Outlook profile (and deleting the old one), Outlook 2016 could actually start. I tried all of the methods suggested on this page. A reason might be some remaining settings caused by Outlook for 32 bit PCs (and caused by remaining files from Office 2007, too, which I had installed previously, too).
After removing Office 2016 and re-installing the entire Office 365 package again (this time for 64 bit PCs), Outlook was still unable to start, nevertheless. Maybe, that could be the reason why Outlook suddenly crashed irreversibly. It appeared that I had downloaded a wrong version (32 bit) from the Microsoft page.
I also experienced this issue being unable to start Outlook 2016.
0 kommentar(er)
