cancel
Showing results for 
Search instead for 
Did you mean: 

Archiving Report Error

tpuck
Level 4
Partner Accredited

In EV 11.0.1 the Archiving Report the Error "Warning: Failed to process Mailbox" will be shown.

But Archiving is working fine in sheduled also in manual mode.

Did anyone knows something about this new behavior.

Best regards

 

Thorsten

2 ACCEPTED SOLUTIONS

Accepted Solutions

RahulG
Level 6
Employee

Refer the following Technote.

You may have to disable and re-enable the Mailbox reporitng the error .

How to remove (zap) Enterprise Vault (EV) properties from Archive-Enabled Exchange mailboxes:

http://www.symantec.com/business/support/index?page=content&id=TECH35614

View solution in original post

Manideep_Neeli
Level 4
Employee

I guess you will also see event - 

Event ID: 3487 The mailbox will not be processed again on this archiving run because there were errors with too many individual items. 
|Mailbox: /o=Exchange/ou=Test/cn=Recipients/cn=Test |Eligible Items: 2103 |Exchange Server: Exchange01 |Task name: Exchange Mailbox Archiving Task for Exchange01 

Refer:

https://www.veritas.com/support/en_US/article.TECH230186

View solution in original post

3 REPLIES 3

RahulG
Level 6
Employee

Refer the following Technote.

You may have to disable and re-enable the Mailbox reporitng the error .

How to remove (zap) Enterprise Vault (EV) properties from Archive-Enabled Exchange mailboxes:

http://www.symantec.com/business/support/index?page=content&id=TECH35614

View solution in original post

Manideep_Neeli
Level 4
Employee

I guess you will also see event - 

Event ID: 3487 The mailbox will not be processed again on this archiving run because there were errors with too many individual items. 
|Mailbox: /o=Exchange/ou=Test/cn=Recipients/cn=Test |Eligible Items: 2103 |Exchange Server: Exchange01 |Task name: Exchange Mailbox Archiving Task for Exchange01 

Refer:

https://www.veritas.com/support/en_US/article.TECH230186

View solution in original post

sonujaiswalit
Level 1

Issue is same for even 12.2 however fixed it, Kindly let me know if any one still facing this issue