Video Screencast Help

Event ID 2262 (Error Processing archiving request for system)

Created: 21 Apr 2011 • Updated: 06 Jul 2011 | 7 comments
This issue has been solved. See solution.

Hi,

I've been having this issue for the past 4 weeks now. The archiving stops on 1 or both Exchange targets that we have and event id 2262 is logged.

We have a support call open with Symantec however nothing has helped the issue so far. When the issue occurs, I can get archiving working again by restarting the MSMQ service. On occasions the service hangs and I have to clear the checkpoint files which fixes this.

We run EV 8.0 SP4 on Win2k3 server with 2 exchange targets running Exchange 2003.

We have tried the following with Symantec but to no avail:

Resinstalled MSMQ

Decreased the number of connection EV makes to Exhange server

Run FIXMAPI

Install Outllook 2003 SP3

Add an entry for the EV server in the host file

Any help is appreciated.

 

thanks!

Comments 7 CommentsJump to latest comment

Ray Hasham's picture

Event Type: Error
Event Source: Enterprise Vault
Event Category: Archive Task
Event ID: 2262
Date: 21/04/2011
Time: 11:29:15
User: N/A
Computer: EV01
Description:
Error processing archiving request for system Exchange1

For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp
 

Thanks

JesusWept3's picture

And there was no errors before that?
Doesnt sound like an MSMQ issue to me, but unfortunately would need to see the dtrace leading up to that as there could be a 1000 +1 causes for that

Ray Hasham's picture

Here is the Dtrace. This was taken by the engineer when the error was occuring.

 

Thanks again.

AttachmentSize
DTrace.zip 8.18 MB
MarkBarefoot's picture

The DTRACE shows the error as being

"CArchivingAgent::MainProcessSystem (Exit) |Unspecified error  [0x80004005] |"

 

This is quite a generic MAPI error and translates to MAPI_E_CALL_FAILED. The following TN gives info about this, but it's probably one of the trickiest errors to resolve as it can be so many things, http://www.symantec.com/docs/TECH35774

 

Thanks,

 

Mark

Supportability Analysis Engineer for Enterprise Vault products.

 

**REMEMBER TO VOTE IF THIS HELPS AND MARK IT AS RESOLVED TOO IF IT IS!!**

Ray Hasham's picture

Hi,

 

Finally managed to fix the issue.

- Had to reinstall MSMQ to a different location.

- Upgrade AV to the latest version and exclude the MSMQ location

- Also used a different disk for the MSMQ.

 

It has been chugging along for the past 4 weeks.

SOLUTION