Forum Discussion

Rohith's avatar
Rohith
Level 3
14 years ago
Solved

Archiving Not happening for one particular user

I am using symantec EV 8.0.4. Archiving was happening smooth for most of the users. but for one user archiving is not happening. I checked the event logs but couldnot find anything related to user. Actually user is in a group in which if the mails are aged more than 2 weeks, it should get archived. All other users in the same group are archived properly. I have disabled and enabled the user again, but no go. i have checked the Archive logs and found that only two folders are getting archived. All the other folder are not archiving. Could you please help me out in this issue

  • I think that KeyPlayers suggestions are great.

    It looks like the excerpt you provided shows some shortcut processing taking place. This implies the mailbox is getting hit.

    Does the Usage report show content being added. The quota could play into it, but I think it is far more likely that you are hitting your number of items per pass. 

    THe hardest thing to catch that could very well be it is related to this HF:

     

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

     

    Ignore the fact that it says move archive. It affects anything that stores. You can see the hex code in a trace if it applies. If you do not have this HF in place and have items which would be affected, the net result is eventually you will have these items consuming all of your items per pass . . .and nothing. . .or very limited ammount of data. . .will be archived.

     

    If this is applicable, you may also see growth in the Failed To Store folder of your journal mailbox. I have seen this HF fix countless EV 8 SP4 customers. The best advice would be got to SP5. .

     

    Hope this helps.

    J

6 Replies

  •  

     

    There might be a case if quota based policy applied along with aged based. Please provide snap shot of "Archiving Rules" window, also what provision report says when you're running it in report mode?

  • Perform a run now against the user mailbox, whilst dtracing agentclientbroker and archivingtask. Look for lines like the below for items in other folders.  Do they say eligable or ineligable?

    405339 15:04:50.488 [5972] (ArchiveTask) <4524> EV:L :CArchivingAgent::IsEligibleForArchive(/o=MYEXCHORG/ou=First Administrative Group/cn=Recipients/cn=mymailbox) |The message titled: FW: Apelo urgente is eligible for archive  

    If you perform a run now archiving report against this user does it report that there is anything that will be archived?

    Have you run or used EVPM against this user?

     

     

  • I Ran a Dtrace. Please find some parts of output

     

    3200    16:39:07.163     [8808]    (ArchiveTask)    <9252>    EV:M    [CCompressor] Decompress|Type: class CZlibCompressor|Header: N|Thin: 1410|Fat: 12542|Fat guess bad: 8484)|CRC: 2796691610
    3201    16:39:07.163     [8808]    (ArchiveTask)    <9252>    EV:M    CArchivingAgent::UncompressItemRequestXML - decompressed moved item xml from 1414 to 12542
    3202    16:39:07.163     [8808]    (ArchiveTask)    <9252>    EV:M    CArchivingAgent::ProcessMovedItemsInFolder - entering function
    3203    16:39:07.163     [8808]    (ArchiveTask)    <9252>    EV:M    CArchivingAgent::ProcessMovedItemsInFolder - Another thread is currently processing mailbox /o=fragroup/ou=eu fr versailles/cn=Recipients/cn=PRivoal, this request will be put to the back of the queue
    3204    16:39:07.163     [8808]    (ArchiveTask)    <9252>    EV:H    :AgentMessageDispenser::ActivateObject() |Exiting routine at point A |
    3205    16:39:07.163     [8808]    (ArchiveTask)    <9252>    EV:M    :AgentMessageDispenser::ProcessNextMessage() |ActivateObject has returned failure |
    3206    16:39:07.163     [8808]    (ArchiveTask)    <9252>    EV:M    AgentMessageDispenser::ProcessNextMessage - AGENTS_E_DISPABORTITEM, agent will sleep and abort the the current MSMQ Transation
    3207    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:M    :AgentMessageDispenser::ProcessNextMessage() |Retrieved a message successfully from the queue |
    3208    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:M    :AgentMessageDispenser::ProcessNextMessage() |Read new message or a message that is within its retry limit (). |About to process the message body |
    3209    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:H    :AgentMessageDispenser::ActivateObject() |Entering routine |
    3210    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:M    :AgentMessageDispenser::ActivateObject() |Message type indicator = MsgID_ProcessMovedItemsInFolder2 |
    3211    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:L    :AgentMessageDispenser::ActivateObject() |Called server side object, with arguments: |m_pIBackgroundArchivingAgent->ProcessMovedItemsInFolder2(ExchangeMailboxDn = "/o=fragroup/ou=eu fr versailles/cn=Recipients/cn=PRivoal",|  ArchiveID = "1F64F65CDF7E72947A2D93603F3AB9A3C1110000EV01EU.eu.fciconnect.com",|  ArchiveFolderID = "196C0FE24B303394B895DED71248779F01110000EV01EU.eu.fciconnect.com", |  FolderRetCat = "1F99DE7FAF90A3442994AD9BFDD4B95971b10000EV01EU.eu.fciconnect.com", |  SourceFolderID = "ID", |  FolderPathName = "?Calendrier", |  CompressedItemRequestXML = "some XML") |
    3212    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:M    CArchivingAgent::ProcessMovedItemsInFolder2 - entering function
    3213    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:M    CArchivingAgent::UncompressItemRequestXML - beginning decompression of moved item xml
    3214    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:L    [class CIStreamSequentialStream] Position: 0 hr:0x0
    3215    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:L    [class CIStreamSequentialStream] Length:1414 hr:0x0
    3216    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:L    [class CIStreamSequentialStream] SetCapacity:8484 hr:0x0
    3217    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:L    [class CIStreamSequentialStream] Position: 4 hr:0x0
    3218    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:L    [class CIStreamSequentialStream] SetPosition: 1414 hr:0x0
    3219    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:L    [class CIStreamSequentialStream] Position: 12542 hr:0x0
    3220    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:L    [class CIStreamSequentialStream] SetLength:12542 hr:0x0
    3221    16:39:07.194     [8808]    (ArchiveTask)    <9472>    EV:L    [class CIStreamSequentialStream] Flush hr:0x0

  • I think that KeyPlayers suggestions are great.

    It looks like the excerpt you provided shows some shortcut processing taking place. This implies the mailbox is getting hit.

    Does the Usage report show content being added. The quota could play into it, but I think it is far more likely that you are hitting your number of items per pass. 

    THe hardest thing to catch that could very well be it is related to this HF:

     

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

     

    Ignore the fact that it says move archive. It affects anything that stores. You can see the hex code in a trace if it applies. If you do not have this HF in place and have items which would be affected, the net result is eventually you will have these items consuming all of your items per pass . . .and nothing. . .or very limited ammount of data. . .will be archived.

     

    If this is applicable, you may also see growth in the Failed To Store folder of your journal mailbox. I have seen this HF fix countless EV 8 SP4 customers. The best advice would be got to SP5. .

     

    Hope this helps.

    J

  • Not much there I am afraid. Can you ZIP and post the entire trace. Did you see anything from the other suggestions I mentioned as per below?

    Can you perform a run now archiving report against this user does it report that there is anything that will be archived?

    Have you run or used EVPM against this user?

  • Try to ZAP the mailbox

    Run the provisioning task do a RUN NOW
    Enable the Mailbox back for archiving it should select its old archive
    Then Synchronise the mailbox and do a Run now on the archive task and check the A3 queue if you see the archive request present in it.
    give it sometime and it should start processing.