Invalid username and passorword accessing OWA and ECP

Article
2020-06-28

Question

_{Sunday, June 28, 2020 12:44 PM}

Hi.

First of all, thank you for reading this blog and for trying to help me with my problem.

I have had this problem for a week or so. And I hope that anyone can help me. Please put in "own server" in commands if you send me some.

I have change and recreated this information on my exchange 2016 server:

- OWA VirDir

- ECP VirDir

- External and Internal url

This is my owa and ecp Auth

[PS] C:\WINDOWS\system32>Get-owavirtualdirectory |fl *url,*authentication

Url : {}
InternalSPMySiteHostURL :
ExternalSPMySiteHostURL :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl : https://xx.mydomain/owa
ExternalUrl : https://xx.mydomain/owa
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False

[PS] C:\WINDOWS\system32>Get-ecpvirtualdirectory |fl *url,*authentication

InternalUrl : https://xx.mydomain//ecp
ExternalUrl : https://xx.mydomain//ecp
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False

I can reach the owa and ecp login page, but when I type the username and password, the error is: Invalid Username or Password, please try again.

I might be an solution in this forum, but please do not send me links, please post the thinks you want me to do in this blog.

I really need help to solve my problem.

Thanks again.

Atle76

All replies (23)

_{Wednesday, July 15, 2020 2:08 AM ✅Answered | 1 vote}

Hi.

This issue is now solved.

Check the link:

/en-us/answers/questions/46764/invalid-username-and-password-accessing-owa-and-ec.html

Thank you very much everyone that has helped me with my problem, and spend time to solve this issue. I really appriciate it. Thank you again.

Atle76

_{Sunday, June 28, 2020 4:54 PM}

Hi,

In Forms Based Authentication, you can login with any of the methods>domain name\username, User Principal Name, user name only.

Please try any of the methods in this list is working?

Regards From: Exchange Online | World of Cloud Computing

_{Monday, June 29, 2020 5:47 AM}

Hi Atle76,

Have you made any changes in your environment right before the issue started?
Does this problem affect all users? For the problematic users, are they able to setup their accounts in Outlook with the same credentials?
Can you access OWA or ECP on the Exchange server by localhost?
Have you run iisreset /noforce to reset IIS after making the changes?

Please have a look at the Event viewer and see if any relevant events were recorded out there.

Besides, it’s recommended to try the things below and see the results:

Check the Site bindings for both the Default Web site and Exchange Back End in IIS manager, make sure the correct certificate is selected.
Check the Authentication method set for OWA and ECP via IIS Manager for both the frontend and Back End virtual directories. Compare the result with the default settings in this link.
Execute the "UpdateCAS.ps1" and “UpdateConfigFiles.ps1” scripts from the Exchange install directory scripts subfolder:
• C:\Program Files\Microsoft\Exchange Server\V15\Bin>.\UpdateCas.ps1
• C:\Program Files\Microsoft\Exchange Server\V15\Bin>.\UpdateConfigFiles.ps1

Any update, please feel free to post back.

Regards,

Yuki Sun

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Monday, June 29, 2020 8:54 PM}

Hi Yuki.

Thank you very much for your reply and advice. You can see my comments in bold under your questions.

I am running Windows Server 2016 and Exchange 2016 U16.

I can send and recive email, but I can't access the mailbox. We can't logon to the mailbox using outlook or web, or other clients exept mobilephones that already had the config before this happend.

Thank you again for helping me with this problem.

*******************************************************

Have you made any changes in your environment right before the issue started?

**** I changed the internal and external url.

Does this problem affect all users? For the problematic users, are they able to setup their accounts in Outlook with the same credentials?

***** Yes It effect all users.

Can you access OWA or ECP on the Exchange server by localhost?

****** Not by localhost or the Exchange Managemnt Consoll - I have to type the internal url.

Have you run iisreset /noforce to reset IIS after making the changes?

******Yes, but when I run the command, the iis server stop, but can not start it again. Have to use IIS Managment Server Consol to restart og start the service.

Besides, it’s recommended to try the things below and see the results:

Check the Site bindings for both the Default Web site and Exchange Back End in IIS manager, make sure the correct certificate is selected.

****** Yes, my own SSL certificate that I use for the exch.server is used on both.

Check the Authentication method set for OWA and ECP via IIS Manager for both the frontend and Back End virtual directories. Compare the result with the default settings in this link.

****** Checked and set the the default settings for all.

Execute the "UpdateCAS.ps1" and “UpdateConfigFiles.ps1” scripts from the Exchange install directory scripts subfolder:
• C:\Program Files\Microsoft\Exchange Server\V15\Bin>.\UpdateCas.ps1
• C:\Program Files\Microsoft\Exchange Server\V15\Bin>.\UpdateConfigFiles.ps1

***** Has executed both update files.

I still have the same problem. Can not logon to owa or ecp. - Invalid username or password. Please try again.

Atle76

_{Monday, June 29, 2020 8:59 PM}

Hi ManU

Thank you for helping me.

I can't logon with domain\username or only username.

Still got the same: Invalid username or password. Please try again.

Atle76

_{Wednesday, July 1, 2020 9:44 AM}

Hi Atle76,

>> We can't logon to the mailbox using outlook or web
May I know the symptom in Outlook?
Please test Autodiscover by running the “Test Email-AutoConfiguration” in Outlook and see if it works fine.

In addition, as mentioned earlier, would you please have a look at the Event Viewer and check if there are any relevant event logs.

Regards,

Yuki Sun

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Wednesday, July 1, 2020 12:41 PM}

Hi Yuki.

I can't logon to the outlook. Prompted by the login.

I can create an account for you on the server, so you can check everything you need if you want. Please send me an mail to [email protected] and I will send you the username and password for the server.

Like I said earliger:

- The website is OK

- In and out e-mail is OK

- But can't logon to accounts from outlook og owa/ecp.

Best regards and thanks again for the help.

Atle76

_{Wednesday, July 1, 2020 1:22 PM}

Hi Atle76,

Any changes to the AD accounts for these mailboxes?

Can you create a new test mailbox from exchange and place the test AD account in default users OU and try to login?

Also check if the connectivity between the exchange server and the domain controllers are fine. Verify the AD replication as well.

As Yuki suggested, have you checked the event viewer when you get the error message in OWA.

Thanks,
Ashok M My blog
________________________________________________________________
Please mark the reply as an answer if you find it is helpful :-)
________________________________________________________________

_{Thursday, July 2, 2020 1:55 AM}

Hi Atle,

I do want to help fix the issue, but please understand that due to our policy of forum support, we are limited to discuss over the issue within the forum. And considering that the forum is public, it’s not recommended to share any personal information in the post. We have covered the email address involved in your last reply for privacy-related concerns.

Regarding this issue, could you please check the event viewer for relevant events so that we can do further research on this?

What’s more, it’s also suggested to go through the IIS logs which by default located at %SystemDrive%\inetpub\logs\LogFiles and see if any more clues can be found.

Regards,

Yuki Sun

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, July 2, 2020 12:32 PM}

Hi Yuki.

Thank you again.

Ok, I am just begin to be desperate to solve this problem or issue.

Here is some info on the IIS event.

A process serving application pool 'MSExchangePowerShellFrontEndAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '6372'. The data field contains the error number.

*****

A process serving application pool 'MSExchangeSyncAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '10072'. The data field contains the error number.

******

A process serving application pool 'MSExchangeMapiFrontEndAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '11508'. The data field contains the error number.

******

A process serving application pool 'MSExchangeECPAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '15180'. The data field contains the error number.

********

A process serving application pool 'MSExchangeAutodiscoverAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '11844'. The data field contains the error number.

*********

From the log file: ( some of it )

#Software: Microsoft Internet Information Services 10.0
#Version: 1.0
#Date: 2020-07-02 00:00:03
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
2020-07-02 00:00:03 127.0.0.1 GET /ecp/ &CorrelationID=<empty>;&cafeReqId=881c28d6-781e-4007-8209-21c55c68a9b3;&LogoffReason=NoCookiesGetOrE14AuthPost 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 302 0 0 2
2020-07-02 00:00:08 127.0.0.1 GET /RPC/rpcproxy.dll [email protected]&CorrelationID=<empty>;&RequestId=de301e2f-3ed8-45c6-9ccb-a76cc5d72e17&cafeReqId=de301e2f-3ed8-45c6-9ccb-a76cc5d72e17; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 2 5 9
2020-07-02 00:00:11 127.0.0.1 GET /ecp/ReportingWebService/ &CorrelationID=<empty>;&cafeReqId=a44aa298-6e74-4b5a-901b-3029374e0cde;&LogoffReason=NoCookiesGetOrE14AuthPost 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 302 0 0 2
2020-07-02 00:00:12 127.0.0.1 GET /Microsoft-Server-ActiveSync/default.eas &CorrelationID=<empty>;&cafeReqId=a55326bd-49ec-42a1-b20c-a00cc023e5d6; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 2 5 2
2020-07-02 00:00:13 127.0.0.1 GET /PowerShell/ &CorrelationID=<empty>; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 111 0 13
2020-07-02 00:00:13 127.0.0.1 GET /PowerShell/ &CorrelationID=<empty>; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 111 0 15
2020-07-02 00:00:19 127.0.0.1 GET /ews/ &CorrelationID=<empty>;&cafeReqId=073ab177-0abf-4fa6-bf8b-7e23ed15dffa; 443 LBRL\HealthMailboxe737625 127.0.0.1 AMProbe/Local/ClientAccess - 200 0 0 5
2020-07-02 00:00:37 127.0.0.1 GET /mapi/emsmdb [email protected]&CorrelationID=<empty>;&cafeReqId=af071259-1e8e-4ff4-a59d-bdfd918e01b6; 443 LBRL\HealthMailboxe737625 127.0.0.1 AMProbe/Local/ClientAccess - 200 0 0 5
2020-07-02 00:00:39 127.0.0.1 GET /OWA/Calendar/[email protected]/calendar/calendar.html &CorrelationID=<empty>;&cafeReqId=d3d67d7a-a737-47a0-81df-a21d7587434a; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 200 0 0 4
2020-07-02 00:00:41 127.0.0.1 GET /AutoDiscover/ &CorrelationID=<empty>;&cafeReqId=5a1e8a74-b900-4f34-aab6-a82162c9f755; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 0 0 2
2020-07-02 00:00:44 127.0.0.1 GET /OAB/ &CorrelationID=<empty>;&cafeReqId=2af1f5eb-ea26-4c50-a92f-f8b1b954a441; 443 LBRL\HealthMailboxe737625 127.0.0.1 AMProbe/Local/ClientAccess - 200 0 0 10
2020-07-02 00:00:49 127.0.0.1 POST /OWA/auth.owa &CorrelationID=<empty>;&cafeReqId=cdc837e3-3ceb-41f8-8bf1-93b61e649e3b;&encoding=; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 302 0 0 1
2020-07-02 00:00:55 fe80::55b6:da0a:7c62:fd21%11 POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.14393.3471&CorrelationID=<empty>;&cafeReqId=a3cab5d8-4ea9-43d3-8a0a-fccb2ecf88a2; 80 - fe80::55b6:da0a:7c62:fd21%11 Microsoft+WinRM+Client - 200 0 0 2
2020-07-02 00:00:55 fe80::55b6:da0a:7c62:fd21%11 POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.14393.3471&CorrelationID=<empty>;&cafeReqId=d8c17abe-4716-45e8-bcd7-1dad098c4de2; 80 LBRL\HealthMailboxe737625 fe80::55b6:da0a:7c62:fd21%11 Microsoft+WinRM+Client - 200 0 0 42
2020-07-02 00:00:55 fe80::55b6:da0a:7c62:fd21%11 POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.14393.3471&sessionID=Version_15.1_(Build_1978.0)=rJqNiZqNgbO9rbPSrJqNiZqN0ZOdjZPRk5CcnpOBzsbLzc/JzM/MyoHNz83P0s/I0s/Nq8/Pxc7PxcrK&CorrelationID=<empty>;&cafeReqId=9b0c0775-d78b-4b1c-ba05-ff96f3593189; 80 - fe80::55b6:da0a:7c62:fd21%11 Microsoft+WinRM+Client - 200 0 0 3
2020-07-02 00:00:55 fe80::55b6:da0a:7c62:fd21%11 POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.14393.3471&sessionID=Version_15.1_(Build_1978.0)=rJqNiZqNgbO9rbPSrJqNiZqN0ZOdjZPRk5CcnpOBzsbLzc/JzM/MyoHNz83P0s/I0s/Nq8/Pxc7PxcrK&CorrelationID=<empty>;&cafeReqId=1f20615b-9078-44ef-9e42-14a562dff070; 80 LBRL\HealthMailboxe737625 fe80::55b6:da0a:7c62:fd21%11 Microsoft+WinRM+Client - 200 0 0 279
2020-07-02 00:00:55 fe80::55b6:da0a:7c62:fd21%11 POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.14393.3471&sessionID=Version_15.1_(Build_1978.0)=rJqNiZqNgbO9rbPSrJqNiZqN0ZOdjZPRk5CcnpOBzsbLzc/JzM/MyoHNz83P0s/I0s/Nq8/Pxc7PxcrJ&CorrelationID=<empty>;&cafeReqId=80ad68bd-6023-4d5c-ac89-5cbc93d90aff; 80 LBRL\HealthMailboxe737625 fe80::55b6:da0a:7c62:fd21%11 Microsoft+WinRM+Client - 200 0 0 21
2020-07-02 00:00:55 fe80::55b6:da0a:7c62:fd21%11 POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.14393.3471&sessionID=Version_15.1_(Build_1978.0)=rJqNiZqNgbO9rbPSrJqNiZqN0ZOdjZPRk5CcnpOBzsbLzc/JzM/MyoHNz83P0s/I0s/Nq8/Pxc7PxcrJ&CorrelationID=<empty>;&cafeReqId=a28c1a8d-009f-42b5-9fb5-9aba4a53315d; 80 LBRL\HealthMailboxe737625 fe80::55b6:da0a:7c62:fd21%11 Microsoft+WinRM+Client - 200 0 0 74
2020-07-02 00:00:55 fe80::55b6:da0a:7c62:fd21%11 POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.14393.3471&sessionID=Version_15.1_(Build_1978.0)=rJqNiZqNgbO9rbPSrJqNiZqN0ZOdjZPRk5CcnpOBzsbLzc/JzM/MyoHNz83P0s/I0s/Nq8/Pxc7PxcrJ&CorrelationID=<empty>;&cafeReqId=24d2682a-2510-45b5-b485-44ce3959f6cc; 80 - fe80::55b6:da0a:7c62:fd21%11 Microsoft+WinRM+Client - 200 0 0 3
2020-07-02 00:00:55 fe80::55b6:da0a:7c62:fd21%11 POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.14393.3471&sessionID=Version_15.1_(Build_1978.0)=rJqNiZqNgbO9rbPSrJqNiZqN0ZOdjZPRk5CcnpOBzsbLzc/JzM/MyoHNz83P0s/I0s/Nq8/Pxc7PxcrJ&CorrelationID=<empty>;&cafeReqId=ee9ba3f8-dd25-4e13-b87a-c5985647ba0d; 80 LBRL\HealthMailboxe737625 fe80::55b6:da0a:7c62:fd21%11 Microsoft+WinRM+Client - 200 0 0 99
2020-07-02 00:00:55 fe80::55b6:da0a:7c62:fd21%11 POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.14393.3471&sessionID=Version_15.1_(Build_1978.0)=rJqNiZqNgbO9rbPSrJqNiZqN0ZOdjZPRk5CcnpOBzsbLzc/JzM/MyoHNz83P0s/I0s/Nq8/Pxc7PxcrJ&CorrelationID=<empty>;&cafeReqId=a410434f-ad2e-47e8-a7a0-da68c1f49486; 80 LBRL\HealthMailboxe737625 fe80::55b6:da0a:7c62:fd21%11 Microsoft+WinRM+Client - 200 0 0 18
2020-07-02 00:00:55 fe80::55b6:da0a:7c62:fd21%11 POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.14393.3471&sessionID=Version_15.1_(Build_1978.0)=rJqNiZqNgbO9rbPSrJqNiZqN0ZOdjZPRk5CcnpOBzsbLzc/JzM/MyoHNz83P0s/I0s/Nq8/Pxc7PxcrJ&CorrelationID=<empty>;&cafeReqId=6a3c4930-6037-4ecf-8dbf-2f5244609f81; 80 LBRL\HealthMailboxe737625 fe80::55b6:da0a:7c62:fd21%11 Microsoft+WinRM+Client - 500 0 64 226
2020-07-02 00:00:55 fe80::55b6:da0a:7c62:fd21%11 POST /powershell clientApplication=ActiveMonitor;PSVersion=5.1.14393.3471&sessionID=Version_15.1_(Build_1978.0)=rJqNiZqNgbO9rbPSrJqNiZqN0ZOdjZPRk5CcnpOBzsbLzc/JzM/MyoHNz83P0s/I0s/Nq8/Pxc7PxcrJ&CorrelationID=<empty>;&cafeReqId=d6fca0fe-b1f5-423e-a394-08b96af2d562; 80 LBRL\HealthMailboxe737625 fe80::55b6:da0a:7c62:fd21%11 Microsoft+WinRM+Client - 200 0 0 18
2020-07-02 00:01:03 127.0.0.1 GET /ecp/ &CorrelationID=<empty>;&cafeReqId=5c7a73d8-56aa-4659-98b3-29a85621ef8a;&LogoffReason=NoCookiesGetOrE14AuthPost 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 302 0 0 2
2020-07-02 00:01:08 127.0.0.1 GET /RPC/rpcproxy.dll [email protected]&CorrelationID=<empty>;&RequestId=98266914-7b8f-46eb-90d4-2d9dee8a70a3&cafeReqId=98266914-7b8f-46eb-90d4-2d9dee8a70a3; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 2 5 12
2020-07-02 00:01:11 127.0.0.1 GET /ecp/ReportingWebService/ &CorrelationID=<empty>;&cafeReqId=2317a19f-f792-444e-bedd-fc9afe9502c9;&LogoffReason=NoCookiesGetOrE14AuthPost 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 302 0 0 3
2020-07-02 00:01:12 127.0.0.1 GET /Microsoft-Server-ActiveSync/default.eas &CorrelationID=<empty>;&cafeReqId=d6fd2f67-49be-46ce-aeca-06d6131869d9; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 2 5 3
2020-07-02 00:01:13 127.0.0.1 GET /PowerShell/ &CorrelationID=<empty>; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 111 0 14
2020-07-02 00:01:13 127.0.0.1 GET /PowerShell/ &CorrelationID=<empty>; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 111 0 15
2020-07-02 00:01:20 127.0.0.1 GET /ews/ &CorrelationID=<empty>;&cafeReqId=27a16cc7-20cf-415a-9431-01977932ed02; 443 LBRL\HealthMailboxe737625 127.0.0.1 AMProbe/Local/ClientAccess - 200 0 0 5
2020-07-02 00:01:37 127.0.0.1 GET /mapi/emsmdb [email protected]&CorrelationID=<empty>;&cafeReqId=0a1b84aa-debd-4021-892a-8b5b0ffee077; 443 LBRL\HealthMailboxe737625 127.0.0.1 AMProbe/Local/ClientAccess - 200 0 0 5
2020-07-02 00:01:39 127.0.0.1 GET /OWA/Calendar/[email protected]/calendar/calendar.html &CorrelationID=<empty>;&cafeReqId=bffd0e9a-dc5e-4b8d-a099-188a8fe67954; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 200 0 0 4
2020-07-02 00:01:41 127.0.0.1 GET /AutoDiscover/ &CorrelationID=<empty>;&cafeReqId=b87c1958-27bd-4a14-b414-d12b02277f79; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 0 0 2
2020-07-02 00:01:44 127.0.0.1 GET /OAB/ &CorrelationID=<empty>;&cafeReqId=a1ef965d-6388-44ea-bc0d-7f18925c7124; 443 LBRL\HealthMailboxe737625 127.0.0.1 AMProbe/Local/ClientAccess - 200 0 0 10
2020-07-02 00:01:46 127.0.0.1 POST /Microsoft-Server-ActiveSync/default.eas Cmd=Settings&[email protected]&DeviceId=EASProbeDeviceId141&DeviceType=EASProbeDeviceType&CorrelationID=<empty>;&cafeReqId=917ae1de-8f89-4f40-b45e-03f76bd240d4; 443 [email protected] 127.0.0.1 TestActiveSyncConnectivity - 200 0 0 59
2020-07-02 00:01:49 127.0.0.1 POST /OWA/auth.owa &CorrelationID=<empty>;&cafeReqId=ab884fdb-103d-46ad-9c90-284d2875dc2e;&encoding=; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 302 0 0 2
2020-07-02 00:02:03 127.0.0.1 GET /ecp/ &CorrelationID=<empty>;&cafeReqId=d87dd27e-e983-4e6e-9865-e18bdd32c779;&LogoffReason=NoCookiesGetOrE14AuthPost 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 302 0 0 2
2020-07-02 00:02:08 127.0.0.1 GET /RPC/rpcproxy.dll [email protected]&CorrelationID=<empty>;&RequestId=869983c8-afa0-48ea-923e-1ed6a4f06cd3&cafeReqId=869983c8-afa0-48ea-923e-1ed6a4f06cd3; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 2 5 2
2020-07-02 00:02:11 127.0.0.1 GET /ecp/ReportingWebService/ &CorrelationID=<empty>;&cafeReqId=1ff6de49-86cb-412c-8038-e1b7483075e1;&LogoffReason=NoCookiesGetOrE14AuthPost 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 302 0 0 3
2020-07-02 00:02:12 127.0.0.1 GET /Microsoft-Server-ActiveSync/default.eas &CorrelationID=<empty>;&cafeReqId=db77ffbb-0bf4-4334-b156-5b2bbcac6a4e; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 2 5 2
2020-07-02 00:02:13 127.0.0.1 GET /PowerShell/ &CorrelationID=<empty>; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 111 0 11
2020-07-02 00:02:13 127.0.0.1 GET /PowerShell/ &CorrelationID=<empty>; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 111 0 14

Atle76

_{Friday, July 3, 2020 8:19 AM}

Hi Atle,

As regards to the application pools mentioned in the events above, could you please have a check via IIS manager and see whether the status of them are all show as “Started”?

Besides, please make sure all services related to Exchange have been started on the server.
It’s also suggested to check if the Exchange server has high CPU or memory usage.

By the way, by “I have to type the internal url”, do you mean you are not able to access OWA or ECP via https://localhost/owa or https://localhost/ecp on the Exchange server itself?
If that is the case, may I know the detailed error message you encountered? (Please remember to remove the personal information like domain name or email address when sharing the information)

Regards,

Yuki Sun

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Friday, July 3, 2020 3:46 PM}

Hi Yuki.

Thanks again.

Every app pool has started.

No, I can't access the owa or ecp using https://localhost/owa on the server.

I have to use: https://xxx.domain/owa or ecp.

Atle76

_{Saturday, July 4, 2020 5:01 PM}

Hi Yuki.

Thanks again.

Every app pool has started.

No, I can't access the owa or ecp using https://localhost/owa on the server.

I have to use: https://xxx.domain/owa or ecp.

Atle76

What is the error message when you try to login to https://localhost/owa and ecp on the server?

_{Monday, July 6, 2020 1:31 PM}

Hi Ashok M

Thank you for reply on my issue.

The error message is:

Can't reach the page - ERR_Connection_Reset

Atle76

_{Monday, July 6, 2020 3:03 PM}

Hi Atle76,

Did you get any HTTP error code in the webpage or on the address bar?

Any errors in Application logs in event viewer?

Can you try re-creating the OWA & ECP virtual directory by using the below commands,

Remove -OwaVirtualDirectory -Identity "Servername\owa (Default Web Site)"

New-OwaVirtualDirectory -WebSiteName "Default Web Site" -InternalUrl "https://FQDN/owa" -ExternalUrl "https://FQDN/owa" -BasicAuthentication:$True -FormsAuthentication:$True


Remove-EcpVirtualDirectory -Identity "Servername\ecp (Default Web Site)"

New-EcpVirtualDirectory -WebSiteName "Default Web Site" -InternalUrl "https://FQDN/ecp"  -ExternalUrl "https://FQDN/ecp" -BasicAuthentication:$True -FormsAuthentication:$True

_{Monday, July 6, 2020 8:49 PM}

Hi Ashok M

I have tried to recreate the OWA and ECP earlier.. Do you want me to do it again.

The event log is copied in over.

Thank you again.

Atle76

_{Tuesday, July 7, 2020 6:26 AM}

Hi Atle76,

No, that's fine if it was already re-created. Earlier, you mentioned, outlook also prompts for credentials.

Any changes to the AD accounts for these mailboxes?

Can you create a new test mailbox from exchange and place the test AD account in default users OU and try to login in outlook/owa?

Also check if the connectivity between the exchange server and the domain controllers are fine. Verify the AD replication as well.

For an existing user, what is the status of the outlook profile? can you run Test-EmailAutoConfiguration and check if the prompt appears?

_{Tuesday, July 7, 2020 6:59 AM}

1. You have to check certificates - one with included all dns-names shoud be assign to Front-End and another one (self-signed) shoud be assigned to Back-End. Be sure both certificates are really assigned and valid.

2. Check you IP configuration for Exchange - which DNS servers are using for it?

3. Check you Domain Controller logs - did you find these errors with wrong login/password?

_{Sunday, July 12, 2020 10:48 PM}

Hi Alexey.

Thank you for helping me. I have answered your quest under each number.

*** I have checked the certificates and they should be right.

2. Check you IP configuration for Exchange - which DNS servers are using for it?

***** I can reach the localhost/owa now, and I can reach the external url for the owa and ecp login page. But I can't login.

3. Check you Domain Controller logs - did you find these errors with wrong login/password?

****** I can't find anything wrong there.

No users can logon to the owa or ecp. It seems that the users are not linked to the exchange by username and password.

I can't test or receive email in outlook, only on my mobile phone, I can receive and read emails. I can both send and recive. But I can't access the mailboxes from web or outlook.

I am starting to get desperate, so please help me with this issue.

Atle76

_{Tuesday, July 14, 2020 9:21 AM}

Hi Atle76,

Have you tried changing the Back-End certificate to the Self-Signed certificate(Microsoft Exchange) and checked if there was any difference after restarting IIS?

Besides, as regards to the Test-EmailAutoConfiguration in Outlook, you may launch Outlook first by adding a personal account like an outlook.com account, then use the credentials of a problematic user account when performing the test. Once the tests finished, check the output in the Results and Log tab.

This Exchange Server 2016 - Setup, Deployment, Updates and Migration Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post** for more details.**

Regards,

Yuki Sun

Exchange Server 2016 - Setup, Deployment, Updates and Migration forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

For more information, please refer to the sticky post.

_{Tuesday, July 14, 2020 12:47 PM}

Hi Yuki Sun.

Thank you for your answer.

I have tried to change the certificate, but no changes for logon.

I can still reach all the pages owa, ecp and localhost. But I still got Invalid username and password. Please try again later.

This happend for all the mailbox users, but everyone can logon to the Windows Server 2016.

/en-us/answers/questions/46764/invalid-username-and-password-accessing-owa-and-ec.html

Atle76

_{Wednesday, July 15, 2020 1:55 AM}

Hi Atle76,

Thanks for getting back.

I checked your link of the new post in Microsoft Q&A and really glad to see that you have got this issue sorted out!! Below is a brief summary of this thread based on your sharing in Microsoft Q&A for quick reference.

Issue Symptom:
Windows Server 2016 and Exchange 2016 CU16

After changing the internal and external url, the OWA, ECP and localhost pages can be reached, but the following error prompts event if the credentials are correct:
"Invalid username or password, please try again later"

It occurs to all users. Both OWA and ECP VirDirs have been recreated but no luck.

Solution:
Using the commands:

Set-OWAVirtualDirectory -Identity "adminsrv\OWA (Default Web Site)" -FormsAuthentication $False -BasicAuthentication $True

Set-OWAVirtualDirectory -Identity "adminsrv\OWA (Default Web Site)" -FormsAuthentication $true -BasicAuthentication $True

Followed by IISreset and also to recycle the app pools for OWA and ECP

Reference Links:
Exchange 2013 unable to login to OWA/ECP
(Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)

This Exchange Server 2016 - Setup, Deployment, Updates and Migration Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post** for more details.**

Regards,

Yuki Sun

Exchange Server 2016 - Setup, Deployment, Updates and Migration forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

For more information, please refer to the sticky post.

_{Wednesday, July 15, 2020 2:12 AM}

Hi Atle76,

Thanks again for your valuable sharing! Have a nice day :)

This Exchange Server 2016 - Setup, Deployment, Updates and Migration Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post** for more details.**

Regards,

Yuki Sun

Exchange Server 2016 - Setup, Deployment, Updates and Migration forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

For more information, please refer to the sticky post.

Share via

Invalid username and passorword accessing OWA and ECP

Question

All replies (23)

Additional resources