![]() ![]() Is it maybe some rogue Group Policy? Move the machine and my user accounts to the default OUs/containers & reboot.Back to the domain it goes, and the fault recurs. OK, but no, that’s not an acceptable solution. Rename the Outlook folder at c:\users\\AppData\Local\Microsoft\Outlook.Set Skype for Business to Disabled in Task Manager / Startup (the logic there being that it might be the Outlook plugin causing it).The peculiar thing here is that I could log into my O365 e-mail from other PCs on the domain here, and log into other accounts from this machine – it just didn’t seem to like the combo of Greig the local AD user (sync’d to the cloud) and “other Greig”, the cloud-only mail user. Naturally, they need to start from the beginning, so whilst on the phone to the support agent – over what turned into a 3 week period – we did the safemode, resetnavpane, new profiles, repair, Support & Recovery Assistant, etc tango over again. I eventually decided it was beyond me and my Googling skills, and I logged a ticket with O365 support. I put up with this for a couple of months – remembering, I’m still away from home for a week at a time, and only back each weekend to do the washing, cuddle/kiss husband and cats as appropriate, and then I’m off again for another week. Add a new motherboard, twice as much RAM, etc. OK, this PC is getting on in years, let’s use this as an excuse for a rebuild – and if I’m going to go to that effort, we might as well do it properly. Whilst I could still use Outlook on the web and my iPhone, I’m really quite dependent on the search syntax in Outlook, and it’s an archive I’m digging into all the time. Ran the “ Outlook Support & Recovery Assistant“.ĭesperation started to set in.(Start / Control Panel / Mail / Show Profiles / Add…) Reset the nav pane (Start / Run / outlook.exe /resetnavpane).I tried all the usual suspects thinking this was going to be a quick fix: The attempt to log on to Microsoft Exchange has failed. It was upon returning from a work trip that I found Windows had pushed an update to it, and it had restarted – and from that moment, Outlook was broken.Ĭannot start Microsoft Outlook. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.I’ve been travelling a lot for work this year, and when I’m away from home I generally leave my home PC on. If the response is helpful, please click "Accept Answer" and upvote it. Please try to re-create a new outlook profile and then run the “outlook /safe” in the run to open the outlook as safe mode.ĥ.In Exchange 2016, MAPI over HTTP is enabled by default at the organization level, please run the following command to check the user whether enable the MAPI: Get-OrganizationConfig | fl mapi.Please try to log in to OWA using the issue mailbox to see if you can log in and open the shared mailbox.So would you like to share with me how you logged in? As a result, users can't log into them directly. According to my research, the shared mailbox is a type of user mailbox that doesn't have its own username and password. In order to better solve the issue, I would like to confirm with you the " sign in using share mailbox" you mentioned. ![]() Does the issue occur to only one user or do all users have the issue? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |