Forum Discussion

vaultlearner's avatar
vaultlearner
Level 4
4 years ago

Archive Task Failure

Hello We are experiencing task failure. We have 3 Exchanges and we have 3 tasks to archive those Exchanges. When we stop 3 task and start 2 of them succesfully 1 of them always failing. It doesn't m...
  • SheldonDsouza's avatar
    SheldonDsouza
    4 years ago

    Hello vaultlearner 

    I am assuming that this issue has erupted after a change. Either upgrading of EV or a change somewhere else. This isn't a day 01 issue, correct?

    Besides reinstalling Outlook or upgrading Outlook, have you cleared out all the MAPI Profiles? What's the Profile Expiry limitation set?

    Also, did you review this article? Archiving Task fails with Events 3460 & 2256 when starting a task that targets Exchange 2013 or 2016 due to RPC issues (I am guessing you would have, if not check it out and let us know).

    Also, why have you increased the number of connections to the Exchange on the task? if 2 out of 3 tasks work but the 3rd fails, then there is a resource overload on the EV Server. Instead of looking at the Concurrent Connections at the task level, I'd suggest reviewing the aforementioned article and see if it makes any difference and also, as GertjanA review the Proxy Server setting.

     

  • vaultlearner's avatar
    vaultlearner
    4 years ago

    Hello SheldonDsouza,

    I just check it. After upgrade of Outlook, tasks are not failing. We are going to observe it for a week. 

    Only thing  Deployment scanner gives warning about Outlook 2016.  Please check the attachment.

    Thanks

    Vaultlearner.

  • GertjanA's avatar
    GertjanA
    4 years ago

    Hello,

    The warning shows because the Compatibility Guide has some specific remarks on that version. See this 

    As it is a warning, it simply indicates you need to check those remarks, but it will not prevent EV functioning/installation.

GertjanA's avatar
GertjanA
Moderator
4 years ago

Hello,

You see CArchiveAgentTask::Initialise - Com Result [0x80004005]

This basically is an error indicating a resource problem. Diskspace, RAM/CPU, is all that ok?

As you state, starting 2 out of 3 tasks works fine, 3rd fails, irrespective which one is started 3rd. This indicates an issue on the EV server. See what happens if you set the number of concurrent connections (task properties, tab advanced) to 3 on each task, then start them. It might also be a limit on Exchange (how many connections can be made), but that should have been removed when ran the powershell script as indicated in the installation guide.

I also see: Proxy server: 'webmail.xxx.com.tr'. Why use your webmail server (which as far as I know) is external facing.IT might be you need to specifically set values on the site. See properties of ..\targets\exchange\your domain 

 

  • vaultlearner's avatar
    vaultlearner
    Level 4
    4 years ago

    Hello,

    Diskspace,Ram/CPU all ok.

    For the script, EV throttling policy still there. I did check again.

    "webmail.xxx.com.tr"  has both External and Internal faces. When client came from internally they are going DAG's IP directly. When client came externally they go Load Balancer. (This is what customer told me)

    "\targets\exchange\your domain"  section we added manually as "webmail.xxx.com.tr" but did not work also. I did test something from connection settings, for 2 task I increase concurrent connection to 10. Startted 2 tasks and they run with no issue.

    We connected with Veritas Support they suggested reinstall Outlook. Outlook version was 2013 sp1 32bit. Tomorrow we will install Outlook 2016 32bit. Do you have any suggestion?

    Thanks

    Vaultlearner

    • SheldonDsouza's avatar
      SheldonDsouza
      Level 4
      4 years ago

      Hello vaultlearner 

      I am assuming that this issue has erupted after a change. Either upgrading of EV or a change somewhere else. This isn't a day 01 issue, correct?

      Besides reinstalling Outlook or upgrading Outlook, have you cleared out all the MAPI Profiles? What's the Profile Expiry limitation set?

      Also, did you review this article? Archiving Task fails with Events 3460 & 2256 when starting a task that targets Exchange 2013 or 2016 due to RPC issues (I am guessing you would have, if not check it out and let us know).

      Also, why have you increased the number of connections to the Exchange on the task? if 2 out of 3 tasks work but the 3rd fails, then there is a resource overload on the EV Server. Instead of looking at the Concurrent Connections at the task level, I'd suggest reviewing the aforementioned article and see if it makes any difference and also, as GertjanA review the Proxy Server setting.

       

      • vaultlearner's avatar
        vaultlearner
        Level 4
        4 years ago

        Hello SheldonDsouza,

        Correct, but nothing chance since it was working fine.

        Profile Expiry limit already 1. Yes we tried remove all profiles.

        "Why I did increased connections to 10?" because I wanted to test is this about profile limitation. So 2x10 makes 20 profiles created with no issue. Normally we have 15 concurrent connections total with 3 task.

        And yes at the article we tried and check everything it points out. (port ok system mailbox ok etc)

        Veritas support suggested us to uninstall and reinstall Outlook we are going to try that  tomorrow.

        Thanks

        Vault Learner