Announcement

Collapse
No announcement yet.

OWA 500 Error after login

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • OWA 500 Error after login

    For the last 6 months I have enjoyed the near flawless operation of my OWA Server. Monday that ceased, following a power failure in our data center OWA is no longer able to communicate with Exchange.
    Current configuration
    NETDIAG passed tests
    owa front end server ----------------PIX|
    Exchange backend server ------------|

    Static ip addresses with the correct addresses and DNS server.

    The SA will not start on OWA

    Getting a DS error

    Event Type: Error
    Event Source: MSExchangeDSAccess
    Event Category: Topology
    Event ID: 2114
    Date: 2/8/2006
    Time: 3:39:36 PM
    User: N/A
    Computer: Exchange
    Description:
    Process EXMGMT.EXE (PID=1264). Topology Discovery failed, error 0x8007077f.

    I have reconfigured IIS and Exchange authentication based on Article ID:327843

    I am able to telnet to the prescribed ports
    For Exchange Communication:
    o Port 80 for HTTP
    o Port 691 for Link State Algorithm routing protocol
    * For Active Directory communication:
    o Port 389 for LDAP (TCP and UDP)
    o Port 3268 for Global Catalog Server LDAP (TCP)
    o Port 88 for Kerberos Authentication (TCP and UDP)

    Any Suggestions.
    TIA

  • #2
    Re: OWA 500 Error after login

    OWA still works on the Backend (isolate to either PIX or FE OWA) or broken there too?
    Exchange IIS APP Pools OK?

    What other diagnosis so far?

    Tx
    Ike

    Comment


    • #3
      Re: OWA 500 Error after login

      OWA Error 500 after Login

      OWA Front-end Server is not able to communicate with Exchange.
      This issue presented following a power strip failure in our Data Center. The failure resulted in key infrastructure components loosing power. The OWA Server lost power as well. The following is a summary of the diagnostic procedures that were applied resulting in location and application of the resolution.

      Indicators:
      The SA will not start on OWA

      Getting a DS error

      Event Type: Error
      Event Source: MSExchangeDSAccess
      Event Category: Topology
      Event ID: 2114
      Date: 2/8/2006
      Time: 3:39:36 PM
      User: N/A
      Computer: Exchange
      Description:
      Process EXMGMT.EXE (PID=1264). Topology Discovery failed, error 0x8007077f.

      Current configuration

      OWA front end server ----------------PIX|
      -----------------------------------------------|Layer3Switch
      Exchange backend server ------------------| |
      Forest Root DNS LDAP-----------------------|

      DC's are 2000 SP 4
      Exchange front end and back end servers are 2003 SP 1 applied August 2005

      Testing Results:

      From DC’s :
      DCiag shows no problems
      From OWA Server:
      I am able to telnet to the prescribed ports
      For Exchange Communication:
      o Port 80 for HTTP
      o Port 691 for Link State Algorithm routing protocol
      * For Active Directory communication:
      o Port 389 for LDAP (TCP and UDP)
      o Port 3268 for Global Catalog Server LDAP (TCP)
      o Port 88 for Kerberos Authentication (TCP and UDP)

      From OWA Server and Exchange Server

      NETDIAG passed tests

      Able to DSQuery objects

      NETDiag shows no problems

      Static IP addresses with the correct addresses and DNS server.


      Able to navigate to http://exchangeServer/exchweb OWA Opens and I am able to receive and send email.


      Resolution:
      Corrected OWA and IIS configuration based on the following articles.
      Troubleshooting Outlook Web Access logon failures in Exchange 2000 and in Exchange 2003 Article ID:327843
      Troubleshooting OWA when the contents frame displays “Loading” Article ID:280823
      Applied Hot Fix: http://www.microsoft.com/downloads/d...displaylang=en

      Re-booted OWA Server and Walla back in business.

      Comment

      Working...
      X