Solved: Event 8390 - Archive Task error

gtsnyder · ‎02-18-2010

Have started seeing more of these errors on our EV servers.

"EnterpriseVault.Directory Connection object reported an error.
Ran out of memory."

They tend to occur on Sunday's when we are running our Archive Tasks all day long. We'll see about 6 entries of this error, and then a 2217 Event stating that the Message dispenser will resume processing.
The errors stop after our services are restarted per the backup scripts.

Have found some posts relating to 8390 errors, but not one that talks to this "Ran out of memory" message. Hopefully a setting adjustment somewhere, perhaps vm, but was looking to see if there was any docs out there that spoke to it before make changes.

Current environment is EV 8.0 SP2, running on Windows Server 2003 R2, Enterprise x64.

Any help is appreciated, thanks.

gtsnyder · ‎04-29-2010

I just wanted to tie this thread up. I worked with support and we scanned over various things, found a setting here or there that needed changing, but nothing really did the trick. I finally just backed the Archive Task schedule from a start of 9a, back to 2p (the task was previously scheduled from 9a to midnight), and right after doing this, the 8390 errors went away. I will probably back the start time down further as we have completed the migration of our user base to MB archiving, so I don't really expect to see the errors again, and thus can't offer an explanation as to their occurrence.

View solution in original post

TonySterling · ‎02-18-2010

How many Archive tasks do you have and how many threads are you using per task?

gtsnyder · ‎02-18-2010

We are generally running 1 Archive Task per server (2 of the 10 servers have two), and running 5 concurrent connections to the Exchange server...I'm assuming that is the thread count you're asking about.

JesusWept3 · ‎02-18-2010

dont suppose you stopped everyone from having their items expired at all?

https://www.linkedin.com/in/alex-allen-turl-07370146

gtsnyder · ‎02-18-2010

Correct, we do not currently have Expiration running...thinking about that question, we also have our default retention set to 1 day, to compensate for an issue with Governance mode when we moved to version 8 from 2007. Customer wants folks to have the ability to delete items, but we lost that after upgrade. As a work-around we were told to modify the retention date until a fix became available.

JesusWept3 · ‎02-18-2010

ok but can you check this for me

go to the vault admin console and go to Archives -> Exchange Mailboxes and pick some archives at random
go to the properties of the archive and then go to the Advanced Tab
under the heading "storage Expiry" is "Delete expired items from this archive automatically" unchecked?

I've seen issues in the past where people uncheck this for every archive in their environment and thats what causes the out of memory errors

https://www.linkedin.com/in/alex-allen-turl-07370146

TonySterling · ‎02-18-2010

I think this is what JW2 is referring to:

http://seer.entsupport.symantec.com/docs/328524.htm

gtsnyder · ‎02-18-2010

Spot check of 10 archives and all had the Checkbox checked.

JesusWept3 · ‎02-18-2010

are you *just* getting the 8390 errors or are you getting 13360 errors too?

https://www.linkedin.com/in/alex-allen-turl-07370146

gtsnyder · ‎02-18-2010

Looking back at the one server log, do not see any 13360 errors occurring during the run of 8390 Events.
I see a 2776 event, and then bunch of 3310's appearing...then the 8390 events start up:

Error 2/14/2010 7:34:22 PM Enterprise Vault Archive Task 8390

Info 2/14/2010 7:34:18 PM Enterprise Vault Archive Task 2217

Error 2/14/2010 7:24:18 PM Enterprise Vault Archive Task 3310

Error 2/14/2010 7:24:17 PM Enterprise Vault Archive Task 8390

Info 2/14/2010 7:24:14 PM Enterprise Vault Archive Task 2217

Error 2/14/2010 7:14:14 PM Enterprise Vault Archive Task 3310

Error 2/14/2010 7:14:13 PM Enterprise Vault Archive Task 8390

Info 2/14/2010 7:14:10 PM Enterprise Vault Archive Task 2217

Error 2/14/2010 7:04:10 PM Enterprise Vault Archive Task 3310

Error 2/14/2010 7:04:09 PM Enterprise Vault Archive Task 8390

Info 2/14/2010 7:04:06 PM Enterprise Vault Archive Task 2217

Error 2/14/2010 6:54:06 PM Enterprise Vault Archive Task 3310

Info 2/14/2010 6:54:02 PM Enterprise Vault Archive Task 2217

Error 2/14/2010 6:44:02 PM Enterprise Vault Archive Task 3310

Info 2/14/2010 6:43:58 PM Enterprise Vault Archive Task 2217

Error 2/14/2010 6:33:58 PM Enterprise Vault Archive Task 3310

Info 2/14/2010 6:33:53 PM Enterprise Vault Archive Task 2217

Error 2/14/2010 6:23:53 PM Enterprise Vault Archive Task 3310

Info 2/14/2010 6:23:49 PM Enterprise Vault Archive Task 2217

Error 2/14/2010 6:13:49 PM Enterprise Vault Archive Task 3310

Info 2/14/2010 6:13:45 PM Enterprise Vault Archive Task 2217

Error 2/14/2010 6:03:45 PM Enterprise Vault Archive Task 3310

Info 2/14/2010 6:03:41 PM Enterprise Vault Archive Task 2217

Error 2/14/2010 5:53:41 PM Enterprise Vault Archive Task 3310

Info 2/14/2010 5:53:36 PM Enterprise Vault Archive Task 2217

Error 2/14/2010 5:43:36 PM Enterprise Vault Archive Task 3310

gtsnyder · ‎04-29-2010

I just wanted to tie this thread up. I worked with support and we scanned over various things, found a setting here or there that needed changing, but nothing really did the trick. I finally just backed the Archive Task schedule from a start of 9a, back to 2p (the task was previously scheduled from 9a to midnight), and right after doing this, the 8390 errors went away. I will probably back the start time down further as we have completed the migration of our user base to MB archiving, so I don't really expect to see the errors again, and thus can't offer an explanation as to their occurrence.

GertjanA · ‎04-29-2010

Hello GT.

If closing, can you select a post as a solution, so it is actually closed.
Reading your last entry, seeing you changed the time, problem went away, is there something on the sql-server happening perhaps? Think backup, index rebuild, compacting?

Regards. Gertjan

VOX

Event 8390 - Archive Task error