pasterwear.blogg.se - Outlook 2016 crashes on startup during autodiscover

#OUTLOOK 2016 CRASHES ON STARTUP DURING AUTODISCOVER MANUAL#
#OUTLOOK 2016 CRASHES ON STARTUP DURING AUTODISCOVER SOFTWARE#
#OUTLOOK 2016 CRASHES ON STARTUP DURING AUTODISCOVER WINDOWS#

#OUTLOOK 2016 CRASHES ON STARTUP DURING AUTODISCOVER MANUAL#

There are different manual techniques to overcome “Outlook crashes while send receive” issue. Manual Methods to Fix “Outlook Crashes on Send/ Receive” Corrupt user account and Configuration File.Conflict with any other program with Outlook.

#OUTLOOK 2016 CRASHES ON STARTUP DURING AUTODISCOVER SOFTWARE#

Antivirus software may conflict with MS Outlook.

Any sort of corruption in MS Office programs.

Corrupt or damaged Outlook (.pst) data files.

MS Outlook is being used by different processes.

Conflict in any add-in installed with MS Outlook.

Outlook application has become outdated.

Outlook crashes because of heavy mailboxes.

Follow below causes due to which Outlook crashes: Such situations can lead to very annoyed because the problem often occurs which sometimes makes it difficult to determine the cause of the crash. Reasons to Fix ” Outlook crashes during Send/ Receive” Let us begin with the causes that why your Outlook keeps crashing on Send or Receive?

Here, in this blog, we will discuss some approaches through which Outlook users will be able to resolve send/ receive issue. Please suggest me a reliable solution to fix Outlook Crashes on Send/ Receive error.”Īre you also facing the same problem? Not able to find a reliable solution? Do not panic, you are landed on the correct page. I am really confused with this situation. However, apart from this send/receive function, the other functions in MS Outlook works very well. Ever since I cannot send or receive any email messages. Recently, it keeps crashing frequently whenever I press Send or Receive button. “I have been using Outlook for the last two years. Get-OutlookAnywhere -Identity "SERVER-FQDN\rpc (Default Web Site)" | Set-OutlookAnywhere -IISAuthenticationMethods "Basic, ntlm"Īfter switching back the App-Pool-Identity to AppliactionPoolIdentity some clients (especially Outlook 2016) again showed the login prompt – so I think it’s necessary to change both settings.Ashwani Tiwari ~ Modified: T11:58:56+00:00 ~ Error, Outlook Error ~ To make this a permanent change (and remove Negotiate until all Exchange 2010 Servers are removed) enter the following command for every Exchange-Server: I repeated this on every other Exchange 2010 CAS-Server and 2016 Server – and after that the login prompt didn’t occur any longer. So I moved NTLM to the top and restarted the IIS (IISRESET). If we now remember that we had to switch our Outlook Anywhere Settings for Exchange 2016 to NTLM to make it compatible with 2010 this doesn’t sound correct. We can now see that Negotiate is the first configured provider.

#OUTLOOK 2016 CRASHES ON STARTUP DURING AUTODISCOVER WINDOWS#

Now select Windows Authentication => Providers. Open IIS Manager and go to Sites => Default Web Site => RPC => Authentication Let’s check the Authentication settings for the RPC Website: What happens if Outlook uses Outlook Anywhere? It “opens” the RPC Website. So it’s often suggested to change the settings to NTLM. Mainly Exchange 2016 uses different methods compared to 2010. All information’s that are available point to an Authentication Problem. Time to check the information’s that I had until now. First I only changed the setting on the 2010 CAS-Servers – than also on 2016. To make sure everything is applied correctly I also did an IISRESET. Now switch the setting to NetworkService.Īfter this confirm the settings with OK (twice) and press Recycle on the right side in the IIS Console (when the Default-App-Pool is selected). Open the IIS Manager on the 2010 CAS and go to Application Pools => DefaultAppPool and choose Advanced Settings on the right side. Luckily the Hotfix also describes a workaround: There was no error message nor anything else – the installation just started fine but never finished. I downloaded the hotfix – but the installation “failed”. I then found Hotfix 2990117 from Microsoft which exactly described our problem. Unfortunately this didn’t fix the problem So time to look for other solutions. Restart IIS to make sure the setting is applied (CMD – IISRESET): Set-OutlookAnywhere -Identity "SERVERNAME\Rpc (Default Web Site)" -ClientAuthenticationMethod ntlm Time to change the Exchange 2010 CAS to NTLM Authentication:

Interestingly the Exchange 2010 Shell shows the option ClientAuthenticationMethod – while the 2016 Shell shows InternalClientAuthenticationMethod AND ExternalClientAuthenticationMethod. Ok – let’s check the current settings with PowerShell (Exchange Management Shell) for each CAS-Server: If you start to google for the problem, the first hint you get is to change the Outlook Anywhere Authentication on Exchange 2016 (the default now is Negotiate) to NTLM. The problem only happened for users that had access to public folders (still hosted on Exchange 2010) or mailboxes that also had not been migrated. Users with a Mailbox on 2016 always received a login prompt when they started Outlook.

During a migration from Exchange 2010 to Exchange 2016 I was facing a strange problem.