cancel
Showing results for 
Search instead for 
Did you mean: 

Error 2262 when provision task starts

mzadriennemc
Level 3

I am receiving an event ID 2262 when my provision tasks starts and emails are not archiving.  This is EV 10, any solutions?

1 ACCEPTED SOLUTION

Accepted Solutions

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

This has been solved in the past by a re-install of MSMQ.

This TN should help:

Article URL http://www.symantec.com/docs/TECH126256

 

View solution in original post

4 REPLIES 4

AndrewB
Moderator
Moderator
Partner    VIP    Accredited

please paste the event.

other solutions in the past have had to do with MSMQ and AV exclusions not being correct but we need to see the context of your event to know for sure.

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

It would help for you to post the exact message you are seeing, the error codes can vary even though the Event ID is the same.

 

mzadriennemc
Level 3

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault
Date:          5/10/2012 9:00:14 PM
Event ID:      2262
Task Category: Archive Task
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MB300 EV server
Description:
Error processing archiving request for system QMBXAP01 Exchange server

For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp?EvtID=2262
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Enterprise Vault " />
    <EventID Qualifiers="49156">2262</EventID>
    <Level>2</Level>
    <Task>19</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-05-11T04:00:14.000000000Z" />
    <EventRecordID>724603</EventRecordID>
    <Channel>Symantec Enterprise Vault</Channel>
    <Computer></Computer>
    <Security />
  </System>
  <EventData>
    <Data>QMBXAP01</Data>
  </EventData>
</Event>

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

This has been solved in the past by a re-install of MSMQ.

This TN should help:

Article URL http://www.symantec.com/docs/TECH126256