Archiving event error 2776

[alan_koch]

Last night I had a number of the following event log errors on my EV 8, SP2 server"

------------------------------------------------------------------------------------------------------------------------
Event Type:        Error
Event Source:    Enterprise Vault
Event Category:                Archive Task

Event ID:              2776

Date:                     10/8/2009

Time:                     7:01:00 PM

User:                     N/A

Computer:          ComputerXXX

Description:
An exception occurred in routine DelAttachFromMsgAndAppendList

EXCEPTION_ACCESS_VIOLATION @ 0x10009F4E

----------------------------------------------------------------------------------------------------
Does anyone have any information on the cause of this error?
Thanks.

[MichelZ]

The closest I came up with is this:
http://seer.entsupport.symantec.com/docs/318415.htm

However, it's not an exact match.

Is this the first time this happened?
Did you change anything on the EV Environment?

Cheers
Michel

[GregRountree]

This might be due to an embedded attachment and the Shortcut Size. I would open a case and reference the hex code you are getting (0x10009F4E) this could help diagnose the issue. How many errors are you getting? Are there any other errors?

[alan_koch]

I have seen the 318415 doc.  Since it wasn't an exact match, I wasn't sure if it applied.
This is the first time that I've seen this error message.  It occured 20 times in a 12 minute span in the event log.
I have't made any changes to the EV Environment to precipitate this error.
Thanks for the help.
Alan

[Rob_Wilcox1 · Accepted solution]

The hex code is just a memory reference, so not really that useful.

Do you have any other 2776 events, such as the ones listed :

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

Hope that helps,

[alan_koch]

Rob,
Yes, I had the exact error as listed in doc 331887:
Event ID: 2776  An exception occurred in routine
DelAttachFromMsgAndAppendList
EXCEPTION_ACCESS_VIOLATION @ 0x10009F4E

It looks like I'll have to wait on Symantec to come up with a fix for the problem.
Thanks for the help.
Alan