03-19-2008 11:25 AM
Event Type: Warning
Event Source: Enterprise Vault
Event Category: Web Application (WP)
Event ID: 6287
Date: 3/18/2008
Time: 11:01:16 PM
User: N/A
Computer: PDCNT27
Description:
Unable to fetch item from "evserver.abc.city".
Reason: Not enough storage is available to complete this operation. [0x8007000e]
Saveset Id: 427503230000000~200602082102230000~0~BCE9A25B27E140AC8FC22F247090D98
Archive Name: H_Drive
Archive Folder Path: \\nt19.abc.city\E$\H_Drive\Home\My Documents\Downloads\2006
Reference: [GOAFS]
This error seems to indicate an out-of-memory condition. Our EV server is running Windows server 2003 SP2. Has anyone seen this? If so, do you have a solution?
Thanks.
02-16-2009 05:24 AM
Hi,
I know its a time ago, but maybe you still remember.
I get the same error message now by FSA from a celerra.
After a server reboot it works again, but I don't know it this error will occurr again.
Could you solve the problem and how?
Thanks!
Viktor
02-16-2009 11:05 AM
Here is a document that is listed for this specific error 6287.
Document ID: 278332
http://support.veritas.com/docs/278332 E-Mail this document to a colleague
02-18-2009 01:23 AM
Hi,
thank you for your answer. But its a different problem. There are a couple possible error-messages with the event id 6287.
Our message is: Reason: Not enough storage is available to complete this operation. [0x8007000e].
But there is enough storage! (in the temp-location and on the target server)
We get this message with FSA on a Celerra as target.
Any other ideas?
thank you.
regards,
viktor
02-18-2009 05:17 AM
Alan
Check out the following document
http://support.veritas.com/docs/304985 It apparently says that your issue is addressed in EV2007 SP3.
02-18-2009 05:19 AM
The following document doesn't specifically talk about not enough disk space problems, but it does come up because of FSA and Celerra with error 6287 so you should take a look at this document in any case.
http://support.veritas.com/docs/304985
Judy
02-18-2009 07:38 AM
Hi Judy.
thank you for that. I will have a look at this article. But the subject of it tells about activated Age-based Pruning. This is not the case for us.
I will also take a dtrace and have a look at this.
regards,
viktor