Hi,

Please refer to Sathish's suggestion to have a check. And I will add some related information.

Does all exchange 2013 users occur the issue?

Please confirm if outlook client can connect to exchange server.

Please check OWA setting on IIS. By default only Basic Authentication should be enabled.

Have you try to recreate OWA virtual directory ?

Please check your application log and post related error here for further analysis.

Best Regards,

David

You can re-create OWA virtual directory:

http://exchangeonline.in/re-create-owa-virtual-directory-exchange-2013/

Note: Do not forget to backup OWA settings first (e.g. internal/external URL)

I Have two exchange 2013 fresh server but problem is same on both exchange server 2013

Exchange 2007 Sp3 to Exchange server 2013 CU8

Yes All Exchange 2013 OWA is not open.

Application Logs : 

Are you trying to log in from Exchange 2013 OWA into Exchange 2007 mailbox?
If yes, have you configured legacy OWA URL for Exchange 2007?

http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/

Exchange 2013 to Exchange 2007 OWA is working fine 

New Exchange 2013 Mailbox is not open in Exchange server 2013 Server

Can you connect to your exchange 2013 mailbox using e.g. Outlook or other non-OWA method?
Did you check event logs?

Exchange 2007 Sp3

2 CAS Server-

1 MB Server 

Exchange 2013 CU8

2 CAS+MB Server 

I have created 2 New Mailboxes on Exchange 2013 Server and OWA is not opening on Exchange server 2013 Server.

Hi Gurmeet,

Hi,

Have you recreated OWA virtual directory?

Please try to logon OWA with this URL :

http://ExchangeServer/owa

Make sure the Microsoft Forms Based Authentication service is running on all Exchange servers. 

Best Regards,

David 

• Proposed as answer by Sathish VeerapandianMVP 23 hours 11 minutes ago

Hi,

Have you recreated OWA virtual directory?

Please try to logon OWA with this URL :

http://ExchangeServer/owa

Make sure the Microsoft Forms Based Authentication service is running on all Exchange servers. 

Best Regards,

David 

• Proposed as answer by Sathish VeerapandianMVP Thursday, June 18, 2015 8:16 AM

Hi,

Have you recreated OWA virtual directory?

Please try to logon OWA with this URL :

http://ExchangeServer/owa

Make sure the Microsoft Forms Based Authentication service is running on all Exchange servers. 

Best Regards,

David 

• Proposed as answer by Sathish VeerapandianMVP Thursday, June 18, 2015 8:16 AM

Hi,

Have you recreated OWA virtual directory?

Please try to logon OWA with this URL :

http://ExchangeServer/owa

Make sure the Microsoft Forms Based Authentication service is running on all Exchange servers. 

Best Regards,

David 

• Proposed as answer by Sathish VeerapandianMVP Thursday, June 18, 2015 8:16 AM

Hi,

Have you recreated OWA virtual directory?

Please try to logon OWA with this URL :

http://ExchangeServer/owa

Make sure the Microsoft Forms Based Authentication service is running on all Exchange servers. 

Best Regards,

David 

• Proposed as answer by Sathish VeerapandianMVP Thursday, June 18, 2015 8:16 AM

If David's response did not help - do you see anything else that does not contain IsMonitoringRequest: True?

Hi 

This is because of the stale entries present in the ecp objects as well as in the IIS metabase.

If recreating corresponding affected VD doesnt help you then  try the below steps

Remove the newly created ECP virtual directory

Remove-Ecpvirtualdirectory Identity CAS\Autodiscover (xxxxx)

5)  Remove the ecp objects in AD container

a. Open ADSIEDIT.msc, locate:

Configuration>CN=Services>CN=Microsoft Exchange>CN=Organization>CN=Administrative Groups>CN=Exchange Administrative Groups>CN=Servers>CN=Exchange>CN=Protocols>CN=HTTP

b. In the right pane, please check whether the CN=ECP(xxx) is present. If its present you can remove it

6. Delete the autodsicover in metabase

a. Download the IIS 6.0 Resource Kit Tools from the following link:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en

b. Install it on the CAS server. Open the Metabase Explorer (Open it in elevated mode)

c. Locate: Exchange -> LM -> W3SVC -> 1 -> ROOT.

d. Check if you are able to find ECP virtual directory  is present, if so, remove it.

7. After that, try recreating the ECP virtual directory and see the results

New-Ecpvirtualdirectory Identity CAS\Autodiscover (xxxxx)

Most likely after following the above troubleshooting steps the affected ECP VD should start working. You can also follow the same troubleshooting steps if in case  you are getting the same error in accessing the OWA,EAC ,Autodiscover and PowerShell Virtual Directories.

ECP is Working fine only OWA issue is not working

I have checked Event viewer Error 146 

Outlook Web App failed to create ExchangePrincipal for S-1-5-21-233854755-468709869-478961464-15056. IsMonitoringRequest: True. Error: Microsoft.Exchange.Data.Storage.ObjectNotFoundException: The Active Directory user wasn't found.
   at Microsoft.Exchange.Data.Storage.ExchangePrincipalFactory.FromUserSid(IRecipientSession recipientSession, SecurityIdentifier userSid, RemotingOptions remotingOptions)
   at Microsoft.Exchange.Clients.Owa2.Server.Core.OwaClientSecurityContextIdentity.InternalCreateExchangePrincipal()

Ensure the OWA feature is enabled for these two new mailboxes.  If it is, check the following account security settings:

1. Open the Active Directory Users and Computers snap-in.

• 2. On the View menu, click Advanced Features.

• 3. Open the properties of a user who cannot log on to Outlook Web Access.

• 4. Click the Security tab, and then click Advanced.

• 5. Select the Allow inheritable permissions check box if it has not already been selected.

• 6. Allow time for replication to occur.

• Let us know the results.

OWA Option and Allow Inheritable Permission is already enabled .

Outlook Mailbox is working fine only OWA is not open