Solved
Event 8390 - Archive Task error
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.
"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.
- 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.
