Event ID 0 - Error: "An unhandled exception was caught" occurs on an Exchange Client Access Server (CAS) Server after installing Enterprise Vault (EV) Outlook Web Access (OWA) Extensions.

Article: 100019286
Last Published: 2014-08-13
Ratings: 0 1
Product(s): Enterprise Vault

Problem

The following message may appear multiple times in the Application Event log:
 

Error Message

    Event Type: Error
    Event Source: Enterprise Vault OWA Extensions
    Event Category: None
    Event ID: 0
    Description:

An unhandled exception was caught:
 
Microsoft.Exchange.Clients.Owa.Core.OwaNotSupportedException: WindowsIdentity
at Microsoft.Exchange.Clients.Owa.Core.OwaADUserIdentity.get_WindowsIdentity()
at Symantec.EnterpriseVault.Owa.Core.OwaObjectHelper.get_MailboxSID()
at Symantec.EnterpriseVault.Owa.Core.OwaObjectHelper.get_OWAAvailable()
at Symantec.EnterpriseVault.Owa.Core.RequestProcessor..ctor(HttpContext oContext)
at Symantec.EnterpriseVault.Owa.EVOwaModule.PostRequestHandlerExecute(Object objSender, EventArgs objEventArgs)

Cause

This can happen when clients that use browsers that do not support custom Outlook Web Access (OWA) web forms, such as mobile devices, connect to an Exchange server.
 

Solution

This is a cosmetic issue. Enterprise Vault attempts to insert its custom forms, but the client rejects these custom web forms. These errors may be safely ignored and purged from the Windows Event log.

Note: Enterprise Vault does not currently support browsers that do not work with custom OWA forms.
 

 

Was this content helpful?