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. Still need help? Go to Microsoft Community.I have a strange and unusual situation with Outlook today. This article is intended only to address local network configuration issues that prevent Outlook from connecting to Exchange Online. Multiple results are provided to give the client applications several endpoints to try, all with equivalent functionality. To achieve the highest availability, Microsoft 365 uses an array of IP address for DNS queries. That kind of behavior my affect performance by prohibiting client retry operations. Additionally, Local Domain Name System (LDNS) resolvers and proxy servers shouldn't use any kind of persistent or IP affinity behavior that prefers a single IP address. Instead, they should provide all results to clients to enable application retries. Local Domain Name System (DNS) resolvers and related firewall applications at users' ISPs and corporate networks should never prune the DNS results lists. For more information about the ports that are used in Microsoft 365, the addresses ranges, and ports that are used in Exchange Online, see Microsoft 365 URLs and IP address ranges. Restricted network access may affect all the Microsoft 365 connectivity. To resolve this issue, open port 443 in the network environment through which the user accesses Outlook and Exchange Online. Network proxy configuration redirects clients to one particular Microsoft 365 IP address range or URL. Outlook Anywhere feature: this feature lets Outlook communicate with Exchange Online.Exchange Autodiscover service: this service sets up Outlook profiles.To enable the following features, port 443 must be open: The user is located in a restricted network environment that blocks port 443. Local network configuration issues may prevent access to Exchange Online servers, as in the following scenarios. The user can't create new Outlook profiles.Outlook can't connect to Exchange Online.In Microsoft 365, a user experiences one of the following issues:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |