![]() Where "Username" (for most users) was the same as their SAMAccountName (i.e. o=Organisation/ou=Administrative Group/cn= Recipients/cn=Username Note: I repeated the above steps many times but with no success.Ĭreated a new windows user profile and then created new outlook profile.įor me it was (bear with me, this was an odd one, and yes I tried every single recommended fix/troubleshooting technique I could find, dozens of them, over many months.):Īffected users had a "LegacyExchangeDN" AD attribute that ended with an empty space.Īfter trying every possible fix I could find, I began pouring over every users AD attributes, and comparing attributes of affected users vs unaffected users, and noticed that some had their LegacyExchangeDN value/attribute set to: Then Rename the Outlook Folder c:\users\%username%\AppData\Local\Microsoft\Outlook instead of repairing we rename C:\Users\dhiyab.albalushi\AppData\Local\Microsoft\Outlook as Outlookold - still did not fix the problem.Ħ- On the problem computer, create the registry key HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover Run the "outlook.exe /resetnavpane" command - did not fix the problemĥ. the attempt to log on to Microsoft exchange has failed"ģ. When starting outlook it gives message "cannot start Microsoft outlook. There were origianlly some errors about subscribed calendars, but we removed them through OWA, so they went away without helping. I did run New-MailboxRepairRequest -DecectOnly for a few common corruption types, but it did not find anything. Could it be something in his mail file that is causing this, a bad message, folder setup or something? But it will crash after it gets a certain way through the sync. 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 have a strange and unusual situation with Outlook today.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |