cancel
Showing results for 
Search instead for 
Did you mean: 

Archive Task 8302

Siraj
Level 3
Running 8.0 SP4 and I'm seeing this error.  What storage is it referring to ? 

For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp
Event Type: Error
Event Source: Enterprise Vault
Event Category: Archive Task
Event ID: 8302
Date:  5/13/2010
Time:  12:12:48 PM
User:  N/A
Computer: 
Description:
Failed to create a Directory Vault object, reason: Not enough storage is available to complete this operation.  [0x8007000e]
1 ACCEPTED SOLUTION

Accepted Solutions

JesusWept3
Level 6
Partner Accredited Certified
tony is correct and the fact that its coming from SQL , most likely theres been a query thats returned a huge dataset so you may want to run some dtraces and some SQL profilers and cross reference exactly what query is returning the large dataset

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

View solution in original post

5 REPLIES 5

Liam_Finn1
Level 6
Employee Accredited Certified
I think it is referring to the disk space where you store your Vault store. Check the free space where your archived data is stored

Siraj
Level 3

I have plenty of free disk space for the vault store.  Perhaps time to call support.  Thank you.

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

First glance I would think it would be memory comsumption.  

Is this an upgrade or new install?  When does it occur, on start up?  You could grab a dtrace and see what is going on.

Siraj
Level 3
Hi Tony..been a long time. :)  We did an upgrade to newer hardware (same EV servername and IP) using the following article:

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


It doesn't happen on start up.  I noticed it first time today as I was trying to manually archive an email.  I will try to run a dtrace. 

JesusWept3
Level 6
Partner Accredited Certified
tony is correct and the fact that its coming from SQL , most likely theres been a query thats returned a huge dataset so you may want to run some dtraces and some SQL profilers and cross reference exactly what query is returning the large dataset

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