08-25-2011 10:02 AM
Hi!
Our customer get this error several times per day:
---
Log Name: Application
Source: Enterprise Vault OWA Extensions
Date: 23.08.2011 13:08:07
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: %name%
Description:
An unhandled exception was caught:
System.NullReferenceException: Object reference not set to an instance of an object.
at Symantec.EnterpriseVault.Owa.ResponseFilters.Premium.Folder.ProcessSP1()
at Symantec.EnterpriseVault.Owa.ResponseFilters.ResponseFilterBase.Close()
---
The Error occur sporadic and unregular.
I've found further Events from this source with ID 0 in the KB, but the description doesn't fit.
For the same time-frame we couldn't find any errors in OWA-Logs or IIS-Logs.
Does anybody knows something about this Event and the Description?
Environment:
EV 9.0.2
Exchange 2003 SP2
Windows Server 2003 SP2
Thanks in advance!
Kai
Solved! Go to Solution.
11-11-2011 11:10 AM
Symantec told us that this error should fixed with EV 9.0.3
"It is a problem with the NullException being returned when we request a PreviewMessageClass."
It is rolled up into this TN http://www.symantec.com/docs/TECH160437
Lets see...
08-25-2011 11:54 AM
09-04-2011 11:04 AM
Kai,
Did you get anywhere with this?
09-06-2011 12:37 AM
Sry for the late response. I couldn't found any "real" issues on the Exch.-Servers. I want to open a case at symantec. But I will keep the thread inform.
11-11-2011 11:10 AM
Symantec told us that this error should fixed with EV 9.0.3
"It is a problem with the NullException being returned when we request a PreviewMessageClass."
It is rolled up into this TN http://www.symantec.com/docs/TECH160437
Lets see...
11-16-2011 05:30 AM
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.
11-16-2011 05:40 AM
Hi Muhammad,
unfortunately this solution is too easy.
Of course we've checked this article before.
The Error 0 has different descriptions and unfortunately not just one error-source.
But thanks for the input.
:)