none
Server Error in '/owa' Application.

    Question

  •  

    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 Files\Microsoft\Exchange Server\ClientAccess\owa\

    Machine name: EXCH2007

    Process information:

    Process ID: 5348

    Process name: w3wp.exe

    Account name: NT AUTHORITY\NETWORK 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 Files\Microsoft\Exchange Server\ClientAccess\owa\web.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 AUTHORITY\NETWORK SERVICE

    Thread information:

    Thread ID: 5

    Thread account name: NT AUTHORITY\NETWORK 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 Files\Microsoft\Exchange Server\ClientAccess\Autodiscover\

    Machine name: EXCH2007

    Process information:

    Process ID: 5740

    Process name: w3wp.exe

    Account name: NT AUTHORITY\SYSTEM

    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 AUTHORITY\SYSTEM

    Thread information:

    Thread ID: 5

    Thread account name: NT AUTHORITY\SYSTEM

    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 Settings\exch.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 Settings\exch.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.

    ClientAccessServer  MailboxServer  URL                                                      Scenario Result  Latency (ms)
    ---------------------         -------------         ---                                                          --------      ------     -----
    exch2007                exch2007        https://exch2007.domainname.com/owa/   Logon    Failure  -1
                                    
    VERBOSE: Test-OwaConnectivity : Ending processing.

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

     

     

    Please help.

     

    Thank you.

    Tuesday, December 04, 2007 4:36 AM

Answers

  • Hi Guys,

     

    Sorry that I can't help you in this problem. Because I have reformatted my server and reinstall OS + exchange2007.

     

    I suggest If your server still new (no mailbox yet), you may consider to reformat and it will be faster then waiting for troubleshooting answer.

     

    But, let said if you can't reformat your server due to some other issues, you can try the following steps:

    1. Check whether you have installed Dot Net 1.1 and have you changed IIS mode to 32-Bit? Please disable 32-bit mode and re-register Dot Net 2.0 (x64) for 64-bit exchange.

        How to switch between the 32-bit versions of ASP.NET 1.1 and the 64-bit version of ASP.NET 2.0 on a 64-bit version of Windows

     

    2. Delete owa virtual directory and regenerate owa ONLY

     

    3. Uninstall CAS and reinstall CAS + remove OWA from IIS and regenerate OWA, please do not uninstall / reinstall your IIS server, just try uninstall / reinstall CAS and see whether it can help or not.

     

    4. Try to restore your IIS backup from your IIS

        - Once IIS installed, it will backup itself for default backup.

        - Also, there are some continuous backup (every 3 minutes) on IIS automated backup

        - Please create your new IIS backup before you try to restore IIS

        - You can try to restore your IIS from default backup and then regenerate OWA.

     

    5. If this server only for exchange server (no other server application running on IIS), you can try to uninstall and reinstall IIS, register Dot Net 2.0 (x64), regenerate OWA.

     

    NOTE: Due to my server is new, so that I have decided to reformat the exchange 2007 server instead of waiting for answer for troubleshooting. And, these are the steps that I had tried before I reformatted my exchange server, but still no luck.

     

    IMPORTANT:

    This posted message are ONLY my personal opinion, strongly NOT RECOMMEND to use on production server.

     

    Please backup your server before you try anything.

     

    :-)

     

    Cheers,

    Kent Ng

    Monday, February 11, 2008 10:08 AM

All replies

  • Anyone can help to solve this problem??  Please...

     

    Thursday, December 06, 2007 7:20 AM
  •  

    Server Error in '/owa' Application.

    Configuration Error

    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

    Parser Error Message: Could not load file or assembly 'Microsoft.Exchange.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Failed to grant permission to execute. (Exception from HRESULT: 0x80131418)

    Source Error:

    Line 49: 				the compiler.  All assemblies in the GAC and owa\bin are referenced automatically.
    Line 50: 				-->
    Line 51: 				<add assembly="Microsoft.Exchange.Data,
    Line 52: 					Version=8.0.0.0,
    Line 53: 					Culture=neutral,

    Source File: C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\web.config    Line: 51


    Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832

     

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

    Anyone encounter this problem before?

     

    Thank you so much.....

    Friday, December 07, 2007 5:48 AM
  •  

    looks like no one is helping u, can u email me on kanishka.somaratne @ gmail.com with a ID i can chat with u, i can resolve this problem for u
    Sunday, December 09, 2007 4:28 AM
  • There are a few approaches to this:

     

    1. If you have a backup of your metabase.xml file, you can attempt a restore.

    2. Recreate the website and configure the appropriate authentication settings. You can compare against another server, or run the Exchange .vhd file and do a comparision.

    3. If this is a lab envieonment, it'll be easier removing and re-installing the CAS role. I've done this several time and it takes approximately 10-30 mins.

     

    Cheers,

    Alienix

     

    Sunday, December 09, 2007 10:40 AM
  • I've done somehting similar in my lab.

    uninstalling and reninstalling the CAS role on the server solved the issue.

     

    for more information about how to do that, go the following link:

    http://technet.microsoft.com/en-us/library/aa997281(EXCHG.80).aspx

     

    feel free to contact me if you have any problems doing this. :-)

    Sunday, January 27, 2008 7:25 PM
  •  

    I am running into the same error after installing Project Server 2007 (and the sharepoint server that comes with it). I have tried reinstalling CAS, but the error still remains. Is there another way around this?

     

    Thanks,

    Steve

    Monday, February 04, 2008 3:17 PM
  • Event Type: Warning
    Event Source: ASP.NET 2.0.50727.0
    Event Category: Web Event
    Event ID: 1310
    Date:  2/6/2008
    Time:  9:29:08 AM
    User:  N/A
    Computer: SVREX1
    Description:
    Event code: 3008
    Event message: A configuration error has occurred.
    Event time: 2/6/2008 9:29:08 AM
    Event time (UTC): 2/6/2008 4:29:08 PM
    Event ID: 90c4f064931544a385df4e64a0f29552
    Event sequence: 1
    Event occurrence: 1
    Event detail code: 0
     
    Application information:
        Application domain: /LM/W3SVC/1/ROOT/Autodiscover-3-128467889484687500
        Trust level: Full
        Application Virtual Path: /Autodiscover
        Application Path: D:\Program Files\Microsoft\Exchange Server\ClientAccess\Autodiscover\
        Machine name: SVREX1
     
    Process information:
        Process ID: 5640
        Process name: w3wp.exe
        Account name: NT AUTHORITY\SYSTEM
     
    Exception information:
        Exception type: HttpException
        Exception message: Could not load file or assembly 'System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
     
    Request information:
        Request URL: https://svrex1.darnell.local:443/Autodiscover/Autodiscover.xml
        Request path: /Autodiscover/Autodiscover.xml
        User host address: 192.168.0.30
        User: 
        Is authenticated: False
        Authentication Type: 
        Thread account name: NT AUTHORITY\SYSTEM
     
    Thread information:
        Thread ID: 5
        Thread account name: NT AUTHORITY\SYSTEM
        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.

    Wednesday, February 06, 2008 4:29 PM
  • Hi Kent,

     

    Did you get your issue resolved? I have a very similar problem and Uninstallilng and reinstalling CAS role from the exchange server did not make a difference.

     

    This is my situation,

     

    I have an exchange Server 2007 SP1 with a Windows 2003 Standard x64 Sp2 Operating system.DotNet Framework 2.0 SP1.

    We migrated from another Exchange 2003 Server.

    OWA is not working on the new Exchange 2007 Server.

    I uninstalled and reinstalled the Client Access Server Role from the Exchange 2007 server and  it dod not fix my issue.  I am still getting the same error message.  (See below, Also pasted event viewer errors)

    Do you have any suggestions?

    I was wondering if the problem is at a higher level and I need to Uninstall and reinstall IIS. Is it safe to do that? Please let me know if you have any ideas I could try to solve this issue.

     

    Thank you,

     

    German Escobedo

     

    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>

     

    Event Type:        Warning

    Event Source:    ASP.NET 2.0.50727.0

    Event Category:                Web Event

    Event ID:              1310

    Date:                     2/6/2008

    Time:                     9:28:25 AM

    User:                     N/A

    Computer:          SVREX1

    Description:

    Event code: 3008

    Event message: A configuration error has occurred.

    Event time: 2/6/2008 9:28:25 AM

    Event time (UTC): 2/6/2008 4:28:25 PM

    Event ID: 868b3c39a1104a10a84942b282484830

    Event sequence: 1

    Event occurrence: 1

    Event detail code: 0

     

    Application information:

        Application domain: /LM/W3SVC/1/ROOT/owa-4-128467889051875000

        Trust level: Full

        Application Virtual Path: /owa

        Application Path: D:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\

        Machine name: SVREX1

     

    Process information:

        Process ID: 5908

        Process name: w3wp.exe

        Account name: NT AUTHORITY\SYSTEM

     

    Exception information:

        Exception type: HttpException

        Exception message: Could not load file or assembly 'System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.

     

    Request information:

        Request URL: https://localhost:443/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 AUTHORITY\SYSTEM

     

    Thread information:

        Thread ID: 5

        Thread account name: NT AUTHORITY\SYSTEM

        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 Type:        Warning

    Event Source:    ASP.NET 2.0.50727.0

    Event Category:                Web Event

    Event ID:              1310

    Date:                     2/6/2008

    Time:                     9:29:08 AM

    User:                     N/A

    Computer:          SVREX1

    Description:

    Event code: 3008

     

    Event message: A configuration error has occurred.

     

    Event time: 2/6/2008 9:29:08 AM

     

    Event time (UTC): 2/6/2008 4:29:08 PM

     

    Event ID: 90c4f064931544a385df4e64a0f29552

     

    Event sequence: 1

     

    Event occurrence: 1

     

    Event detail code: 0

     

     

     

    Application information:

     

        Application domain: /LM/W3SVC/1/ROOT/Autodiscover-3-128467889484687500

     

        Trust level: Full

     

        Application Virtual Path: /Autodiscover

     

        Application Path: D:\Program Files\Microsoft\Exchange Server\ClientAccess\Autodiscover\

     

        Machine name: SVREX1

     

     

     

    Process information:

     

        Process ID: 5640

     

    Wednesday, February 06, 2008 4:49 PM
  • Hi Guys,

     

    Sorry that I can't help you in this problem. Because I have reformatted my server and reinstall OS + exchange2007.

     

    I suggest If your server still new (no mailbox yet), you may consider to reformat and it will be faster then waiting for troubleshooting answer.

     

    But, let said if you can't reformat your server due to some other issues, you can try the following steps:

    1. Check whether you have installed Dot Net 1.1 and have you changed IIS mode to 32-Bit? Please disable 32-bit mode and re-register Dot Net 2.0 (x64) for 64-bit exchange.

        How to switch between the 32-bit versions of ASP.NET 1.1 and the 64-bit version of ASP.NET 2.0 on a 64-bit version of Windows

     

    2. Delete owa virtual directory and regenerate owa ONLY

     

    3. Uninstall CAS and reinstall CAS + remove OWA from IIS and regenerate OWA, please do not uninstall / reinstall your IIS server, just try uninstall / reinstall CAS and see whether it can help or not.

     

    4. Try to restore your IIS backup from your IIS

        - Once IIS installed, it will backup itself for default backup.

        - Also, there are some continuous backup (every 3 minutes) on IIS automated backup

        - Please create your new IIS backup before you try to restore IIS

        - You can try to restore your IIS from default backup and then regenerate OWA.

     

    5. If this server only for exchange server (no other server application running on IIS), you can try to uninstall and reinstall IIS, register Dot Net 2.0 (x64), regenerate OWA.

     

    NOTE: Due to my server is new, so that I have decided to reformat the exchange 2007 server instead of waiting for answer for troubleshooting. And, these are the steps that I had tried before I reformatted my exchange server, but still no luck.

     

    IMPORTANT:

    This posted message are ONLY my personal opinion, strongly NOT RECOMMEND to use on production server.

     

    Please backup your server before you try anything.

     

    :-)

     

    Cheers,

    Kent Ng

    Monday, February 11, 2008 10:08 AM
  • Hi,

     

    I had the same issue but it was related to something else, using wordpad to edit my web.config file corrupted the file and i started to receive similar runtime error, when comparing the modified web.config file by the original one using windiff tool i found that wordpad changed some characters to "." and "?", i resolved the issue by copying the web.config file from another CAS server having the same configuration of the affected CAS server and it worked

     

    Thursday, August 21, 2008 3:45 AM
  • Hi,

    i solved the problem.
    it´s very strange that sharepoint deletes also the other sites,
    in my opinion it´s a bug...

    For other admins,
    who lost the default web side:

    - fist create a new web side, called Default Web Side (naming does not matter)
      if there allready exist a site with port tcp 80, change the tcp port 80 to 81 or something else.
      do Tasks --> Save config to file.
      open the xml and change the identifier back to 1 (about 4 or 5 sections...).
      (you can view the identifier if you mark "web sides" and look on the right details view...)
      recover iis default side from file

    - Open inetpub wwwroot

    delete/move everything, remain iisstart.htm and pageerror.gif and the folder aspnet_client (yes the folder size is 0 bytes)
    (in my case, i got exchange server and sharepoint, if you got other websides that are definitley not sharepoint based, leave them too...)

    - start iis

    - Follow the kb http://support.microsoft.com/kb/320202
      and uninstall client access role, install it
      and run the power shell commands

    - open exchange console and publish the public address under the owa and activesnc site again
      (setup cleans your config...)

    - restart iis

    do a webmail and sync your devices, you will see it will function again...

    the problem is due to the web.config and the sharepoint folders in the root of sharepoint.
    with my steps you can recreate the whole web access system, that will run again for several years...


    Bye Mathias Rühn (Kopyczynski)
    Monday, February 01, 2010 7:17 AM
  • Just like to add to this I had edited the web.config file and changed the <sessionState mode="Off" /> to <sessionState mode="On" /> in Notepad when I changed the value back to off again I typed OFF instead of Off it was case sensitive typing the corect case fixed this for me.


    JammJ
    Friday, March 18, 2011 9:33 AM