Exchange 2016 OWA - 440 Login Timeout

Gebauer, Roman 0

Hello!

I have an Exchange 2016 Server on premise - latest CU, latest SU.

Everything worked fine, a few day ago problems started.

Outlooks working fine, iPhone Sync working fine too, but OWA and ECP and Exchange Shell stopped working.

I just receive a white page with: 440 Login Timeout (in OWA and ECP)

Certificate is presented correct, same error external or internal, same error if I try local Server Name or IP address.

I tried all the articles regarding OAuth Certs, lost IIS Bindings and Backend Certs.
Exchange Healthecker Scripts detects nothing special.

Any ideas what the problem could cause?

Thank you!!
Roman

Miguel Gonçalves | AVANADE 811 Reputation points

2024-06-12T16:53:07.06+00:00
Hi Gebauer,

The “440 Login Timeout” error can be quite frustrating, but lets start;

Exchange version?

"Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion"

Already done "iisreset"?

OWA from mobile browser, same issue?

Online Test errors? https://testconnectivity.microsoft.com/tests/exchange

Your Admin mailbox is on an Exchange Server. If the admin account has no mailbox, ensure that all arbitration mailboxes (especially the “SystemMailbox {bb558c35-97f1-4cb9-8ff7-d53741dc928c}”) are on an Exchange Server. https://support.microsoft.com/en-us/topic/cumulative-update-23-for-exchange-server-2016-kb5011155-98183ada-e4cd-465f-b201-69d40fb74678
Gebauer, Roman 0 Reputation points

2024-06-13T06:30:25.09+00:00
Hi Miguel!- Exchange Version 15.1 (Build 2507.6

Tried iisreset multiple times and of course multiple clean Server boots

OWA from mobile Safari -> same result

No errors in the MS Connectivity Test, Autodiscover and everything works fine

You mean the Domain administrator Account? Yes it has a Mailbox

These are my arbitration Mailboxes: Name ServerName Database AdminDisplayVersion

FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 Servername DB01 Version 15.1 (Build 2507.6)

SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} Servername DB01 Version 15.1 (Build 2507.6)

SystemMailbox{1f05a927-369e-40cb-9613-2b74bba4e81e} Servername DB01 Version 15.1 (Build 2507.6)

SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} Servername DB01 Version 15.1 (Build 2507.6)

Migration.8f3e7716-2011-43e4-96b1-aba62d229136 Servername DB01 Version 15.1 (Build 2507.6)

SystemMailbox{D0E409A0-AF9B-4720-92FE-AAC869B0D201} Servername DB01 Version 15.1 (Build 2507.6)

SystemMailbox{2CE34405-31BE-455D-89D7-A7C7DA7A0DAA} Servername DB01 Version 15.1 (Build 2507.6)

This is the only relevant Event Error I can find:

ASP.NET 4.0.30319.0

Event sequence: 7804

Event occurrence: 7803

Event detail code: 0

Application information:

Application domain: /LM/W3SVC/1/ROOT/owa/Calendar-3-133624990251024301

Trust level: Full

Application Virtual Path: /owa/Calendar

Application Path: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\owa\

Machine name: SERVERNAME

Process information:

Process ID: 12528

Process name: w3wp.exe

Account name: NT-AUTORITÄT\SYSTEM

Exception information:

Exception type: HttpException

Exception message: Keine Umleitung, nachdem die HTTP-Header gesendet wurden.

   bei System.Web.HttpResponse.Redirect(String url, Boolean endResponse, Boolean permanent)

   bei Microsoft.Exchange.HttpProxy.FbaModule.RedirectToFbaLogon(HttpApplication httpApplication, LogonReason reason)

   bei Microsoft.Exchange.HttpProxy.FbaModule.OnEndRequestInternal(HttpApplication httpApplication)

   bei Microsoft.Exchange.HttpProxy.ProxyModule.<>c__DisplayClass20_0.<OnEndRequest>b__0()

   bei Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func2 filterDelegate, Action1 catchDelegate)

   bei System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

   bei System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)

   bei System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Request information:

Request URL: https://localhost:443/OWA/Calendar/HealthMailboxbd9f62d723fd4ad8a564177a00d8bc73@Huber.int/calendar/calendar.html

Request path: /OWA/Calendar/HealthMailboxbd9f62d723fd4ad8a564177a00d8bc73@Huber.int/calendar/calendar.html

User host address: ::1

User:

Is authenticated: False

Authentication Type:

Thread account name: NT-AUTORITÄT\SYSTEM

Thread information:

Thread ID: 244

Thread account name: NT-AUTORITÄT\SYSTEM

Is impersonating: False

Stack trace: bei System.Web.HttpResponse.Redirect(String url, Boolean endResponse, Boolean permanent)

   bei Microsoft.Exchange.HttpProxy.FbaModule.RedirectToFbaLogon(HttpApplication httpApplication, LogonReason reason)

   bei Microsoft.Exchange.HttpProxy.FbaModule.OnEndRequestInternal(HttpApplication httpApplication)

   bei Microsoft.Exchange.HttpProxy.ProxyModule.<>c__DisplayClass20_0.<OnEndRequest>b__0()

   bei Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func2 filterDelegate, Action1 catchDelegate)

   bei System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

   bei System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)

   bei System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Custom event details:Event sequence: 7804

Event occurrence: 7803

Event detail code: 0

Application information:

Application domain: /LM/W3SVC/1/ROOT/owa/Calendar-3-133624990251024301

Trust level: Full

Application Virtual Path: /owa/Calendar

Application Path: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\owa\

Machine name: SERVERNAME

Process information:

Process ID: 12528

Process name: w3wp.exe

Account name: NT-AUTORITÄT\SYSTEM

Exception information:

Exception type: HttpException

Exception message: Keine Umleitung, nachdem die HTTP-Header gesendet wurden.

   bei System.Web.HttpResponse.Redirect(String url, Boolean endResponse, Boolean permanent)

   bei Microsoft.Exchange.HttpProxy.FbaModule.RedirectToFbaLogon(HttpApplication httpApplication, LogonReason reason)

   bei Microsoft.Exchange.HttpProxy.FbaModule.OnEndRequestInternal(HttpApplication httpApplication)

   bei Microsoft.Exchange.HttpProxy.ProxyModule.<>c__DisplayClass20_0.<OnEndRequest>b__0()

   bei Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func2 filterDelegate, Action1 catchDelegate)

   bei System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

   bei System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)

   bei System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Request information:

Request URL: https://localhost:443/OWA/Calendar/HealthMailboxbd9f62d723fd4ad8a564177a00d8bc73@Huber.int/calendar/calendar.html

Request path: /OWA/Calendar/HealthMailboxbd9f62d723fd4ad8a564177a00d8bc73@Huber.int/calendar/calendar.html

User host address: ::1

User:

Is authenticated: False

Authentication Type:

Thread account name: NT-AUTORITÄT\SYSTEM

Thread information:

Thread ID: 244

Thread account name: NT-AUTORITÄT\SYSTEM

Is impersonating: False

Stack trace: bei System.Web.HttpResponse.Redirect(String url, Boolean endResponse, Boolean permanent)

   bei Microsoft.Exchange.HttpProxy.FbaModule.RedirectToFbaLogon(HttpApplication httpApplication, LogonReason reason)

   bei Microsoft.Exchange.HttpProxy.FbaModule.OnEndRequestInternal(HttpApplication httpApplication)

   bei Microsoft.Exchange.HttpProxy.ProxyModule.<>c__DisplayClass20_0.<OnEndRequest>b__0()

   bei Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func2 filterDelegate, Action1 catchDelegate)

   bei System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

   bei System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)

   bei System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Custom event details:

1 answer

Jake Zhang-MSFT 2,400 Reputation points Microsoft Vendor

2024-06-17T09:29:22.17+00:00
Hi @Gebauer, Roman，

Welcome to the Microsoft Technical Support Forum.

Based on your description, the error you are experiencing usually indicates a problem in the HTTP request/response cycle and is usually related to configuration issues in IIS, authentication settings, or Exchange redirection settings.

I recommend that you follow some of the following troubleshooting steps:

1.Check Redirect Settings in IIS：

Open IIS Manager.

Navigate to the Default Web Site.

Select the HTTP Redirect feature.

Ensure that redirection settings are configured correctly or disable them if they are not needed.

2.Sometimes, issues in the web.config file can cause such errors. Look for any custom redirection rules or errors in the web.config file for OWA and ECP.

The web.config files are usually located in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa and C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp.

3.Re-check the authentication settings for the OWA and ECP directories in IIS:

Open IIS Manager. - Navigate to the Default Web Site and select the owa and ecp directories.

Under the Authentication feature, ensure that Basic Authentication and Windows Authentication are enabled, and Anonymous Authentication is disabled.

Please feel free to contact me if you have any queries.

Best,

Jake Zhang
Please sign in to rate this answer.
Gebauer, Roman 0 Reputation points

2024-06-18T08:59:57.1466667+00:00

Hi Jake!

There is no redirect configured on the default Web Site.
I only habe the URL Rewrite Rule EEMS 1.1

I can't find any redirects in the web.config files, but I may be worth testing to regenerate these files?

On ECP Frontend I have Anonymous and Basic Auth acitvated On OWA Frontend I have only Basic Auth activated But I think this ist correct, because I installed a fresh Exchange 2016 CU23 for testing. OWA and ECP works correct on this Test Server and the Auth settings are exactly the same as I have it on my faulty Exchange Server.

Regards

Roman

Jake Zhang-MSFT 2,400 Reputation points Microsoft Vendor

2024-06-20T10:19:50.91+00:00

Hi @Gebauer, Roman，

Thanks for your response.Based on your description, since the setup is fine on the test server, the problem is focused on a specific Exchange server, and you can further try the following methods to find and resolve the issue:1. It is necessary to check the web.config file

Compare the 'web.config' file of the problematic server with that of the test server:

a. Navigate to 'C:\inetpub\wwwroot' and 'C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp'. 2.

b. Compare the 'web.config' files in these two locations to see if there are any differences. 3.

c. If there are differences, consider copying the 'web.config' file from the test server to the problem server.

Clean up ASP.NET temporary files

Sometimes temporary files compiled by ASP.NET may cause problems, you can try to clean up these files:

a. Stop IIS:

iisreset /stop

b. Delete the temporary files:

Navigate to 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files' and 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ Temporary ASP.NET Files' and 'C: \Windows\Microsoft.NET\Framework64\v4.0.30319\var', delete all the contents.

c. Restart IIS:

iisreset /start

Please feel free to contact me if you have any queries.

Best,

Jake Zhang
Sign in to comment

Share via

Exchange 2016 OWA - 440 Login Timeout

1 answer