Event ID: 0 -> System.Exception: EVOWA - Request not Authenticated (Could not establish the UserContext)

[fpoli]

Hi All!,
I have an Exchange 2007 Sp1 RU7 with the event log full of the following events:

Event Type: Error
Event Source: Enterprise Vault OWA Extensions
Event Category: None
Event ID: 0
Date: 06/05/2009
Time: 11.54.11
User: N/A
Computer: MOSCA3
Description:
An unhandled exception was caught in PostRequestHandlerExecute:

System.Exception: EVOWA - Request not Authenticated (Could not establish the UserContext)
in Symantec.EnterpriseVault.Owa.Core.EVContext.GetOWASessionId(HttpContext oHttpContext)
in Symantec.EnterpriseVault.Owa.Core.EVContext.GetEVContext(HttpContext oHttpContext, SecurityIdentifier sid)
in Symantec.EnterpriseVault.Owa.Core.RequestProcessor..ctor(HttpContext oContext)
in Symantec.EnterpriseVault.Owa.EVOwaModule.PostRequestHandlerExecute(Object objSender, EventArgs objEventArgs)


Someone has seen this before, or can give adivices on what to check on the sever?
Enterprise Vault is the 7.5 version.

Thanks for the help!

Francesco

[TonySterling]

sounds like this technote:


http://seer.entsupport.symantec.com/docs/310658.htm

Cannot retrieve archived items via Outlook Web Access (OWA) on Exchange 2007. Retrieval failures result in Event ID 0.
Details:
When attempting to retrieve an archived item through OWA the following Event ID is generated below and the Enterprise Vault buttons do not show up in OWA. In addition when clicking on an email the message "This message has been archived. Double click the message to retrieve" will show as well.

[Wayne_Humphrey]

Edit Web.config and change the following entries in it.
(Replace localhost with the IP address of the client access server)
If the second key does not exist in the web.config just create it.

<add key="EnterpriseVault_WebDAVRequestHost" value="CAS IP Address"/>
<add key="EnterpriseVault_ExchangeWebServicesUrl" value="https://<CAS IP ADDRESS>/ews/exchange.asmx"/>

[fpoli]

Hi Thanks for the reply,
looking at the faulty stack trace, it's anyway completly different.

The event id is the same because it fall under the same area (Unhandled Exception) but the failure stack differ. In this case this fails because it fails to (impersonate\authenticate?) the user?

Thanks Francesco