Ошибка сервера в приложении owa

Hi all,

Recently, I have installed a new Exchange 2007 server (named exch2007) in our Exchange 2003 environment. The server was installed Office SharePoint Server 2007 before Exchange 2007. The installation of Exchange 2007 was successful and it works fine.

Last Friday, I was accidentally removed the «Default Web Site» from IIS server using «SharePoint Central Administration» website. Then I realise that I can’t login to OWA again, because the «Default Web Site» was removed. And I found a KB (http://support.microsoft.com/kb/320202), I had followed all the instruction under «Exchange 2007» to regenerate the CAS, but no luck.

Web Error Msg:

=======================================================================

Server Error in ‘/owa’ Application.

---

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.

Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a «web.config» configuration file located in the root directory of the current web application. This <customErrors> tag should then have its «mode» attribute set to «RemoteOnly». To enable the details to be viewable on remote machines, please set «mode» to «Off».

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the «defaultRedirect» attribute of the application’s <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="On" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

==============================================================

Under Event logs (application), there are so many WARNING message from source — «ASP.NET 2.0.50727.0».

Event 1310:

Date: 04/12/2007

Source: ASP.NET 2.0.50727.0

Time: 12:16:56PM

Category: Web Event

Type: Warning

Event ID: 1310

User: N/A

Computer: EXCH2007

Description:

Event code: 3008

Event message: A configuration error has occurred.

Event time: 04/12/2007 12:16:56 PM

Event time (UTC): 04/12/2007 4:16:56 AM

Event ID: 83e3b6988a774615b1cebd8cae62b6bc

Event sequence: 1

Event occurrence: 1

Event detail code: 0

Application information:

Application domain: /LM/W3SVC/1/ROOT/owa-3-128412154157243048

Trust level: WSS_Minimal

Application Virtual Path: /owa

Application Path: C:Program FilesMicrosoftExchange ServerClientAccessowa

Machine name: EXCH2007

Process information:

Process ID: 5348

Process name: w3wp.exe

Account name: NT AUTHORITYNETWORK SERVICE

Exception information:

Exception type: HttpException

Exception message: Could not load file or assembly ‘Microsoft.Exchange.Data.Storage, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. Failed to grant permission to execute. (Exception from HRESULT: 0x80131418) (C:Program FilesMicrosoftExchange ServerClientAccessowaweb.config line 55)

Request information:

Request URL: https://localhost/owa/auth/logon.aspx?url=https://localhost/owa/&reason=0

Request path: /owa/auth/logon.aspx

User host address: 127.0.0.1

User:

Is authenticated: False

Authentication Type:

Thread account name: NT AUTHORITYNETWORK SERVICE

Thread information:

Thread ID: 5

Thread account name: NT AUTHORITYNETWORK SERVICE

Is impersonating: False

Stack trace: at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException()

at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()

at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)

Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event 1309:

Date: 04/12/2007

Source: ASP.NET 2.0.50727.0

Time: 12:18:14PM

Category: Web Event

Type: Warning

Event ID: 1309

User: N/A

Computer: EXCH2007

Description:

Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 04/12/2007 12:18:14 PM

Event time (UTC): 04/12/2007 4:18:14 AM

Event ID: ecbd8e5617d24d18a5a27ae84e20e95a

Event sequence: 8

Event occurrence: 7

Event detail code: 0

Application information:

Application domain: /LM/W3SVC/1/ROOT/Autodiscover-1-128412142521461798

Trust level: WSS_Minimal

Application Virtual Path: /Autodiscover

Application Path: C:Program FilesMicrosoftExchange ServerClientAccessAutodiscover

Machine name: EXCH2007

Process information:

Process ID: 5740

Process name: w3wp.exe

Account name: NT AUTHORITYSYSTEM

Exception information:

Exception type: FileLoadException

Exception message: Could not load file or assembly ‘Microsoft.Exchange.Diagnostics, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A)

Request information:

Request URL: https://exch2007.domainname.com/Autodiscover/Autodiscover.xml

Request path: /Autodiscover/Autodiscover.xml

User host address: x.x.x.x

User:

Is authenticated: False

Authentication Type:

Thread account name: NT AUTHORITYSYSTEM

Thread information:

Thread ID: 5

Thread account name: NT AUTHORITYSYSTEM

Is impersonating: True

Stack trace: at Microsoft.Exchange.Autodiscover.Global.Application_BeginRequest(Object sender, EventArgs e)

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

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

Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

===============================================

Message from Exchange Management Shell:

[PS] C:Documents and Settingsexch.admin>Get-OwaVirtualDirectory

Name                                       Server                    OwaVersion
—-                                           ——                        ———-
Exchange (Default Web S…       EXCH2007              Exchange2003or2000
Exadmin (Default Web Site)       EXCH2007              Exchange2003or2000
Public (Default Web Site)           EXCH2007              Exchange2003or2000
Exchweb (Default Web Site)       EXCH2007              Exchange2003or2000
owa (Default Web Site)              EXCH2007               Exchange2007

[PS] C:Documents and Settingsexch.admin>Test-OwaConnectivity -Verbose
VERBOSE: Test-OwaConnectivity : Beginning processing.
VERBOSE: Do you want to test OWA connectivity on Client Access server exch2007.domainname.com?
VERBOSE: Test-OwaConnectivity : Creating a list of Outlook Web Access virtual directories to test for Client Access server ‘exch2007’,  Mailbox server ‘exch2007’.
VERBOSE: Test-OwaConnectivity : Adding test case for Client Access server ‘exch2007’, Mailbox server ‘exch2007’, URL
‘https://exch2007.domainname.com/owa/’.
VERBOSE: Test-OwaConnectivity : Starting test with target URL = ‘https://exch2007.domainname.com/owa/’.
VERBOSE: Test-OwaConnectivity : This URL type is Internal, so any certificate will be trusted.
VERBOSE: Test-OwaConnectivity : Sending HTTP GET logon request without credentials for authentication type verification.
WARNING: The test encountered an error while making the initial request to Outlook Web Access.
HTTP code: 500
WARNING: Test FAILED for URL ‘https://exch2007.domainname.com/owa/’.

WARNING: column «Error» does not fit into the display and was removed.

==================================================================

Please help.

Thank you.

Exchange OWA and ECP are not working. Signing in to Exchange Server OWA is showing you an error. The error is showing that there is a Server Error in ‘/owa’ Application. When trying with ECP, it’s showing Server Error in ‘/ecp’ Application. How did this happen, and what is the solution to it? In this article, you will learn how to fix Exchange Server Error in ‘/owa’ Application.

When starting Exchange OWA (Outlook Web Access) and entering the credentials, the below error appears. The same happens when going to the ECP (Exchange Control Panel) page.

Server Error in ‘/owa’ Application.
https://ex01-2016/owa/auth/errorFE.aspx?CafeError=SSLCertificateProblem
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.Web.HttpException: https://ex01-2016/owa/auth/errorFE.aspx?CafeError=SSLCertificateProblemSource Error:An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.Stack Trace:[HttpException (0x80004005): https://ex01-2016/owa/auth/errorFE.aspx?CafeError=SSLCertificateProblem]
Microsoft.Exchange.HttpProxy.FbaModule.OnBeginRequestInternal(HttpApplication httpApplication) +441
Microsoft.Exchange.HttpProxy.<>c__DisplayClass16_0.b__0() +1672
Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func2 filterDelegate, Action1 catchDelegate) +35
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +142
System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +75
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +93Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.3928.0

Why is this happening and what is the solution for Exchange 2016 OWA and ECP not working?

Explanation Server Error in ‘/owa’ Application

Why did the error start to show when signing in to Exchange OWA and ECP? This can happen if you, for example:

• Install Exchange Cumulative Update
• Remove certificate that was assigned to Exchange Server

If you already have a third-party certificate installed, select that in the next part. If you don’t have a third-party certificate because you removed it, select the default Microsoft Exchange self-signed certificate. You can always select the self-signed certificate to get access to the Exchange Admin Center. After that, you can import a new certificate.

Solution for Server Error in ‘/owa’ Application

Sign in to the Exchange Server. Start Internet Information Services (IIS) Manager. Unfold the Exchange Server and click the Sites list. You will find the Default Web Site and Exchange Back End.

Default Web Site configure bindings

Click on Default Web Site and click Bindings in the actions panel.

Check both the site bindings with type https. Double-click the first type https with IP Address * (asterisk).

The SSL certificate is Not selected.

Click on Not selected and select the Microsoft Exchange self-signed certificate from the dropdown menu. Do you have a third-party certificate? Select that certificate instead. Click OK.

In my example, I selected the Exchange self-signed certificate. That’s because I don’t yet have a third-party certificate configured. The self-signed certificate is created by default when you install Exchange Server.

Read more: Install free let’s encrypt certificate in Exchange Server »

On my end, after assigning the certificate it was reverted back to Not selected. Select the certificate again from the dropdown menu and click OK. To make sure it’s now selected, check again. This time it’s selected.

Important: After selecting the certificate from the dropdown menu, it sometimes does not get selected. Make sure that you double-check after assigning the certificate.

Do the same with the second site binding. Double-click IP Address 127.0.0.1.

Select the certificate and click OK. Again, double-check if it’s assigned. If the certificate is already bound to the site, you don’t have to make any changes.

Now that we have the certificates assigned and checked both site bindings, we can proceed to the next step.

Exchange Back End configure bindings

Click on Exchange Back End and click Bindings in the actions panel.

Select the site binding with type https and port 444. Click Edit...

Select the Microsoft Exchange self-signed certificate from the dropdown menu. Click OK. If you have a third-party certificate, select that. Don’t forget to double-check after assigning the certificate.

After applying and double-checking, you have to restart IIS.

After IIS restarts, go to Exchange OWA or ECP and sign in. You can now successfully sign in.

I hope this article helped you fix the server error in ‘/owa’ application in Exchange Server. Good to know is that it also fixed the server error in ‘/ecp’ application in Exchange Server.

Keep reading: Recreate virtual directories in Exchange Server »

Conclusion

You learned why you get Server Error in ‘/owa’ Application in Exchange Server. This happens when the bindings are not configured to the Exchange web sites in IIS. Bind the certificates to both the Exchange Default Web Site and Exchange Back End. Don’t forget to double-check after selecting the certificates. As of last, restart IIS. Now you can sign in to OWA and ECP without the Server Error in ‘/owa’ Application showing up.

Did you enjoy this article? You may also like the article Exchange Hybrid test plan checklist. Don’t forget to follow us and share this article.